daedfffd95
Avoid adding the current tenant to the flavor access list when a private flavor is created. In ordeir to add tenants to the flavor access list we should use the add_tenant api. Tempest has to be updated accordingly: https://review.openstack.org/81551 Documentation has to be updated as well: https://review.openstack.org/82175 Partially (just for the V2 API rather than V2 and V3) reverts commit 6ba248635b70860a44e486e7739efa4cc6612ce6 Fixes unittest which was added in the original commit so it checks for the behaviour we have now rather than the behaviour after the backwards incompatible change which is being reverted. Change-Id: I731081b6df0d96df1bc1763d214d28c62bbbb51c Closes-Bug: #1286297
OpenStack Nova README
OpenStack Nova provides a cloud computing fabric controller, supporting a wide variety of virtualization technologies, including KVM, Xen, LXC, VMware, and more. In addition to its native API, it includes compatibility with the commonly encountered Amazon EC2 and S3 APIs.
OpenStack Nova is distributed under the terms of the Apache License, Version 2.0. The full terms and conditions of this license are detailed in the LICENSE file.
Nova primarily consists of a set of Python daemons, though it requires and integrates with a number of native system components for databases, messaging and virtualization capabilities.
To keep updated with new developments in the OpenStack project follow @openstack on Twitter.
To learn how to deploy OpenStack Nova, consult the documentation available online at:
For information about the different compute (hypervisor) drivers supported by Nova, read this page on the wiki:
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 wishing to work on the OpenStack Nova project should always base their work on the latest Nova code, available from the master GIT repository at:
Developers should also join the discussion on the mailing list, at:
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
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:
For information on how to contribute to Nova, please see the contents of the CONTRIBUTING.rst file.
-- End of broadcast