Important

End of Software Development for F5 OpenStack LBaaS version 1

F5 announces the End of Software Development (EoSD) for the F5 OpenStack LBaaS version 1 integration, effective October 1, 2016. This announcement is in compliance with the OpenStack community deprecation of the OpenStack Neutron LBaaS version 1 plugin. Customers are encouraged to move to OpenStack LBaaS version 2.

F5 will continue to repair defects and perform maintenance on the F5 OpenStack LBaaS version 1 integration until the Openstack Ocata release in April 2017.

For additional information, please refer to the F5 OpenStack Releases and Support Matrix.

Running Multiple F5 Agents on the Same Host

Warning

You should never run two agents for the same environment on the same host, as the environment_prefix setting in the agent config file allows Neutron to distinguish between agents. Multiple agent processes for different environments – meaning each agent is associated with a different iControl® endpoint – can run on the same host.

Follow the steps below to set up multiple F5® agents on the same host.

  1. Create a new environment.
$ python -m f5.oslbaasv1driver.utils.generate_env dsc4 dsc4
  1. Add a service provider driver entry in /etc/neutron/neutron_lbaas to activate the new environment.
[service_providers]
# Must be in form:
# service_provider=<service_type>:<name>:<driver>[:default]
# List of allowed service types includes LOADBALANCER
# Combination of <service type> and <name> must be unique; <driver> must also be unique
# This is multiline option
# service_provider=LOADBALANCER:name:lbaas_plugin_driver_path:default
service_provider=LOADBALANCER:DSC4:f5.oslbaasv1driver.drivers.plugin_driver_Dsc4.F5PluginDriverDsc4
service_provider=LOADBALANCER:F5:f5.oslbaasv1driver.drivers.plugin_driver.F5PluginDriver
#service_provider=LOADBALANCER:Haproxy:neutron_lbaas.services.loadbalancer.drivers.haproxy.plugin_driver.HaproxyOnHostPluginDriver:default
  1. Create a unique configuration file for each agent.
$ cd /etc/neutron
$ cp f5-oslbaasv1-agent.ini f5-oslbaasv1-agent-dsc4.ini
  1. Edit the new config file as needed.

Note

Each agent configuration file must have a unique iControl® endpoint.

  1. Create additional upstart, init.d, or systemd service definitions for additional agents, using the default service definitions as a guide.

Example: Create a new service definition on a Ubuntu server

$ cd /etc/init
$ cp f5-oslbaasv1-agent.conf f5-oslbaasv1-agent-dsc4.conf

\\ Edit the new agent start config file
$ exec start-stop-daemon --start --chuid neutron --exec /usr/bin/f5-oslbaasv1-agent --config-file=/etc/neutron/f5-oslbaasv1-agent-dsc4.ini --config-file=/etc/neutron/neutron.conf --log-file=/var/log/neutron/f5-oslbaasv1-agent-dsc4.log
  1. Start the new agent using the name of its unique upstart, init.d, or systemd service name.
$ sudo service f5-oslbaasv1-agent-dsc4 start
  1. Restart neutron-server.
$ sudo service neutron-server restart