Chapter 8. Load balancing network traffic at the edge

Procedure

1. Source your credentials file.

   Example

   $ source ~/centralrc

2. Create a file, octavia-dcn-parameters.yaml, and using the syntax shown below, add the Load-balancing service AZs and their management networks for which you want the Ansible playbook to create the required networking resources.

   The value, octavia_controller_AZ_name, is the name of the AZ in which all of the Load-balancer services run:

   octavia_controller_availability_zone: <octavia_controller_AZ_name>
   octavia_availability_zones:
     <octavia_controller_AZ_name>: # no cidr needed, it uses the already existing subnet
     <octavia_AZ_n>:
       lb_mgmt_subnet_cidr: <CIDR_address_n>
     <octavia_AZ_n2>:
       lb_mgmt_subnet_cidr: <CIDR_address_n2>

   Important

   The names of the Load-balancing service AZs that you specify must match the names of the pre-existing Compute service AZs. You can obtain the names of the Compute service AZs by running openstack availability zone list --compute.

   The Ansible playbook creates a network, subnet, and router for each AZ, and names them using the AZ names that you specify in octavia-dcn-parameters.yaml following this convention: lb-mgmt-<AZ_name>-net, lb-mgmt-<AZ_name>-subnet, and lb-mgmt-<AZ_name>-router, respectively. The exception is for the network resources for octavia_controller_AZ_name: the playbook uses the existing load-balancing management network and subnet, lb-mgmt-net and lb-mgmt-subnet, respectively, and creates an associated router that it names, lb-mgmt-router.

   In this example, 3 AZs are specified: az-central, az-dcn1, and az-dcn2. The az-central AZ uses the existing load-balancing management network, lb-mgmt-net. The other two AZs use 172.47.0.0/16 and 172.48.0.0/16, respectively:

   Example

   octavia_controller_availability_zone: az-central
   octavia_availability_zones:
     az-central: # no cidr needed; it uses the existing subnet
     az-dcn1:
       lb_mgmt_subnet_cidr: 172.47.0.0/16
     az-dcn2:
       lb_mgmt_subnet_cidr: 172.48.0.0/16

3. Run the Ansible playbook, octavia-dcn-deployment.yaml, and include the AZ definitions that you created in octavia-dcn-parameters.yaml:

   Example

   $ ansible-playbook -i overcloud-deploy/central/config-download/\
   central/tripleo-ansible-inventory.yaml \
   /usr/share/ansible/tripleo-playbooks/octavia-dcn-deployment.yaml \
   -e @octavia-dcn-parameters.yaml -e stack=central -v

Verification

1. Confirm that the required lb-mgmt-* subnets are present.

   $ openstack subnet list -c Name -c Subnet

   Sample output

   +-------------------------+------------------+
   | Name                    | Subnet           |
   +-------------------------+------------------+
   | lb-mgmt-az-dcn2-subnet  | 172.48.0.0/16    |
   | segment5                | 10.0.20.0/24     |
   | segment3                | 10.101.30.0/24   |
   | segment2                | 10.101.20.0/24   |
   | lb-mgmt-az-dcn1-subnet  | 172.47.0.0/16    |
   | heat_tempestconf_subnet | 192.168.199.0/24 |
   | segment4                | 10.0.10.0/24     |
   | lb-mgmt-subnet          | 172.24.0.0/16    |
   | segment1                | 10.101.10.0/24   |
   | lb-mgmt-backbone-subnet | 172.49.0.0/16    |
   | segment6                | 10.0.30.0/24     |
   +-------------------------+------------------+

2. Confirm that the required virtual routers are present.

   $ openstack router list -c Name -c Status

   Sample output

   +------------------------+--------+
   | Name                   | Status |
   +------------------------+--------+
   | lb-mgmt-az-dcn2-router | ACTIVE |
   | lb-mgmt-az-dcn1-router | ACTIVE |
   | lb-mgmt-router         | ACTIVE |
   +------------------------+--------+

Procedure

1. Source your credentials file.

   Example

   $ source ~/centralrc

2. Gather the names of the Compute service AZs that you will use to name your Load-balancing service AZs.

   Important

   The names of the Load-balancing service AZ that you create must match the names of your Compute service AZs.

   $ openstack availability zone list --compute

   Sample output

   +------------+-------------+
   | Zone Name  | Zone Status |
   +------------+-------------+
   | az-central | available   |
   | az-dcn1    | available   |
   | az-dcn2    | available   |
   | internal   | available   |
   +------------+-------------+

3. Gather the IDs for the management networks that you will use to create your Load-balancing service AZs:

   $ openstack network list -c Name -c ID

   Sample output

   +--------------------------------------+--------------------------+
   | ID                                   | Name                     |
   +--------------------------------------+--------------------------+
   | 10458d6b-e7c9-436f-92d9-711677c9d9fd | lb-mgmt-az-dcn2-net      |
   | 662a94f5-51eb-4a4c-86c4-52dcbf471ef9 | lb-mgmt-net              |
   | 6b97ef58-2a25-4ea5-931f-b7c07cd09474 | lb-mgmt-backbone-net     |
   | 99f4215b-fad8-432d-8444-1f894154dc30 | heat_tempestconf_network |
   | a2884aaf-846c-4936-9982-3083f6a71d9b | lb-mgmt-az-dcn1-net      |
   | d7f7de6c-0e84-49e2-9042-697fa85d2532 | public                   |
   | e887a9f9-15f7-4854-a797-033cedbfe5f3 | public2                  |
   +--------------------------------------+--------------------------+

4. Create an AZ profile. Repeat this step to create an AZ profile for each Load-balancing service AZ that you want to create:

   $ openstack loadbalancer availabilityzoneprofile create \
   --name <AZ_profile_name> --provider amphora --availability-zone-data '{"compute_zone": "<compute_AZ_name>","management_network": "<lb_mgmt_AZ_net_UUID>"}'

   Example - create profile for az-central

   In this example, an AZ profile (az_profile_central) is created that uses the management network (lb-mgmt-net) on a Compute node that runs in the Compute AZ (az-central):

   $ openstack loadbalancer availabilityzoneprofile create \
   --name az_profile_central --provider amphora --availability-zone-data \
   '{"compute_zone": "az-central","management_network": \
   "662a94f5-51eb-4a4c-86c4-52dcbf471ef9"}'

5. Repeat step 4 to create an AZ profile for each Load-balancing service AZ that you want to create.

   Example - create profile for az-dcn1

   In this example, an AZ profile (az-profile-dcn1) is created that uses the management network (lb-mgmt-az-dcn1-net) on a Compute node that runs in the Compute AZ (az-dcn1):

   $ openstack loadbalancer availabilityzoneprofile create \
   --name az-profile-dcn1 --provider amphora --availability-zone-data \
   '{"compute-zone": "az-dcn1","management-network": \
   "a2884aaf-846c-4936-9982-3083f6a71d9b"}'

   Example - create profile for az-dcn2

   In this example, an AZ profile (az-profile-dcn2) is created that uses the management network (lb-mgmt-az-dcn2-net) on a Compute node that runs in the Compute AZ (az-dcn2):

   $ openstack loadbalancer availabilityzoneprofile create \
   --name az-profile-dcn2 --provider amphora --availability-zone-data \
   '{"compute-zone": "az-dcn2","management-network": \
   "10458d6b-e7c9-436f-92d9-711677c9d9fd"}'

6. Using the AZ profile, create a Load-balancing service AZ. Repeat this step for any additional AZs, using the appropriate profile for each AZ.

   Example - create AZ: az-central

   In this example, a Load-balancing service AZ (az-central) is created by using the AZ profile (az-profile-central):

   $ openstack loadbalancer availabilityzone create --name az-central \
   --availabilityzoneprofile az-profile-central \
   --description "AZ for Headquarters" --enable

   Example - create AZ: az-dcn1

   In this example, a Load-balancing service AZ (az-dcn1) is created by using the AZ profile (az-profile-az-dcn1):

   $ openstack loadbalancer availabilityzone create --name az-dcn1 \
   --availabilityzoneprofile az-profile-az-dcn1 \
   --description "AZ for South Region" --enable

   Example - create AZ: az-dcn2

   In this example, a Load-balancing service AZ (az-dcn2) is created by using the AZ profile (az-profile-az-dcn2):

   $ openstack loadbalancer availabilityzone create --name az-dcn2 \
   --availabilityzoneprofile az-profile-az-dcn2 \
   --description "AZ for North Region" --enable

Procedure

1. Source your credentials file.

   Example

   $ source ~/centralrc

2. To create a load balancer for a DCN environment, use the loadbalancer create command with the --availability-zone option and specify the appropriate AZ.

   Example

   For example, to create a non-terminated HTTPS load balancer (lb1) on a public subnet (public_subnet) on availability zone (az-central), you would enter the following command:

   $ openstack loadbalancer create --name lb1 --vip-subnet-id \
   public_subnet --availability-zone az-central

3. Continue to create your load balancer by adding a listener, pool, health monitor, and load balancer members.

   For more information, see the Configuring load balancing as a service guide.