Please keep in mind that Nova keeps some volume state in the BlockDeviceMapping table. Without changes to Nova, a force_detach function is not complete.
I am interested in this use case, as are other Cinder developers. Please feel free to contact me in IRC with questions as "scottda". Scott D'Angelo ________________________________ From: joehuang <joehu...@huawei.com> Sent: Sunday, September 18, 2016 3:29:29 AM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [tricircle] Should we discuss the use cases of force volume detach in the Tricircle This is a good question. I also sent a mail in cinder thread that wants to know why the tempest test cases missing for the "force volume detach". The spec for the "force volume detach" could be found here: https://github.com/openstack/cinder-specs/blob/master/specs/liberty/implement-force-detach-for-safe-cleanup.rst ________________________________ From: cr_...@126.com [cr_...@126.com] Sent: 18 September 2016 16:53 To: openstack-dev Subject: [openstack-dev] [tricircle] Should we discuss the use cases of force volume detach in the Tricircle Hello， When the patch "force volume detach" has submited , some proposals have came back. The important point is wheathe this function is needed or safe. Should we disscuss some uses cases of this function. Such as the define of this function, when this function been triggered. ________________________________ Best regards, Ronghui Cao, Ph.D. Candidate College of Information Science and Engineering Hunan University, Changsha 410082, Hunan, China
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
