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.

OpenStack and BIG-IP® Multi-tenancy

BIG-IP® Multi-tenancy

Fig. 11 BIG-IP® Multi-tenancy

To configure the F5® agent for multi-tenancy:

  1. Edit /etc/neutron/f5-oslbaasv1-agent.ini.

    ###############################################################################
    #  L3 Segmentation Mode Settings
    ###############################################################################
    #
    ...
    #
    f5_global_routed_mode = False
    #
    # Allow overlapping IP subnets across multiple tenants.
    # This creates route domains on big-ip in order to
    # separate the tenant networks.
    #
    # This setting is forced to False if
    # f5_global_routed_mode = True.
    #
    use_namespaces = True
    #
    # When use_namespaces is True there is normally only one route table
    # allocated per tenant. However, this limit can be increased by
    # changing the max_namespaces_per_tenant variable. This allows one
    # tenant to have overlapping IP subnets.
    ...
    #
    max_namespaces_per_tenant = 1
    #
    # Dictates the strict isolation of the routing
    # tables.  If you set this to True, then all
    # VIPs and Members must be in the same tenant
    # or less they can't communicate.
    #
    # This setting is only valid if use_namespaces = True.
    #
    f5_route_domain_strictness = False
    #
    ...