metadata for instances that boot from volumes

asked 2017-04-19 16:14:32 -0600

xdaxdb gravatar image

In my environment all instances boot from cinder volumes. So when I launch an instance I do so by creating a volume using an image as the source. Then I launch the instance using the volume as the boot source.

I am trying to modify he instances metadata to add a RNG device using

glance image-update --property hw_rng=true <UUID>

But my concern is that the metadata does not survive through my instance launching process because the instance is launched with a volume as the source rather than a glance image.

I would like to know if my assumptions about why this is not working are correct, and if there is a way I can overcome this.

edit retag flag offensive close merge delete

1 answer

Sort by ยป oldest newest most voted

answered 2017-04-19 20:26:57 -0600

xdaxdb gravatar image

updated 2017-04-20 18:41:50 -0600

Image metadata still works when using volumes as a boot source because when the volume is created it has a source property. This provides a relationship (somehow) between the volume and the metadata of the image from which it was created.

In order to customize the instance properties, metadata needs to be configured in both the image and the flavor. The image metadata allows the tenant to customize the instance to their preference. The flavor metadata allows the administrator to allow/configure which properties the image can actually set.

Both image and flavor metadata can be configured via Horizon by selecting update metadata from their respective drop-down lists.


edit flag offensive delete link more

Get to know Ask OpenStack

Resources for moderators

Question Tools

1 follower


Asked: 2017-04-19 16:14:32 -0600

Seen: 395 times

Last updated: Apr 20 '17