On 12/17/2015 9:24 AM, Matt Riedemann wrote:
On 12/17/2015 8:51 AM, Andrea Rosa wrote:
The communication with cinder is async, Nova doesn't wait or check if
the detach on cinder side has been executed correctly.
Yeah, I guess nova gets the 202 back:
>> The communication with cinder is async, Nova doesn't wait or check if
>> the detach on cinder side has been executed correctly.
>
> Yeah, I guess nova gets the 202 back:
>
>
On 12/17/2015 8:51 AM, Andrea Rosa wrote:
The communication with cinder is async, Nova doesn't wait or check if
the detach on cinder side has been executed correctly.
Yeah, I guess nova gets the 202 back:
On 12/14/2015 11:24 AM, Andrea Rosa wrote:
On 10/12/15 15:29, Matt Riedemann wrote:
In a simplified view of a detach volume we can say that the nova code
does:
1 detach the volume from the instance
2 Inform cinder about the detach and call the terminate_connection on
the cinder API.
3
On 10/12/15 14:42, Sean Dague wrote:
> On 12/02/2015 12:37 PM, Rosa, Andrea (HP Cloud Services) wrote:
>> Hi
>>
>> thanks Sean for bringing this point, I have been working on the change and
>> on the (abandoned) spec.
>> I'll try here to summarize all the discussions we had and what we decided.
On 10/12/15 15:29, Matt Riedemann wrote:
>> In a simplified view of a detach volume we can say that the nova code
>> does:
>> 1 detach the volume from the instance
>> 2 Inform cinder about the detach and call the terminate_connection on
>> the cinder API.
>> 3 delete the dbm recod in the nova
On 12/02/2015 12:37 PM, Rosa, Andrea (HP Cloud Services) wrote:
> Hi
>
> thanks Sean for bringing this point, I have been working on the change and on
> the (abandoned) spec.
> I'll try here to summarize all the discussions we had and what we decided.
>
>> From: Sean Dague
On 12/2/2015 11:37 AM, Rosa, Andrea (HP Cloud Services) wrote:
Hi
thanks Sean for bringing this point, I have been working on the change and on
the (abandoned) spec.
I'll try here to summarize all the discussions we had and what we decided.
From: Sean Dague [mailto:s...@dague.net]
Sent: 02
Thanks to Andrea for clarifying this complex and long history problem.
As he says, we have talked about many solutions, and finally we found
this using nova-mange to call the terminate_connection and clean the
bdm entry.
It's simple and clear IMO and no bad impact to Nova API.
2015-12-03 1:37
Hi
thanks Sean for bringing this point, I have been working on the change and on
the (abandoned) spec.
I'll try here to summarize all the discussions we had and what we decided.
> From: Sean Dague [mailto:s...@dague.net]
> Sent: 02 December 2015 13:31
> To: OpenStack Development Mailing List
10 matches
Mail list logo
