# Does ansible in pull mode have access to other nodes fact? **URL:** \ **Category:** Ansible Project\ **Created:** [November 14, 2012, 1:27pm UTC](https://forum.ansible.com/t/does-ansible-in-pull-mode-have-access-to-other-nodes-fact/12085 "2012-11-14T13:27:34Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![Jeremiah\_Snapp](https://avatars.discourse-cdn.com/v4/letter/j/3bc359/32.png) [@Jeremiah\_Snapp](https://forum.ansible.com/u/Jeremiah_Snapp)\ **Post date:** [November 14, 2012, 1:27pm UTC](https://forum.ansible.com/t/does-ansible-in-pull-mode-have-access-to-other-nodes-fact/12085/1 "2012-11-14T13:27:34Z")
I’m pretty sure my understanding of ansible push mode is correct in that since you are pushing from a central location you have all facts available to you. Therefore, all those facts are inherently available to all nodes’ playbooks. But what about if you use ansible in pull mode? It seems to me that since each node is running it’s own separate instance of ansible you inherently lose awareness of surrounding nodes and their facts. Is that true? Thanks, Jeremiah ---
**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:** [November 14, 2012, 1:48pm UTC](https://forum.ansible.com/t/does-ansible-in-pull-mode-have-access-to-other-nodes-fact/12085/2 "2012-11-14T13:48:02Z")
That is mostly how pull seems to be intended to be used. But we have had the case in which someone cloned the full config, which ‘worked’. You have to carefully setup playbooks then or you can get unintended actions being run, either on other hosts or multiple times locally. Brian Coca ---
**Author:** ![Michael\_DeHaan](https://avatars.discourse-cdn.com/v4/letter/m/c4cdca/32.png) [@Michael\_DeHaan](https://forum.ansible.com/u/Michael_DeHaan)\ **Post date:** [November 14, 2012, 2:13pm UTC](https://forum.ansible.com/t/does-ansible-in-pull-mode-have-access-to-other-nodes-fact/12085/3 "2012-11-14T14:13:44Z")
Ansible pull does not contain the orchestration features of regular ansible. If you are merely looking for speed and scaling, fireball mode is a better choice. Ansible-pull is a great choice for where you want periodic host-initiated remediation or \*extremely large scale\*, though I believe it would still be useful to write an extremely basic cron script that periodically runs ansible across hosts in classic form. ---
**Author:** ![Jeremiah\_Snapp](https://avatars.discourse-cdn.com/v4/letter/j/3bc359/32.png) [@Jeremiah\_Snapp](https://forum.ansible.com/u/Jeremiah_Snapp)\ **Post date:** [November 14, 2012, 2:37pm UTC](https://forum.ansible.com/t/does-ansible-in-pull-mode-have-access-to-other-nodes-fact/12085/4 "2012-11-14T14:37:28Z")
Thanks Michael, that confirms my understanding then. I figured fireball would be your suggestion. Seems like the best way to maintain both speed as well as full features of ansible. Your last suggestion “I believe it would still be useful to write an extremely basic cron script that periodically runs ansible across hosts in classic form”. You mean running cron’d ansible on the central machine for central-initiated periodic remediation right? That makes sense to me also. ---
**Author:** ![Michael\_DeHaan](https://avatars.discourse-cdn.com/v4/letter/m/c4cdca/32.png) [@Michael\_DeHaan](https://forum.ansible.com/u/Michael_DeHaan)\ **Post date:** [November 14, 2012, 2:39pm UTC](https://forum.ansible.com/t/does-ansible-in-pull-mode-have-access-to-other-nodes-fact/12085/5 "2012-11-14T14:39:19Z")
> Thanks Michael, that confirms my understanding then. I figured fireball > would be your suggestion. Seems like the best way to maintain both speed as > well as full features of ansible. > > Your last suggestion "I believe it would still be useful to write an > extremely basic cron script that periodically runs ansible across hosts in > classic form". > You mean running cron'd ansible on the central machine for central-initiated > periodic remediation right? That makes sense to me also. Yes. Maybe there's a bit of a useful wrapper around that which we could deliver with ansible, and maybe that cron is all that's needed. (It should probably need to run under ssh-agent.)