Procedure 7.16. Configuring the Open vSwitch Plug-in Agent

1. Confirm that the openvswitch package is installed. This is normally installed as a dependency of the neutron-plugin-openvswitch package.

   # rpm -qa | grep openvswitch
   openvswitch-1.10.0-1.el6.x86_64
   openstack-neutron-openvswitch-2013.1-3.el6.noarc

2. Start the openvswitch service.

   # service openvswitch start

3. Enable the openvswitch service permanently.

   # chkconfig openvswitch on

4. Each host running the Open vSwitch agent also requires an Open vSwitch bridge named br-int. This bridge is used for private network traffic. Use the ovs-vsctl command to create this bridge before starting the agent.

   # ovs-vsctl add-br br-int

   Warning

   The br-int bridge is required for the agent to function correctly. Once created do not remove or otherwise modify the br-int bridge.
5. Ensure that the br-int device persists on reboot by creating a /etc/sysconfig/network-scripts/ifcfg-br-int file with these contents:

   DEVICE=br-int
   DEVICETYPE=ovs
   TYPE=OVSBridge
   ONBOOT=yes
   BOOTPROTO=none

6. Set the value of the bridge_mappings configuration key. This configuration key must contain a list of physical networks and the network bridges associated with them.
   The format for each entry in the comma separated list is:

   PHYSNET:BRIDGE

   Where PHYSNET is replaced with the name of a physical network, and BRIDGE is replaced by the name of the network bridge.
   The physical network must have been defined in the network_vlan_ranges configuration variable on the OpenStack Networking server.

   # openstack-config --set /etc/neutron/plugin.ini \
      OVS bridge_mappings MAPPINGS

   Replace MAPPINGS with the physical network to bridge mappings.
7. Use the service command to start the neutron-openvswitch-agent service.

   # service neutron-openvswitch-agent start

8. Use the chkconfig command to ensure that the neutron-openvswitch-agent service is started automatically in the future.

   # chkconfig neutron-openvswitch-agent on

9. Use the chkconfig command to ensure that the neutron-ovs-cleanup service is started automatically on boot. When started at boot time this service ensures that the OpenStack Networking agents maintain full control over the creation and management of tap devices.

   # chkconfig neutron-ovs-cleanup on

Procedure 7.17. Configuring the Linux Bridge plug-in agent

1. Set the value of the physical_interface_mappings configuration key. This configuration key must contain a list of physical networks and the VLAN ranges associated with them that are available for allocation to tenant networks.
   The format for each entry in the comma separated list is:

   PHYSNET:VLAN_START:VLAN_END

   Where PHYSNET is replaced with the name of a physical network, VLAN_START is replaced by an identifier indicating the start of the VLAN range, and VLAN_END is replaced by an identifier indicating the end of the VLAN range.
   The physical networks must have been defined in the network_vlan_ranges configuration variable on the OpenStack Networking server.

   # openstack-config --set /etc/neutron/plugin.ini \
      LINUX_BRIDGE physical_interface_mappings MAPPINGS

   Replace MAPPINGS with the physical network to VLAN range mappings.
2. Use the service command to start the neutron-linuxbridge-agent service.

   # service neutron-linuxbridge-agent start

3. Use the chkconfig command to ensure that the neutron-linuxbridge-agent service is started automatically in the future.

   # chkconfig neutron-linuxbridge-agent on