User Tools

Site Tools


opendaylight_quickstack_guide

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Next revision
Previous revision
opendaylight_quickstack_guide [2015/02/11 19:54]
Tim Rozet created
opendaylight_quickstack_guide [2015/03/02 17:31] (current)
Tim Rozet
Line 10: Line 10:
  
 ==== What's working? ==== ==== What's working? ====
-We have tested successful bring up of two tenants and with DHCP in an private VXLAN network and been able to ping between them.  Limited testing has been done so far, and there is more scenarios that need to be tried/​tested.+We have tested successful bring up of two tenants and with DHCP in an private VXLAN network and been able to ping between them.  Limited testing has been done so far, and there are more scenarios that need to be tried/​tested.
  
 ==== Step by Step Guide ==== ==== Step by Step Guide ====
Line 17: Line 17:
 === Puppet Module Changes === === Puppet Module Changes ===
 In /​etc/​puppet/​environments/​production/​modules:​ In /​etc/​puppet/​environments/​production/​modules:​
-  - Replace trystack with: https://​github.com/​trozet/​puppet-trystack.git ​//quickstack branch +  - Replace trystack with: https://​github.com/​trozet/​puppet-trystack.git ​-quickstack branch 
-  - Replace quickstack with: https://​github.com/​trozet/​astapor.git ​//opendaylight branch +  - Replace quickstack with: https://​github.com/​trozet/​astapor.git ​opendaylight branch 
-  - Install https://​github.com/​dfarrell07/​puppet-opendaylight.git ​(pending trozet pull request for a fix)+  - Install https://​github.com/​dfarrell07/​puppet-opendaylight.git
   - Install https://​github.com/​basti1302/​puppet-wait-for.git   - Install https://​github.com/​basti1302/​puppet-wait-for.git
 +  - Remember to move all folders to rename them and remove the '​puppet-'​
 +  - Now in Foreman, re-import puppet classes to get trystack::​controller_networker node.
 +
 +=== Global Parameter Changes ===
 +There are new global parameters needed with the new puppet modules. ​ Additional ones are shown below:
 +
 +  * ovs_tunnel_if ​ - Interface that OVS will use to tunnel network data through. ​ This will be overridden per host so you can set to "​em1"​ for now. 
 +  * odl_flag ​      - Set to "​true"​ if you want OpenDaylight used.
 +  * odl_rest_port ​ - Optional. ​ Specifies ODL REST API port.  Defaults to 8081 to avoid conflicts with Swift.
 +  * odl_control_ip - Optional for controller_networker. ​ Required for network node.  ODL's IP.  Defaults to private_ip for controller_networker.
 +
 +=== Host Changes ===
 +If using the same server hardware or VMs throughout your environment then you can get away with just setting the private interface name as the global value for ovs_tunnel_if (since they will all be the same name). ​ However if you use different model servers or different NIC interfaces you need to override this parameter per host.  To do this in Foreman Web GUI:
 +  - Go to your Host->​Edit
 +  - Click Parameters and find ovs_tunnel_if
 +  - Click override, and enter the name of the private subnet interface for this host.
 +  - Do this for all hosts that will run OVS (network and compute nodes).
 +
 +=== Checking Results ===
 +Run puppet agent --test on all nodes to update them.  Once everything is complete on your network node you should be able to see service "​opendaylight"​ running. ​ You should also check OVS instances to make sure br-int is created and default flows are pushed by opendaylight:​
 +  * ovs-vsctl show
 +  * ovs-ofctl dump-flows -O openflow13 br-int
opendaylight_quickstack_guide.1423684486.txt.gz · Last modified: 2015/02/11 19:54 by Tim Rozet