x/deb-os-client-config
Code Issues Proposed changes

Clarify one-per-cloud network values

Browse Source 
Make it clear in the docs that default_interface and nat_destination can
each be set only once per cloud.

Change-Id: Ic862b9f4dc31580c4e192f13f100428bbec7faa2
This commit is contained in:
Monty Taylor 2016-04-02 09:47:52 -05:00
parent 7c439073f3
commit fdb80ad04f
1 changed files with 4 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
doc/source/network-config.rst
View File

@ -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 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 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 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 `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 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 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 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.