CFEngine and saltstack

 Triviality  2 Responses »
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?

Settled down

 Triviality  No Responses »
Jul 062014
 

I’m working for the big chip company now, sound a little bit weird, though ๐Ÿ˜‰ .

Anyway, I’m sitting in backend team focusing on DevOps, I guess I will be in this mixed role till we find a dedicated DevOps guy. I guess whenever that happens, I’ve already finished monitoring facility (plus logistical stuffs like on-call schedule, etc.), and should have finished the plan to migrate from Rackspace to AWS.

Everything works smoothly so far except git – I admit current company is using git in a modern way, but I don’t think previous company was doing something wrong. Anyway, I believe people do have different ideas of how to use git, I just have to fit into the company’s style.

I don’t quite like saltstack although I’m still trying to get familiar with it. However, before I raise this as a concern to the team, I’d like to make sure everything that saltstack is doing can be done by cfengine.

Ah yea, also need to evaluate Shinken as it’s a pure Python solution, and “we are a python house”.