This refactors resource dependencies to avoid unnecessary dependencies
across services. For example zaqar service does not require cinder db.
Change-Id: I8b2c64ab4896c6fbb407eaa58e99056da3b5170c
The purge_config parameters only accept boolean values. This enforces
that using the typed parameters.
Change-Id: Ie504006737f094704bbff8499ac9ddbb9e8f75f5
The option has been managed by the underlying puppet-oslo module but
has not been configurable. This introduces the parameter to customize
the option.
Change-Id: Iac1ebf8af8900e9e351ef359f1c5c2e4c1704d00
This change introduces the new purge_config parameter to the policy
class so that any policy rules not managed by puppet manifests can be
cleared.
Co-Authored-By: Martin Schuppert <mschuppert@redhat.com>
Depends-On: https://review.opendev.org/802305
Change-Id: I7e453f3abf08e13d2366ea68af1ce859a88e8448
This changes all the puppet 3 validate_* functions
to use the validate_legacy function.
The validate_legacy function has been available since
about three years but require Puppet >= 4.4.0 and since
there is Puppet 4.10.12 as latest we should assume people
are running a fairly new Puppet 4 version.
This is the first step to then remove all validate function
calls and use proper types for parameter as described in spec [1].
[1] https://review.openstack.org/#/c/568929/
Change-Id: Ib31134bb604e32fd274b41dc78c4356500f71ab0
Make sure documentation is the same and follow
the standard which we are trying to enforce on
all modules.
Change-Id: I04fb9ead983cc8f7df40093b6404cac15cc9ac07
The move of policy.json into code means the file may not exist. We've
added support to ensure that the file exists in the openstacklib but we
need to make sure the permissions are right for each service. This adds
the group information to the policies so it works right.
Depends-On: I26e8b1384f4f69712da9d06a4c565dfd1f17c9ed
Related-Bug: #1742154
Change-Id: I10b322d05042fdef23758d46906cf57aa9def97f
This adds defined anchor points for external modules to hook into the
software install, config and service dependency chain. This allows
external modules to manage software installation (virtualenv,
containers, etc) and service management (pacemaker) without needing rely
on resources that may change or be renamed.
Change-Id: If4f585264f5f5a15549855d97b532866d91f5215