Browse code
Merge "Documentation for single interface Neutron networking with OVS"
Jenkins authored on 2015/06/10 08:00:12Showing 3 changed files
| ... | ... |
@@ -26,7 +26,7 @@ import os |
| 26 | 26 |
|
| 27 | 27 |
# Add any Sphinx extension module names here, as strings. They can be extensions |
| 28 | 28 |
# coming with Sphinx (named 'sphinx.ext.*') or your custom ones. |
| 29 |
-extensions = [ 'oslosphinx' ] |
|
| 29 |
+extensions = [ 'oslosphinx', 'sphinxcontrib.blockdiag', 'sphinxcontrib.nwdiag' ] |
|
| 30 | 30 |
|
| 31 | 31 |
todo_include_todos = True |
| 32 | 32 |
|
| ... | ... |
@@ -5,11 +5,77 @@ Using DevStack with neutron Networking |
| 5 | 5 |
This guide will walk you through using OpenStack neutron with the ML2 |
| 6 | 6 |
plugin and the Open vSwitch mechanism driver. |
| 7 | 7 |
|
| 8 |
-Network Interface Configuration |
|
| 9 |
-=============================== |
|
| 10 | 8 |
|
| 11 |
-To use neutron, it is suggested that two network interfaces be present |
|
| 12 |
-in the host operating system. |
|
| 9 |
+Using Neutron with a Single Interface |
|
| 10 |
+===================================== |
|
| 11 |
+ |
|
| 12 |
+In some instances, like on a developer laptop, there is only one |
|
| 13 |
+network interface that is available. In this scenario, the physical |
|
| 14 |
+interface is added to the Open vSwitch bridge, and the IP address of |
|
| 15 |
+the laptop is migrated onto the bridge interface. That way, the |
|
| 16 |
+physical interface can be used to transmit tenant network traffic, |
|
| 17 |
+the OpenStack API traffic, and management traffic. |
|
| 18 |
+ |
|
| 19 |
+ |
|
| 20 |
+Physical Network Setup |
|
| 21 |
+---------------------- |
|
| 22 |
+ |
|
| 23 |
+In most cases where DevStack is being deployed with a single |
|
| 24 |
+interface, there is a hardware router that is being used for external |
|
| 25 |
+connectivity and DHCP. The developer machine is connected to this |
|
| 26 |
+network and is on a shared subnet with other machines. |
|
| 27 |
+ |
|
| 28 |
+.. nwdiag:: |
|
| 29 |
+ |
|
| 30 |
+ nwdiag {
|
|
| 31 |
+ inet [ shape = cloud ]; |
|
| 32 |
+ router; |
|
| 33 |
+ inet -- router; |
|
| 34 |
+ |
|
| 35 |
+ network hardware_network {
|
|
| 36 |
+ address = "172.18.161.0/24" |
|
| 37 |
+ router [ address = "172.18.161.1" ]; |
|
| 38 |
+ devstack_laptop [ address = "172.18.161.6" ]; |
|
| 39 |
+ } |
|
| 40 |
+ } |
|
| 41 |
+ |
|
| 42 |
+ |
|
| 43 |
+DevStack Configuration |
|
| 44 |
+---------------------- |
|
| 45 |
+ |
|
| 46 |
+ |
|
| 47 |
+:: |
|
| 48 |
+ |
|
| 49 |
+ HOST_IP=172.18.161.6 |
|
| 50 |
+ SERVICE_HOST=172.18.161.6 |
|
| 51 |
+ MYSQL_HOST=172.18.161.6 |
|
| 52 |
+ RABBIT_HOST=172.18.161.6 |
|
| 53 |
+ GLANCE_HOSTPORT=172.18.161.6:9292 |
|
| 54 |
+ ADMIN_PASSWORD=secrete |
|
| 55 |
+ MYSQL_PASSWORD=secrete |
|
| 56 |
+ RABBIT_PASSWORD=secrete |
|
| 57 |
+ SERVICE_PASSWORD=secrete |
|
| 58 |
+ SERVICE_TOKEN=secrete |
|
| 59 |
+ |
|
| 60 |
+ ## Neutron options |
|
| 61 |
+ Q_USE_SECGROUP=True |
|
| 62 |
+ FLOATING_RANGE="172.18.161.1/24" |
|
| 63 |
+ FIXED_RANGE="10.0.0.0/24" |
|
| 64 |
+ Q_FLOATING_ALLOCATION_POOL=start=172.18.161.250,end=172.18.161.254 |
|
| 65 |
+ PUBLIC_NETWORK_GATEWAY="172.18.161.1" |
|
| 66 |
+ Q_L3_ENABLED=True |
|
| 67 |
+ PUBLIC_INTERFACE=eth0 |
|
| 68 |
+ Q_USE_PROVIDERNET_FOR_PUBLIC=True |
|
| 69 |
+ OVS_PHYSICAL_BRIDGE=br-ex |
|
| 70 |
+ PUBLIC_BRIDGE=br-ex |
|
| 71 |
+ OVS_BRIDGE_MAPPINGS=public:br-ex |
|
| 72 |
+ |
|
| 73 |
+ |
|
| 74 |
+ |
|
| 75 |
+ |
|
| 76 |
+ |
|
| 77 |
+Using Neutron with Multiple Interfaces |
|
| 78 |
+====================================== |
|
| 13 | 79 |
|
| 14 | 80 |
The first interface, eth0 is used for the OpenStack management (API, |
| 15 | 81 |
message bus, etc) as well as for ssh for an administrator to access |