OpenStack Compute (Nova)
Go to file
jichenjc 6abb88befe Check flavor type before add tenant access
Currently we allow tenant access for public flavor, however,
we can't query it after that because flavor is public.
This patch adds check for add access function to raise exception
if the flavor is public.

Also, a nit change is use methods introduced in
793bcc07b9 to get flavor.

APIImpact: Adds new 2.7 API microversion due to new error condition
           in flavor access API
Implements blueprint check-flavor-type-before-add-tenant
Closes-Bug: #1361476

Change-Id: I461175e9969a0dd5b2b7ef75ea7d9f36f3a306d0
2015-07-24 15:36:29 +03:00
contrib Merge "changed quantum to neutron in vif-openstack" 2014-03-05 10:45:05 +00:00
devstack cells: add devstack/tempest-dsvm-cells-rc for gating 2015-06-23 00:47:59 +00:00
doc Check flavor type before add tenant access 2015-07-24 15:36:29 +03:00
etc/nova Merge "Switch to oslo.service library" 2015-07-22 04:50:24 +00:00
nova Check flavor type before add tenant access 2015-07-24 15:36:29 +03:00
plugins/xenserver xenapi: don't send terminating chunk on errors 2015-01-14 13:58:18 +00:00
tools Merge "XenAPI: Refactor rotate_xen_guest_logs to avoid races" 2015-07-20 13:00:18 +00:00
.coveragerc Port Cheetah templates to Jinja2 2013-09-02 16:03:34 +02:00
.gitignore remove all traces of pylint testing infrastructure 2015-01-08 11:56:45 +00:00
.gitreview Add .gitreview config file for gerrit. 2011-10-24 15:07:19 -04:00
.mailmap Add mailmap entry 2014-05-07 12:14:26 -07:00
.testr.conf Add tox -e functional 2014-11-12 15:31:06 -05:00
CONTRIBUTING.rst Workflow documentation is now in infra-manual 2014-12-05 03:30:37 +00:00
HACKING.rst Merge "Update HACKING.rst for running tests and building docs" 2015-07-20 16:03:32 +00:00
LICENSE initial commit 2010-05-27 23:05:26 -07:00
MAINTAINERS Add a maintainers file 2015-05-23 03:22:07 +10:00 Finish AUTHORS transition. 2012-07-05 09:11:37 -05:00
README.rst Update links in README 2014-05-07 16:06:24 -07:00
babel.cfg Get rid of distutils.extra. 2012-02-08 19:30:39 -08:00
bandit.yaml Add bandit for security static analysis testing 2015-07-02 09:17:48 -07:00
openstack-common.conf Switch to oslo.reports 2015-07-23 00:36:01 +03:00
requirements.txt Merge "Updated from global requirements" 2015-07-23 22:06:05 +00:00 Fix likely undesired use of redirection 2015-02-02 16:26:31 +01:00
setup.cfg Merge "Switch to oslo.service library" 2015-07-22 04:50:24 +00:00 Updated from global requirements 2015-07-18 16:07:43 +00:00
test-requirements.txt Updated from global requirements 2015-07-23 12:52:36 +00:00
tox.ini Merge "Add bandit for security static analysis testing" 2015-07-23 09:40:08 +00:00


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:

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