Help says location file:/// is a valid IMAGE_URL on the remote server

[Attila Fazekas]

$ glnace help image-create
..
  --location <IMAGE_URL>
                        URL where the data for this image already resides. For
                        example, if the image data is stored in the filesystem
                        local to the glance server at
                        '/usr/share/image.tar.gz', you would specify
                        'file:///usr/share/image.tar.gz'.
...

It is very scary without restrictions, but on the glance side per the https://bugs.launchpad.net/glance/+bug/942118 it is fixed.
(Some unittest still contains file:// )

Please update the help to reflect the actual behavior.

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/17425
Committed: http://github.com/openstack/python-glanceclient/commit/2500e69b22c7291d1a01e86145ddfca87277ecd0
Submitter: Jenkins
Branch: master

commit 2500e69b22c7291d1a01e86145ddfca87277ecd0
Author: Brian Waldon <email address hidden>
Date: Mon Dec 3 15:00:46 2012 -0800

    Update --location help to reference swift store.

    Fixes bug 1085575.

    Change-Id: I6b325874a21e63fa02fe261f19e3d071f2b220d9