Hi Brano,
I apologize for reviving an old thread.
On Wed, Mar 20, 2013 at 4:39 AM, Brano Zarnovican wrote:
> Hi devs,
>
> we are using backend iSCSI provider (Netapp) which is mapping
> Openstack volumes to iSCSI LUNs. This mapping is not static and
> changes over time. For example when the vol
On Mar 20, 2013, at 11:20 AM, Brano Zarnovican wrote:
> On Wed, Mar 20, 2013 at 5:06 PM, Vishvananda Ishaya
> wrote:
>>> 2) Wipeout connection_info after disconnect. At least for Netapp
>>> provider it makes no sense to retain the info which is no longer valid
>>> anyway.
>>
>> This seems reas
On Wed, Mar 20, 2013 at 5:06 PM, Vishvananda Ishaya
wrote:
>> 2) Wipeout connection_info after disconnect. At least for Netapp
>> provider it makes no sense to retain the info which is no longer valid
>> anyway.
>
> This seems reasonable. In fact, the whole block_device_mapping item
> can be delet
On Mar 20, 2013, at 3:39 AM, Brano Zarnovican wrote:
> Hi devs,
>
> we are using backend iSCSI provider (Netapp) which is mapping
> Openstack volumes to iSCSI LUNs. This mapping is not static and
> changes over time. For example when the volume is detached then his
> LUN id becomes unused. Afte
Hi devs,
we are using backend iSCSI provider (Netapp) which is mapping
Openstack volumes to iSCSI LUNs. This mapping is not static and
changes over time. For example when the volume is detached then his
LUN id becomes unused. After a while a _different_ volume may get the
same LUN id, as Netapp is
5 matches
Mail list logo
