c930638fcf
Right now we only check to see if the user can see the image before we kick off an import operation. However, that will never work unless the user is the *owner* of the image (or an admin) which means we return a 202 to the API caller and then the task fails immediately. This change makes us check that authorization up front and return an appropriate error to the user so they know it failed, and avoid starting a task destined for failure. Note that there was already a check for a Forbidden result when calling the import API. However, that used a context.owner=None which could never happen in reality. A more suitable check would have been to use a context with a different real owner, but it turns out that the task creation would have succeeded in that case as well. This test is changed to use an alternate owner and ensure that we get the forbidden result from the new check immediately. Change-Id: I385f222c5e3b46978b40bdefdc28fcb20d9c67d3 Closes-Bug: #1884587 |
||
|---|---|---|
| api-ref/source | ||
| doc | ||
| etc | ||
| glance | ||
| httpd | ||
| playbooks/legacy/glance-dsvm-grenade-multinode | ||
| rally-jobs | ||
| releasenotes | ||
| tools | ||
| .coveragerc | ||
| .gitignore | ||
| .gitreview | ||
| .mailmap | ||
| .stestr.conf | ||
| .zuul.yaml | ||
| CONTRIBUTING.rst | ||
| HACKING.rst | ||
| LICENSE | ||
| README.rst | ||
| babel.cfg | ||
| bindep.txt | ||
| lower-constraints.txt | ||
| pylintrc | ||
| requirements.txt | ||
| setup.cfg | ||
| setup.py | ||
| test-requirements.txt | ||
| tox.ini | ||
README.rst
OpenStack Glance
Glance is an OpenStack project that provides services and associated libraries to store, browse, share, distribute and manage bootable disk images, other data closely associated with initializing compute resources, and metadata definitions.
Use the following resources to learn more:
API
To learn how to use Glance's API, consult the documentation available online at:
Developers
For information on how to contribute to Glance, please see the contents of the CONTRIBUTING.rst in this repository.
Any new code must follow the development guidelines detailed in the HACKING.rst file, and pass all unit tests.
Further developer focused documentation is available at:
Operators
To learn how to deploy and configure OpenStack Glance, consult the documentation available online at:
In the unfortunate event that bugs are discovered, they should be reported to the appropriate bug tracker. You can raise bugs here:
Release notes
To learn more about Glance's new features, optimizations, and changes between versions, consult the release notes online at:
Other Information
During each design summit, we agree on what the whole community wants to focus on for the upcoming release. You can see image service plans:
For more information about the Glance project please see: