More information along these lines, highlighting ease of use and tools
for users to see their catalogs, will go along way towards soothing us
touchy sysadmins. The performance gains while nice don't have the appeal
of better troubleshooting. I'm happy to learn yet another stack, but I'd
like t
Hello,
When I tried adding a node to my puppet server running puppet 3.7.1 (on
both server and the client) I'm getting an error stating that puppet can't
find the node definition:
Warning: Unable to fetch my node definition, but the agent run will
continue:
Warning: Error 400 on SERVER: Failed t
> (1) at my current shop, there's an immense hatred of everything JVM. That's
> going to be a hard transition. Not to mention Puppet is the only place we
> run Ruby, so it's nice and easy to let puppet do whatever it wants with Ruby.
> Not so much for installing JVMs that may break production (im
> Hmm... I didn't even know this existed. Ironically, given your question, it
> sounds like something I'd want to use. But if it's going away, I guess I'll
> just totally forget that I heard it...
Oh to be clear Jason, the functionality is of course still staying for
PuppetDB :-). Its just the tra
Yeah. I found an error in the puppetlabs-mcollective module (
https://tickets.puppetlabs.com/browse/MODULES-1192) where it doesn't work
with "trusted_node_data = true", which per the docs is a 3.6.2 recommended
safe setting. When I was testing my fix, I made the mistake of running
specs with future
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
IMO there's no sane way to do this automatically. What would it do, put
every file on the system into a module? The code certainly wouldn't be
properly modularized and parameterized, and would be a maintenance
nightmare.
On Thu, Sep 25, 2014 at 8:42 AM, Paul Tötterman
wrote:
> Anyone knows if th
Not built-in to puppet, but this should be trivial to do with nmap or a
similar tool and a list of the nodes that *are* running puppet.
On Fri, Sep 26, 2014 at 10:35 AM, kaustubh chaudhari
wrote:
> Hi,
>
> Just had a though if this is possible. I have seen this feature in HPSA.
>
> Is there a wa
What facter versions are you running?
On Fri, Sep 26, 2014 at 6:02 AM, kaustubh chaudhari
wrote:
>
> Hi,
>
> I am also facing same issue. unable to find where to look for, puppet
> agent runes file facter runes fine if run manually.
>
>
> But schedule run still not working.
>
> Any help is appre
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
Hmm... I didn't even know this existed. Ironically, given your question, it
sounds like something I'd want to use. But if it's going away, I guess I'll
just totally forget that I heard it...
Use case: We still have a bunch of legacy systems that aren't puppetized
and probably never will be (lots o
IMO...
The "right" way to do this is to use a parameterized class in your module
that generates the config files.
Beyond that, it's up to you how you set that parameter to the correct value
for a node - you could use Hiera, you could use an ENC, or if you still
have a small setup and are using no
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
FWIW,
(1) at my current shop, there's an immense hatred of everything JVM. That's
going to be a hard transition. Not to mention Puppet is the only place we
run Ruby, so it's nice and easy to let puppet do whatever it wants with
Ruby. Not so much for installing JVMs that may break production (impro
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
16 matches
Mail list logo
