@flaxking said in Which is easier to learn Ansible or Chef or Puppet:

The whole container/CM thing is kind of at a weird place right now. With containers, we've sort of migrated back to the golden image thing, just with the pressure to create an image using a config file. I don't really like images on docker hub that don't have links to the dockerfile.

Yes, images that can't be tweaked without rebuilding. It's has benefits, and a lot of caveats. Having to deploy new containers for every patch is pretty silly. And so many things can't be immutable, including the platform on which the containers run.

At the end of the day, containers are either mutable, or immutable. The former need CM inside the container, the later need it outside the container.

http://blog.takipi.com/deployment-management-tools-chef-vs-puppet-vs-ansible-vs-saltstack-vs-fabric/

That's a standard systemctl cannot start message. And it is just telling you that you need to tail /var/log/messages to see what the error was.

@Aaron-Studer said:

@scottalanmiller said:

@Aaron-Studer said:

Should I learn Chef or Puppet?

Good question. The answer is squarely... It depends.

Do you want hosted or on premise? On Prem

How many machines do you want to support? 25ish

Do you need a graphical interface? Yes.

What platforms do you want to support? Windows, and Linux.

Then Puppet as Chef doesn't do graphical.