pective use cases
for volume's admin_metadata, metadata and glance_image_metadata
> -Original Message-
> From: Tripp, Travis S
> Sent: 07 May 2014 18:06
> To: OpenStack Development Mailing List (not for usage questions)
> Subject: Re: [openstack-dev] [Cinder] Confu
> -Original Message-
> From: Tripp, Travis S
> Sent: 07 May 2014 18:06
> 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 an
On 03:08 Thu 08 May , Zhangleiqiang (Trump) wrote:
> Thanks for the summary and detailed explanation.
>
> > 1. Volume metadata - this is for the tenant's own use. Cinder and nova don't
> > assign meaning to it, other than treating it as stuff the tenant can set.
> > It is
> > entirely unrela
> -Original Message-
> From: Duncan Thomas [mailto:duncan.tho...@gmail.com]
> Sent: Wednesday, May 07, 2014 9:57 PM
> To: OpenStack Development Mailing List (not for usage questions)
> Subject: Re: [openstack-dev] [Cinder] Confusion about the respective use cases
> for volu
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 7 May 2014 09:36, Trump.Zhang wrote:
> > @Tripp, Thanks for your reply and info.
> >
On 7 May 2014 09:36, Trump.Zhang wrote:
> @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 th
t; From: Mike Perez [mailto:thin...@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,
@Mike
Thanks.
Sorry for misleading you. I mean that I know volume already has a bootable
field.
My question is that once a volume has been created, its
glance_image_metadata will be immutable. However, the volume is constantly
having blocks changed, so some property of its glance_image_metadata
nder] 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
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 v
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 i
On 6 May 2014 14:46, Trump.Zhang wrote:
> Did you mean using volume metadata was not the right way for the first
> situation I mentioned in ealier mail?
Correct. Volume metadata is entirely for the tenant to use, it is not
interpreted by cinder or nova as meaning anything.
@Duncan
Thanks for your reply and help, :)
About "I expect that other than adding filtering on metadata to the API (if
it isn't
already there - I can't remember) that it will stay this way." you
mentioned, I am
sorry that I am not quite understand what you men.
Did you mean using volume metadata
Glance has the concept of 'protected properties' which is really just
policies around metadata. property = metadata in glance.
https://wiki.openstack.org/wiki/Glance-property-protections
-Alex
On Tue, May 6, 2014 at 6:50 AM, Duncan Thomas wrote:
> 'metadata' is a free form key-value space for
'metadata' is a free form key-value space for the tenant to use for
their own purposes - it has no semantic meaning to cinder. I expect
that other than adding filtering on metadata to the API (if it isn't
already there - I can't remember) that it will stay this way.
I take your point on the glance
Hi, stackers:
I have some confusion about the respective use cases for volume's
admin_metadata, metadata and glance_image_metadata.
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
billin
16 matches
Mail list logo
