Chef vs. Ansible
-
@johnhooks said:
From their docs:
Ansible-Pull
Should you want to invert the architecture of Ansible, so that nodes check in to a central location, instead of pushing configuration out to them, you can.
The ansible-pull is a small script that will checkout a repo of configuration instructions from git, and then run ansible-playbook against that content.
Assuming you load balance your checkout location, ansible-pull scales essentially infinitely.
Run ansible-pull --help for details.
There’s also a clever playbook available to configure ansible-pull via a crontab from push mode.
Doing this, there would be no need for the Ansible server at all, I presume.
-
@scottalanmiller said:
@johnhooks said:
From their docs:
Ansible-Pull
Should you want to invert the architecture of Ansible, so that nodes check in to a central location, instead of pushing configuration out to them, you can.
The ansible-pull is a small script that will checkout a repo of configuration instructions from git, and then run ansible-playbook against that content.
Assuming you load balance your checkout location, ansible-pull scales essentially infinitely.
Run ansible-pull --help for details.
There’s also a clever playbook available to configure ansible-pull via a crontab from push mode.
Doing this, there would be no need for the Ansible server at all, I presume.
Ya looks like you could just pretty much create a git repo and they pull from it.
-
Chef can do that too. A lot of people do that. You lose reporting, but it scales like crazy and is very easy to manage.
-
Ya I think it's more suited to central deployments, or small local dev.
I'm assuming tower addresses this. It has job scheduling and reporting with some other stuff, but it's fairly expensive.
-
Yes, the cost of these hosted management solutions seems unrealistic. I know no one that pays for them and they are priced way out of the scope of the SMB. They only make sense for shops with huge numbers of servers which are also the shops that can easily afford to figure out how to run the systems for free. The people who need it hosted are the ones for whom the value is low.
-
You don't think $5,000 a year for 100 nodes is reasonable?
-
@johnhooks said:
You don't think $5,000 a year for 100 nodes is reasonable?
Not so much, no. When you consider that the assumption is that many of those nodes are $5/mo to operate. That could be nearly 10% of your entire server budget!
-
@johnhooks said:
You don't think $5,000 a year for 100 nodes is reasonable?
That's $5000 for what? updates?
I hear you guys talking about Chef and Ansible all the time, but haven't dug into it at all.
-
@scottalanmiller said:
@johnhooks said:
You don't think $5,000 a year for 100 nodes is reasonable?
Not so much, no. When you consider that the assumption is that many of those nodes are $5/mo to operate. That could be nearly 10% of your entire server budget!
lol plus thats the base price with only 30 days of support and no SLA ....
-
@Dashrender said:
@johnhooks said:
You don't think $5,000 a year for 100 nodes is reasonable?
That's $5000 for what? updates?
I hear you guys talking about Chef and Ansible all the time, but haven't dug into it at all.
Pretty graphs and help installing.
You do get remote job running though, but still.
-
@johnhooks said:
@scottalanmiller said:
@johnhooks said:
You don't think $5,000 a year for 100 nodes is reasonable?
Not so much, no. When you consider that the assumption is that many of those nodes are $5/mo to operate. That could be nearly 10% of your entire server budget!
lol plus thats the base price with only 30 days of support and no SLA ....
Exactly. Those prices get a bit crazy. $5/year/server would make a lot more sense. There are many cases where I would pay more for Ansible than I would for the server itself!
