Este conteúdo não está disponível no idioma selecionado.
Chapter 4. Installing and configuring the Load-balancing service
When you deploy the Red Hat OpenStack Platform (RHOSP) Load-balancing service (octavia) using RHOSP director, you can decide to make its VM instances (amphorae) highly available. You also use director when you want to make configuration changes to the Load-balancing service.
4.1. Deploying the Load-balancing service Copiar o linkLink copiado para a área de transferência!
You use Red Hat OpenStack Platform (RHOSP) director to deploy the Load-balancing service (octavia). Director uses Orchestration service (heat) templates that are a set of plans for your environment. The undercloud imports these plans and follows their instructions to create the Load-balancing service and your RHOSP environment.
Prerequisites
- Ensure that your environment has access to the octavia image.
Procedure
Run the deployment command and include the core heat templates, environment files, and the
octavia.yamlheat template.Example
openstack overcloud deploy --templates \ -e <your_environment_files> \ -e /usr/share/openstack-tripleo-heat-templates/environments/services/octavia.yaml
$ openstack overcloud deploy --templates \ -e <your_environment_files> \ -e /usr/share/openstack-tripleo-heat-templates/environments/services/octavia.yamlCopy to Clipboard Copied! Toggle word wrap Toggle overflow NoteDirector updates the amphorae to the latest amphora image during a stack update or upgrade.
4.2. Enabling active-standby topology for Load-balancing service instances Copiar o linkLink copiado para a área de transferência!
You can make Load-balancing service instances (amphorae) highly available when you implement an active-standby topology using Red Hat OpenStack Platform (RHOSP) director. Director uses Orchestration service (heat) templates that are a set of plans for your environment. The undercloud imports these plans and follows their instructions to create the Load-balancing service and your RHOSP environment.
Prerequisites
- Ensure that anti-affinity is enabled for the Compute service. This is the default.
A minimum of three Compute node hosts:
- Two Compute node hosts to place the amphorae on different hosts (Compute anti-affinity).
- A third host to successfully fail over an active-standby load balancer, when a problem arises.
Procedure
-
Log in to the undercloud host as the
stackuser. Source the undercloud credentials file:
source ~/stackrc
$ source ~/stackrcCopy to Clipboard Copied! Toggle word wrap Toggle overflow Create a custom YAML environment file.
Example
vi /home/stack/templates/my-octavia-environment.yaml
$ vi /home/stack/templates/my-octavia-environment.yamlCopy to Clipboard Copied! Toggle word wrap Toggle overflow In the custom environment file, add the following parameter:
parameter_defaults: OctaviaLoadBalancerTopology: "ACTIVE_STANDBY"parameter_defaults: OctaviaLoadBalancerTopology: "ACTIVE_STANDBY"Copy to Clipboard Copied! Toggle word wrap Toggle overflow Run the deployment command and include the core heat templates, environment files, and this new custom environment file.
ImportantThe order of the environment files is important as the parameters and resources defined in subsequent environment files take precedence.
Example
openstack overcloud deploy --templates \ -e <your_environment_files> \ -e /usr/share/openstack-tripleo-heat-templates/environments/services/octavia.yaml \ -e /home/stack/templates/my-octavia-environment.yaml
$ openstack overcloud deploy --templates \ -e <your_environment_files> \ -e /usr/share/openstack-tripleo-heat-templates/environments/services/octavia.yaml \ -e /home/stack/templates/my-octavia-environment.yamlCopy to Clipboard Copied! Toggle word wrap Toggle overflow
Verification
After the deployment is complete and you have created a load balancer, run the following commands:
source overcloudrc openstack loadbalancer amphora list
$ source overcloudrc $ openstack loadbalancer amphora listCopy to Clipboard Copied! Toggle word wrap Toggle overflow If your Load-balancing service instance highly available configuration is successful, you see output for two instances (amphorae), and no occurrence of
roleequalingSINGLE.
4.3. Changing Load-balancing service default settings Copiar o linkLink copiado para a área de transferência!
You make configuration changes to the Load-balancing service (octavia) using Red Hat OpenStack Platform (RHOSP) director. Director uses Orchestration service (heat) templates that are a set of plans for your environment. The undercloud imports these plans and follows their instructions to create the Load-balancing service and your RHOSP environment.
Prerequisites
- Determine which RHOSP Orchestration service (heat) parameters that director already uses to deploy the Load-balancing service by consulting the following file on the undercloud:
/usr/share/openstack-tripleo-heat-templates/deployment/octavia/octavia-deployment-config.j2.yaml
/usr/share/openstack-tripleo-heat-templates/deployment/octavia/octavia-deployment-config.j2.yaml
Decide which parameters that you want to modify.
Here are a few examples:
OctaviaControlNetworkThe name of the neutron network used for the load-balancing management network.
OctaviaControlSubnetCidrThe subnet for amphora control subnet in CIDR form.
You can use this parameter to specify the amphora control subnet as an IPv6 CIDR. Using an IPv6 CIDR in
OctaviaControlSubnetCidrrequires you to also set IPv6 addresses inOctaviaControlSubnetPoolStartandOctaviaControlSubnetPoolEnd.ImportantThis feature, using IPv6 CIDRs for the load-balancing management network, is available in this release as a Technology Preview, and therefore is not fully supported by Red Hat. It should only be used for testing, and should not be deployed in a production environment.
For more information about Technology Preview features, see Scope of Coverage Details.
ImportantAfter you have set CIDRs for the amphora control subnet, you cannot modify these values. This also means that you cannot upgrade from an IPv4 subnet to an IPv6 subnet.
OctaviaMgmtPortDevNameThe name of the octavia management network interface used for communication between octavia worker/health-manager with the amphora machine.
Procedure
-
Log in to the undercloud host as the
stackuser. Source the undercloud credentials file:
source ~/stackrc
$ source ~/stackrcCopy to Clipboard Copied! Toggle word wrap Toggle overflow Create a custom YAML environment file.
Example
vi /home/stack/templates/my-octavia-environment.yaml
$ vi /home/stack/templates/my-octavia-environment.yamlCopy to Clipboard Copied! Toggle word wrap Toggle overflow Your environment file must contain the keywords
parameter_defaults. Put your parameter value pairs after theparameter_defaultskeyword.Example
Copy to Clipboard Copied! Toggle word wrap Toggle overflow Run the deployment command and include the core heat templates, environment files, and this new custom environment file.
ImportantThe order of the environment files is important as the parameters and resources defined in subsequent environment files take precedence.
Example
openstack overcloud deploy --templates \ -e <your_environment_files> \ -e /usr/share/openstack-tripleo-heat-templates/environments/services/octavia.yaml \ -e /home/stack/templates/my-octavia-environment.yaml
$ openstack overcloud deploy --templates \ -e <your_environment_files> \ -e /usr/share/openstack-tripleo-heat-templates/environments/services/octavia.yaml \ -e /home/stack/templates/my-octavia-environment.yamlCopy to Clipboard Copied! Toggle word wrap Toggle overflow