openstack
/
nova
Code Issues Proposed changes
OpenStack Compute (Nova)
43,054 Commits 9 Branches 85 Tags 1.6 GiB
Python 97.7%
Smarty 2.2%
Shell 0.1%
Go to file
Sam Betts 28e6faecbf Ensure we mark baremetal links as phy links 
In the Ironic multi-tenant case, the neutron ports will remain unbound
until later in the deploy process. Nova generates the network_data.json
file with all the links marked as unbound, which we need to correct as
these links will be bound after the config drive is generated and
written to the node. This patch updates the Ironic virt driver to
correct the network metadata.

Change-Id: I1881f4a9bca6a6d6a3b4e0e89a82b0765ae09eee
Closes-Bug: #1656854
(cherry picked from commit b34809dfae)
 		2017-01-20 10:13:35 +00:00
api-guide/source Merge "Change api-site to v2.1 format" 2016-09-08 15:57:36 +00:00
api-ref/source Add flavor extra_spec info link to api_ref 2016-11-16 02:20:20 +00:00
contrib Merge "changed quantum to neutron in vif-openstack" 2014-03-05 10:45:05 +00:00
devstack Add RC file for excluding tempest tests for LVM job 2016-05-17 10:25:45 -04:00
doc Update docs for serial console support 2016-11-09 09:46:26 -05:00
etc/nova Remove nova.network namespace from nova-config-generator.conf 2016-07-28 18:14:12 -04:00
nova Ensure we mark baremetal links as phy links 2017-01-20 10:13:35 +00:00
plugins/xenserver plugins/xenserver: Resolve PEP8 issues 2016-08-15 18:11:49 +01:00
releasenotes Add release note for bug 1635446 2016-10-31 11:54:30 -04:00
tools Remove locals() for formatting strings. 2016-08-22 17:32:38 +07:00
.coveragerc Change ignore-errors to ignore_errors 2015-09-21 14:34:39 +00:00
.gitignore Ignore generated merged policy files 2016-08-31 08:54:25 -07:00
.gitreview Update .gitreview for stable/newton 2016-09-16 09:59:46 +02:00
.mailmap Add mailmap entry 2014-05-07 12:14:26 -07:00
.testr.conf Add initial framing of placement API 2016-07-29 10:31:36 +00:00
CONTRIBUTING.rst Workflow documentation is now in infra-manual 2014-12-05 03:30:37 +00:00
HACKING.rst Remove hacking check [N347] for config options. 2016-08-11 14:23:21 +02: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
README.rst Refresh README and its docs links 2016-08-08 10:26:08 +01: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
bindep.txt List system dependencies for running common tests 2016-08-24 06:49:32 +02:00
requirements.txt Updated from global requirements 2016-09-22 21:15:03 +00:00
run_tests.sh Add description on how to run ./run_test.sh -8 2016-01-11 13:17:04 +00:00
setup.cfg Merge "Adds nova-policy-check cmd" 2016-09-01 17:56:56 +00:00
setup.py Updated from global requirements 2015-09-17 16:41:48 +00:00
test-requirements.txt Updated from global requirements 2016-09-03 01:59:32 +00:00
tests-py3.txt Remove nova/api/validator.py 2016-08-16 09:52:29 +00:00
tox.ini Update UPPER_CONSTRAINTS_FILE for stable/newton 2016-09-16 09:59:58 +02:00

README.rst

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 and OpenStack Ironic.

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.

API

To learn how to use Nova's API, consult the documentation available online at:

http://developer.openstack.org/api-guide/compute/ http://developer.openstack.org/api-ref/compute/

For more information on OpenStack APIs, SDKs and CLIs, please see:

http://www.openstack.org/appdev/ http://developer.openstack.org/

Operators

To learn how to deploy and configure OpenStack Nova, consult the documentation available online at:

http://docs.openstack.org

For information about the different compute (hypervisor) drivers supported by Nova, please read:

http://docs.openstack.org/developer/nova/feature_classification.html

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:

http://bugs.launchpad.net/nova

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:

http://docs.openstack.org/developer/nova/