{"id":21038,"date":"2021-04-19T23:11:46","date_gmt":"2021-04-19T23:11:46","guid":{"rendered":"https:\/\/www.devopsschool.com\/blog\/?p=21038"},"modified":"2021-10-28T06:42:17","modified_gmt":"2021-10-28T06:42:17","slug":"what-is-ansible-pull-and-how-can-we-use-it","status":"publish","type":"post","link":"https:\/\/www.devopsschool.com\/blog\/what-is-ansible-pull-and-how-can-we-use-it\/","title":{"rendered":"What is ansible pull and how can we use it?"},"content":{"rendered":"\n

ansible-pull pulls playbooks from a VCS repo(git) and executes them for the local host.<\/p>\n\n\n\n

The ansible-pull command is a special feature of Ansible that allows you to, all in one go, pull a playbook from a Git repository (for example, GitHub) and then execute it, hence saving the usual steps such as cloning (or updating the working copy of) the repository, then executing the playbook. The great thing about ansible-pull is that it allows you to centrally store and version control your playbooks and then execute them with a single command, hence enabling them to be executed using the cron scheduler without the need to even install the Ansible playbooks on a given box.<\/p>\n\n\n\n

ansible-pull is used to up a remote copy of ansible on each managed node, each set to run via cron and update playbook source via a source repository. This inverts the default push architecture of ansible into a pull architecture, which has near-limitless scaling potential.<\/p>\n\n\n\n

The setup playbook can be tuned to change the cron frequency, logging locations, and parameters to ansible-pull. This is useful both for extreme scale-out as well as periodic remediation. Usage of the \u2018fetch\u2019 module to retrieve logs from ansible-pull runs would be an excellent way to gather and analyze remote logs from ansible-pull.<\/p>\n\n\n\n

The Cronjob
This is the easy part, all you will be doing is adding the following as a cronjob to your system.<\/p>\n\n\n

0<\/span> 3<\/span> * * * \/usr\/<\/span>local\/bin\/ansible-pull -U https:\/\/github.com\/scmgalaxy\/ansible-pull-example -i hosts<\/span><\/code><\/span>Code language:<\/span> JavaScript<\/span> (<\/span>javascript<\/span>)<\/span><\/small><\/pre>\n\n\n
  • If you\u2019re new to cronjobs, all you need to know is this job is being run every day at 3am.<\/li>
  • The next part of the command is simply the full path to the ansible-pull command, in this instance, we are using the -U option to make sure our code is updated, if it is already installed.<\/li>
  • Then finally, the command also includes a hosts file that our playbook will run against.<\/li><\/ul>\n\n\n\n
    Manual Use of ansible-pull<\/h2>\n\n\n
    To run the ansible-pull manually use<\/span> a<\/span> command<\/span> like<\/span> the<\/span> following<\/span>:\n\nurl<\/span>='https<\/span>:\/\/github<\/span>.com<\/span>\/jschulthess<\/span>\/ansible<\/span>-pull<\/span>-update<\/span>.git<\/span>' # URL<\/span> of<\/span> the<\/span> playbook<\/span> repository<\/span>\ncheckout<\/span>='develop<\/span>'                                            # branch<\/span>\/tag<\/span>\/commit<\/span> to<\/span> checkout<\/span>\ndirectory<\/span>='\/var<\/span>\/projects<\/span>\/ansible<\/span>-pull<\/span>-update<\/span>'           # directory<\/span> to<\/span> checkout<\/span> repository<\/span> to<\/span>\nlogfile<\/span>='\/var<\/span>\/log<\/span>\/ansible<\/span>-pull<\/span>-update<\/span>.log<\/span>'                            # where<\/span> to<\/span> put<\/span> the<\/span> logs<\/span>\n\nsudo<\/span> ansible<\/span>-pull<\/span> -o<\/span> -C<\/span> ${checkout<\/span>} -d<\/span> ${directory<\/span>} -i<\/span> ${directory<\/span>}\/inventory<\/span> -U<\/span> ${url<\/span>} \\\n  2>&1 | sudo<\/span> tee<\/span> -a<\/span> ${logfile<\/span>}\n<\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
    Example Code<\/h2>\n\n\n\n