[tripleo] Configuration Management without Puppet

Clark Boylan cboylan at sapwetik.org
Tue May 28 16:11:44 UTC 2019

On Mon, May 27, 2019, at 4:36 PM, Emilien Macchi wrote:
> (First of all: thanks to Alex Schultz who initiated the discussion 
> during the last PTG).
> Context:
> With the containerization of the services in TripleO, our usage of 
> Puppet is pretty much limited to laying down parameters into 
> configuration files.
> Our long term goal is to reduce our number of tools in TripleO and 
> converge toward more Ansible and we are currently investigating how to 
> make it happen for Configuration Management, in a backward compatible 
> and non-disruptive way.
> Problems:
> - Our current interface to configure things is very tight to Puppet and 
> Hiera, which would make it complicated to bind it with Hiera. Some of 
> us have tried (to create some Hiera module in Ansible) but clearly this 
> is not the path we want to take as far I know.
> - We don't use the logic (generally) in the Puppet modules and again 
> only care about the configuration providers (in puppet-openstacklib and 
> for some services, templates files), so the Puppet modules now do too 
> much for what we need in TripleO.


I'm not sure if this is useful but what the Infra team did was to transplant all of its hiera data into /etc/ansible/hosts/host_vars and /etc/ansible/hosts/group_vars. Then we updated our puppetry to pull hiera data out of there. This means that puppet and ansible read the same data sources which has made transitioning things easy for us.

Though I think the ansible-role-puppet role copies hiera data sources from /etc/ansible/hosts to the appropriate puppet hiera location on the remote source. But you mostly don't have to think about that and there is no double accounting from an ops perspective.


More information about the openstack-discuss mailing list