Red Hat SummitDieser Inhalt ist in der von Ihnen ausgewählten Sprache nicht verfügbar.
Chapter 2. Configuring and deploying the overcloud for autoscaling
You must configure the templates for the services on your overcloud that enable autoscaling.
Procedure
- Create environment templates and a resource registry for autoscaling services before you deploy the overcloud for autoscaling. For more information, see Section 2.1, “Configuring the overcloud for autoscaling”
- Deploy the overcloud. For more information, see Section 2.2, “Deploying the overcloud for autoscaling”
2.1. Configuring the overcloud for autoscaling
Create the environment templates and resource registry that you need to deploy the services that provide autoscaling.
Procedure
-
Log in to the undercloud host as the
stackuser. Create a directory for the autoscaling configuration files:
mkdir -p $HOME/templates/autoscaling/
$ mkdir -p $HOME/templates/autoscaling/Copy to Clipboard Copied! Toggle word wrap Toggle overflow Create the resource registry file for the definitions that the services require for autoscaling:
Copy to Clipboard Copied! Toggle word wrap Toggle overflow Create an environment template to configure the services required for autoscaling:
Copy to Clipboard Copied! Toggle word wrap Toggle overflow If you use Red Hat Ceph Storage as the data storage back end for the time-series database service, add the following parameters to your
parameters-autoscaling.yamlfile:parameter_defaults: GnocchiRbdPoolName: 'metrics' GnocchiBackend: 'rbd'
parameter_defaults: GnocchiRbdPoolName: 'metrics' GnocchiBackend: 'rbd'Copy to Clipboard Copied! Toggle word wrap Toggle overflow You must create the defined archive policy
genericbefore you can store metrics. You define this archive policy after the deployment. For more information, see Section 3.1, “Creating the generic archive policy for autoscaling”.-
Set the
polling_intervalparameter, for example, 60 seconds. The value of thepolling_intervalparameter must match the gnocchi granularity value that you defined when you created the archive policy. For more information, see Section 3.1, “Creating the generic archive policy for autoscaling”. - Deploy the overcloud. For more information, see Section 2.2, “Deploying the overcloud for autoscaling”
2.2. Deploying the overcloud for autoscaling
You can deploy the overcloud for autoscaling by using director or by using a standalone environment.
Prerequisites
- You have created the environment templates for deploying the services that provide autoscaling capabilities. For more information, see Section 2.1, “Configuring the overcloud for autoscaling”.
Procedure
2.2.1. Deploying the overcloud for autoscaling by using director
Use director to deploy the overcloud. If you are using a standalone environment, see Section 2.2.2, “Deploying the overcloud for autoscaling in a standalone environment”.
Prerequisites
- A deployed undercloud. For more information, see Installing director on the undercloud.
Procedure
-
Log in to the undercloud as the
stackuser. Source the
stackrcundercloud credentials file:source ~/stackrc
[stack@director ~]$ source ~/stackrcCopy to Clipboard Copied! Toggle word wrap Toggle overflow Add the autoscaling environment files to the stack with your other environment files and deploy the overcloud:
openstack overcloud deploy --templates \ -e [your environment files] \ -e $HOME/templates/autoscaling/parameters-autoscaling.yaml \ -e $HOME/templates/autoscaling/resources-autoscaling.yaml
(undercloud)$ openstack overcloud deploy --templates \ -e [your environment files] \ -e $HOME/templates/autoscaling/parameters-autoscaling.yaml \ -e $HOME/templates/autoscaling/resources-autoscaling.yamlCopy to Clipboard Copied! Toggle word wrap Toggle overflow
2.2.2. Deploying the overcloud for autoscaling in a standalone environment
To test the environment files in a pre-production environment, you can deploy the overcloud with the services required for autoscaling by using a standalone deployment.
This procedure uses example values and commands that you must change to suit a production environment.
If you want to use director to deploy the overcloud for autoscaling, see Section 2.2.1, “Deploying the overcloud for autoscaling by using director”.
Prerequisites
- An all-in-one RHOSP environment has been staged with the python3-tripleoclient. For more information, see Installing the all-in-one Red Hat OpenStack Platform environment.
- An all-in-one RHOSP environment has been staged with the base configuration. For more information, see Configuring the all-in-one Red Hat OpenStack Platform environment.
Procedure
Change to the user that manages your overcloud deployments, for example, the
stackuser:su - stack
[root@standalone ~]# su - stackCopy to Clipboard Copied! Toggle word wrap Toggle overflow Replace or set the environment variables
$IP,$NETMASKand$VIPfor the overcloud deployment:export IP=192.168.25.2 export VIP=192.168.25.3 export NETMASK=24
$ export IP=192.168.25.2 $ export VIP=192.168.25.3 $ export NETMASK=24Copy to Clipboard Copied! Toggle word wrap Toggle overflow Deploy the overcloud to test and verify the resource and parameter files:
Copy to Clipboard Copied! Toggle word wrap Toggle overflow Export the
OS_CLOUDenvironment variable:export OS_CLOUD=standalone
$ export OS_CLOUD=standaloneCopy to Clipboard Copied! Toggle word wrap Toggle overflow
Additional resources
2.3. Verifying the overcloud deployment for autoscaling
Verify that the autoscaling services are deployed and enabled. Verification output is from a standalone environment, but director-based environments provide similar output.
Prerequisites
- You have deployed the autoscaling services in an existing overcloud using standalone or director. For more information, see Section 2.2, “Deploying the overcloud for autoscaling”.
Procedure
-
Log in to your environment as the
stackuser. For standalone environments set the
OS_CLOUDenvironment variable:export OS_CLOUD=standalone
[stack@standalone ~]$ export OS_CLOUD=standaloneCopy to Clipboard Copied! Toggle word wrap Toggle overflow For director environments, source the
stackrcundercloud credentials file:source ~/stackrc
[stack@undercloud ~]$ source ~/stackrcCopy to Clipboard Copied! Toggle word wrap Toggle overflow
Verification
Verify that the deployment was successful and ensure that the service API endpoints for autoscaling are available:
Copy to Clipboard Copied! Toggle word wrap Toggle overflow Copy to Clipboard Copied! Toggle word wrap Toggle overflow Copy to Clipboard Copied! Toggle word wrap Toggle overflow Verify that the services are running on the overcloud:
Copy to Clipboard Copied! Toggle word wrap Toggle overflow Verify that the time-series database service is available:
Copy to Clipboard Copied! Toggle word wrap Toggle overflow
'%20d='M201.5%20305.5c-13.8%200-24.9-11.1-24.9-24.6%200-13.8%2011.1-24.9%2024.9-24.9%2013.6%200%2024.6%2011.1%2024.6%2024.9%200%2013.6-11.1%2024.6-24.6%2024.6zM504%20256c0%20137-111%20248-248%20248S8%20393%208%20256%20119%208%20256%208s248%20111%20248%20248zm-132.3-41.2c-9.4%200-17.7%203.9-23.8%2010-22.4-15.5-52.6-25.5-86.1-26.6l17.4-78.3%2055.4%2012.5c0%2013.6%2011.1%2024.6%2024.6%2024.6%2013.8%200%2024.9-11.3%2024.9-24.9s-11.1-24.9-24.9-24.9c-9.7%200-18%205.8-22.1%2013.8l-61.2-13.6c-3-.8-6.1%201.4-6.9%204.4l-19.1%2086.4c-33.2%201.4-63.1%2011.3-85.5%2026.8-6.1-6.4-14.7-10.2-24.1-10.2-34.9%200-46.3%2046.9-14.4%2062.8-1.1%205-1.7%2010.2-1.7%2015.5%200%2052.6%2059.2%2095.2%20132%2095.2%2073.1%200%20132.3-42.6%20132.3-95.2%200-5.3-.6-10.8-1.9-15.8%2031.3-16%2019.8-62.5-14.9-62.5zM302.8%20331c-18.2%2018.2-76.1%2017.9-93.6%200-2.2-2.2-6.1-2.2-8.3%200-2.5%202.5-2.5%206.4%200%208.6%2022.8%2022.8%2087.3%2022.8%20110.2%200%202.5-2.2%202.5-6.1%200-8.6-2.2-2.2-6.1-2.2-8.3%200zm7.7-75c-13.6%200-24.6%2011.1-24.6%2024.9%200%2013.6%2011.1%2024.6%2024.6%2024.6%2013.8%200%2024.9-11.1%2024.9-24.6%200-13.8-11-24.9-24.9-24.9z'/%3e%3c/svg%3e){kind=small}