From b938d27cc452d385f158a86ac1da66b461b36571 Mon Sep 17 00:00:00 2001 From: Anne Gentle Date: Thu, 8 Jan 2015 10:50:34 -0600 Subject: [PATCH] Corrects required information for floating IP creation Change-Id: I163ce5d2d7fed7a2f8eb07f8c51d72db239aef9b Closes-bug: 1359987 --- api-ref/src/wadls/netconn-api/src/common.ent | 18 +++++++++++++----- 1 file changed, 13 insertions(+), 5 deletions(-) diff --git a/api-ref/src/wadls/netconn-api/src/common.ent b/api-ref/src/wadls/netconn-api/src/common.ent index 94a8c7743..4965dcb4e 100644 --- a/api-ref/src/wadls/netconn-api/src/common.ent +++ b/api-ref/src/wadls/netconn-api/src/common.ent @@ -715,7 +715,7 @@ '> - A floatingip object. + A floatingip object. When you associate a + floating IP address with a VM, the instance has the same public IP + address each time that it boots, basically to maintain a consistent + IP address for maintaining DNS assignment. '> '> The fixed IP address associated with the floating - IP. + IP. If you intend to associate the floating IP with a + fixed IP at creation time, then you must indicate the + identifier of the internal port. If an internal port + has multiple associated IP addresses, the service chooses the first IP + unless you explicitly specify the parameter fixed_ip_address to select + a specific IP. '>