pull model
An arrangement where an agent on each host periodically asks a central server for its configuration and applies it.
In more detail
Pull tools keep hosts converging on a timer, even ones that were offline, but they need an agent everywhere and changes arrive on the agent's schedule rather than when you choose. Ansible normally pushes; its separate ansible-pull command can be used to pull instead.
Related terms
- push model — An arrangement where a central machine sends changes out to the hosts when someone runs it, as Ansible does.
- agent — A program that runs in the background on every managed machine, checking in with a central server and applying the configuration it is given.
- GitOps — Operating a system by keeping its desired state in Git and letting a controller continuously make the live system match it.
- reconciliation — The repeated check-and-fix loop in which a program compares desired state with observed state and changes the world to match.
Taught in
- Ansible Architecture And The Control Node — Ansible Configuration Management at Scale
- The Push Model vs. The Pull Model — Continuous Integration & Continuous Delivery Pipelines
- What is GitOps? — Continuous Integration & Continuous Delivery Pipelines