Red Hat Summit Red Hat SummitSuporteConsoleDesenvolvedoresComeçar um testeContato

Este conteúdo não está disponível no idioma selecionado.

Chapter 2. Configuring and deploying the overcloud for autoscaling

You must configure the templates for the services on your overcloud that enable autoscaling.

Procedure

  1. 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”
  2. Deploy the overcloud. For more information, see Section 2.2, “Deploying the overcloud for autoscaling”

2.1. Configuring the overcloud for autoscaling
Copiar o link

Create the environment templates and resource registry that you need to deploy the services that provide autoscaling.

Procedure

  1. Log in to the undercloud host with your overcloud administrator credentials, for example overcloudrc.

  2. Create a directory for the autoscaling configuration files: 

    $ mkdir -p $HOME/templates/autoscaling/

  3. Create the resource registry file for the definitions that the services require for autoscaling: 

    $ cat <<EOF > $HOME/templates/autoscaling/resources-autoscaling.yaml
resource_registry:
  OS::TripleO::Services::AodhApi: /usr/share/openstack-tripleo-heat-templates/deployment/aodh/aodh-api-container-puppet.yaml
  OS::TripleO::Services::AodhEvaluator: /usr/share/openstack-tripleo-heat-templates/deployment/aodh/aodh-evaluator-container-puppet.yaml
  OS::TripleO::Services::AodhListener: /usr/share/openstack-tripleo-heat-templates/deployment/aodh/aodh-listener-container-puppet.yaml
  OS::TripleO::Services::AodhNotifier: /usr/share/openstack-tripleo-heat-templates/deployment/aodh/aodh-notifier-container-puppet.yaml
  OS::TripleO::Services::CeilometerAgentCentral: /usr/share/openstack-tripleo-heat-templates/deployment/ceilometer/ceilometer-agent-central-container-puppet.yaml
  OS::TripleO::Services::CeilometerAgentNotification: /usr/share/openstack-tripleo-heat-templates/deployment/ceilometer/ceilometer-agent-notification-container-puppet.yaml
  OS::TripleO::Services::ComputeCeilometerAgent: /usr/share/openstack-tripleo-heat-templates/deployment/ceilometer/ceilometer-agent-compute-container-puppet.yaml
  OS::TripleO::Services::GnocchiApi: /usr/share/openstack-tripleo-heat-templates/deployment/gnocchi/gnocchi-api-container-puppet.yaml
  OS::TripleO::Services::GnocchiMetricd: /usr/share/openstack-tripleo-heat-templates/deployment/gnocchi/gnocchi-metricd-container-puppet.yaml
  OS::TripleO::Services::GnocchiStatsd: /usr/share/openstack-tripleo-heat-templates/deployment/gnocchi/gnocchi-statsd-container-puppet.yaml
  OS::TripleO::Services::HeatApi: /usr/share/openstack-tripleo-heat-templates/deployment/heat/heat-api-container-puppet.yaml
  OS::TripleO::Services::HeatEngine: /usr/share/openstack-tripleo-heat-templates/deployment/heat/heat-engine-container-puppet.yaml
  OS::TripleO::Services::Redis: /usr/share/openstack-tripleo-heat-templates/deployment/database/redis-pacemaker-puppet.yaml
EOF

  4. Create an environment template to configure the services required for autoscaling: 

    cat <<EOF > $HOME/templates/autoscaling/parameters-autoscaling.yaml
parameter_defaults:
  NotificationDriver: 'messagingv2'
  GnocchiDebug: false
  CeilometerEnableGnocchi: true
  ManagePipeline: true
  ManageEventPipeline: true

  EventPipelinePublishers:
    - gnocchi://?archive_policy=generic
  PipelinePublishers:
    - gnocchi://?archive_policy=generic

  ManagePolling: true
  ExtraConfig:
    ceilometer::agent::polling::polling_interval: 60
EOF

    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.yaml file: 

    parameter_defaults:
  GnocchiRbdPoolName: 'metrics'
  GnocchiBackend: 'rbd'

    You must create the defined archive policy generic before 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”.

  5. Set the polling_interval parameter, for example, 60 seconds. The value of the polling_interval parameter 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”.
  6. Deploy the overcloud. For more information, see Section 2.2, “Deploying the overcloud for autoscaling”

2.2. Deploying the overcloud for autoscaling
Copiar o link

You can deploy the overcloud for autoscaling by using director.

Prerequisites

Procedure

2.2.1. Deploying the overcloud for autoscaling by using director
Copiar o link

Use director to deploy the overcloud.

Prerequisites

Procedure

  1. Log in to the undercloud as the stack user.

  2. Source the stackrc undercloud credentials file: 

    [stack@director ~]$ source ~/stackrc

  3. Add the autoscaling environment files to the stack with your other environment files and deploy the overcloud: 

    (undercloud)$ openstack overcloud deploy --templates \
  -e [your environment files] \
  -e $HOME/templates/autoscaling/parameters-autoscaling.yaml \
  -e $HOME/templates/autoscaling/resources-autoscaling.yaml

2.3. Verifying the overcloud deployment for autoscaling
Copiar o link

Verify that the autoscaling services are deployed and enabled. The verification output examples might be different from your use case.

Prerequisites

Procedure

  1. Log in to your environment as the stack user.

  2. For director environments, source the overcloudrc overcloud credentials file: 

    $ source ~/overcloudrc

Verification

  1. Verify that the deployment was successful and ensure that the service API endpoints for autoscaling are available: 

    $ openstack endpoint list --service metric
+----------------------------------+-----------+--------------+--------------+---------+-----------+--------------------------+
| ID                               | Region    | Service Name | Service Type | Enabled | Interface | URL                      |
+----------------------------------+-----------+--------------+--------------+---------+-----------+--------------------------+
| 2956a12327b744b29abd4577837b2e6f | regionOne | gnocchi      | metric       | True    | internal  | http://192.168.25.3:8041 |
| 583453c58b064f69af3de3479675051a | regionOne | gnocchi      | metric       | True    | admin     | http://192.168.25.3:8041 |
| fa029da0e2c047fc9d9c50eb6b4876c6 | regionOne | gnocchi      | metric       | True    | public    | http://192.168.25.3:8041 |
+----------------------------------+-----------+--------------+--------------+---------+-----------+--------------------------+
     
    $ openstack endpoint list --service alarming
+----------------------------------+-----------+--------------+--------------+---------+-----------+--------------------------+
| ID                               | Region    | Service Name | Service Type | Enabled | Interface | URL                      |
+----------------------------------+-----------+--------------+--------------+---------+-----------+--------------------------+
| 08c70ec137b44ed68590f4d5c31162bb | regionOne | aodh         | alarming     | True    | internal  | http://192.168.25.3:8042 |
| 194042887f3d4eb4b638192a0fe60996 | regionOne | aodh         | alarming     | True    | admin     | http://192.168.25.3:8042 |
| 2604b693740245ed8960b31dfea1f963 | regionOne | aodh         | alarming     | True    | public    | http://192.168.25.3:8042 |
+----------------------------------+-----------+--------------+--------------+---------+-----------+--------------------------+

    Use the overcloud credentials to check the heat service: 

    $ source ~/overcloudrc

$ openstack endpoint list --service orchestration
+----------------------------------+-----------+--------------+---------------+---------+-----------+-------------------------------------------+
| ID                               | Region    | Service Name | Service Type  | Enabled | Interface | URL                                       |
+----------------------------------+-----------+--------------+---------------+---------+-----------+-------------------------------------------+
| 00966a24dd4141349e12680307c11848 | regionOne | heat         | orchestration | True    | admin     | http://192.168.25.3:8004/v1/%(tenant_id)s |
| 831e411bb6d44f6db9f5103d659f901e | regionOne | heat         | orchestration | True    | public    | http://192.168.25.3:8004/v1/%(tenant_id)s |
| d5be22349add43ae95be4284a42a4a60 | regionOne | heat         | orchestration | True    | internal  | http://192.168.25.3:8004/v1/%(tenant_id)s |
+----------------------------------+-----------+--------------+---------------+---------+-----------+-------------------------------------------+

  2. Verify that the services are running on the overcloud: 

    $ sudo podman ps --filter=name='heat|gnocchi|ceilometer|aodh'
CONTAINER ID  IMAGE                                                                  COMMAND      CREATED         STATUS                       PORTS       NAMES
31e75d62367f  registry.redhat.io/rhosp-rhel9/openstack-aodh-api:17.1                 kolla_start  27 minutes ago  Up 27 minutes ago (healthy)              aodh_api
77acf3487736  registry.redhat.io/rhosp-rhel9/openstack-aodh-listener:17.1            kolla_start  27 minutes ago  Up 27 minutes ago (healthy)              aodh_listener
29ec47b69799  registry.redhat.io/rhosp-rhel9/openstack-aodh-evaluator:17.1           kolla_start  27 minutes ago  Up 27 minutes ago (healthy)              aodh_evaluator
43efaa86c769  registry.redhat.io/rhosp-rhel9/openstack-aodh-notifier:17.1            kolla_start  27 minutes ago  Up 27 minutes ago (healthy)              aodh_notifier
0ac8cb2c7470  registry.redhat.io/rhosp-rhel9/openstack-aodh-api:17.1                 kolla_start  27 minutes ago  Up 27 minutes ago (healthy)              aodh_api_cron
31b55e091f57  registry.redhat.io/rhosp-rhel9/openstack-ceilometer-central:17.1       kolla_start  27 minutes ago  Up 27 minutes ago (healthy)              ceilometer_agent_central
5f61331a17d8  registry.redhat.io/rhosp-rhel9/openstack-ceilometer-compute:17.1       kolla_start  27 minutes ago  Up 27 minutes ago (healthy)              ceilometer_agent_compute
7c5ef75d8f1b  registry.redhat.io/rhosp-rhel9/openstack-ceilometer-notification:17.1  kolla_start  27 minutes ago  Up 27 minutes ago (healthy)              ceilometer_agent_notification
88fa57cc1235  registry.redhat.io/rhosp-rhel9/openstack-gnocchi-api:17.1              kolla_start  23 minutes ago  Up 23 minutes ago (healthy)              gnocchi_api
0f05a58197d5  registry.redhat.io/rhosp-rhel9/openstack-gnocchi-metricd:17.1          kolla_start  23 minutes ago  Up 23 minutes ago (healthy)              gnocchi_metricd
6d806c285500  registry.redhat.io/rhosp-rhel9/openstack-gnocchi-statsd:17.1           kolla_start  23 minutes ago  Up 23 minutes ago (healthy)              gnocchi_statsd
7c02cac34c69  registry.redhat.io/rhosp-rhel9/openstack-heat-api:17.1                 kolla_start  27 minutes ago  Up 27 minutes ago (healthy)              heat_api_cron
d3903df545ce  registry.redhat.io/rhosp-rhel9/openstack-heat-api:17.1                 kolla_start  27 minutes ago  Up 27 minutes ago (healthy)              heat_api
db1d33506e3d  registry.redhat.io/rhosp-rhel9/openstack-heat-api-cfn:17.1             kolla_start  27 minutes ago  Up 27 minutes ago (healthy)              heat_api_cfn
051446294c70  registry.redhat.io/rhosp-rhel9/openstack-heat-engine:17.1              kolla_start  27 minutes ago  Up 27 minutes ago (healthy)              heat_engine

  3. Verify that the time-series database service is available: 

    $ openstack metric status --fit-width
+-----------------------------------------------------+--------------------------------------------------------------------------------------------------------------------+
| Field                                               | Value                                                                                                              |
+-----------------------------------------------------+--------------------------------------------------------------------------------------------------------------------+
| metricd/processors                                  | ['host-80.general.local.0.a94fbf77-1ac0-49ed-bfe2-a89f014fde01',                                             |
|                                                     | 'host-80.general.local.3.28ca78d7-a80e-4515-8060-233360b410eb',                                              |
|                                                     | 'host-80.general.local.1.7e8b5a5b-2ca1-49be-bc22-25f51d67c00a',                                              |
|                                                     | 'host-80.general.local.2.3c4fe59e-23cd-4742-833d-42ff0a4cb692']                                              |
| storage/number of metric having measures to process | 0                                                                                                                  |
| storage/total number of measures to process         | 0                                                                                                                  |
+-----------------------------------------------------+--------------------------------------------------------------------------------------------------------------------+
Red Hat logoGithubredditYoutubeTwitter

Aprender

Experimente, compre e venda

Comunidades

Sobre a documentação da Red Hat

Ajudamos os usuários da Red Hat a inovar e atingir seus objetivos com nossos produtos e serviços com conteúdo em que podem confiar. Explore nossas atualizações recentes.

Tornando o open source mais inclusivo

A Red Hat está comprometida em substituir a linguagem problemática em nosso código, documentação e propriedades da web. Para mais detalhes veja o Blog da Red Hat.

Sobre a Red Hat

Fornecemos soluções robustas que facilitam o trabalho das empresas em plataformas e ambientes, desde o data center principal até a borda da rede.

Theme

© 2026 Red HatVoltar ao topo