From 2ac329b90274ecbf7dd3234b39c74dc974658c30 Mon Sep 17 00:00:00 2001 From: Boden R Date: Mon, 9 Oct 2017 14:49:49 -0600 Subject: [PATCH] clarify deferred fixed IP assignment for ports on routed networks 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 --- doc/source/admin/config-routed-networks.rst | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/doc/source/admin/config-routed-networks.rst b/doc/source/admin/config-routed-networks.rst index bff9e556a32..cf5740b0618 100644 --- a/doc/source/admin/config-routed-networks.rst +++ b/doc/source/admin/config-routed-networks.rst @@ -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: