On 16:34 Mon 09 Feb , Nilesh P Bhosale wrote:
Adding an ability to Add/Remove existing volumes to/from CG looks fine.
But, it does not help the use-case where one would want to directly delete
a volume from CG.
Why do we force him to first remove a volume from CG and then delete?
Xing
: [openstack-dev] [cinder] Why not allow deleting volume
from a CG ?
As Mike said, allowing deletion of a single volume from a CG is error
prone. User could be deleting a single volume without knowing that it is
part of a CG. The new Modify CG feature for Kilo allows you to remove a
volume
On 9 February 2015 at 13:04, Nilesh P Bhosale nilesh.bhos...@in.ibm.com
wrote:
Adding an ability to Add/Remove existing volumes to/from CG looks fine.
But, it does not help the use-case where one would want to directly delete
a volume from CG.
Why do we force him to first remove a volume from
On 15:51 Fri 06 Feb , Nilesh P Bhosale wrote:
snip
I understand this is as per design, but curious to understand logic behind
this.
snip
Why not allow deletion of volumes form the CG? at least when there are no
dependent snapshots.
From the review [1], this is because allowing a volume
(not for usage questions)
Subject: Re: [openstack-dev] [cinder] Why not allow deleting volume from a CG ?
On 15:51 Fri 06 Feb , Nilesh P Bhosale wrote:
snip
I understand this is as per design, but curious to understand logic
behind this.
snip
Why not allow deletion of volumes form the CG? at least
Hi All,
I see the following error, while deleting a volume from a consistency
group:
$ [admin]cinder delete vol1
Delete for volume vol1 failed: Bad Request (HTTP 400) (Request-ID:
req-7c958443-edb2-434f-82a2-4254ab357e99)
ERROR: Unable to delete any of specified volumes.
And when I tried to
