[openstack-dev] Booting multiple instances with block device mapping

John Griffith john.griffith at solidfire.com
Wed Dec 12 23:07:14 UTC 2012


On Wed, Dec 12, 2012 at 3:49 PM, Phillip Pao <paophillip at gmail.com> wrote:

> +1
>
> "it would be nice for cinder to have a concept of a read-only volume that
> could be attached to multiple instances"
>
> On Tue, Dec 11, 2012 at 1:00 PM, Vishvananda Ishaya <vishvananda at gmail.com
> > wrote:
>
>> Ultimately it would be nice for cinder to have a concept of a read-only
>> volume that could be attached to multiple instances, but in this case I
>> think it is a bug. The whole point of reserving the volume in cinder is so
>> that this cannot happen. Reserving should be atomic and cinder should
>> reject the reserve if it is already reserved.
>>
>> Vish
>>
>> On Dec 11, 2012, at 11:19 AM, "Karajgi, Rohit" <Rohit.Karajgi at nttdata.com>
>> wrote:
>>
>> Hi,****
>> ** **
>> I would like to get opinions on whether we should allow multiple
>> instances to be booted from a single volume.****
>> ** **
>> This is incorrectly allowed currently, the same volume seems to get
>> attached to each instance and the instances boot to Active status.****
>> More details can be seen in description of the bug
>> https://bugs.launchpad.net/nova/+bug/1087253.****
>> ** **
>> Ideally, the best way to achieve this would be pass a list of block
>> device mappings equal to the number of instances requested,****
>> changes going in to the Nova API code.****
>> Is it more feasible to restrict more than one instance to be passed with
>> a single block device mapping, or accept a list of BDMs?****
>> ** **
>> Regards,****
>> Rohit****
>> ** **
>>
>> ______________________________________________________________________
>> Disclaimer:This email and any attachments are sent in strictest
>> confidence for the sole use of the addressee and may contain legally
>> privileged, confidential, and proprietary data. If you are not the intended
>> recipient, please advise the sender by replying promptly to this email and
>> then delete and destroy this email and any attachments without any further
>> use, copying or forwarding
>> _______________________________________________
>> OpenStack-dev mailing list
>> OpenStack-dev at lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>>
>>
>> _______________________________________________
>> OpenStack-dev mailing list
>> OpenStack-dev at lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>>
>
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
> Read only volumes is something we talked about at the last Summit, I'm
hoping to have it early in G3.  Still needs a BP etc.

John
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20121212/8bb85e65/attachment.html>


More information about the OpenStack-dev mailing list