diff --git a/doc/source/guides/neutron.rst b/doc/source/guides/neutron.rst index e99a143592..5891f68033 100644 --- a/doc/source/guides/neutron.rst +++ b/doc/source/guides/neutron.rst @@ -72,98 +72,6 @@ DevStack Configuration - - -Using Neutron with Multiple Interfaces -====================================== - -The first interface, eth0 is used for the OpenStack management (API, -message bus, etc) as well as for ssh for an administrator to access -the machine. - -:: - - stack@compute:~$ ifconfig eth0 - eth0 Link encap:Ethernet HWaddr bc:16:65:20:af:fc - inet addr:192.168.1.18 - -eth1 is manually configured at boot to not have an IP address. -Consult your operating system documentation for the appropriate -technique. For Ubuntu, the contents of `/etc/network/interfaces` -contains: - -:: - - auto eth1 - iface eth1 inet manual - up ifconfig $IFACE 0.0.0.0 up - down ifconfig $IFACE 0.0.0.0 down - -The second physical interface, eth1 is added to a bridge (in this case -named br-ex), which is used to forward network traffic from guest VMs. -Network traffic from eth1 on the compute nodes is then NAT'd by the -controller node that runs Neutron's `neutron-l3-agent` and provides L3 -connectivity. - -:: - - stack@compute:~$ sudo ovs-vsctl add-br br-ex - stack@compute:~$ sudo ovs-vsctl add-port br-ex eth1 - stack@compute:~$ sudo ovs-vsctl show - 9a25c837-32ab-45f6-b9f2-1dd888abcf0f - Bridge br-ex - Port br-ex - Interface br-ex - type: internal - Port phy-br-ex - Interface phy-br-ex - type: patch - options: {peer=int-br-ex} - Port "eth1" - Interface "eth1" - - - - - -Neutron Networking with Open vSwitch -==================================== - -Configuring neutron, OpenStack Networking in DevStack is very similar to -configuring `nova-network` - many of the same configuration variables -(like `FIXED_RANGE` and `FLOATING_RANGE`) used by `nova-network` are -used by neutron, which is intentional. - -The only difference is the disabling of `nova-network` in your -local.conf, and the enabling of the neutron components. - - -Configuration -------------- - -:: - - FIXED_RANGE=10.0.0.0/24 - FLOATING_RANGE=192.168.27.0/24 - PUBLIC_NETWORK_GATEWAY=192.168.27.2 - - disable_service n-net - enable_service q-svc - enable_service q-agt - enable_service q-dhcp - enable_service q-meta - enable_service q-l3 - - Q_USE_SECGROUP=True - ENABLE_TENANT_VLANS=True - TENANT_VLAN_RANGE=1000:1999 - PHYSICAL_NETWORK=default - OVS_PHYSICAL_BRIDGE=br-ex - -In this configuration we are defining FLOATING_RANGE to be a -subnet that exists in the private RFC1918 address space - however in -in a real setup FLOATING_RANGE would be a public IP address range. - Neutron Networking with Open vSwitch and Provider Networks ========================================================== @@ -206,6 +114,48 @@ Physical Network Setup } +On a compute node, the first interface, eth0 is used for the OpenStack +management (API, message bus, etc) as well as for ssh for an +administrator to access the machine. + +:: + + stack@compute:~$ ifconfig eth0 + eth0 Link encap:Ethernet HWaddr bc:16:65:20:af:fc + inet addr:10.0.0.3 + +eth1 is manually configured at boot to not have an IP address. +Consult your operating system documentation for the appropriate +technique. For Ubuntu, the contents of `/etc/network/interfaces` +contains: + +:: + + auto eth1 + iface eth1 inet manual + up ifconfig $IFACE 0.0.0.0 up + down ifconfig $IFACE 0.0.0.0 down + +The second physical interface, eth1 is added to a bridge (in this case +named br-ex), which is used to forward network traffic from guest VMs. + +:: + + stack@compute:~$ sudo ovs-vsctl add-br br-ex + stack@compute:~$ sudo ovs-vsctl add-port br-ex eth1 + stack@compute:~$ sudo ovs-vsctl show + 9a25c837-32ab-45f6-b9f2-1dd888abcf0f + Bridge br-ex + Port br-ex + Interface br-ex + type: internal + Port phy-br-ex + Interface phy-br-ex + type: patch + options: {peer=int-br-ex} + Port "eth1" + Interface "eth1" + Service Configuration ---------------------