#chef #ConfigManagememt #devops
@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)