{"id":231,"date":"2016-09-01T07:07:53","date_gmt":"2016-09-01T05:07:53","guid":{"rendered":"http:\/\/www.dolicapax.org\/?p=231"},"modified":"2016-09-01T07:32:25","modified_gmt":"2016-09-01T05:32:25","slug":"fast-track-installing-ansible-2-1-stable-on-oracle-linux-6-7","status":"publish","type":"post","link":"https:\/\/www.dolicapax.org\/?p=231","title":{"rendered":"Fast track: Installing Ansible 2.1 stable on Oracle Linux 6.7"},"content":{"rendered":"<p><em>Ansible can certainly be installed using prebuilt packages from the EPEL repository, but while convenient, their offering is limited to Ansible 1.9.x &#8211; 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. <\/em><\/p>\n<p><em>You will, more than likely, want to run <em>2.1.2,\u00a0<\/em>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. <\/em><\/p>\n<p><em>That being said, I&#8217;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&#8217;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.<\/em><\/p>\n<p>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 &#8211; 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.<\/p>\n<p>I&#8217;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\u00a0without any modifications other than variations to the name of the generated RPM file.<\/p>\n<pre>sudo yum -y install git python2-devel rpm-build asciidoc\r\ncd \/usr\/src ; sudo\u00a0git clone git:\/\/github.com\/ansible\/ansible.git -b stable-2.1 --recursive\r\ncd ansible ; sudo make rpm<\/pre>\n<p>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:<\/p>\n<pre>#############################################\r\nAnsible RPM is built:\r\n rpm-build\/ansible-2.1.2.0-100.git201608311757.e83840c.HEAD.el6.noarch.rpm\r\n#############################################\r\n[roy@kayna ansible]$ <strong>sudo yum -y install rpm-build\/ansible-2.1.2.0-100.git201608311757.e83840c.HEAD.el6.noarch.rpm<\/strong>\r\nLoaded plugins: fastestmirror, refresh-packagekit, rhnplugin, security, ulninfo\r\nThis system is receiving updates from ULN.\r\nSetting up Install Process\r\n....\r\n....<\/pre>\n<p>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.<\/p>\n<pre>[roy@kayna ansible]$ ansible --version\r\nansible 2.1.2.0\r\n config file = \/etc\/ansible\/ansible.cfg\r\n configured module search path = Default w\/o overrides<\/pre>\n","protected":false},"excerpt":{"rendered":"<p>Ansible can certainly be installed using prebuilt packages from the EPEL repository, but while convenient, their offering is limited to Ansible 1.9.x &#8211; that is to say only versions prior to the major 2.0 release that includes a number of &hellip; <a href=\"https:\/\/www.dolicapax.org\/?p=231\">Continue reading <span class=\"meta-nav\">&rarr;<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[61,41,58,59,60,4],"tags":[62,63,65,66,64],"_links":{"self":[{"href":"https:\/\/www.dolicapax.org\/index.php?rest_route=\/wp\/v2\/posts\/231"}],"collection":[{"href":"https:\/\/www.dolicapax.org\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.dolicapax.org\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.dolicapax.org\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.dolicapax.org\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=231"}],"version-history":[{"count":7,"href":"https:\/\/www.dolicapax.org\/index.php?rest_route=\/wp\/v2\/posts\/231\/revisions"}],"predecessor-version":[{"id":235,"href":"https:\/\/www.dolicapax.org\/index.php?rest_route=\/wp\/v2\/posts\/231\/revisions\/235"}],"wp:attachment":[{"href":"https:\/\/www.dolicapax.org\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=231"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.dolicapax.org\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=231"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.dolicapax.org\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=231"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}