Validate the combination of the flavor extra-specs and image properties as early as possible once they're both known (since you can specify mutually-incompatible changes in the two places). If validation failed then synchronously return error to user. We need to do this anywhere the flavor or image changes, so basically instance creation, rebuild, and resize. - Rename _check_requested_image() to _validate_flavor_image() and add a call from the resize code path. (It's already called for create and rebuild.) - In _validate_flavor_image() add new checks to validate numa related options from flavor and image including CPU policy, CPU thread policy, CPU topology, memory topology, hugepages, CPU pinning, serial ports, realtime mask, etc. - Added new 400 exceptions in Server API correspondent to added validations. blueprint: flavor-extra-spec-image-property-validation Change-Id: I06fad233006c7bab14749a51ffa226c3801f951b Signed-off-by: Jack Ding <email@example.com> Signed-off-by: Chris Friesen <firstname.lastname@example.org>
Team and repository tags
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.
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:
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:
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: