fc1e18e3e4
The new field 'physical_network' was added to Port in version
1.7, and port creation was moved from the API to the conductor
service in commit 9e3f412186.
This change adds a method can_send_create_port() to the conductor
RPCAPI that allows the caller to determine whether the conductor is able
to create ports. During a rolling upgrade this may return False, and the
API will need to determine whether it is able to create the port locally
as was done previously.
The create_port RPC method was added to support validation of the
physical_network field of ports in portgroups. A port may therefore be
safely created in the API service if it is not a member of a portgroup.
If the port being created is a member of a portgroup, then it cannot be
safely validated by the API service and the request must be rejected.
Change-Id: I8c417cba085f61c3d2ffe1f7e97c64fa85a014cb
Related-Bug: #1666009
Related-Bug: #1526283
40 lines
1.9 KiB
YAML
40 lines
1.9 KiB
YAML
---
|
|
features:
|
|
- |
|
|
Adds a ``physical_network`` field to the port object in REST API version
|
|
1.34.
|
|
|
|
This field specifies the name of the physical network to which the port is
|
|
connected, and is empty by default. This field may be set by the operator
|
|
to allow the Bare Metal service to incorporate physical network information
|
|
when attaching virtual interfaces (VIFs).
|
|
|
|
The REST API endpoints related to ports provide support for the
|
|
``physical_network`` field. The `ironic developer documentation
|
|
<https://docs.openstack.org/ironic/latest/admin/multitenancy.html>`_
|
|
provides information on how to configure and use physical networks.
|
|
upgrade:
|
|
- |
|
|
Adds a ``physical_network`` field to the port object in REST API version
|
|
1.34.
|
|
|
|
This field specifies the name of the physical network to which the port is
|
|
connected, and is empty by default. This field may be set by the operator
|
|
to allow the Bare Metal service to incorporate physical network information
|
|
when attaching virtual interfaces (VIFs).
|
|
|
|
The REST API endpoints related to ports provide support for the
|
|
``physical_network`` field. The `ironic developer documentation
|
|
<https://docs.openstack.org/ironic/latest/admin/multitenancy.html>`_
|
|
provides information on how to configure and use physical networks.
|
|
|
|
Following an upgrade to this release, all ports will have an empty
|
|
``physical_network`` field. Attachment of Virtual Interfaces (VIFs) will
|
|
continue to function as in the previous release until any ports have their
|
|
physical network field set.
|
|
|
|
During a live upgrade to this release, the ``physical_network`` field will
|
|
not be available. It will also not be possible to create ports which are
|
|
members of a port group during a live upgrade, as the API service will be
|
|
unable to validate the consistency of the request.
|