openstack
/
nova
Code Issues Proposed changes
OpenStack Compute (Nova)
57,201 Commits 9 Branches 85 Tags 1.6 GiB
Python 97.7%
Smarty 2.2%
Shell 0.1%
Go to file
Stephen Finucane eedc0b5ff3 hardware: Raise useful error for invalid mempage size 
The 'hw:mem_page_size' extra spec allows you to specify values in three
ways: via a relative size alias (large, small, any), via exact byte
values, and via an SI/IEC/mixed representation (e.g. 2MB, 1GB).
Currently, attempting to use an invalid variant of the latter, such as
'2M', will raise a rather confusing error message:

  Invalid memory page size '0'

Correct this so we instead see something like so:

  Invalid memory page size '2M'

Change-Id: I3af99f03514904da09f7b71f430b43bf75e8be67
Signed-off-by: Stephen Finucane <stephenfin@redhat.com>
Closes-Bug: #1879964
(cherry picked from commit f76d09b19d)
 		2020-06-17 01:04:59 +00:00
api-guide/source Add release notes for Cyborg-Nova integration. 2020-04-03 17:13:04 +08:00
api-ref/source [Trivial] FUP: addressed comments in support non-admin filter instances 2020-04-10 09:17:48 +00:00
devstack Merge "Find instance in another cell during floating IP re-association" 2019-09-13 15:19:55 +00:00
doc Add admin doc information about image cache resource accounting 2020-05-21 09:09:12 +02:00
etc/nova Allow versioned discovery unauthenticated 2020-04-03 21:24:28 +00:00
gate nova-live-migration: Only stop n-cpu and q-agt during evacuation testing 2020-03-21 17:08:47 +00:00
nova hardware: Raise useful error for invalid mempage size 2020-06-17 01:04:59 +00:00
playbooks Enable cross-cell resize in the nova-multi-cell job 2019-12-23 10:10:57 -05:00
releasenotes Reserve DISK_GB resource for the image cache 2020-05-20 07:25:32 +00:00
roles Enable cross-cell resize in the nova-multi-cell job 2019-12-23 10:10:57 -05:00
tools Check cherry-pick hashes in pep8 tox target 2020-06-16 06:47:20 -07: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 Update .gitreview for stable/ussuri 2020-04-23 21:37:31 +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: Switch to the Zuulv3 grenade job 2020-04-28 22:29:08 +00:00
CONTRIBUTING.rst [Community goal] Update contributor documentation 2020-03-25 12:01:37 +00: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 "Use oslo policy flag to disable default change warning instead of all" 2020-04-21 10:04:19 +00:00
requirements.txt Merge "Use oslo policy flag to disable default change warning instead of all" 2020-04-21 10:04:19 +00:00
setup.cfg api: Add support for new cyborg extra specs 2020-04-08 13:19:39 +00:00
setup.py Updated from global requirements 2017-03-02 11:50:48 +00:00
test-requirements.txt Bump hacking min version to 3.0.1 2020-05-18 09:48:56 +00:00
tox.ini Check cherry-pick hashes in pep8 tox target 2020-06-16 06:47:20 -07: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: