OpenStack Compute (Nova)
Go to file
Ilya Etingof 69ee625a66 Add JSON schema and test for network_data.json
Added JSON schema defining `network_data.json` contents and
beefed up the MetadataTest functional test cases to use a
real instance instead of a database shell. This way the
tests see real data in the metadata service like a real
network_data.json.

Besides internal Nova consumption, this schema might be
helpful to other tools (such as ironic or Glean) to
validate human-generated `network_data.json` prior to
using it.

Co-Authored-By: Balazs Gibizer <balazs.gibizer@est.tech>
Change-Id: Ie5a5a1fc81c7c2d3f61b72d19de464cfc9dab5ec
2020-02-17 15:35:24 +01:00
api-guide/source Merge "Fix typos in nova doc" 2020-01-10 23:27:11 +00:00
api-ref/source Merge "Remove 'nova-xvpvncproxy'" 2020-01-08 06:27:03 +00:00
devstack Merge "Find instance in another cell during floating IP re-association" 2019-09-13 15:19:55 +00:00
doc Add JSON schema and test for network_data.json 2020-02-17 15:35:24 +01:00
etc/nova Remove unused rootwrap filters 2019-12-04 12:32:49 +01:00
gate Convert legacy nova-live-migration and nova-multinode-grenade to py3 2019-11-14 16:06:02 +00:00
nova Add JSON schema and test for network_data.json 2020-02-17 15:35:24 +01:00
playbooks Enable cross-cell resize in the nova-multi-cell job 2019-12-23 10:10:57 -05:00
releasenotes Merge "Add a workaround config toggle to refuse ceph image upload" 2020-01-10 08:41:44 +00:00
roles Enable cross-cell resize in the nova-multi-cell job 2019-12-23 10:10:57 -05:00
tools Keep pre-commit inline with hacking and fix whitespace 2019-12-12 14:56:39 +00:00
.coveragerc Remove nova/openstack/* from .coveragerc 2016-10-12 16:20:49 -04:00
.gitignore Delete the placement code 2019-04-28 20:06:15 +00:00
.gitreview OpenDev Migration Patch 2019-04-19 19:45:52 +00:00
.mailmap Add mailmap entry 2014-05-07 12:14:26 -07:00
.pre-commit-config.yaml Keep pre-commit inline with hacking and fix whitespace 2019-12-12 14:56:39 +00:00
.stestr.conf Finish stestr migration 2017-11-24 16:51:12 -05:00
.zuul.yaml Merge "Restore test_minbw_allocation_placement in nova-next job" 2020-01-03 20:45:45 +00:00
CONTRIBUTING.rst Update links in documents 2018-01-12 17:05:11 +08:00
HACKING.rst Merge "Make it easier to run a selection of tests relevant to ongoing work" 2019-11-22 20:58:18 +00:00
LICENSE initial commit 2010-05-27 23:05:26 -07:00
MAINTAINERS Fix broken URLs 2017-09-07 15:42:31 +02:00
README.rst Start README.rst with a better title 2019-11-19 17:29:28 +01:00
babel.cfg Get rid of distutils.extra. 2012-02-08 19:30:39 -08:00
bindep.txt Added openssh-client into bindep 2019-10-23 07:21:23 +00:00
lower-constraints.txt Merge "Report trait 'COMPUTE_IMAGE_TYPE_PLOOP'" 2020-01-07 05:29:24 +00:00
requirements.txt Merge "Report trait 'COMPUTE_IMAGE_TYPE_PLOOP'" 2020-01-07 05:29:24 +00:00
setup.cfg Remove 'nova-xvpvncproxy' 2019-12-23 14:20:28 +00:00
setup.py Updated from global requirements 2017-03-02 11:50:48 +00:00
test-requirements.txt Revert "(Temporarily) readd bare support for py27" 2019-12-13 12:45:52 +00:00
tox.ini Stop testing Python 2 2019-11-18 10:31:06 +00:00

README.rst

OpenStack Nova

image

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: