8153cddad1
Removes the unnecessary QuotaDriver.destroy_all_by_project() and destroy_all_by_project_and_users() methods. nova.objects.Quotas already had these methods and this patch changes the one place that was calling the old QuotaDriver method (from the nova API /quota_sets endpoint) to just call the nova.objects.Quotas methods of the same name. Note that the NoopQuotaDriver's destroy_all_by_project() and destroy_all_by_project_and_user() methods were no-ops. Now the quota-sets API will be calling the objects.Quotas.destroy_xxx() methods which will raise ProjectUserQuotaNotFound instead of returning a 204. If the user is calling DELETE /os-quota-sets and there is the Noop quota driver configured, and the response is a 404 Not Found, do we really care? In the future, we should be getting rid of the os-quota-sets API entirely and using Keystone's /limits API. One more set of methods gone from QuotaDriver... Change-Id: Ifc0a409bd179807db18f2e7b59ea9d4d67e9a798 |
||
|---|---|---|
| api-guide/source | ||
| api-ref/source | ||
| contrib | ||
| devstack | ||
| doc | ||
| etc/nova | ||
| gate | ||
| nova | ||
| placement-api-ref | ||
| playbooks/legacy | ||
| releasenotes | ||
| tools | ||
| .coveragerc | ||
| .gitignore | ||
| .gitreview | ||
| .mailmap | ||
| .stestr.conf | ||
| .zuul.yaml | ||
| CONTRIBUTING.rst | ||
| HACKING.rst | ||
| LICENSE | ||
| MAINTAINERS | ||
| README.rst | ||
| babel.cfg | ||
| bindep.txt | ||
| lower-constraints.txt | ||
| requirements.txt | ||
| setup.cfg | ||
| setup.py | ||
| test-requirements.txt | ||
| tox.ini | ||
README.rst
Team and repository tags
OpenStack Nova
OpenStack Nova provides a cloud computing fabric controller, supporting a wide variety of compute technologies, including: libvirt (KVM, Xen, LXC and more), Hyper-V, VMware, XenServer, OpenStack Ironic and PowerVM.
Use the following resources to learn more.
API
To learn how to use Nova's API, consult the documentation available online at:
For more information on OpenStack APIs, SDKs and CLIs in general, refer to:
Operators
To learn how to deploy and configure OpenStack Nova, consult the documentation available online at:
In the unfortunate event that bugs are discovered, they should be reported to the appropriate bug tracker. If you obtained the software from a 3rd party operating system vendor, it is often wise to use their own bug tracker for reporting problems. In all other cases use the master OpenStack bug tracker, available at:
Developers
For information on how to contribute to Nova, please see the contents of the CONTRIBUTING.rst.
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:
Other Information
During each Summit and Project Team Gathering, we agree on what the whole community wants to focus on for the upcoming release. The plans for nova can be found at: