Ansible can certainly be installed using prebuilt packages from the EPEL repository, but while convenient, their offering is limited to Ansible 1.9.x – that is to say only versions prior to the major 2.0 release that includes a number of significant improvements, that were seen further polished in 2.1.
Coda has been discontinued. Looking for Coda support, older versions, plug-ins, or serial number? Visit the Panic Library. Looking for Coda, the new doc company? They're over here. See our ODA solutions page or contact us now to see how ODA solutions can boost the profitability of everyone's business. Mac OS OS X 10.8 Mountain Lion OS X 10.9 Mavericks OS X 10.10 Yosemite. Windows Microsoft Internet Explorer or Google Chrome Mac OS.
You will, more than likely, want to run 2.1.2, the latest stable release, for any production use, or perhaps the penultimate 2.0.1 release, if you are of a slightly more conservative origin.
That being said, I've always been told that DBAs like myself are about as conservative as they come, and I surprisingly experience no additional anxiety doing mission critical work with Ansible 2.1.2, which in truth, appear to be a solid release of the project's most mature code yet. I should say these feelings are in strong contrast to those that come attached with Enterprise Linux 7 and Oracle Database 12c, products which are still years away from prime time in my twisted paradigm of the world.
These few commands should take care of dependencies required to build an RPM, pull Ansible code from their official repository on GitHub and do a checkout of the 2.1 stable release before building an RPM package on and for your system – which you can then install locally on your machine or distribute in your environment as you see fit. On a side note, I like to maintain local/internal repositories with custom built packages and approved updates, which lets me stay in control while keeping yum in position to deal with the tedious bits.
Oda Oslomet
I'm using Oracle Linux 6.7 and have not tested this elsewhere, but the commands and package names should be identical on any 6 or 7 release of Oracle Linux, CentOS or RHEL and you should consequently be able to install without any modifications other than variations to the name of the generated RPM file.
Mac Os Versions
Cube dodge (arctic dev) mac os. You should now be presented with the name of the ready to install RPM package, you do need to grab said name and customize the final yum command:
Mac Os Download
In my case I had the Ansible 1.9.4-1 package from EPEL already installed on my system, yum smoothly replaced the existing RPM installation and upgraded to Ansible 2.1.2 without any fuzz. To the edge of the sky (itch) mac os.