UnderstandingFlatNetworking - Revision history

Ryan Lane: Text replace - "NOTOC" to ""

2013-02-17T23:30:36Z

Text replace - "__NOTOC__" to ""

Clark Boylan at 21:48, 16 February 2013

2013-02-16T21:48:52Z

AnneGentle at 13:31, 20 September 2011

2011-09-20T13:31:33Z

JosephHeck at 19:16, 27 June 2011

2011-06-27T19:16:45Z

JosephHeck at 19:11, 27 June 2011

2011-06-27T19:11:55Z

New page

__NOTOC__
= Understanding [[FlatNetworking]] =

(''this took me quite a while to get into my head, so I'm writing it down for anyone else'')

[[OpenStack]]/Nova has two general catagories (as of Cactus/Diablo releases) for networking:

* [[FlatNetworking]]
* VLANNetworking

== [[FlatNetworking]] ==

[[FlatNetworking]] uses ethernet adapters configured as bridges to allow network traffic to transit between all the various nodes. This setup can be done with a single adapter on the physical host, or multiple. This option _*does not*_ require a switch that does VLAN tagging (VLANNetworking does) - and is a common development installation or proof of concept setup.

=== Single Adapter, All in one setup ===

* extremely common development setup

AllInOneSingleInterface.png!

=== Multiple nodes with a single adapter ===

* smoke testing, proof of concept layout

FlatNetworkSingleInterface.png!

=== Multiple nodes, multiple adapters ===

* server setup with separate admin and data traffic

FlatNetworkMultInterface.png!

== Outbound Traffic Flow ==

In any set up with [[FlatNetworking]], the host with `nova-network` on it is responsible for forwarding traffic from the private network configured with the {{--fixed_range=...} directive in nova.conf. This host needs to have br100 configured and talking to any other nodes that are hosting VMs. With either of the Flat Networking options, the default gateway for the virtual machines is set to the host which is running `nova-network`.

=== Single adaptor hosts ===

* When a virtual machine sends traffic out to the public networks, it sends it first to it's default gateway (where ever `nova-network` is configured)

SingleInterface_1Outbound.png!

* Then the host on which `nova-network` is configured acts as a router and forwards the traffic out to the Internet.

SingleInterfaceOutbound_2.png!

<pre><nowiki>#!wiki caution
If you're using a single interface, then that interface (often eth0) needs to be set into promiscuous mode for the forwarding to happen correctly. This _does not_ appear to be needed if you're running with physical hosts that have and use two interfaces.
</nowiki></pre>

=== Multiple adaptor hosts ===

* When a virtual machine sends traffic out to the public networks, it sends it first to it's default gateway (where ever `nova-network` is configured). In a multiple adapter setup, this is over the adapter that is configured as a bridge interface and connected to the other hosts via a switch.

MultiInterfaceOutbound_1.png!

* Then the host on which `nova-network` is configured acts as a router and forwards the traffic out to the Internet. Typically over the second interface, which has been configured with the hosts internet IP address.

MultiInterfaceOutbound_2.png!

== Inbound Traffic ==

For inbound traffic (assuming a floating IP address has been set up), the `nova-network` host is responsible for hosting that IP address and doing the DNAT/SNAT addressing to route the traffic to the appropriate virtual machine.

← Older revision		Revision as of 23:30, 17 February 2013
Line 1:		Line 1:
−	~~__NOTOC__~~	+
	= Understanding [[FlatNetworking]] =		= Understanding [[FlatNetworking]] =

@@ Line 17: / Line 17: @@
 * extremely common development setup
-[[Image:UnderstandingFlatNetworking$FlatNetworkSingleInterfaceAllInOne.png]]
+[[Image:FlatNetworkSingleInterfaceAllInOne.png]]
 === Multiple nodes with a single adapter ===
@@ Line 23: / Line 23: @@
 * smoke testing, proof of concept layout
-[[Image:UnderstandingFlatNetworking$FlatNetworkSingleInterface.png]]
+[[Image:FlatNetworkSingleInterface.png]]
 === Multiple nodes, multiple adapters ===
@@ Line 29: / Line 29: @@
 * server setup with separate admin and data traffic
-[[Image:UnderstandingFlatNetworking$FlatNetworkMultInterface.png]]
+[[Image:FlatNetworkMultInterface.png]]
 == Outbound Traffic Flow ==
@@ Line 39: / Line 39: @@
 * When a virtual machine sends traffic out to the public networks, it sends it first to it's default gateway (where ever `nova-network` is configured)
-[[Image:UnderstandingFlatNetworking$SingleInterfaceOutbound_1.png]]
+[[Image:SingleInterfaceOutbound_1.png]]
 * Then the host on which `nova-network` is configured acts as a router and forwards the traffic out to the Internet.
-[[Image:UnderstandingFlatNetworking$SingleInterfaceOutbound_2.png]]
+[[Image:SingleInterfaceOutbound_2.png]]
 <pre><nowiki>#!wiki caution
 If you're using a single interface, then that interface (often eth0) needs to be set into promiscuous mode for the forwarding to happen correctly. This _does not_ appear to be needed if you're running with physical hosts that have and use two interfaces.
 </nowiki></pre>
 === Multiple adapter hosts ===
@@ Line 55: / Line 53: @@
 * When a virtual machine sends traffic out to the public networks, it sends it first to it's default gateway (where ever `nova-network` is configured). In a multiple adapter setup, this is over the adapter that is configured as a bridge interface and connected to the other hosts via a switch.
-[[Image:UnderstandingFlatNetworking$MultiInterfaceOutbound_1.png]]
+[[Image:MultiInterfaceOutbound_1.png]]
 * Then the host on which `nova-network` is configured acts as a router and forwards the traffic out to the Internet. Typically over the second interface, which has been configured with the hosts internet IP address.
-[[Image:UnderstandingFlatNetworking$MultiInterfaceOutbound_2.png]]
+[[Image:MultiInterfaceOutbound_2.png]]
 == Inbound Traffic ==
 For inbound traffic (assuming a floating IP address has been set up), the `nova-network` host is responsible for hosting that IP address and doing the DNAT/SNAT addressing to route the traffic to the appropriate virtual machine.