I would agree. I don't think that Cinder should/could be able to act upon
Nova's state for the VM. Force-delete is really in place as a backup to
clean-up after certain failures in Cinder. Other mechanisms are in place
to handle issues in Nova.
Jay S. Bryant
IBM Cinder Subject Matter Expert & Cinder Core Member
Department 7YLA, Building 015-2, Office E125, Rochester, MN
Telephone: (507) 253-4270, FAX (507) 253-6410
TIE Line: 553-4270
E-Mail: [email protected]
--------------------------------------------------------------------
All the world's a stage and most of us are desperately unrehearsed.
-- Sean O'Casey
--------------------------------------------------------------------
From: "zhangyu (AI)" <[email protected]>
To: "OpenStack Development Mailing List (not for usage questions)"
<[email protected]>,
Cc: "Luohao \(brian\)" <[email protected]>
Date: 02/25/2014 08:20 PM
Subject: Re: [openstack-dev] [Cinder] [Nova]Do you think volume
force delete operation should not apply to the volume being used?
IMHO, Attach/detach operations can only be issued from the Nova side
because they are in fact VM/instance management operations.
Meanwhile, volume create/delete are volume management stuffs, therefore
Cinder exposes API for them.
Also, according to current Cinder code base, no nova detach-volume action
is issued from the execution flow of a volume deletion.
Thank you for suggestions~
From: Yuzhou (C) [mailto:[email protected]]
Sent: Wednesday, February 26, 2014 9:46 AM
To: OpenStack Development Mailing List (not for usage questions)
Cc: Luohao (brian)
Subject: Re: [openstack-dev] [Cinder] [Nova]Do you think volume force
delete operation should not apply to the volume being used?
I think force delete = nova detach volume,then cinder delete volume
Volume status in db shoud be modified after nova detach volume.
Thanks!
From: zhangyu (AI) [mailto:[email protected]]
Sent: Wednesday, February 26, 2014 8:56 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [Cinder] [Nova]Do you think volume force
delete operation should not apply to the volume being used?
If I understand your question correctly, the case you describe should be
like the following:
Assume we have created both an instance and a volume, then we try to
attach that volume to the instance.
Before that operation is completed (the status of the volume is
“attaching” now), for whatever reasons we decide to apply a “force delete”
operation on that volume.
Then, after we applied that force delete, we come to see that, from the
Cinder side, the volume has been successfully deleted and the status is
surely “deleted”.
However, from the Nova side, we see that the status of the deleted volume
remains to be “attaching”.
If this is truly your case, I think it is a bug. The reason might lie in
that, Cinder forgets to refresh the attach_status attribute of a volume in
DB when applying a “force delete” operation.
Is there any other suggestions?
Thanks!
From: yunling [mailto:[email protected]]
Sent: Monday, February 17, 2014 9:14 PM
To: [email protected]
Subject: [openstack-dev] [Cinder]Do you think volume force delete
operation should not apply to the volume being used?
Hi stackers:
I found that volume status become inconsistent (nova volume status is
attaching, verus cinder volume status is deleted) between nova and cinder
when doing volume force delete operation on an attaching volume.
I think volume force delete operation should not apply to the volume being
used, which included the attached status of attaching, attached and
detached.
How do you think?
thanks_______________________________________________
OpenStack-dev mailing list
[email protected]
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
_______________________________________________
OpenStack-dev mailing list
[email protected]
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
