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

Very interesting, will check that out.

@scottalanmiller said in Red Hat Open Sources Ansible Galaxy:

That's awesome. Now just waiting on Tower, too.

Thought exactly the same: Free/open Tower would be awesome.

That's a nice aspect of systems like Ansible, they basically force good practices like this.

@wirestyle22 I agree... and I like that better than the usual "you look like Anthony Michael Hall."

After signing up, you can go to My Membership to cancel the auto-renewal so you don't forget and get charged.

Updated as I figured out where things have moved away from the documentation that I had. The five minute install video is for Stacki 1.x and they have changed quite a bit at the core so that is why the video does not reflect the needs of the current installer. Avoid the StackiQ video for installation.

So perhaps Red Hat is screwing up the Ansible quality? That's a depressing thought.

@scottalanmiller You should also include cloud-init

https://cloudinit.readthedocs.org/en/latest/

I tried Rundeck. It was more confusing than just using Ansible without a GUI. IMO, just having the playbook with yaml and jinja files is easier to read and use. GUIs always have at least one thing you need in a place you wouldn't think.

I guess I wouldn't mind having some reports in a GUI but I'll stick with just text files.

@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!

As long as it is "almost" boring, it is still exciting!

This is interesting as not too long ago Red Hat made a major effort to integrate Puppet inside of their Satellite product.

Now to make our first organization, we will make a test one to get started.

chef-server-ctl org-create SHORTNAME LONGNAME --association_user USERNAME -f filename

That's the format, here is a real command:

chef-server-ctl org-create test "Chef Testing NonProd" --association_user scott -f scott.pem

Really quite simple since NVM is so simple itself. Just used the standard curl + bash command to run the NVM install of the version of my choice (handling updates will have to come in a later version.) I use the install directory relocation option and that puts NVM into /usr/local/nvm rather than into the user's own folder. Then just source the newly installed nvm.sh file and run the NVM Node.js install command as usual. Voila.

@dafyre said:

If you haven't, make a specific AD account for the TFS server and let it run under that account and see what happens?

That's the plan, well not a specific one. we have a service account and it should have been setup that way but it was not, now I have to deal with the issues. It will have to wait til tonight when no DevOPs are doing anything to check it.

Good article, thanks.