Thanks again, Jason. I'll spin some up today and run through some more
docs, tutorias.
On Sat, Sep 27, 2014 at 9:27 AM, Jason Antman wrote:
> With a very small edge-case asterisk (the puppet Device support, which
> I've never used), yes. The agent is a piece of software that runs (as a
> daemon
With a very small edge-case asterisk (the puppet Device support, which I've
never used), yes. The agent is a piece of software that runs (as a daemon,
via cron, manually, or via some other scheduling mechanism like
mcollective) on a host ("node" in Puppet nomenclature) and applies catalogs
to that
Thanks Jason. If I ever get to 1000 nodes, then I guess I'll have something
to worry about, then. LOL! One final question.
An 'agent' is really a managed server instance, not a Puppet worker
managing something else, (as the word 'Agent' would suggest). So really,
Agents only apply catalogs to them
Agents never control other agents. Aside from supporting technology
(PuppetDB, an ENC if you have one, a database to back PuppetDB), yeah, a
master and N agents is the gist of it.
There are some docs online (see specifically the "Tuning and Scaling"
section of the Puppet Documentation Index,
https
Been burnnig up the keyboard and spewing packets to search for this answer,
but haven't seen it.
>From what I've read, there is only:
A/ A Puppet Master
B/ Infinite number of 'Agent' nodes.
Is this right?
Is there any other kinds of nodes?
Do Agent nodes ever control other nodes?
What hap
