# Deploy a basic load balancer¶

The series of code samples provided here demonstrate how to configure a basic loadbalancer via the OpenStack Neutron CLI with the F5 Integration for OpenStack Neutron LBaaS. The OpenStack CLI documentation has a full list of all neutron lbaas commands.

Important

The LBaaSv2 CLI commands begin with lbaas-. Commands beginning with lb- are part of the deprecated OpenStack LBaaS v1 project.

Example: Project_9572afc14db14c8a806d8c8219446e7b

## Create a Neutron LBaaS load balancer¶

Tip

Neutron LBaaS load balancer == BIG-IP partition

The name assigned to the new BIG-IP partition follows the naming convention <environment-prefix>_<openstack-tenant-ID>. The default environment prefix is Project_. You can change the environment prefix in the F5 Agent configuration file.

Specify the name you want to assign to the load balancer and the existing OpenStack subnet you want to assign to it.



## Add a secure BIG-IP virtual server¶

Important

OpenStack uses the Transport Layer Security (TLS) protocol to secure network traffic. You must configure Barbican and Keystone before you can create a secure BIG-IP virtual server.

1. Set up Keystone and Barbican, if you haven’t already. [1]

2. Complete the Certificate Manager settings section of the F5 Agent configuration file.

3. Create a listener using the TERMINATED_HTTPS protocol; specify the location of the Barbican container where the certificate you want to use for authentication lives.

The F5 Agent will add this certificate to the BIG-IP device(s) and use it to create a new BIG-IP SSL profile.



## Create a health monitor¶

When creating a health monitor, specify the delay; monitor type; number of retries; timeout period; and the name of the pool you want to monitor.

\$ neutron lbaas-healthmonitor-create --delay 3 --type HTTP --max-retries 3 --timeout 3 --pool pool1


## What’s Next¶

Use the BIG-IP configuration utility to verify that all of your Neutron LBaaS objects appear on the BIG-IP device(s).

1. Log in to the BIG-IP configuration utility at the management IP address (e.g., https://1.2.3.4/tmui/login.jsp).