There is currently no simple way to clean up Cinder attachments if the Nova node (or the instance) has gone away. We’ve put this topic on the agenda for the Cinder mid-cycle this week: https://etherpad.openstack.org/p/mitaka-cinder-midcycle L#113<https://etherpad.openstack.org/p/mitaka-cinder-midcycle%20L#113>
From: Avishay Traeger [mailto:[email protected]] Sent: Monday, January 25, 2016 7:21 AM To: OpenStack Development Mailing List (not for usage questions) Subject: [openstack-dev] [Nova][Cinder] Cleanly detaching volumes from failed nodes 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: [email protected]<mailto:[email protected]> [http://www.stratoscale.com/wp-content/uploads/Logo-Signature-Stratoscale-230.jpg] 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: [email protected]?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
