Bug 1322129

Summary: [RFE][cinder] Rolling Upgrades Support
Product: Red Hat OpenStack Reporter: Sean Cohen <scohen>
Component: openstack-cinderAssignee: Eric Harney <eharney>
Status: CLOSED CURRENTRELEASE QA Contact: Tzach Shefi <tshefi>
Severity: high Docs Contact: Don Domingo <ddomingo>
Priority: high    
Version: unspecifiedCC: egafford, eharney, geguileo, jdonohue, pgrist, srevivo
Target Milestone: ---Keywords: FutureFeature
Target Release: 13.0 (Queens)   
Hardware: Unspecified   
OS: Unspecified   
URL: http://git.openstack.org/cgit/openstack/cinder/plain/doc/source/upgrade.rst?id=6c698bc8e36
Whiteboard:
Fixed In Version: Doc Type: Technology Preview
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-05-18 14:56:54 UTC Type: Feature Request
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On:    
Bug Blocks: 1419948, 1422243    

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.