[openstack-dev] [Cinder] Confusion about the respective use cases for volume's admin_metadata, metadata and glance_image_metadata

Trump.Zhang zhangleiqiang at gmail.com
Wed May 7 08:36:24 UTC 2014


@Tripp, Thanks for your reply and info.

I am also thinking if it is proper to add support for updating the volume's
glance_image_metadta to reflect the "newest status" of volume.

However, there may be alternative ways to achieve it:
1. Using the volume's metatadata
2. Using the volume's admin_metadata

So I am wondering which is the most proper method.


2014-05-07 12:32 GMT+08:00 Tripp, Travis S <travis.tripp at hp.com>:

> A few days ago I entered a client blueprint on the same topic [1], but
> maybe it has a server side dependency as well?
>
> When it comes to scheduling, as far as I have been able to tell from
> looking at Nova code, the scheduler is only getting volume_image_metadata
> and not the regular cinder_metadata.  So, if you want to add some
> volume_image_metadata for scheduler filtering or for passing compute driver
> options through after creating a volume, there doesn't seem to be a way to
> do this from the python-cinderclient.  If I'm wrong, please correct me.
>
> [1]
> https://blueprints.launchpad.net/python-cinderclient/+spec/support-volume-image-metadata
>
> > -----Original Message-----
> > From: Mike Perez [mailto:thingee at gmail.com]
> > Sent: Tuesday, May 06, 2014 9:10 PM
> > To: OpenStack Development Mailing List (not for usage questions)
> > Subject: Re: [openstack-dev] [Cinder] Confusion about the respective use
> cases
> > for volume's admin_metadata, metadata and glance_image_metadata
> >
> > On 06:31 Wed 07 May     , Trump.Zhang wrote:
> > > Thanks for your further instructions.
> > >
> > > I think the situations I mentioned are the reasonable use cases. They
> > > are similar to the "bootable" volume use cases, user can create an
> > > empty volume and install os in it from an image or create bootable
> > > volume from instance ([1]).
> > >
> > > If volume metadata is not intended to be interpreted by cinder or nova
> > > as meaning anything, maybe Cinder needs to add support for updating
> > > some of glance_image_metadata of volume or introduce new property for
> > > volume like "bootable" ? I don't think these two methods are good
> either.
> > >
> > > [1] https://blueprints.launchpad.net/cinder/+spec/add-bootable-option
> >
> > Volume already has a bootable field:
> >
> >
> https://github.com/openstack/cinder/blob/master/cinder/db/sqlalchemy/model
> > s.py#L122
> >
> > --
> > Mike Perez
> >
> > _______________________________________________
> > 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
>



-- 
-------------------
Best Regards

Trump.Zhang
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20140507/cef38034/attachment.html>


More information about the OpenStack-dev mailing list