[openstack-dev] [Cinder] Regarding manage_existing and unmanage
Duncan Thomas
duncan.thomas at gmail.com
Thu Apr 24 15:09:31 UTC 2014
On 17 April 2014 18:01, Deepak Shetty <dpkshetty at gmail.com> wrote:
> On Fri, Apr 11, 2014 at 7:29 PM, Duncan Thomas <duncan.thomas at gmail.com>
> wrote:
>> The scenario I *don't want to see is:
>> 1) Admin import a few hundred volumes into the cloud
>> 2) Some significant time goes by
>> 3) Cloud is being decommissioned / the storage transfer / etc. so the
>> admin runs unmanage on all cinder volumes on that storage
>> 4) The volumes get renamed or not, based on whether they happened to
>> come into cinder via manage or volume create
>>
>> *That* I would consider broken.
> What exactly is broken here.. Sorry but i didn't get it!
What is broken is that volumes that came into cinder via manage, and
volumes that came into cinder via volume create behave differently
when unmanaged.
Since manage and unmanage would generally be run with a very long
separation in time, there is no reason for the admin to expect some
volumes to be renames and some not when they do the unmanage.
More information about the OpenStack-dev
mailing list