My plan was to store the connector object at attach_volume time. I was going to add an additional column to the cinder volume attachment table that stores the connector that came from nova. The problem is live migration. After live migration the connector is out of date. Cinder doesn't have an existing API to update attachment. That will have to be added, so that the connector info can be updated.
We have needed this for force detach for some time now.

It's on my list, but most likely not until N, or at least not until the microversions land in Cinder.
Walt


Hi all,
I was wondering if there was any way to cleanly detach volumes from failed nodes. In the case where the node is up nova-compute will call Cinder's terminate_connection API with a "connector" that includes information about the node - e.g., hostname, IP, iSCSI initiator name, FC WWPNs, etc. If the node has died, this information is no longer available, and so the attachment cannot be cleaned up properly. Is there any way to handle this today? If not, does it make sense to save the connector elsewhere (e.g., DB) for cases like these?

Thanks,
Avishay

--
*Avishay Traeger, PhD*
/System Architect/

Mobile:+972 54 447 1475
E-mail: avis...@stratoscale.com <mailto:avis...@stratoscale.com>



Web <http://www.stratoscale.com/> | Blog <http://www.stratoscale.com/blog/> | Twitter <https://twitter.com/Stratoscale> | Google+ <https://plus.google.com/u/1/b/108421603458396133912/108421603458396133912/posts> | Linkedin <https://www.linkedin.com/company/stratoscale>



__________________________________________________________________________
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

__________________________________________________________________________
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

Reply via email to