Sep 182014
I, personally, still don’t think saltstack is a configuration management tool, it’s more like a remote execution engine that allow you launch command to multiple hosts at the same time. saltstack does not do well in maintaining configuration up-to-date, or maybe it does, but we are using it in a wrong way.
Now I’ve done most of my part with monitoring, after migrating to AWS I think the next thing is to review configuration management, I would still prefer CFEngine, though keep saltstack as a remote execution engine, as anyway we (read: ops) need this.
So the next question is, how to migrate saltstack’s state to CFEngine’s promise?
2 Responses to “CFEngine and saltstack”
Sorry, the comment form is closed at this time.
Did you manage move to CFEngine promise ?
No.
It took me 9 months to migrate everything to AWS, much longer than I thought.
And I moved to another company after that, I don’t think I’m going to try anything to migrate saltstack to CFEngine at least in near future.