|
|
|
|
|
|
by eropple
3863 days ago
|
|
|
> Does your Ansible setup provide that? I suspect not. My Chef and Packer one does. The deltas between a Vagrant image and an AWS image are exactly the ones I know to be there and are there because the environments are different. Those minimal differences exist because these environments are fundamentally different and I need to be mindful of them when operating at scale--something that Docker will occlude but never, by its nature, solve any better. |
|
|
The point was, start with docker, get that for mostly free. You can feel free to further manage the underlying hosts with chef, puppet, or ansible, but docker will make the systems interface to your app quite a bit neater and you'll still chef to configure the app.
Your CM now does less, which is a good thing.
Throw in mesos or kubernetes because your CM isn't really amazingly helpful at deciding where things should run and your CM will now do even less.
That doesn't mean your CM will definitely go in the bin, but if all it's doing is changing a couple of system settings during an image build, it arguably could be bash, though I personally would rather it wasn't.