Service Version Behavior Changes

Registered by John Garbutt on 2015-09-30

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:
milestone icon mitaka-2
Started by
John Garbutt on 2015-10-02
Completed by
John Garbutt on 2016-01-15

Related branches

Sprints

Whiteboard

Gerrit topic: https://review.openstack.org/#q,topic:bp/service-version-behavior,n,z

Addressed by: https://review.openstack.org/223320
    Add get_minimum_version() to Service object and DB API

Addressed by: https://review.openstack.org/223321
    Allow automatic determination of compute_rpc version by service

Addressed by: https://review.openstack.org/229049
    Make service create/update fail if version is too old

Addressed by: https://review.openstack.org/230227
    Extend the ServiceTooOld exception with more data

Addressed by: https://review.openstack.org/242206
    Add service records for nova-api services

Gerrit topic: https://review.openstack.org/#q,topic:okay-we-got-it,n,z

Addressed by: https://review.openstack.org/255972
    Add SIGHUP handlers for compute rpcapi to console and conductor

Addressed by: https://review.openstack.org/273441
    Revise the compute_upgrade_levels_auto release note

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.