Home OpenStack-Ansible Installation Guide

Configuring the Networking service (neutron) (optional)

The OpenStack Networking service (neutron) includes the following services:

Firewall as a Service (FWaaS)

Provides a software-based firewall that filters traffic from the router.

Load Balancer as a Service (LBaaS)

Provides load balancers that direct traffic to OpenStack instances or other servers outside the OpenStack deployment.

VPN as a Service (VPNaaS)

Provides a method for extending a private network across a public network.

Firewall service (optional)

The following procedure describes how to modify the /etc/openstack_deploy/user_variables.yml file to enable FWaaS.

1. Override the default list of neutron plugins to include firewall:

   neutron_plugin_base:
     - firewall
     - ...
   

2. neutron_plugin_base is as follows:

   neutron_plugin_base:
      - router
      - firewall
      - neutron_lbaas.services.loadbalancer.plugin.LoadBalancerPluginv2
      - vpnaas
      - metering
      - qos
   

3. Execute the neutron install playbook in order to update the configuration:

   # cd /opt/openstack-ansible/playbooks
   # openstack-ansible os-neutron-install.yml
   

4. Execute the horizon install playbook to show the FWaaS panels:

   # cd /opt/openstack-ansible/playbooks
   # openstack-ansible os-horizon-install.yml
   

The FWaaS default configuration options may be changed through the conf override mechanism using the neutron_neutron_conf_overrides dict.

Load balancing service (optional)

OpenStack-Ansible currently provides the OpenStack neutron LBaaS service using HAProxy as the load balancer. LBaaS has two implementations available: v1 and v2.

Both implementations use agents that manage HAProxy daemons. However, LBaaS v1 has a limitation of one port per load balancer. LBaaS v2 allows for multiple ports (called listeners) per load balancer.

Note

Horizon panels for LBaaS v2 are not yet available.

Deploying LBaaS v1

Note

We do not recommend LBaaS v1 for new deployments as it is deprecated as of Liberty.

1. Add the LBaaS v1 plugin to the neutron_plugin_base variable in /etc/openstack_deploy/user_variables.yml:

   neutron_plugin_base:
     - router
     - metering
     - lbaas
   

   Ensure that neutron_plugin_base includes all of the plugins that you want to deploy with neutron in addition to the LBaaS plugin.

2. Run the neutron and horizon playbooks to deploy the LBaaS v1 agent and enable the LBaaS panels in horizon:

   # cd /opt/openstack-ansible/playbooks
   # openstack-ansible os-neutron-install.yml
   # openstack-ansible os-horizon-install.yml
   

Deploying LBaaS v2

1. Add the LBaaS v2 plugin to the neutron_plugin_base variable in /etc/openstack_deploy/user_variables.yml:

   neutron_plugin_base:
     - router
     - metering
     - neutron_lbaas.services.loadbalancer.plugin.LoadBalancerPluginv2
   

   Ensure that neutron_plugin_base includes all of the plugins that you want to deploy with neutron in addition to the LBaaS plugin.

2. Run the neutron playbook to deploy and enable the LBaaS v2 agent:

   # cd /opt/openstack-ansible/playbooks
   # openstack-ansible os-neutron-install.yml
   

3. Set horizon_enable_neutron_lbaas to True in /etc/openstack_deploy/user_variables.yml and run the horizon playbook to enable the LBaaS v2 panels in horizon:

   # cd /opt/openstack-ansible/playbooks
   # openstack-ansible os-horizon-install.yml
   

Special notes about LBaaS

The LBaaS default configuration options are changed through the conf override mechanism using the neutron_lbaas_agent_ini_overrides dict.

LBaaS v1 and v2 agents are unable to run at the same time. If you switch LBaaS v1 to v2, the v2 agent is the only agent running. The LBaaS v1 agent stops along with any load balancers provisioned under the v1 agent. The same is true if you choose to move from LBaaS v2 to v1.

Load balancers are not migrated between LBaaS v1 and v2 automatically. Each implementation has different code paths and database tables. You need to manually delete load balancers, pools, and members before switching LBaaS versions. Recreate these objects afterwards.

Virtual private network service (optional)

The following procedure describes how to modify the /etc/openstack_deploy/user_variables.yml file to enable VPNaaS.

1. Override the default list of neutron plugins to include vpnaas:

   neutron_plugin_base:
     - router
     - metering
   

2. neutron_plugin_base is as follows:

   neutron_plugin_base:
      - router
      - metering
      - vpnaas
   

3. Override the default list of specific kernel modules in order to include the necessary modules to run ipsec:

   openstack_host_specific_kernel_modules:
      - { name: "ebtables", pattern: "CONFIG_BRIDGE_NF_EBTABLES=", group: "network_hosts" }
      - { name: "af_key", pattern: "CONFIG_NET_KEY=", group: "network_hosts" }
      - { name: "ah4", pattern: "CONFIG_INET_AH=", group: "network_hosts" }
      - { name: "ipcomp", pattern: "CONFIG_INET_IPCOMP=", group: "network_hosts" }
   

4. Execute the openstack hosts setup in order to load the kernel modules at boot and runtime in the network hosts

   # openstack-ansible openstack-hosts-setup.yml --limit network_hosts\
   --tags "openstack-hosts-setup,openstack-host-specific-kernel-modules"
   

5. Execute the neutron install playbook in order to update the configuration:

   # cd /opt/openstack-ansible/playbooks
   # openstack-ansible os-neutron-install.yml
   

6. Execute the horizon install playbook to show the VPNaaS panels:

   # cd /opt/openstack-ansible/playbooks
   # openstack-ansible os-horizon-install.yml
   

The VPNaaS default configuration options are changed through the conf override mechanism using the neutron_neutron_conf_overrides dict.

---

• Documentation Home
• Installation Guide
• Upgrade Guide
• Developer Documentation