diff options
| author | Mark Goddard <mark@stackhpc.com> | 2017-07-20 10:41:54 +0100 |
|---|---|---|
| committer | Mark Goddard <mark@stackhpc.com> | 2017-07-26 18:23:17 +0100 |
| commit | fc1e18e3e4a28b1163e7a597ee8b07d465d7a174 (patch) | |
| tree | 183b8040f72f164ca797ac746b95f4f6dba2539e /releasenotes/notes/port-physical-network-a7009dc514353796.yaml | |
| parent | 338fdb94fc3b031e8d91bc7131cb4cadf05d7b92 (diff) | |
| download | ironic-fc1e18e3e4a28b1163e7a597ee8b07d465d7a174.tar.gz | |
Rolling upgrades support for create_port RPCAPI
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 9e3f4121865807294dd3768b095b67eb01ef539e.
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
Diffstat (limited to 'releasenotes/notes/port-physical-network-a7009dc514353796.yaml')
| -rw-r--r-- | releasenotes/notes/port-physical-network-a7009dc514353796.yaml | 5 |
1 files changed, 5 insertions, 0 deletions
diff --git a/releasenotes/notes/port-physical-network-a7009dc514353796.yaml b/releasenotes/notes/port-physical-network-a7009dc514353796.yaml index 97c36cac0..6fe1c8c45 100644 --- a/releasenotes/notes/port-physical-network-a7009dc514353796.yaml +++ b/releasenotes/notes/port-physical-network-a7009dc514353796.yaml @@ -32,3 +32,8 @@ upgrade: ``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. |