Namespace: cfengine
Description: Open source configuration management system
Github Org Link: CFEngine · GitHub
Admins: larsewi larsewi (Lars Erik Wik) · GitHub
Hi @larsewi
Disclaimer: despite being part of the SC, I am not involved in the assignment of namespaces. Personally I see no problem in reserving this namespace to you.
That being said, I am very puzzled by the fact that you seem to be using (or going to us) one configuration mgmt system to run another configuration mgmt system. I did use cfengine myself, almost 20 yrs ago. Any chance you could share a bit of the use case you have in mind?
Hi @russoz
It is relatively common, at least for large organizations and infrastructures to use both Ansible and CFEngine (and other combinations). There can be different reasons for doing so, different people, teams, preferences, use cases, limitations, etc. Hence, we are working on making this experience better and easier for our users, through various modules, integrations.
It seemed like the right approach, to get this published under the “cfengine” namespace.
We have written numerous blog posts on how you can leverage the best of both, and want to make these tools work better together.
An example use case could be to let CFEngine distribute playbooks and tell Ansible when to execute them. This way the agent can keep a continuous state enforcement when parts of the inventory is unreachable.
Let us know if you have any questions or need anything more from our side.
2 Likes
Thanks for sharing that perspective. 
I must confess I haven’t thought of cfengine for a long time now, but then again I don’t manage any environment that is big and/or complex enough to warrant a combined solution like that. Cheers.
1 Like