F5 Agent for OpenStack Neutron
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 clouddocs.f5.com.
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 --
debug_bundler.py -- to package information about your environment for debugging purposes.
When the you install
debug_bundler.py script installs itself in
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/debug_bundler.py /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/debug_bundler.py --log-dir=/var/log/mylogs --config-dir /etc/myconfigs/ ~/
If you find any issues with the debug_bundler, please file an issue.
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.
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.
We use the
hacking module for our style checks.
$ pip install tox $ tox -e style
tox to run our
pytest unit tests.
To run the unit tests, use the
$ pip install tox $ tox -e unit
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.
Copy and edit the symbols.json.example with the correct values for your BIG-IP device.
tox -e functestwith the
--symbolsflag pointing to your updates symbols.json file.
For example, the command below calls the symbols file and runs the
neutronless/disconnected_servicefunctional test cases. The
toxtarget changes to the
[test/functional](test/functional)directory before the tests run.
$ tox -e functest -- \ --symbols ~/path/to/symbols/symbols.json \ neutronless/disconnected_service
Copyright (c) 2015-2018, F5 Networks, Inc.
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 Openstack_CLA@f5.com before their code submission can be added to this project.