home.social

#cfengine — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #cfengine, aggregated by home.social.

fetched live
  1. Sigh, 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.

  2. Sigh, 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.

  3. @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.

  4. @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)

  5. @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)

  6. Its 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!

    #altadena #eatonfire

  7. Its 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!

    #altadena #eatonfire

  8. @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.

  9. @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.

  10. 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?

  11. 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?

  12. Found out about the Firefox Profile Maker 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

  13. Found out about the Firefox Profile Maker 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

  14. Can you believe it? It's Friday again, the last Friday of the year and the last 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.

    cfengine.com/blog/2024/feature

    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.

  15. Can 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.

    cfengine.com/blog/2024/feature

    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.

  16. Yes, it's Feature Friday once again. For the penultimate (41st of 42) post in the series I wrote about quoting.

    cfengine.com/blog/2024/feature

    On more Friday to go, what do you think will be #42?

  17. Yes, it's #CFEngine Feature Friday once again. For the penultimate (41st of 42) post in the series I wrote about quoting.

    cfengine.com/blog/2024/feature

    On more Friday to go, what do you think will be #42?

  18. Yes, it's Friday the 13th, but do not fear the 40th (of 42) posts in the 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.

    cfengine.com/blog/2024/feature

  19. 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.

    cfengine.com/blog/2024/feature

  20. Yes, it's Friday again and the 39th (of 42) Feature Friday posts is out. This time it's about the power of lists and implicit iteration.

    cfengine.com/blog/2024/feature

  21. Yes, it's Friday again and the 39th (of 42) #CFEngine Feature Friday posts is out. This time it's about the power of lists and implicit iteration.

    cfengine.com/blog/2024/feature

  22. In case you missed it, Feature Friday #38 (of 42) about developing modules that take input was published cfengine.com/blog/2024/feature

  23. In case you missed it, #CFEngine Feature Friday #38 (of 42) about developing modules that take input was published cfengine.com/blog/2024/feature

  24. It's Friday! For the 37th (of 42) posts in the Feature Friday series I wrote about making decisions based on arbitrary semantic versions using the version_compare() function.
    cfengine.com/blog/2024/feature

  25. It's Friday! For the 37th (of 42) posts in the #CFEngine Feature Friday series I wrote about making decisions based on arbitrary semantic versions using the version_compare() function.
    cfengine.com/blog/2024/feature

  26. Yep, it's my favorite day of the week, Feature Friday! This time for the 36th (of 42) posts in the series it's about cffmt, a CFEngine policy language formatting tool from @[email protected]

    cfengine.com/blog/2024/feature

    Happy Friday! 🎉

  27. Yep, it's my favorite day of the week, #CFEngine Feature Friday! This time for the 36th (of 42) posts in the series it's about cffmt, a CFEngine policy language formatting tool from @miek

    cfengine.com/blog/2024/feature

    Happy Friday! 🎉

  28. Oh, yay. Friday could not have come fast enough. For the 35th (of 42) posts in the Feature Friday series I wrote about Groups in Mission Portal. cfengine.com/blog/2024/feature

  29. Oh, yay. Friday could not have come fast enough. For the 35th (of 42) posts in the #CFEngine Feature Friday series I wrote about Groups in Mission Portal. cfengine.com/blog/2024/feature

  30. @unrznbl wrote a nice post about using cf-secret cfrom cfengine policy for setting up git credentials cfengine.com/blog/2024/promise

  31. @unrznbl wrote a nice post about using cf-secret cfrom cfengine policy for setting up git credentials cfengine.com/blog/2024/promise

    #CFEngine

  32. It's Feature Friday time again. For the 34th (of 42) post I talked about self organized groups using select_class.

    cfengine.com/blog/2024/feature

  33. It's #CFEngine Feature Friday time again. For the 34th (of 42) post I talked about self organized groups using select_class.

    cfengine.com/blog/2024/feature

  34. the agent is in, episode 42 is starting soon .... cfengine.com/webinars/

  35. Anyone know anything about #cfengine inside an #lxc container on #proxmox? I'm getting errors saying it can't follow /proc/mounts and similar proc symlinks because it is not owned by root or the user running this process... Etc. seems problematic. Do I have to use only VMs if I want cfengine? Or privileged containers?

  36. Anyone know anything about #cfengine inside an #lxc container on #proxmox? I'm getting errors saying it can't follow /proc/mounts and similar proc symlinks because it is not owned by root or the user running this process... Etc. seems problematic. Do I have to use only VMs if I want cfengine? Or privileged containers?

  37. It's Feature Friday time again :D. We are closing in on the end, only 9 more to go.

    For #33 (of 42) I wrote about a benefits of associative arrays (aka classic arrays) over data containers. cfengine.com/blog/2024/feature

  38. It's #CFEngine Feature Friday time again :D. We are closing in on the end, only 9 more to go.

    For #33 (of 42) I wrote about a benefits of associative arrays (aka classic arrays) over data containers. cfengine.com/blog/2024/feature

  39. Oh, it's Feature Friday time again. For #32 (of 42) we talk about doing math in policy with eval().

    cfengine.com/blog/2024/feature

  40. Oh, it's #CFEngine Feature Friday time again. For #32 (of 42) we talk about doing math in policy with eval().

    cfengine.com/blog/2024/feature

  41. Oh my, it's Friday again. You know what that means? Yeah, Feature Friday #30 (of 42) is out. Today it's about generating Agent logos in varying poses with agent-svg. Useful? I dunno, but it's fun!
    cfengine.com/blog/2024/feature

  42. Oh my, it's Friday again. You know what that means? Yeah, Feature Friday #30 (of 42) is out. Today it's about generating #CFEngine Agent logos in varying poses with agent-svg. Useful? I dunno, but it's fun!
    cfengine.com/blog/2024/feature

  43. The 28th (of 42) Feature Friday posts is out. Today it's about using if and unless to restrict individual promises.

    cfengine.com/blog/2024/feature

  44. The 28th (of 42) #CFEngine Feature Friday posts is out. Today it's about using if and unless to restrict individual promises.

    cfengine.com/blog/2024/feature

  45. The 27th (of 42) Feature Friday posts is out. Today it's about promises with multiple outcomes. cfengine.com/blog/2024/feature

    Happy Friday🥳

  46. The 27th (of 42) #CFEngine Feature Friday posts is out. Today it's about promises with multiple outcomes. cfengine.com/blog/2024/feature

    Happy Friday🥳

  47. The 26th (of 42) Feature Friday posts is about the groups custom promise type. Check it out: cfengine.com/blog/2024/feature

  48. The 26th (of 42) #CFEngine Feature Friday posts is about the groups custom promise type. Check it out: cfengine.com/blog/2024/feature

  49. Hey hey. It's Friday. Post 22 (of 42) in the Feature Friday series is out. cfengine.com/blog/2024/feature

  50. Happy CFEngine Feature Friday! For the 19th (of 42) post in the series I talked about the --show-evaluated-vars and --show-evaluated-classes command line options for cf-agent. cfengine.com/blog/2024/feature

  51. Happy CFEngine Feature Friday! For the 19th (of 42) post in the series I talked about the --show-evaluated-vars and --show-evaluated-classes command line options for cf-agent. cfengine.com/blog/2024/feature

    #CFEngine

  52. It's Friday again. For the 17th (of 42) post in the Feature Friday series I wrote about using tags for inventory and reporting. cfengine.com/blog/2024/feature

  53. It's Friday again. For the 17th (of 42) post in the #CFEngine Feature Friday series I wrote about using tags for inventory and reporting. cfengine.com/blog/2024/feature

  54. For the 16th (of 42) in the #CFEngine Feature Friday series I wrote about the host_info report.
    cfengine.com/blog/2024/feature