Provisioning made more complex

February 2, 2015

Your favorite cookbook

Something’s going wrong.

I, as devops, or root, or whoever is in charge of configuring these servers, have to admit that there are now a LOT of provisionning tools available for us to work. This is probably a good thing in general (although looking at the number of js frameworks and the state of js development shows that this can be a bad thing) although one can but wonder:


And the fact is that each of them has its niceties and weaknesses. Most of them are backed by more or less large companies that can deliver certifications, support and everything cash can buy. But the truth is that choosing the right framework is difficult without too much prior experience. Our choice includes:

Each of these tools will have you deploy daemons, clients, SSL certificates, HTTP proxies and write some code before you can decide if the framework is for you. The technological price is quite huge and next times somebody trolls you with the fact that you are using 70% of the AWS services for your infrastructure, ask this ugly person whether its provisioning infrastructure is not « vendor-locked » too. Your provisioning tool must have some special abilities to be useful to you:

Last time I checked, chef was almost the right tool and ansible, very close to it. But I’m still looking for the next tool…

What’s your favorite provisioning tool? And Why?

Contact? Question?


I am Pierre Baillet, senior software engineer. I write here mostly on computers and code, games, life and server stuff.