Re: Puppet versus CFEngine
Aleksey Tsalolikhin <[email protected]> Sun, 17 Sep 2023 19:49:31 +0000
| Newsgroups | gmane.comp.sysutils.cfengine.general |
|---|---|
| Message-ID | <CANNWuVURJdXgEgKDNoTiSOTmKqVLZNhYRdsgTm0fDWMNdbzbwg@mail.gmail.com> |
On Tue, Sep 12, 2023 at 3:44 PM Marco Marongiu <[email protected]> wrote: > 11 years old blog post, you decide if it's relevant: > https://syslog.me/2012/06/17/why-i-gave-up-puppet-and-chose-cfengine-3/ > In this blog post, Marco wrote: < [After reading "Learning CFEngine 3"] all the things that were confusingly buzzing in my head started to line themselves orderly I had a similar experience attending Mark's CFE3 tutorial at USENIX LISA. I had tried to learn it from documentation earlier but had a lot of confusions and questions. I remember sitting in the front row and I kept raising my hand with question after question, which Mark all patiently and kindly answered, and about halfway through the talk, something just clicked for me (the lightbulb went on) and all the ideas flying around settled aligned into this elegant towering structure and IT ALL MADE SENSE. I'm working with Ansible at $WORK and we've been having issues with long-running hosts having a stale configuration (out of date relative to the current state of policy) because hosts are configured at provision time. I explained how with CFEngine you have an agent on each host that runs _continuously_ so you'd never have state drift like that. Brilliant design! So an example, Mike, for the examples collection you suggestied, would be removing a user's account (or locking it) after they leave the organization. Best, -at -- You received this message because you are subscribed to the Google Groups "help-cfengine" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/help-cfengine/CANNWuVURJdXgEgKDNoTiSOTmKqVLZNhYRdsgTm0fDWMNdbzbwg%40mail.gmail.com.