From fdb80ad04f5611ebc62b4c64f896448c9213a75c Mon Sep 17 00:00:00 2001 From: Monty Taylor Date: Sat, 2 Apr 2016 09:47:52 -0500 Subject: [PATCH] Clarify one-per-cloud network values Make it clear in the docs that default_interface and nat_destination can each be set only once per cloud. Change-Id: Ic862b9f4dc31580c4e192f13f100428bbec7faa2 --- doc/source/network-config.rst | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/doc/source/network-config.rst b/doc/source/network-config.rst index 9bbbf9d..5a27b8e 100644 --- a/doc/source/network-config.rst +++ b/doc/source/network-config.rst @@ -38,10 +38,12 @@ one that programs should use. It defaults to false. An example of needing to use this value is a cloud with two private networks, and where a user is running ansible in one of the servers to talk to other servers on the private network. Because both networks are private, there would otherwise be no way -to determine which one should be used for the traffic. +to determine which one should be used for the traffic. There can only be one +`default_interface` per cloud. `nat_destination` is a boolean field that indicates which network floating ips should be attached to. It defaults to false. Normally this can be inferred by looking for a network that has subnets that have a gateway_ip. But it's possible to have more than one network that satisfies that condition, so the -user might want to tell programs which one to pick. +user might want to tell programs which one to pick. There can be only one +`nat_destination` per cloud.