Puppet Future and Multi Tenant Setups

Posted on

In 6.7, puppet repositories show a deprecation warning. Besides the fact, that the documentation still refers to puppet repositories as the way to go for puppet modules, this will have implications for multi tenant environments.

Ansible has been mostly useless for multi tenant environments, since it requires the roles to be stored directly on the Satellite server and imported from there. This never works for independent tenants: the main administrators have to be involved for every change, and the roles are visible for everybody, not just the tenant.

Puppet repositories always worked for multiple tenants (mostly), as repositories could be created on a per organization base. There were some issues when it came to configure the classes, but the administrator was not involved with every single small code change.

With the puppet repositories discarded: is there any way to use configuration management with some integration in Satellite for independent tenants?

Responses