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 BP soon. Best regards. wanghong 2014-04-03 18:12 GMT+08:00 Duncan Thomas <duncan.thomas at gmail.com>: > On 3 April 2014 08:28, 王宏 <w.wanghong1 at 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. we can source for a QCOW image, but > we always upload raw), but as long as these are dealt with it seems > like a useful feature > > _______________________________________________ > OpenStack-dev mailing list > OpenStack-dev at lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20140403/1320a83b/attachment.html>