The F5 Agent for OpenStack Neutron allows you to deploy BIG-IP services in an OpenStack environment.
Latest commit 89ea4af Dec 12, 2018
Type Name Latest commit message Commit time
Failed to load latest commit information.
.github additional pulled changes for updated files in F5Network/mitaka Aug 16, 2017
bin Adding 2018 to all copyright notices Mar 27, 2018
docs fix Makefile syntax error Oct 19, 2018
etc Changing default logging option in agent INI Apr 4, 2018
f5-openstack-agent-dist enable_pkcs7_certificate Sep 4, 2018
f5_openstack_agent Merge pull request #1376 from Niklaus-xie/esd-to-master-new-2 Dec 12, 2018
lib/systemd/system Agent should run as neutron user instead of root Aug 8, 2016
test not the original url anymore Oct 8, 2018
.coveragerc Add l7 policy unit testing Nov 27, 2017
.git-commit-template.txt - updated README Jan 14, 2016
.gitignore Add ignores for Eclipse IDE Nov 23, 2017
.travis.yml Issues: Mar 28, 2018 Adding 2018 to all copyright notices Mar 27, 2018
Gemfile Fixes: Add configuration files for Travis CI Nov 4, 2015 Add ESD demo configuration to the MANIFEST for packaging. Nov 23, 2017
Makefile Add L2 population docs Jan 12, 2018
README.rst Adding 2018 to all copyright notices Mar 27, 2018 additional pulled changes for updated files in F5Network/mitaka Aug 16, 2017
VERSION Configure Travis-CI Feb 29, 2016
deb_setup_requirements.txt enable_pkcs7_certificate Sep 4, 2018 Add Apache License 2.0 Oct 13, 2015 additional changes from F5Network/mitaka pre merge Aug 16, 2017
requirements.functest.txt Remove references to internal F5 sites. Mar 14, 2018 complete refactor of test_esd Nov 8, 2017
requirements.unittest.txt enable_pkcs7_certificate Sep 4, 2018
rpm_setup_requirements.txt enable_pkcs7_certificate Sep 4, 2018 Update add/delete fdb entries with f5-sdk support for FDB records. Apr 3, 2018
tox.ini Issues: Mar 8, 2018


F5 Agent for OpenStack Neutron

Build Status Slack Coveralls



The F5 Agent for OpenStack Neutron is an OpenStack Neutron plugin agent. It works in conjunction with the F5 driver for OpenStack LBaaSv2 to manage F5 BIG-IP Local Traffic Manager (LTM) services via the OpenStack Neutron API.


Documentation is published on


The F5 Agent for OpenStack Neutron is compatible with OpenStack releases from Liberty forward.

See the F5 OpenStack Releases and Support Matrix for more information.

Installing the F5 Agent

Please see the product documentation.

Using the Built-in Debugger

Use the built-in debugger -- -- to package information about your environment for debugging purposes.

When the you install f5-openstack-agent, the script installs itself in /usr/bin/f5/. When you run the debugger, it searches for log and config files and dumps a complete listing of the pip lists output. The debugger bundles everything it finds into a tarfile that you can provide to F5's support representatives to assist them in identifying the cause of your issue.


The files added to the debug bundle may contain VERY SENSITIVE INFORMATION such as encryption keys, passwords, and usernames. Do not upload this bundle, or any information within, to a public forum unless you have thoroughly scrubbed sensitive information. When in doubt, don't upload it at all.

Basic usage with the default command-line arguments

The command below creates a .tar file in the specified directory (in this example, /home/myuser/debug_bundle_output/) containing all logs and configuration files the script found. The script offers a best-effort search of the specified directories. If it cannot find the log files it is looking for in those directories, it prints an error message and continues to run.

$ python /usr/bin/f5/ /home/myuser/debug_bundle_output/

Override log/config file locations

The default log location is /var/log/neutron. The default configuration file location is /etc/neutron.

To override the log and/or config file locations, use the command-line arguments shown below:

$ python /usr/bin/f5/ --log-dir=/var/log/mylogs --config-dir /etc/myconfigs/ ~/


If you find any issues with the debug_bundler, please file an issue.

For Developers

Filing Issues

If you find an issue, we would love to hear about it. Please file an issue in this repository. Use the issue template to tell us as much as you can about what you found, how you found it, your environment, etc. Admins will triage your issue and assign it for a fix based on the priority level assigned. We also welcome you to file issues for feature requests.


See Contributing.


Before you open a pull request, your code must have passing pytest unit tests. In addition, you should include a set of functional tests written to use an actual BIG-IP device for testing. Information on how to run our test set is included below.

Style Checks

We use the hacking module for our style checks.

$ pip install tox
$ tox -e style

Unit Tests

We use tox to run our pytest unit tests.

To run the unit tests, use the tox unit environment.

$ pip install tox
$ tox -e unit

Functional Tests

You can run functional tests without a full OpenStack deployment. They do require access to a BIG-IP device or BIG-IP Virtual Edition (VE) instance.

  1. Copy and edit the symbols.json.example with the correct values for your BIG-IP device.

  2. Run tox -e functest with the --symbols flag pointing to your updates symbols.json file.

    For example, the command below calls the symbols file and runs the neutronless/disconnected_service functional test cases. The tox target changes to the [test/functional](test/functional) directory before the tests run.

$ tox -e functest -- \
  --symbols ~/path/to/symbols/symbols.json \


Copyright (c) 2015-2018, F5 Networks, Inc.


See Support.


Apache V2.0

Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at

Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.

Contributor License Agreement

Individuals or business entities who contribute to this project must complete and submit the F5 Contributor License Agreement to before their code submission can be added to this project.