Versioned objects support for Nailgun DB
In order to ensure *automated* upgrades/updates & downgrades/
The idea is to use a finite machine style approach while designing a complex upgrade (updates & downgrades/
Nailgun side should provide enough versioning info for all affected objects and any other DB entities involved.
As a ref, please see the Nova unified object model as well https:/
Blueprint information
- Status:
- Not started
- Approver:
- Evgeniy L
- Priority:
- Undefined
- Drafter:
- Bogdan Dobrelya
- Direction:
- Needs approval
- Assignee:
- Fuel Python (Deprecated)
- Definition:
- Discussion
- Series goal:
- Accepted for future
- Implementation:
- Not started
- Milestone target:
- next
- Started by
- Completed by
Related branches
Related bugs
Sprints
Whiteboard
Work Items
Dependency tree
* Blueprints in grey have been implemented.