On 09/12/2013 13:34, Juha Tynninen wrote:
Thanks.Isn't the "EC2 MountPoint Property Type" used in Volumes property for mounting storage volumes when the VM instance is already running? So the effect would be similar to this working example: "DemoInstance" : { "Type" : "AWS::EC2::Instance", "Properties" : { "KeyName" : { "Ref" : "KeyName" }, "ImageId" : "cirros-0.3.1-x86_64-disk", "InstanceType": "m1.small" } }, "StorageVolume" : { "Type" : "OS::Cinder::VolumeAttachment", "Properties" : { "instance_uuid" : { "Ref" : "DemoInstance" }, "mountpoint" : "/dev/vdb", "volume_id" : "04fbad7a-41bf-41d9-9b53-2c2bb715f25c" } } ...but the question remains is it possible somehow to define that the instance is started (booted) from the volume. E.g. instead of ImageId defined for AWS::EC2::Instance, define the reference to the volume somehow.
You're right, I read the AWS docs too quickly. I guess you'll have to use the OS::Nova::Server resource [1] (see the block_device_mapping property) if this is possible for you.
[1] http://docs.openstack.org/developer/heat/template_guide/openstack.html#OS::Nova::Server
On 9 December 2013 12:56, Juha Tynninen <[email protected] <mailto:[email protected]>> wrote: Hi, I'm using stable/havana version of Openstack. I can boot instance from the pre-existing bootable Cinder volume with nova command: nova boot --flavor 2 --block_device_mapping vda=<volume id>:::0 <name for instance> ...but how can this be done with a Heat template? Or can it be done? AWS::EC2::Instance resource doesn't seem to have a property for this. Thanks, -Juha _______________________________________________ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : [email protected] Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
_______________________________________________ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : [email protected] Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
