> -----Original Message----- > From: Mike Perez [mailto:[email protected]] > 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 wrote: > > 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 people's use > > cases and not just our own. > > 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 Best regards to you. Ricky > -- > Mike Perez > > _______________________________________________ > OpenStack-dev mailing list > [email protected] > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev _______________________________________________ OpenStack-dev mailing list [email protected] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
