Bug 1322129 - [RFE][cinder] Rolling Upgrades Support
Summary: [RFE][cinder] Rolling Upgrades Support
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-cinder
Version: unspecified
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 13.0 (Queens)
Assignee: Eric Harney
QA Contact: Tzach Shefi
Don Domingo
URL: http://git.openstack.org/cgit/opensta...
Whiteboard:
Depends On:
Blocks: 1419948 1422243
TreeView+ depends on / blocked
 
Reported: 2016-03-29 21:10 UTC by Sean Cohen
Modified: 2019-03-19 13:05 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Technology Preview
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-05-18 14:56:54 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
OpenStack gerrit 393395 0 None None None 2016-12-15 17:57:49 UTC
OpenStack gerrit 412393 0 None None None 2017-01-04 16:16:21 UTC

Description Sean Cohen 2016-03-29 21:10:12 UTC 
Scope:

To be able to perform Cinder upgrade without downtime of control plane services by
allowing Cinder services to be updated one at a time and yet still be operational.


Rolling upgrades capabilities have been introduced in Mitaka release
with Online DB schema upgrade [1] and  RPC and VersionedObject Compatibility [2], where RPC versions and objects are pinned to a backwards compatible version and later switched to the latest Version. 

[1] https://blueprints.launchpad.net/cinder/+spec/online-schema-upgrades
[2] https://blueprints.launchpad.net/cinder/+spec/rpc-object-compatibility
Comment 1 Sean Cohen 2016-05-16 01:36:17 UTC 
Pending test upgrades in upstream CI (http://lists.openstack.org/pipermail/openstack-dev/2016-January/084528.html)
Comment 3 Paul Grist 2017-05-18 14:56:54 UTC 
Closing this one out based on the rolling upgrade tag and support being in Cinder now and patches merged. 

We can open new RFEs as needed for no-downtime, there may be dependencies there on A-A and the container deployment/upgrade.
Note You need to log in before you can comment on or make changes to this bug.