<div dir="ltr">Glance has the concept of 'protected properties' which is really just policies around metadata. property = metadata in glance.<div><br></div><div><a href="https://wiki.openstack.org/wiki/Glance-property-protections">https://wiki.openstack.org/wiki/Glance-property-protections</a><br>
</div><div><br></div><div>-Alex</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Tue, May 6, 2014 at 6:50 AM, Duncan Thomas <span dir="ltr"><<a href="mailto:duncan.thomas@gmail.com" target="_blank">duncan.thomas@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">'metadata' is a free form key-value space for the tenant to use for<br>
their own purposes - it has no semantic meaning to cinder. I expect<br>
that other than adding filtering on metadata to the API (if it isn't<br>
already there - I can't remember) that it will stay this way.<br>
<br>
I take your point on the glance metadata. Glance has the concept to<br>
mutable and immutable metadata, maybe we can do something with that?<br>
I'll ask somebody who knows more about glance than me and get back to<br>
you...<br>
<div class="HOEnZb"><div class="h5"><br>
On 4 May 2014 10:33, Zhangleiqiang (Trump) <<a href="mailto:zhangleiqiang@huawei.com">zhangleiqiang@huawei.com</a>> wrote:<br>
> Hi, stackers:<br>
><br>
> I have some confusion about the respective use cases for volume's admin_metadata, metadata and glance_image_metadata.<br>
><br>
> I know glance_image_metadata comes from image which is the volume created from, and it is immutable. Glance_image_metadata is used for many cases, such as billing, ram requirement, etc. And it also includes property which can effects the "use-pattern" of volume, such as volumes with "hw_scsi_mode=virtio-scsi" will be supposed that there is corresponding virtio-scsi driver installed and will be used as a device of "virtio-scsi" controller which has higher performance when booting from it with scsi bus type.<br>
><br>
> However, volume is constantly having blocks changed, which may result in situations as follows:<br>
><br>
> 1. A volume not created from image or created from image without "hw_scsi_mode" property at first but then has the virtio-scsi driver manually installed, there will be no method to make the volume used with virito-scsi controller when booting from it.<br>
><br>
> 2. If a volume was created from an image with "hw_scsi_mode" property at first, and then the "virtio-scsi" driver in the instance is uninstalled, there will be no method to make the volume not used with "virtio-scsi" controller when booting from it.<br>
><br>
> For the first situation, is it suitable to set corresponding metadata to volume? Should we use metadata or admin_metadata? I notice that volumes will have "attach_mode" and "readonly" admin_metadata and empty metadata after created, and I can't find the respective use cases for admin_metada and metadata.<br>
><br>
> For the second situation, what is the better way to handle it?<br>
><br>
> Any advice?<br>
><br>
><br>
> ----------<br>
> zhangleiqiang (Trump)<br>
><br>
> Best Regards<br>
><br>
><br>
><br>
> _______________________________________________<br>
> OpenStack-dev mailing list<br>
> <a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>
> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br>
<br>
<br>
</div></div><span class="HOEnZb"><font color="#888888">--<br>
Duncan Thomas<br>
</font></span><div class="HOEnZb"><div class="h5"><br>
_______________________________________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
</div></div></blockquote></div><br></div>