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.
der-midcycle%20L#113>
From: Avishay Traeger [mailto:avis...@stratoscale.com]
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 the
t; *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.
On 1/26/2016 5:55 AM, Avishay Traeger wrote:
OK great, thanks! I added a suggestion to the etherpad as well, and
found this link helpful: https://review.openstack.org/#/c/266095/
On Tue, Jan 26, 2016 at 1:37 AM, D'Angelo, Scott mailto:scott.dang...@hpe.com>> wrote:
There is currently no
On Wed, Jan 27, 2016 at 1:01 PM, Matt Riedemann
wrote:
> I've replied on https://review.openstack.org/#/c/266095/ and the related
> cinder change https://review.openstack.org/#/c/272899/ which are adding a
> new key to the volume connector dict being passed around between nova and
> cinder, whic
On 1/27/2016 11:22 AM, Avishay Traeger wrote:
On Wed, Jan 27, 2016 at 1:01 PM, Matt Riedemann
mailto:mrie...@linux.vnet.ibm.com>> wrote:
I've replied on https://review.openstack.org/#/c/266095/ and the
related cinder change https://review.openstack.org/#/c/272899/ which
are adding
On 27 January 2016 at 06:40, Matt Riedemann
wrote:
> On 1/27/2016 11:22 AM, Avishay Traeger wrote:
>
>>
>> I agree with you. Actually, I think it would be more correct to have
>> Cinder store it, and not pass it at all to terminate_connection().
>>
>>
> That would be ideal but I don't know if ci
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 hav
On Thu, Feb 4, 2016 at 6:38 PM, Walter A. Boring IV
wrote:
> 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. Aft