Re:Puppet 4 is now production-ready
by girvo on Thursday April 16, 2015 @03:07AM
(#9386337)
Is it weird that I've basically replaced Puppet/Chef/Ansible with Dockerfiles and Docker Compose?
[ Parent
| on HN ]
Not necessarily weird, but docker will not give you the same coverage and capabilities, we could invoke the "apples and oranges" comparison here.
I'm wondering about a possible execution mode for Ansible where instead of connecting via SSH and uploading/running each task, you dump each task in a shared volume and run them in a container with docker exec. Then you can commit the final result to an image.
I was under the impression that Packer was used to create machine images for EC2 and DigitalOcean, but apparently it supports building Docker images now. That's perfect!
I'll have to make some changes to my pipeline :)
I have too. After I moved to containers, the hosts themselves are so simple now. In fact, I just have a VM image I use for hosts, and then the devs make the container images running on them.
Re:Puppet 4 is now production-ready
by hackerboos on Thursday April 16, 2015 @05:34AM
(#9386768)
Still need to provision your host.
Immutable infrastructure can be implemented using sole Dockerfile and Docker Compose.
And Docker Machine can create/manage whole environments on various types of cloud providers.
They are not solving the same problem at all.
You'd still need something to bring your docker up to the desired state, unless you want to do it with bash commands line by line.
It doesn't take a lot to install and configure the Docker daemon, and if you're running a cluster you'd want to put that in your cloud-init. Of course, you can always use ansible-pull to bootstrap your hosts.