Please make sure you have gone through Initial Foreman Setup Guide before attempting this guide. This guide builds on top of the previous guide by replacing and adding more infrastructure to enable OpenDaylight installation and configuration into the Neutron/ML2 plugin.

Please contact trozet@redhat.com or radez@redhat.com with any questions.

Per our testing, we have used a single Compute Node + one Control/Network consolidated node. Each node will run its own OVS instance, connected to ODL (OpenDaylight). ODL will be running on the Control/Network node along with all of the usual OpenStack services. l2_population, ovs_agent are disabled, but L3_agent, DHCP Neutron services are enabled.

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.

The guide currently relies on puppet module changes to puppet-trystack and quickstack (astapor). It also requires two new puppet modules to be installed on your foreman-server: a puppet-opendaylight module as well as a puppet-wait-for module. New global parameters have to be added to Foreman as well to tell QuickStack we want to use ODL as our network driver.

In /etc/puppet/environments/production/modules:

1. Replace trystack with: https://github.com/trozet/puppet-trystack.git quickstack branch - Replace quickstack with: https://github.com/trozet/astapor.git opendaylight branch
2. Install https://github.com/dfarrell07/puppet-opendaylight.git (pending trozet pull request for a fix)
3. Install https://github.com/basti1302/puppet-wait-for.git