diff options
| author | Anne Gentle <anne@openstack.org> | 2010-11-17 15:58:10 -0600 |
|---|---|---|
| committer | Anne Gentle <anne@openstack.org> | 2010-11-17 15:58:10 -0600 |
| commit | 8257fcc259185e5b13f09d3e15cb81487c799c3b (patch) | |
| tree | 365a256d0290d4556a4fe772ae1ea6a40b2e380c /doc/source | |
| parent | 908f7505792408a5f0070b59325ff4c1b484e723 (diff) | |
Documenting all nova-manage commands
Diffstat (limited to 'doc/source')
| -rw-r--r-- | doc/source/adminguide/network.vlan.rst | 5 |
1 files changed, 3 insertions, 2 deletions
diff --git a/doc/source/adminguide/network.vlan.rst b/doc/source/adminguide/network.vlan.rst index a7cccc098..5bbc54bed 100644 --- a/doc/source/adminguide/network.vlan.rst +++ b/doc/source/adminguide/network.vlan.rst @@ -31,8 +31,9 @@ In this mode, each project gets its own VLAN, Linux networking bridge, and subne In the VLAN network mode, all the VM instances of a project are connected together in a VLAN with the specified private subnet. Each running VM instance is assigned an IP address within the given private subnet. -.. todo:: Insert Figure 2 from "An OpenStack Network Overview" contributed by Citrix - +.. image:: /images/Novadiagram.png + :width: 790 + While network traffic between VM instances belonging to the same VLAN is always open, Nova can enforce isolation of network traffic between different projects by enforcing one VLAN per project. In addition, the network administrator can specify a pool of public IP addresses that users may allocate and then assign to VMs, either at boot or dynamically at run-time. This capability is similar to Amazon's 'elastic IPs'. A public IP address may be associated with a running instances, allowing the VM instance to be accessed from the public network. The public IP addresses are accessible from the network host and NATed to the private IP address of the project. |