openstack/neutron
Code Issues Proposed changes

clarify deferred fixed IP assignment for ports on routed networks

Browse Source 
This patch clarifies the routed network configuration doc with respect
to when a fixed IP is assigned to a port on a routed network. For
more details see related bug.

Change-Id: Id8e97afdfc488069ac3a910e017c34b085b4eb36
Closes-Bug: #1718320
This commit is contained in:
Boden R 2017-10-09 14:49:49 -06:00
parent 779a8d31e7
commit 2ac329b902
1 changed files with 2 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
doc/source/admin/config-routed-networks.rst
View File

@ -440,7 +440,8 @@ segment contains one IPv4 subnet and one IPv6 subnet.
If a fixed IP is specified by the user in the port create request, that
particular IP is allocated immediately to the port. However, creating a
port and passing it to an instance yields a different behavior than
conventional networks. The Networking service defers assignment of IP
conventional networks. If the fixed IP is not specified on the port
create request, the Networking service defers assignment of IP
addresses to the port until the particular compute node becomes
apparent. For example: