Cloud Docs Home > F5 OpenStack LBaaSv2 Index

Attention

The F5 OpenStack Integrations documentation is moving to clouddocs.f5.com. Thank you for your patience during construction.

Manage Multi-Tenant BIG-IP Devices with F5 LBaaSv2

Overview

BIG-IP® devices allow users to create and customize partitions for which specific features that meet a tenant’s needs can be enabled. This type of configuration, called multi-tenancy, allows a greater degree of flexibility in allocating network resources to multiple individual projects. [1]

Multi-tenant BIG-IP and F5 LBaaS

Multi-tenant BIG-IP and F5 LBaaS

Prerequisites

Caveats

When using BIG-IP Virtual Edition (VE) with the Linux bridge or Open vSwitch Neutron core plugins, F5 LBaaS can be deployed in two ways:

  1. Global Routed Mode: BIG-IP VE is connected only to provider networks; all pool member L3 addresses must be routable using cloud infrastructure routers.
  2. L2 Segmentation Modes using GRE or VxLAN tunnels: BIG-IP VE has a data connection to a provider network which can route IP packets to the local_ip VTEP addresses of the compute and network nodes through a cloud infrastructure router.

Configuration

  1. Edit the Agent Configuration File:
$ sudo vi /etc/neutron/services/f5/f5-openstack-agent.ini
  1. Configure the L2 Segmentation Mode settings as appropriate for your environment.

Important

You must configure these settings correctly to ensure your tenant networks connect to the right interfaces on the BIG-IP(s) and that traffic is allowed to flow through the corresponding ports.

Footnotes

[1]In OpenStack, the terms ‘tenant’ and ‘project’ are used interchangeably.