Chris Friesen 2b3ba2286a Improve existing flavor and image metadata validation
This improves the existing validation of flavor extra-specs and image
properties in hardware.py in preparation for calling the validation from
more places in a follow-on patch.

get_cpu_topology_constraints() becomes public as we'll need to call it
from the API code in the next patch in the series.

If the CPU topology is not valid, raise an InvalidRequest exception with
a useful error message instead of a ValueError message without any
context.

Add checks to ensure that the CPU and CPU thread policies are valid,
and if not then raise newly-added exceptions with useful error messages.

Tweak various docstrings to more accurately reflect what exceptions
they might raise.

Change-Id: I20854134c80b8f4598f375eae137fd2920114891
blueprint: flavor-extra-spec-image-property-validation
Signed-off-by: Chris Friesen <chris.friesen@windriver.com>
2019-03-04 14:29:37 -06:00
2018-10-18 17:55:36 -04:00
2018-12-08 04:56:56 +00:00
2018-08-10 20:04:19 +00:00
2018-11-28 03:38:41 +00:00
2014-05-07 12:14:26 -07:00
2017-11-24 16:51:12 -05:00
2012-02-08 19:30:39 -08:00
2018-01-12 17:05:11 +08:00
2010-05-27 23:05:26 -07:00
2017-09-07 15:42:31 +02:00
2018-03-24 20:27:11 +08:00
2017-03-02 11:50:48 +00:00
2019-02-12 10:30:47 -06:00

Team and repository tags

image

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, 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:

Description
OpenStack Compute (Nova)
Readme 1.6 GiB
Languages
Python 97.7%
Smarty 2.2%
Shell 0.1%