Ben Nemec 158f7543e0 Enable configuration of rndc controls
For ha deployments we need to be able to allow rndc commands from
other controllers.  We don't want to allow rndc commands from
anywhere though, so we need to be able to configure it to only
listen on a specific network (which will be internal_api by default).
This can be done via the controls parameter.

However, because the value is a hash and the top-level key for the
hash is a dynamic value, it is problematic to represent the data
structure in a Heat template.  For our purposes, it is sufficient
to break apart the hash into its component parts and build the hash
in our Puppet manifest.

Change-Id: I2c97ff30c4c59ef32b6b918ba52973451e1b6241
Depends-On: https://review.openstack.org/581898
2018-07-17 17:01:34 +00:00
2018-02-28 14:42:12 +08:00
2018-06-28 17:02:39 -04:00
2018-06-05 07:30:44 -07:00
2018-03-19 17:18:16 +01:00
2017-01-25 19:32:31 +00:00
2017-12-16 02:49:05 +00:00
2017-10-06 12:28:56 -07:00
2018-02-28 14:42:12 +08:00

Team and repository tags

Team and repository tags

puppet-tripleo

Lightweight composition layer for Puppet TripleO.

Contributing

Description
RETIRED, Lightweight composition layer for Puppet TripleO
Readme 63 MiB