openstack
/
tripleo-heat-templates
Code Issues Proposed changes

[Rocky and older] Actually install tmpwatch on overcloud nodes 

This is the equivalent of https://review.opendev.org/698232 but we can't
backport it "as-is" due to the huge tree change.

Closes-Bug: #1855802
Change-Id: I3cd1c343bba473e3f8c9da1f0933a4810d678e76
This commit is contained in:
Cédric Jeanneret 2019-12-10 14:23:07 +01:00
parent 4b46adcc27
commit 4d2b188ec1
2 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
extraconfig/services/tmpwatch-install.yaml
View File

@ -1,7 +1,7 @@
heat_template_version: rocky
description: >
Install tmpwatch on the undercloud/standalone
Install tmpwatch
parameters:
EndpointMap:
@ -33,7 +33,7 @@ parameters:
outputs:
role_data:
description: Role data for tmpwatch install on undercloud or standalone
description: Role data for tmpwatch install
value:
service_name: logrotate_tmpwatch
deploy_steps_tasks:

2
overcloud-resource-registry-puppet.j2.yaml
View File

@ -341,7 +341,7 @@ resource_registry:
OS::TripleO::Services::Multipathd: docker/services/multipathd.yaml
# Logging
OS::TripleO::Services::Tmpwatch: OS::Heat::None
OS::TripleO::Services::Tmpwatch: extraconfig/services/tmpwatch-install.yaml
OS::TripleO::Services::Logging::BarbicanApi: docker/services/logging/files/barbican-api.yaml
OS::TripleO::Services::Logging::GlanceApi: docker/services/logging/files/glance-api.yaml
OS::TripleO::Services::Logging::HAProxy: docker/services/logging/files/haproxy.yaml