Bug 2097963
| Summary: | [RHOSP 17.1] how to disable OSP components used with STF | ||
|---|---|---|---|
| Product: | Red Hat OpenStack | Reporter: | youngcheol <yocha> |
| Component: | Service Telemetry Framework | Assignee: | Leif Madsen <lmadsen> |
| Status: | CLOSED DUPLICATE | QA Contact: | Leonid Natapov <lnatapov> |
| Severity: | medium | Docs Contact: | Joanne O'Flynn <joflynn> |
| Priority: | medium | ||
| Version: | 16.2 (Train) | CC: | augol, bshephar, jschluet, lmadsen, mmagr, mrunge, ramishra, tkajinam |
| Target Milestone: | ga | Keywords: | Documentation, Triaged |
| Target Release: | 17.1 | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | No Doc Update | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2022-11-28 15:26:28 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | |||
| Bug Blocks: | 2096853 | ||
I'm closing this issue as a duplicate in favour of 2096853 which is where we'll provide documentation on how to disable telemetry components pointed at STF. Scope is disabling the services. Additional development needs to be completed upstream in order to perform automated clean up of the environment which would target RHOSP 18.0. For now we'll just disable the appropriate services. *** This bug has been marked as a duplicate of bug 2096853 *** |
Description of problem: There is no documented procedure to disable OSP telmetry components that are enabled when using STF. But My customer decided to disable it But My customer decided to not use STF, so need to safe way to do it. Version-Release number of selected component (if applicable): RHOSP16.2.1 STF 1.3 How reproducible: install openstack STF componets with related yaml. after then remove related yaml and include below parameter to disable. resource_registry: OS::TripleO::Services::CeilometerAgentCentral: OS::Heat::None OS::TripleO::Services::CeilometerAgentNotification: OS::Heat::None OS::TripleO::Services::CeilometerAgentIpmi: OS::Heat::None OS::TripleO::Services::ComputeCeilometerAgent: OS::Heat::None OS::TripleO::Services::Redis: OS::Heat::None OS::TripleO::Services::Collectd: OS::Heat::None OS::TripleO::Services::MetricsQdr: OS::Heat::None Steps to Reproduce: 1. Before : openstack overcloud deploy --templates \ -n /home/stack/templates/network_data.yaml \ -e /home/stack/templates/node_info.yaml\ -e /home/stack/containers-prepare-parameter.yaml \ -e /usr/share/openstack-tripleo-heat-templates/environments/net-single-nic-with-vlans.yaml \ -e /usr/share/openstack-tripleo-heat-templates/environments/network-isolation.yaml \ -e /home/stack/openstack-tripleo-heat-templates-rendered/environments/network-environment.yaml \ -e /usr/share/openstack-tripleo-heat-templates/environments/metrics/ceilometer-write-qdr.yaml \ -e /usr/share/openstack-tripleo-heat-templates/environments/metrics/collectd-write-qdr.yaml \ -e /usr/share/openstack-tripleo-heat-templates/environments/metrics/qdr-edge-only.yaml \ -e /home/stack/enable-stf.yaml \ -e /home/stack/stf-connectors.yaml \ --ntp-server 192.168.24.1 --libvirt-type qemu 2. After : openstack overcloud deploy --templates \ -n /home/stack/templates/network_data.yaml \ -e /home/stack/templates/node_info.yaml\ -e /home/stack/containers-prepare-parameter.yaml \ -e /usr/share/openstack-tripleo-heat-templates/environments/net-single-nic-with-vlans.yaml \ -e /usr/share/openstack-tripleo-heat-templates/environments/network-isolation.yaml \ -e /home/stack/openstack-tripleo-heat-templates-rendered/environments/network-environment.yaml \ -e /home/stack/disable-stf.yaml \ --ntp-server 192.168.24.1 --libvirt-type qemu cat disable-stf.yaml resource_registry: OS::TripleO::Services::CeilometerAgentCentral: OS::Heat::None OS::TripleO::Services::CeilometerAgentNotification: OS::Heat::None OS::TripleO::Services::CeilometerAgentIpmi: OS::Heat::None OS::TripleO::Services::ComputeCeilometerAgent: OS::Heat::None OS::TripleO::Services::Redis: OS::Heat::None OS::TripleO::Services::Collectd: OS::Heat::None OS::TripleO::Services::MetricsQdr: OS::Heat::None Actual results: there is remained some STF related containers after run "2.after" [root@overcloud-novacompute-0 ~]# podman ps|egrep "collect|ceilo|metrics" 4f5ecdb7035a undercloud.ctlplane.localdomain:8787/rhosp-rhel8/openstack-qdrouterd:16.2 kolla_start 28 hours ago Up 28 hours ago metrics_qdr [root@overcloud-controller-0 ~]# podman ps|egrep "collect|ceilo|metrics" 3677ca356e24 undercloud.ctlplane.localdomain:8787/rhosp-rhel8/openstack-collectd:16.2 kolla_start 28 hours ago Up 22 hours ago collectd Expected results: clean up all stf components in OSP side. Additional info: Additional Info: There is an email thread title "[cloudops][rhos-tech] How to removal STF component in a deployed env?" which contains the following content. mrunge: ~~~ no, you need to actively set the services to none. (the following is untested!) OS::TripleO::Services::CeilometerAgentCentral: OS::Heat::None OS::TripleO::Services::CeilometerAgentNotification: OS::Heat::None OS::TripleO::Services::CeilometerAgentIpmi: OS::Heat::None OS::TripleO::Services::ComputeCeilometerAgent: OS::Heat::None OS::TripleO::Services::Redis: OS::Heat::None OS::TripleO::Services::Collectd: OS::Heat::None OS::TripleO::Services::MetricsQdr: OS::Heat::None in an environment file. If a service is not explicitly named/changed, director won't touch it. ~~~ tkajinam: ~~~ While ceilometer/collectd/qdr service would be removed by just disabling these services (although you might need some manual clean up tasks like removing logs, dropping db, ...) you need some caution about Redis. Redis by default is managed by pacemaker and disabling the service would NOT remove pacemaker resources afair. so you should disable/delete the pacemaker resource manually before you run that deployment. Maybe it'd be better to stop the service and disable/delete the redis then try updating overcloud. ~~~