Bug 1131335

Summary: [RFE][cinder]: Ceph rbd support retype volume
Product: Red Hat OpenStack Reporter: RHOS Integration <rhos-integ>
Component: openstack-cinderAssignee: Jon Bernard <jobernar>
Status: CLOSED CURRENTRELEASE QA Contact: Yogev Rabl <yrabl>
Severity: unspecified Docs Contact:
Priority: high    
Version: 6.0 (Juno)CC: egafford, eharney, jobernar, markmc, mburns, nlevinki, pneedle, scohen, sgotliv, srevivo
Target Milestone: ---Keywords: FutureFeature, ZStream
Target Release: 7.0 (Kilo)   
Hardware: All   
OS: Linux   
URL: https://blueprints.launchpad.net/cinder/+spec/ceph-rbd-support-retype
Whiteboard: upstream_milestone_none upstream_definition_obsolete upstream_status_unknown
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-12-07 03:02:03 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1121610, 1122356    
Bug Blocks:    

Description RHOS Integration 2014-08-19 04:05:40 UTC 
Cloned from launchpad blueprint https://blueprints.launchpad.net/cinder/+spec/ceph-rbd-support-retype.

Description:

Currently ceph rbd doesn't support migrate volume function. This BP add support retype volume function for rbd driver.

Specification URL (additional information):

None
Comment 8 Mike McCune 2016-03-28 22:47:43 UTC 
This bug was accidentally moved from POST to MODIFIED via an error in automation, please see mmccune with any questions
Comment 9 Mike Burns 2017-06-28 16:48:58 UTC 
This bug appears to have been fixed since 7.0 GA (fixed upstream in 2015.1.0b1 tag).  Is there any reason to not close this currentrelease?
Comment 10 Jon Bernard 2017-06-28 19:53:00 UTC 
Not that I'm aware of.  There are improvements that can be made to the existing implementation but the core feature as described in this bug is complete and functional.
Comment 12 Sean Cohen 2017-12-07 03:02:03 UTC 
(In reply to Jon Bernard from comment #10)
> Not that I'm aware of.  There are improvements that can be made to the
> existing implementation but the core feature as described in this bug is
> complete and functional.

Closing accourdongly
Sean