[openstack-dev] Booting multiple instances with block device mapping
Isaku Yamahata
yamahata at valinux.co.jp
Tue Dec 25 08:08:28 UTC 2012
On Fri, Dec 21, 2012 at 08:26:39AM -0800, Vishvananda Ishaya wrote:
> 2. In AWS EC2 API, volume ID?s are ignored/rejected in block device
> mapping. Instances can only be booted from snapshot (in which case a volume
> is created). Is the Openstack EC2 API a deviation from the AWS EC2
> implementation? Our cloud.py seems to not ignore volume id?s and use them
> to boot instances. What is the correct behavior here?
>
>
> Are you sure about this? How do you boot from a pre-existing volume that you
> created earler?
Pass vol-xxx instead of snap-xxx. That's the intended deviation from
the original EC2. When I implemented boot-from-volume, I found it quite
handy. For example, ISO boot.
So I left the implementation deviated thinking that the check can
be done by client like euca2ools if necessary.
--
yamahata
More information about the OpenStack-dev
mailing list