Open Stack

On 01:32 Fri 04 Apr     , Bohai (ricky) wrote:
> > -----Original Message-----
> > From: Mike Perez [mailto:thingee at 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
> > 
> > What use case is that exactly? I mentioned earlier the original purpose was for
> > knowing if something was bootable. I'm curious on how else this is being used.
> > 
> 
> 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 properties back to the new glance image.
> Without this ability, user has to find all the properties in origin image and set them back by hand.
> This is useful when user just want to make a little modify to an origin image.
> 
> An image --(1)--> cinder volume --(2)--> An new Image

Hi Ricky,

Thanks for further explaining that to me. It does make sense, but I'm wondering
if there would be cases that people can think of where the properties specified
could become outdated because of changes that happen to the volume.  In glance
the properties make sense because an image is uploaded and has properties set.
The image is not going to be changed. If you want to change something about
that image, you upload a new one with the specified properties.  Rather with
a volume, it's constantly having blocks changed. Is there potential for that?
Could this problem be potential if a volume is migrated to a different backend?

-- 
Mike Perez