OpenStack Compute (Nova)
Go to file
Stephen Finucane 7f4c7bfcc1 db: Remove nova-network models
There are a number of nova-network tables which we can now drop.

nova-network
  Feature removed entirely in Ussuri.

  - dns_domains
  - fixed_ips
  - floating_ips
  - networks
  - provider_fw_rules
  - security_group_default_rules

Unfortunately we can't get rid of the security group-related entries due
to the unfortunate presence of the 'security_groups' attribute on the
'Instance' object and corresponding table, which in turn brings in a
load of other tables. We'll address that separately. For now, just drop
what we can easily drop.

Change-Id: I8858faa14119f4daa9630b0ff6dcf082d0ff8fba
Signed-off-by: Stephen Finucane <stephenfin@redhat.com>
2021-11-03 17:33:53 +00:00
api-guide/source [doc] port-resource-request-groups not landed in Xena 2021-09-06 13:03:22 +02:00
api-ref/source Merge "Add some missing parameters in docs of os-cells" 2021-09-01 17:06:06 +00:00
devstack Switch to new rolevar for run-tempest role 2021-04-09 16:06:10 +00:00
doc objects: Remove 'bandwidth' fields from notifications 2021-11-03 17:33:43 +00:00
etc/nova Merge "Add missing [oslo_reports] options" 2021-08-24 13:41:16 +00:00
gate gate: Remove test_evacuate.sh 2021-06-15 17:35:20 +01:00
nova db: Remove nova-network models 2021-11-03 17:33:53 +00:00
playbooks zuul: Replace grenade and nova-grenade-multinode with grenade-multinode 2021-04-29 11:05:58 +01:00
releasenotes objects: Remove 'bandwidth' fields from notifications 2021-11-03 17:33:43 +00:00
roles [OVN] Adapt the live-migration job scripts to work with OVN 2021-03-15 09:41:03 +00:00
tools tools: Ignore bot-generated branch creation patches 2021-09-27 10:20:34 +01:00
.coveragerc Remove nova/openstack/* from .coveragerc 2016-10-12 16:20:49 -04:00
.gitignore db: Enable auto-generation of API DB migrations 2021-10-18 20:26:18 +01: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 Switch to hacking 2.x 2020-01-17 11:30:40 +00:00
.stestr.conf Finish stestr migration 2017-11-24 16:51:12 -05:00
.zuul.yaml zuul: Move live migration jobs back to voting 2021-10-07 11:21:51 +01:00
CONTRIBUTING.rst [Community goal] Update contributor documentation 2020-03-25 12:01:37 +00:00
HACKING.rst Add two new hacking rules 2021-09-01 12:26:52 +01: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 docs: Remove references to XenAPI driver 2020-08-31 15:53:31 +01:00
bindep.txt tests: Allow bindep and test-setup.sh to run on EL distros 2021-06-18 12:34:27 +01:00
lower-constraints.txt db: Final cleanups 2021-08-17 13:50:19 +01:00
mypy-files.txt mypy: Add type annotations to 'nova.pci' 2021-04-26 18:06:21 +01:00
requirements.txt db: Final cleanups 2021-08-17 13:50:19 +01:00
setup.cfg setup.cfg: Resolve warning 2021-03-09 12:49:50 +00:00
setup.py Updated from global requirements 2017-03-02 11:50:48 +00:00
test-requirements.txt requirements: Add types-paramiko 2021-06-09 15:18:47 +01:00
tox.ini Define new functional test tox env for placement gate to run 2021-10-12 18:20:35 -05: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, 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: