Service Version Behavior Changes
There are a lot of situations where operators may have multiple versions of nova code running in a single deployment, either intentionally or accidentally. There are several things we can do make this safer and smoother in code to make the operator’s life easier.
Blueprint information
- Status:
- Complete
- Approver:
- John Garbutt
- Priority:
- High
- Drafter:
- Dan Smith
- Direction:
- Approved
- Assignee:
- Dan Smith
- Definition:
- Approved
- Series goal:
- Accepted for mitaka
- Implementation:
- Implemented
- Milestone target:
- mitaka-2
- Started by
- John Garbutt
- Completed by
- John Garbutt
Related branches
Related bugs
Sprints
Whiteboard
Gerrit topic: https:/
Addressed by: https:/
Add get_minimum_
Addressed by: https:/
Allow automatic determination of compute_rpc version by service
Addressed by: https:/
Make service create/update fail if version is too old
Addressed by: https:/
Extend the ServiceTooOld exception with more data
Addressed by: https:/
Add service records for nova-api services
Gerrit topic: https:/
Addressed by: https:/
Add SIGHUP handlers for compute rpcapi to console and conductor
Addressed by: https:/
Revise the compute_