Cloud Docs Home > F5 OpenStack LBaaSv2 Index
F5 OpenStack Neutron LBaaSv2¶
Contents¶
- Quick Start Guide
- User Guide
- Basic Environment Requirements
- F5 LBaaSv2 to BIG-IP Mapping
- Supported Features
- Device Driver Settings / iControl Driver Settings
- L2 Adjacent Mode
- Global Routed Mode
- High Availability
- Device Clusters
- Multi-Tenancy
- Certificate Manager / SSL Offloading
- Hierarchical Port Binding
- Agent Redundancy and Scale Out
- Differentiated Service Environments
- F5 LBaaSv2 and vCMP
- F5 LBaaSv2 L7 Content Switching
- Enhance L7 Policy Capabilites with Enhanced Service Definitions
- Unsupported Features
- Neutron
- F5 OpenStack
- Sample Configuration Files
- Coding Example
- Upgrading
- Glossary
- Troubleshooting
- Solution Test Plan
Release¶
Release 9.3.1.b1 is compatible with OpenStack Mitaka. For more information, please see the F5® OpenStack Releases, Versioning, and Support Matrix.
Overview¶
The F5® OpenStack LBaaSv2 service provider driver and agent (also called, simply, ‘F5 LBaaSv2’) make it possible to provision F5 BIG-IP® Local Traffic Manager (LTM®) services in an OpenStack cloud.
How the plugin works¶
The F5 LBaaSv2 plugin consists of an agent and a service provider driver (also just called ‘driver’, for short). The driver listens to the Neutron RPC messaging queue. When you make a call to the LBaaSv2 API – for example, neutron lbaas-loadbalancer-create – the F5 LBaaSv2 service provider driver picks it up and directs it to the agent.
The F5 agent manages services on your BIG-IP. When it first receives a task from the F5 driver, it starts and communicates with the BIG-IP(s) identified in the Agent Configuration File. Then, it registers its own named queue. The F5 driver assigns all lbaas tasks in the Neutron messaging queue to the agent’s queue. The F5 agent makes callbacks to the F5 driver to query additional Neutron network, port, and subnet information; to allocate Neutron objects (for example, fixed IP addresses); and to report provisioning and pool status.
