{"id":736,"date":"2018-06-06T10:17:06","date_gmt":"2018-06-06T10:17:06","guid":{"rendered":"https:\/\/www.nicktailor.com\/?p=736"},"modified":"2018-06-06T13:33:42","modified_gmt":"2018-06-06T13:33:42","slug":"how-to-setup-anisble-for-to-manage-windows-hosts-on-ubuntu-16-04","status":"publish","type":"post","link":"https:\/\/nicktailor.com\/tech-blog\/how-to-setup-anisble-for-to-manage-windows-hosts-on-ubuntu-16-04\/","title":{"rendered":"How to setup Anisble on Ubuntu 16.04"},"content":{"rendered":"

Installation
\n<\/strong><\/p>\n

Type the following\u00a0apt-get command<\/a>\u00a0or\u00a0apt command<\/a>:
\n$ sudo apt-get update
\n$ sudo apt-get upgrade
\n$ sudo apt-get install software-properties-common
\nNext add ppa:ansible\/ansible to your system\u2019s Software Source:
\n$ sudo apt-add-repository ppa:ansible\/ansible<\/p>\n\n\n\n
\u00a0Ansible is a radically simple IT automation platform that makes your applications and systems easier to deploy. Avoid writing scripts or custom code to deploy and update your applications\u2014 automate in a language that approaches plain English, using SSH, with no agents to install on remote systems.<\/p>\n

 <\/p>\n

http:\/\/ansible.com\/<\/p>\n

More info: https:\/\/launchpad.net\/~ansible\/+archive\/ubuntu\/ansible<\/p>\n

Press [ENTER]<\/strong> to continue or Ctrl-c to cancel adding it.<\/p>\n

gpg: keybox ‘\/tmp\/tmp6t9bsfxg\/pubring.gpg’ created<\/p>\n

gpg: \/tmp\/tmp6t9bsfxg\/trustdb.gpg: trustdb created<\/p>\n

gpg: key 93C4A3FD7BB9C367: public key “Launchpad PPA for Ansible, Inc.” imported<\/p>\n

gpg: Total number processed: 1<\/p>\n

gpg:\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 imported: 1<\/p>\n

OK<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

Update your repos:
\n$ sudo apt-get update
\nSample outputs:<\/p>\n

To install the latest version of ansible, enter:<\/span><\/p>\n\n\n\n
Ign:1 http:\/\/dl.google.com\/linux\/chrome\/deb stable InRelease<\/p>\n

Hit:2 http:\/\/dl.google.com\/linux\/chrome\/deb stable Release<\/p>\n

Get:4 http:\/\/in.archive.ubuntu.com\/ubuntu artful InRelease [237 kB]<\/strong><\/p>\n

Hit:5 http:\/\/security.ubuntu.com\/ubuntu artful-security InRelease<\/p>\n

Get:6 http:\/\/ppa.launchpad.net\/ansible\/ansible\/ubuntu artful InRelease [15.9 kB]<\/strong><\/p>\n

Get:7 http:\/\/ppa.launchpad.net\/ansible\/ansible\/ubuntu artful\/main amd64 Packages [560 B]<\/strong><\/p>\n

Get:8 http:\/\/in.archive.ubuntu.com\/ubuntu artful-updates InRelease [65.4 kB]<\/strong><\/p>\n

Hit:9 http:\/\/in.archive.ubuntu.com\/ubuntu artful-backports InRelease<\/p>\n

Get:10 http:\/\/ppa.launchpad.net\/ansible\/ansible\/ubuntu artful\/main i386 Packages [560 B]<\/strong><\/p>\n

Get:11 http:\/\/ppa.launchpad.net\/ansible\/ansible\/ubuntu artful\/main Translation-en [340 B]<\/strong><\/p>\n

Fetched 319 kB in 5s (62.3 kB\/s)<\/p>\n

Reading package lists… Done<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

$ sudo apt-get install ansible<\/p>\n

Type the following command:<\/span>Finding out Ansible version<\/strong><\/p>\n

$ ansible –version
\nSample outputs:<\/p>\n\n\n\n
ansible 2.4.0.0<\/p>\n

config file =<\/strong> \/etc\/ansible\/ansible.cfg<\/p>\n

configured module search path =<\/strong> [u’\/home\/vivek\/.ansible\/plugins\/modules’, u’\/usr\/share\/ansible\/plugins\/modules’]<\/strong><\/p>\n

ansible python module location =<\/strong> \/usr\/lib\/python2.7\/dist-packages\/ansible<\/p>\n

executable location =<\/strong> \/usr\/bin\/ansible<\/p>\n

python version =<\/strong> 2.7.14 (default, Sep 23 2017, 22:06:14) [GCC 7.2.0]<\/strong><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

Creating your hosts file<\/strong><\/p>\n

Ansible needs to know your remote server names or IP address. This information is stored in a file called hosts. The default is \/etc\/ansible\/hosts. You can edit this one or create a new one in your $HOME directory:
\n$ sudo vi \/etc\/ansible\/hosts
\nOr
\n$ vi $HOME\/hosts
\nAppend your server\u2019s DNS or IP address:<\/p>\n

[webservers]<\/p>\n

server1.nicktailor.com<\/p>\n

192.168.0.21<\/p>\n

192.168.0.25<\/p>\n

 <\/p>\n

[devservers]<\/p>\n

192.168.0.22<\/p>\n

192.168.0.23<\/p>\n

192.168.0.24<\/p>\n

I have two groups. The first one named as webserver and other is called devservers.<\/p>\n

Setting up ssh keys<\/strong><\/p>\n

You\u00a0must configure ssh keys between your machine and remote servers\u00a0specified in ~\/hosts file:
\n$ ssh-keygen -t rsa -b 4096 -C “My ansisble key”
\nUse scp or ssh-copy-id command to copy your public key file (e.g., $HOME\/.ssh\/id_rsa.pub) to your account on the remote server\/host:
\n$ ssh-copy-id -i $HOME\/.ssh\/id_rsa.pub root@server1.cyberciti.biz
\n$ ssh-copy-id -i $HOME\/.ssh\/id_rsa.pub root@192.168.0.22
\n$ ssh-copy-id -i $HOME\/.ssh\/id_rsa.pub root@192.168.0.23
\n$ ssh-copy-id -i $HOME\/.ssh\/id_rsa.pub root@192.168.0.24
\n$ eval $(ssh-agent)
\n$ ssh-add
\nNow ansible can talk to all remote servers using ssh command.<\/p>\n

Send ping server to all servers<\/strong><\/p>\n

Just type the following command:
\n$ ansible -i ~\/hosts -m ping all
\nSample outputs:<\/p>\n

192.168.0.22 | SUCCESS => {<\/p>\n

“changed”: false,<\/p>\n

“failed”: false,<\/p>\n

“ping”: “pong”<\/p>\n

}<\/p>\n

192.168.0.23 | SUCCESS => {<\/p>\n

“changed”: false,<\/p>\n

“failed”: false,<\/p>\n

“ping”: “pong”<\/p>\n

}<\/p>\n

192.168.0.24 | SUCCESS => {<\/p>\n

“changed”: false,<\/p>\n

“failed”: false,<\/p>\n

“ping”: “pong”<\/p>\n

}<\/p>\n

Find out uptime for all hosts<\/strong><\/p>\n

$ ansible -i hosts -m shell -a ‘uptime’ all
\nSample outputs:<\/p>\n\n\n\n
do-de.public | SUCCESS | rc=<\/strong>0<\/p>\n

10:37:02 up 1 day,\u00a0 8:39,\u00a0 1 user,\u00a0 load average: 0.95, 0.27, 0.12<\/p>\n

 <\/p>\n

do-blr-vpn | SUCCESS | rc=<\/strong>0<\/p>\n

16:07:11 up 1 day,\u00a0 8:43,\u00a0 1 user,\u00a0 load average: 0.01, 0.01, 0.00<\/p>\n

 <\/p>\n

ln.gfs01 | SUCCESS | rc=<\/strong>0<\/p>\n

10:37:17 up 22 days,\u00a0 5:30,\u00a0 1 user,\u00a0 load average: 0.18, 0.12, 0.05<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

Where,<\/p>\n

    \n
  1. -i ~\/hosts<\/strong>: Specify inventory host path. You can setup shell variable and skip the -i option. For e.g.:\u00a0export ANSIBLE_HOSTS=~\/hosts<\/strong><\/li>\n
  2. -m shell<\/strong>: Module name to execute such as shell, apt, yum and so on<\/li>\n
  3. -a ‘uptime’<\/strong>: Module arguments. For example, shell module will accept Unix\/Linux command names. The apt module will accept options to update remote boxes using apt-get\/apt command and so on.<\/li>\n
  4. all<\/strong>: The all means \u201call hosts.\u201d You can speificy group name such as devservers (ansible -i hosts -m shell -a ‘uptime’ dbservers) or host names too.<\/li>\n<\/ol>\n

    Update all Debian\/Ubuntu server using apt module<\/strong><\/p>\n

    Run the following command:
    \n$ ansible -i ~\/hosts -m apt -a ‘update_cache=yes upgrade=dist’ dbservers<\/p>\n

    Writing your first playbook<\/strong><\/p>\n

    You can combine all modules in a text file as follows in yml format i.e. create a file named update.yml:<\/p>\n

    —<\/p>\n

    – hosts: dbservers<\/p>\n

    tasks:<\/p>\n

    – name: Updating host using apt<\/p>\n

    apt:<\/p>\n

    update_cache: yes<\/p>\n

    \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 upgrade: dist<\/span><\/p>\n

    Fig.01: Ansible playbook in action<\/span>Now you can run it as follows:
    \n$ ansible-playbook -i ~\/hosts update.yml<\/p>\n","protected":false},"excerpt":{"rendered":"

    Installation Type the following\u00a0apt-get command\u00a0or\u00a0apt command: $ sudo apt-get update $ sudo apt-get upgrade $ sudo apt-get install software-properties-common Next add ppa:ansible\/ansible to your system\u2019s Software Source: $ sudo apt-add-repository ppa:ansible\/ansible \u00a0Ansible is a radically simple IT automation platform that makes your applications and systems easier to deploy. Avoid writing scripts or custom code to deploy and update your applications\u2014Read More …<\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[51],"tags":[],"class_list":["post-736","post","type-post","status-publish","format-standard","hentry","category-ansible"],"_links":{"self":[{"href":"https:\/\/nicktailor.com\/tech-blog\/wp-json\/wp\/v2\/posts\/736","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/nicktailor.com\/tech-blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/nicktailor.com\/tech-blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/nicktailor.com\/tech-blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/nicktailor.com\/tech-blog\/wp-json\/wp\/v2\/comments?post=736"}],"version-history":[{"count":9,"href":"https:\/\/nicktailor.com\/tech-blog\/wp-json\/wp\/v2\/posts\/736\/revisions"}],"predecessor-version":[{"id":747,"href":"https:\/\/nicktailor.com\/tech-blog\/wp-json\/wp\/v2\/posts\/736\/revisions\/747"}],"wp:attachment":[{"href":"https:\/\/nicktailor.com\/tech-blog\/wp-json\/wp\/v2\/media?parent=736"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/nicktailor.com\/tech-blog\/wp-json\/wp\/v2\/categories?post=736"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/nicktailor.com\/tech-blog\/wp-json\/wp\/v2\/tags?post=736"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}