# agent on server

**URL:** <https://forum.ansible.com/t/agent-on-server/16227>\
**Category:** Ansible Project\
**Created:** [September 15, 2014, 11:46am UTC](https://forum.ansible.com/t/agent-on-server/16227 "2014-09-15T11:46:28Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![Nitin\_Kumar](https://avatars.discourse-cdn.com/v4/letter/n/c4cdca/32.png) [@Nitin\_Kumar](https://forum.ansible.com/u/Nitin_Kumar)\
**Post date:** [September 15, 2014, 11:46am UTC](https://forum.ansible.com/t/agent-on-server/16227/1 "2014-09-15T11:46:28Z")

</div>

Hi,

For Ansible we say its agentless. But in our requirement we need to have a agent on client which polls management server depending on some events to trigger some activities back.

Say client is going down, it will trigger event and notify Management server. Then server can send requests to save logs.

As we have agent in puppet/chef we can leverage that feature.

is there a way we implement such feature using Ansible?

Thanks  
Nitin Kr

---

<div class="post-metadata">

**Author:** ![Nitin\_Kumar](https://avatars.discourse-cdn.com/v4/letter/n/c4cdca/32.png) [@Nitin\_Kumar](https://forum.ansible.com/u/Nitin_Kumar)\
**Post date:** [September 15, 2014, 11:48am UTC](https://forum.ansible.com/t/agent-on-server/16227/2 "2014-09-15T11:48:10Z")

</div>

last mail got wrong subject line. So sending once again.

---

<div class="post-metadata">

**Author:** ![Brian\_Coca1](https://avatars.discourse-cdn.com/v4/letter/b/278dde/32.png) [@Brian\_Coca1](https://forum.ansible.com/u/Brian_Coca1)\
**Post date:** [September 15, 2014, 11:52am UTC](https://forum.ansible.com/t/agent-on-server/16227/3 "2014-09-15T11:52:48Z")

</div>

look at ansible-pull

---

<div class="post-metadata">

**Author:** ![James\_Cammarata](https://avatars.discourse-cdn.com/v4/letter/j/7c8e57/32.png) [@James\_Cammarata](https://forum.ansible.com/u/James_Cammarata)\
**Post date:** [September 15, 2014, 8:59pm UTC](https://forum.ansible.com/t/agent-on-server/16227/4 "2014-09-15T20:59:19Z")

</div>

Hi Nitin,

For this purpose you could simply install Ansible on any end-point systems and write an init script which was run on system shutdown to execute your playbooks. For periodic updates at regular times, we also provide the ansible-pull utility ([http://docs.ansible.com/playbooks\_intro.html#ansible-pull](http://docs.ansible.com/playbooks_intro.html#ansible-pull)), which is typically setup via a cron job.

Thanks!

---

<div class="post-metadata">

**Author:** ![John\_Favorite](https://avatars.discourse-cdn.com/v4/letter/j/ba9def/32.png) [@John\_Favorite](https://forum.ansible.com/u/John_Favorite)\
**Post date:** [September 16, 2014, 2:34am UTC](https://forum.ansible.com/t/agent-on-server/16227/5 "2014-09-16T02:34:20Z")

</div>

awesome. missed this. thanks for sharing

---

<div class="post-metadata">

**Author:** ![Michael\_DeHaan1](https://avatars.discourse-cdn.com/v4/letter/m/5e9695/32.png) [@Michael\_DeHaan1](https://forum.ansible.com/u/Michael_DeHaan1)\
**Post date:** [September 16, 2014, 2:47pm UTC](https://forum.ansible.com/t/agent-on-server/16227/6 "2014-09-16T14:47:53Z")

</div>

Also, Ansible Tower – [http://ansible.com/tower](http://ansible.com/tower).

Tower has the ability to set up

(A) timers to run projects repeatedly at set times

(B) web callbacks that can allow a node to phone in and request configuration (useful for autoscaling setups).