ad4f798362
If more than one numbered request group is in the placement a_c query then the group_policy is mandatory. Based on the PTG discussion [1] 'none' seems to be a good default policy from nova perspective. So this patch makes sure that if the group_policy is not provided in the flavor extra_spec and there are more than one numbered group in the request and the flavor only provide one or zero groups (so groups are coming from other sources like neutron ports) then the group_policy is defaulted to 'none'. The reasoning behind this change: If more than one numbered request group is coming from the flavor extra_spec then the creator of the flavor is responsible to add a group_policy to the flavor. So in this nova only warns but let the request fail in placement to force the fixing of the flavor. However when numbered groups are coming from other sources (like neutron ports) then the creator of the flavor cannot know if additional group will be included so we don't want to force the flavor creator but simply default the group_policy. [1] http://lists.openstack.org/pipermail/openstack-discuss/2019-May/005807.html Change-Id: I0681de217ed9f5d77dae0d9555632b8d160bb179
Team and repository tags
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: