On 22:55 Wed 02 Apr , Mike Perez wrote:
On 02:58 Thu 03 Apr , Bohai (ricky) wrote:
Hi,
When I use an image to create a cinder volume, I found image's metadata is
saved into DB table volume_glance_metadata.
But when I use os-volume_upload_image to create image from cinder
Mike
Glance metadata gets used for billing tags, among things, that we
would like to stay as attached to a volume as possible, as another
example. Windows images use this - which is why cinder copies all of
the glance metadata in the first place, rather than just a bootable
flag.
Apparently
My advice is two-fold:
- No need to wait for the blueprint to be approved before submitting
a review - put a review up and let people see the details, then
respond to the discussion as necessary
- Drop into the Wednesday (16:00 UTC) IRC meeting for Cinder - most
if not all of the core team are
Message-
From: Mike Perez [mailto:thin...@gmail.com]
Sent: Thursday, April 03, 2014 1:55 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [Cinder]a question about
os-volume_upload_image
On 02:58 Thu 03 Apr , Bohai (ricky) wrote:
Hi
: Thursday, April 03, 2014 1:55 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [Cinder]a question about
os-volume_upload_image
On 02:58 Thu 03 Apr , Bohai (ricky) wrote:
Hi,
When I use an image to create a cinder volume, I found
On 3 April 2014 08:28, 王宏 w.wangho...@gmail.com wrote:
I agree. Actually, I already have a BP on it:
https://blueprints.launchpad.net/cinder/+spec/restore-image.
I am happy for any suggestion.
Needs a little thought since container_format and some other fields
will need to be regenerated (e.g.
Thanks Duncan for your answer.
I am very interested in making a contribution towards this effort, but
what to do next? Waiting for approving for this blueprint? Or see
others' opinions on this before we putting more efforts in achieving
this? I just want to make sure that we could handle other
Hi Duncan Thomas.
I agree with you that some fields will need to be regenerated. I think we
can allow users supply the fields which need to be regenerated in the
request body. And the supplied fields will recover the fields in the
restore_properties parameter. I will modify the description in my
-Original Message-
From: Mike Perez [mailto:thin...@gmail.com]
Sent: Friday, April 04, 2014 1:20 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [Cinder]a question about
os-volume_upload_image
On 18:37 Thu 03 Apr , Lingxian Kong
2014-04-04 9:32 GMT+08:00 Bohai (ricky) bo...@huawei.com:
An image has the property for example: hw_scsi_model=virtio-scsi or other
user specify property.
In process (1), cinder has saved the image property in the cinder DB.
I hope in process(2), cinder could provide an option to save the
On 01:32 Fri 04 Apr , Bohai (ricky) wrote:
-Original Message-
From: Mike Perez [mailto:thin...@gmail.com]
Sent: Friday, April 04, 2014 1:20 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [Cinder]a question about
os
Hi,
When I use an image to create a cinder volume, I found image's metadata is
saved into DB table volume_glance_metadata.
But when I use os-volume_upload_image to create image from cinder volume,
the metadata in volume_glance_metadata
is not setted back to the newly created image. I can't
12 matches
Mail list logo
