Bug 2096853

Description of problem: There is no documented procedure to disable OSP telmetry components that are enabled when using STF. It should be possible for someone to do a clean up of OSP components when STF is no longer in use.


Version-Release number of selected component (if applicable): RHOSP 17.1


Additional Info:

There is an email thread title "" which contains the following content. None of this is tested and needs to be verified prior to publishing documentation.

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.

DISCLAIMER: I've never tested the actual scenario

~~~