Reject server create with extended resource req
To prepare for the unlikely event that Neutron merges and an operator enables the port-resource-request-groups neutron API extension before nova adds support for it, this patch rejects server creation if such extension is enabled in Neutron. Enabling that extension has zero benefits without nova support hence the harsh but simple rejection. A subsequent patch will reject server lifecycle operations in a more sophisticated way and as soon as we support some operations, like boot, the deployer might rightfully choose to enable the Neutron extension. Change-Id: I2c55d9da13a570efbc1c862116cea31aaa6aa02e blueprint: qos-minimum-guaranteed-packet-rate
This commit is contained in:
@@ -39,5 +39,15 @@ servers with neutron ports having resource requests.
|
||||
As of 23.0.0 (Wallaby), nova supports attaching neutron ports having QoS
|
||||
minimum bandwidth rules.
|
||||
|
||||
Extended resource request
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
Since neutron 19.0.0 (Xena), neutron implements an extended resource request
|
||||
format via the the ``port-resource-request-groups`` neutron API extension. As
|
||||
of nova 24.0.0 (Xena), nova does not support the new extension. If the
|
||||
extension is enabled in neutron, then nova will reject server create and move
|
||||
operations, as well as interface attach operation. Admins should not enable
|
||||
this API extension in neutron.
|
||||
|
||||
See :nova-doc:`the admin guide <admin/port_with_resource_request.html>` for
|
||||
administrative details.
|
||||
|
||||
Reference in New Issue
Block a user