On 05/22/2013 12:35 PM, Brian Rosmaita wrote: > Hello all, > > Anyone interested in the new upload/download workflow, please take a look at the full specs of the new blueprints so we can discuss at tomorrow's meeting: > > BPs: > https://blueprints.launchpad.net/glance/+spec/new-upload-workflow > https://blueprints.launchpad.net/glance/+spec/new-download-workflow > > Full specs: > https://wiki.openstack.org/wiki/Glance-new-upload-workflow > https://wiki.openstack.org/wiki/Glance-new-download-workflow I don't really see the need to add a whole new workflow and API resource for this. Why not just add the new status called "Verifying" and then place images that are done with the "Saving" state into this "Verifying" state until someone (or something) calls: PUT /images/<UUID> with a body of: { 'status': 'ACTIVE' } You can use the existing policy stuff to enforce that only users with certain privileges can change an image's status from Verifying to Active, and images never show up in a user's list of images (public or otherwise) until they are in ACTIVE state anyway. For images added to Glance with copy_from or location, simply change the current behaviour of setting the image status to Active after the image has been copy_from'd instead to Verifying. This way, there's no need to introduce a new /image-imports resource at all, and you don't change the image retrieval workflow at all. Best, -jay