viqSigh, is it time to move my shit to #CFEngine? I guess I will need to look a bit what's been going on with that.
Теодор Златанов / Ted Zlatanov@vivekanandanks thanks for the interesting post. I want to suggest that the #configmanagememt analogy part (where #ansible sits, and so do several other widely used tools like #saltstack, #puppet, #chef, #cfengine) can be improved. The central premise of configuration management is that current state is dynamic, a moving target. Constantly pruning a growing tree might be a better analogy.
@lkanies @atpfm @siracusa @marcoarment I thought about why Marco and others might consider and then decide #configmanagememt is not needed… here’s where I think it shines normally, whether you use #cfengine or #puppet or #chef or #saltstack or others:
- scale / machine count / OS flavors (count of at least 150 in my experience to justify the investment, while all <100 minis are on the same OS)
- expressing diversity through machine roles and profiles (all of Marco’s machines are managed the same way)
- autonomous drift repair (probably the strongest need, but Marco seems happy doing it himself)
- DSL and wrappers/macros to express intent in an abstract way (but that requires a large investment in learning that DSL)
- dedicated infrastructure for extended functionality like monitoring outcomes and triggering actions (seems not strongly needed for those minis)
Daniel LakelandIts been a year and a half since we moved my desk out of the office to do a flooring remodel, found asbestos, remediated, refloored, discovered the flooring people had sliced all my Ethernet cables, then went to Christmas, came back, the neighborhood burned to the ground...
But I finally have a desktop machine booting on my desk and after #Debian upgrade and #cfengine converges may finally be able to log in!
@mawhrin I think #saltstack is a good choice, the community is pretty decent both in size and in attitude. I feel they will endure through the Broadcom ownership. Currently that’s the best option IMO.
#cfengine is around if you’re looking for speed but the community is small. #mgmtconfig is very new, just had a first release, fun for hackers, and there’s no large company in charge, and of course @purpleidea is awesome.
#ansible is a workhorse, reliable, large community. Puppet and Chef I would not recommend nowadays.
I’m doing a company training on #saltstack and am curious how others like to structure #configuration_management trainings? Regardless of whether it’s #ansible or #cfengine or #puppet #chef etc. I think there’s got to be some common paths people find easiest to follow.
Do you start with examples of the syntax or with the architecture or do a quick start CLI demo first? How quickly do you dig into writing “hello world” and what directions do you like to explore? What are the hard and the easy parts for you and for the students?
Found out about the Firefox Profile Maker https://ffprofile.com and generated a prefs file and enterprise policy for my computer. Will be installing the enterprise stuff across my machines via #cfengine pretty soon. It gives you 7 or 8 screens with check boxes to enable and disable various privacy related options in Firefox. Takes about 10 mins to go through and build an improved privacy scenario. Also will let you choose some key add ones to enhance privacy
Nick AndersonCan you believe it? It's Friday again, the last Friday of the year and the last #CFEngine Feature Friday post in the series. For the 42nd post I shared some tooling (ob-cfengine3) that has been saving me countless hours for the last seven years. I hope you enjoyed the series.
https://cfengine.com/blog/2024/feature-friday-42-ob-cfengine3/
While I won't promise to embark on another long series, I do encourage you to send me your own tips, you never know what it might spark.
Yes, it's #CFEngine Feature Friday once again. For the penultimate (41st of 42) post in the series I wrote about quoting.
https://cfengine.com/blog/2024/feature-friday-41-how-can-i-quote-thee/
On more Friday to go, what do you think will be #42?
Yes, it's Friday the 13th, but do not fear the 40th (of 42) posts in the #CFEngine Feature Friday series is out. This week I took a look at the --simulate option (an extended dry-run of sorts) for cf-agent to see the details of what CFEngine would do.
https://cfengine.com/blog/2024/feature-friday-40-what-would-cfengine-do/