Add upload_image policy for glance v1 api

There are 3 ways an upload image can be specified :

  * location
  * file
  * copy-from

For file and location I agree that the upload_image policy should be applied. For the copy-from, not entirely.

--copy-from takes an <IMAGE_URL>, this will work only if the user has access to this URI, else the user will be presented with a 403 Forbidden.

Should we apply an upload_image policy also for copy-from, or strictly for location and file ?

On top of what I've said above, location policy is already handled by set_image_location. So the policy to define would only concern uploading data via --file option

Fix proposed to branch: master
Review: https://review.openstack.org/58559

Reviewed: https://review.openstack.org/58559
Committed: http://github.com/openstack/glance/commit/ab7ea6baf7e67ee6353257f112e315369dd8d36e
Submitter: Jenkins
Branch: master

commit ab7ea6baf7e67ee6353257f112e315369dd8d36e
Author: Yanis Guenane <email address hidden>
Date: Tue Nov 26 15:55:09 2013 +0000

    Set upload_image policy to control data upload

    There was no policy to control data upload.
    Up until today, the add_image policy was a all or nothing, from metadata
    to the actual data. Now, with the combination of add_image and upload_image
    an administrator will have finer control over the whole chain.

    Change-Id: I1a7966ffb5c63dd8239a54fe2963b031d9fe1f9a
    Closes-bug: #1254521