fac6dca139
Implemented Client, Action, Job, Session, ActionAttachment, ActionReport, JobAttachment classes which are associated with database tables and allows working with them using orm. Implements: blueprint oslo-db Change-Id: I768bb580882b1dd86c5d8553e5fec8e4a44eae33
23 lines
1005 B
YAML
23 lines
1005 B
YAML
---
|
|
prelude: >
|
|
Currently Freezer uses Elastic Search (ES) as a database backend, which
|
|
is a NoSQL database specialized for ranked query results. Elastic Search
|
|
adds additional complexity to an OpenStack system. Most of the OpenStack
|
|
components use a relational database management system (DBMS like MySQL or
|
|
PostgreSQL) which is more common. It is more familiar how to
|
|
maintain, troubleshoot and develop on top of relational databases.
|
|
Also relational databases unlike ES database allow to perform rolling
|
|
upgrades.
|
|
|
|
Since Freezer related data turned out to be relational, it would be more
|
|
convenient to use it trough the oslo.db pattern library. Using it, the
|
|
database mapping would be more uniform to other OpenStack projects.
|
|
It would be less challenging for new developers to contribute.
|
|
features:
|
|
- |
|
|
Added support of oslo.db storage backend
|
|
upgrade:
|
|
- |
|
|
oslo.db storage can be upgraded/downgraded using freezer-manage db sync
|
|
command.
|