openstack/nova
Code Issues Proposed changes
OpenStack Compute (Nova)
58,414 Commits 10 Branches 95 Tags 1.6 GiB
Python 97.7%
Smarty 2.2%
Shell 0.1%
8cddd243bf
Go to file
Lee Yarwood 8cddd243bf nova-status: Add hw_machine_type check for libvirt instances 
This change introduces a new nova-status check to ensure a machine type
has been recorded for each instance within an environment.

nova-status will fail with a warning when instances are found, directing
the operator to use the previously added nova-manage list_unset and
update commands to set a machine type for these instances. The logic for
this check comes entirely from the list_unset command.

It is noted in the warning output that this can be ignored if no libvirt
or HyperV based computes are present in the environment as
hw_machine_type is only used by these two virt drivers at present.

blueprint: libvirt-default-machine-type
Change-Id: Ic3ae48c57e61c4e45883fbae1328a448be025953
2021-03-03 14:03:49 +00:00
api-guide/source Support interface attach with QoS ports 2021-02-11 16:43:17 +01:00
api-ref/source Merge "api-ref: Add notes about volume attach and detach being async" 2021-01-20 17:54:42 +00:00
devstack Revert "nova-multi-cell: Skip test_cold_migrate_unshelved_instance" 2020-12-17 10:24:27 +00:00
doc nova-status: Add hw_machine_type check for libvirt instances 2021-03-03 14:03:49 +00:00
etc/nova Allow versioned discovery unauthenticated 2020-04-03 21:24:28 +00:00
gate Merge "Revert "Temporarily disable parts of heal port allocation test"" 2020-12-16 18:37:40 +00:00
nova nova-status: Add hw_machine_type check for libvirt instances 2021-03-03 14:03:49 +00:00
playbooks Restart glance after updating policy in job 2021-01-29 16:16:24 -08:00
releasenotes nova-status: Add hw_machine_type check for libvirt instances 2021-03-03 14:03:49 +00:00
roles nova-live-migration: Disable *all* virt services during negative tests 2020-11-27 13:35:42 +00:00
tools tools: Allow check-cherry-picks.sh to be disabled by an env var 2020-12-07 12:53:42 +00:00
.coveragerc Remove nova/openstack/* from .coveragerc 2016-10-12 16:20:49 -04:00
.gitignore tox: Integrate mypy 2020-05-15 15:59:53 +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 Merge "Run nova-live-migration job with neutron-trunk enabled" 2021-02-17 15:22:01 +00:00
bindep.txt bindep: Install python3 and python3-devel on CentOS 8 and Fedora 2020-10-03 13:20:21 +01:00
CONTRIBUTING.rst [Community goal] Update contributor documentation 2020-03-25 12:01:37 +00:00
HACKING.rst Add a hacking rule for assert_has_calls 2020-09-28 23:08:15 +09:00
LICENSE initial commit 2010-05-27 23:05:26 -07:00
lower-constraints.txt scheduler: Add 'socket' PCI NUMA affinity policy trait 2021-02-24 10:50:23 +00:00
MAINTAINERS Fix broken URLs 2017-09-07 15:42:31 +02:00
mypy-files.txt nova-manage: Add libvirt get_machine_type command 2021-03-03 14:03:49 +00:00
README.rst docs: Remove references to XenAPI driver 2020-08-31 15:53:31 +01:00
requirements.txt scheduler: Add 'socket' PCI NUMA affinity policy trait 2021-02-24 10:50:23 +00:00
setup.cfg Fix config option default value for sample config file 2020-11-25 00:05:08 +00:00
setup.py Updated from global requirements 2017-03-02 11:50:48 +00:00
test-requirements.txt use psycopg2 binary instead of source package 2021-01-14 18:12:04 +00:00
tox.ini tox: Add passenv DISABLE_CHERRY_PICK_CHECK to pep8 2021-02-17 11:23:49 +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, 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: