Object Version Registry
Nova needs to maintain a registry of all the object versions for all nodes so that we know what version of each must be sent to a given node.
Blueprint information
- Status:
- Started
- Approver:
- Russell Bryant
- Priority:
- Low
- Drafter:
- None
- Direction:
- Needs approval
- Assignee:
- Dan Smith
- Definition:
- Review
- Series goal:
- None
- Implementation:
-
Started
- Milestone target:
-
next
- Started by
- Russell Bryant
- Completed by
Related branches
Related bugs
Sprints
Whiteboard
Proposed design:
- A new API to conductor that lets a node register its object versions in a single go
- Compute will do this on startup
- Conductor will register its own versions on its own startup, always storing the latest version of all its objects
- On receipt from a compute node, conductor will store only the versions that are older than it knows to be current for each object type
- A new API will be needed to query the registry for things like the API nodes
This will be required before we can do any migrations that do online data upgrading, as we will need to know when all conductor nodes have been upgraded to allow the migration to proceed.
Gerrit topic: https:/
Addressed by: https:/
WIP Add Object Version Registry WIP
This blueprint has been deferred from the icehouse-3 milestone to Juno because it missed the "feature proposal freeze" deadline. https:/
Unapproved - please re-submit via nova-spec --johnthetubagy (20th March 2014)
Work Items
Dependency tree
* Blueprints in grey have been implemented.
