Chapter 3. Configuring and deploying autoscaling
Chapter 3. Configuring and deploying autoscaling To configure and deploy autoscaling, you must complete the following prerequisites: Create environment templates and a resource registry for autoscaling services before you deploy the cloud for autoscaling. Deploy the cloud. 3.1. Enabling the control plane resources for autoscaling Use the following procedure to enable the control plane resources that you need for autoscaling. Prerequisites A deployed Red Hat OpenStack Services on OpenShift (RHOSO) environment. Procedure Edit the OpenStackControlPlane custom resource to enable the Orchestration (heat) and telemetry services. Inside the telemetry section of the .yaml file, enable the Ceilometer, Autoscaling, and MetricStorage objects: Verification Verify that the required custom resources are ready: Verify that there is an Alarming service endpoint: Verify that there is an Orchestration service endpoint: Verify that Prometheus is enabled and can scrape each endpoint. Confirm that the value in the output is 1 for each row, except for the Prometheus container, which is 0 when TLS is enabled:
oc edit oscp heat: enabled: true telemetry: apiOverride: {} enabled: true template: autoscaling: enabled: true heatInstance: heat ceilometer: enabled: true metricStorage: enabled: true oc get heat heat -o jsonpath='{.status.conditions[?(@.type=="Ready")].status}{"\n"}' True oc get ceilometer ceilometer -o jsonpath='{.status.conditions[?(@.type=="Ready")].status}{"\n"}' True oc get autoscaling autoscaling -o jsonpath='{.status.conditions[?(@.type=="Ready")].status}{"\n"}' True oc get metricstorage metric-storage -o jsonpath='{.status.conditions[?(@.type=="Ready")].status}{"\n"}' True oc rsh openstackclient openstack endpoint list --service alarming +----------------------------------+-----------+--------------+--------------+---------+-----------+------------------------------------------------+ | ID | Region | Service Name | Service Type | Enabled | Interface | URL | +----------------------------------+-----------+--------------+--------------+---------+-----------+------------------------------------------------+ | 62d20961a3354daa8adf52db62cc809d | regionOne | aodh | alarming | True | public | https://aodh-public-openstack.apps.example.testing | | 8e526119b01248aba8d304de627a6267 | regionOne | aodh | alarming | True | internal | http://aodh-internal.openstack.svc:8042 | +----------------------------------+-----------+--------------+--------------+---------+-----------+------------------------------------------------+ oc rsh openstackclient openstack endpoint list --service orchestration +----------------------------------+-----------+--------------+---------------+---------+-----------+---------------------------------------------------------------------+ | ID | Region | Service Name | Service Type | Enabled | Interface | URL | +----------------------------------+-----------+--------------+---------------+---------+-----------+---------------------------------------------------------------------+ | 77190103ae3b479290138ebeca4a54d7 | regionOne | heat | orchestration | True | internal | http://heat-api-internal.openstack.svc:8004/v1/%(tenant_id)s | | c302ee5ff5cc45709d20b2d4a872d08f | regionOne | heat | orchestration | True | public | https://heat-api-public-openstack.apps.example.testing/v1/%(tenant_id)s | +----------------------------------+-----------+--------------+---------------+---------+-----------+---------------------------------------------------------------------+ oc rsh openstackclient openstack metric query up --disable-rbac -c instance -c container -c value +----------------------+----------------------+-------+ | instance | container | value | +----------------------+----------------------+-------+ | 10.217.1.27:9093 | alertmanager | 1 | | 10.217.1.27:9093 | prometheus | 0 | | 10.217.1.52:3000 | proxy-httpd | 1 | | 10.217.0.169:3000 | | 1 | | 192.168.122.100:9100 | | 1 | | 192.168.122.101:9100 | | 1 | +----------------------+----------------------+-------+