I'm new to puppet and am working on testing it at this point. I'm
interested in generating some custom reports, but can't figure out where to
place them or how to include them in the console.
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To
Using puppet 3.0.1, can exec ENC see the incoming environment value?
Perhaps indirectly from a log or report somewhere?
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an e
List
I want to have a per server snmp password setup. When I set it up as below
and run the client it is unable to process the module because it cannot
find the $snmp_password.
Is there a way to export a $variable from a node so it can be read when the
node processes one of its inherited modu
Is there an api (rest or gem) to delete a node and also remove from the
dashboard?
To delete the node like "node clean ", I did not see a remove
node in the rest api docs, just a remove the certificate call
Not sure of even a command-line to remove from the dashboard.
Better even if one call?
Greetings!
Thanks for all the pointers in the right direction. I was finally able to
figure it out today. I figured I would post my solution in case someone
else finds this thread later on and might be able to use it. I am running
this on a few servers successfully, but again, I just figured it
Does puppet have a menas to do what chkconfig --del does?
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To post to t
Windows NuBQ:
I'm running windows with a clean install of puppet and an empty node
definition. puppet agent -t pauses with no prompt. When I hit enter, I
get this warning:
Using Facter::Util::Resolution.exec with a shell built-in is deprecated.
Most built-ins can be replaced with native ruby
On Thursday, April 11, 2013 5:49:16 PM UTC-4, Jens Fahnenbruck wrote:
> I seem to have the same problem, did you solve it?
>
I did not solve the actual problem, no.
I moved forward with the project by going to master-less Puppet.
>
> On Thursday, December 13, 2012 6:05:00 PM UTC+1, jblaine wr
- Original Message -
> From: "Josh"
> To: puppet-users@googlegroups.com
> Sent: Friday, April 12, 2013 5:07:48 PM
> Subject: Re: [Puppet Users] MCollective and Puppet with periodic runs disabled
>
> On Friday, April 12, 2013 4:41:24 PM UTC+1, R.I. Pienaar wrote:
>
> > so it works now?
On Friday, April 12, 2013 4:41:24 PM UTC+1, R.I. Pienaar wrote:
> so it works now?
>
> if not - first make sure 'mco rpc rpcutil ping -I your.node' works
> when that works the rest will also work.
>
No, still not working, and the ping (and everything else for that matter
just as inventory) wo
- Original Message -
> From: "Josh"
> To: puppet-users@googlegroups.com
> Sent: Friday, April 12, 2013 4:31:45 PM
> Subject: Re: [Puppet Users] MCollective and Puppet with periodic runs disabled
>
> On Friday, April 12, 2013 4:23:14 PM UTC+1, R.I. Pienaar wrote:
>
> > everywhere, all c
On Friday, April 12, 2013 4:23:14 PM UTC+1, R.I. Pienaar wrote:
> everywhere, all client.cfg and server.cfg.
Yup, it is everywhere then
Josh
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving
On Friday, April 12, 2013 3:54:16 PM UTC+1, ForumUser wrote:
>
> what if I have 192.168.* with exception of 192.168.100.* ?
> Is the order in case statement important ?
> E.g.:
>
> case $::ipaddress_eth0 {
> /^192.168.100/: { $nameserver = '192.168.100.254' }
> /^192.168./: { $nameserver = '192.1
- Original Message -
> From: "Josh"
> To: puppet-users@googlegroups.com
> Sent: Friday, April 12, 2013 4:21:38 PM
> Subject: Re: [Puppet Users] MCollective and Puppet with periodic runs disabled
>
> On Friday, April 12, 2013 3:55:49 PM UTC+1, R.I. Pienaar wrote:
>
> > you need this eve
On Friday, April 12, 2013 3:55:49 PM UTC+1, R.I. Pienaar wrote:
> you need this everywhere if you set it...
>
It is in the client.cfg and the server.cfg across both hosts. I don't need
to add anything into my activemq configuration do I?
Josh
--
You received this message because you are subs
- Original Message -
> From: "Josh"
> To: puppet-users@googlegroups.com
> Sent: Friday, April 12, 2013 3:43:34 PM
> Subject: Re: [Puppet Users] MCollective and Puppet with periodic runs disabled
>
> On Friday, April 12, 2013 3:10:05 PM UTC+1, R.I. Pienaar wrote:
>
> > can you show your
Josh,
what if I have 192.168.* with exception of 192.168.100.* ?
Is the order in case statement important ?
E.g.:
case $::ipaddress_eth0 {
/^192.168.100/: { $nameserver = '192.168.100.254' }
/^192.168./: { $nameserver = '192.168.1.254' }
}
On Friday, 12 April 2013 10:09:00 UTC+1, Josh wrote:
On Friday, April 12, 2013 3:10:05 PM UTC+1, R.I. Pienaar wrote:
> can you show your client.cfg either /etc/mcollective/client.cfg or
> ~/.mcollective
> where you ran this 'mco rpc' command?
>
Almost the same as the server.cfg tbh:
topicprefix = /topic/
main_collective = mcollective
collec
- Original Message -
> From: "Josh"
> To: puppet-users@googlegroups.com
> Sent: Friday, April 12, 2013 2:04:45 PM
> Subject: Re: [Puppet Users] MCollective and Puppet with periodic runs disabled
>
> On Friday, April 12, 2013 12:13:12 PM UTC+1, R.I. Pienaar wrote:
>
> > ok - so if you d
Hi John,
Thanks for the reply. It turns out "puppet cert clean" is not good enough,
one has to restart either puppetmaster or the httpd service (I am running
puppetmaster behind apache) to clean it up from memory.
--
On Friday, April 12, 2013 9:01:13 AM UTC-5, jcbollinger wrote:
>
>
>
> O
On Thursday, April 11, 2013 11:30:45 AM UTC-5, iamauser wrote:
>
> I revoked the certificate of one of the clients by issuing the following
> command on puppetmaster :
>
> puppet cert clean
>
> Then tried to access the catalog from via :
>
>puppet agent --server=puppet
>
> and I c
On Thursday, April 11, 2013 1:11:16 PM UTC-5, Rahul Khengare wrote:
>
> Hi all,
> I am writing two modules abc and xyz. In both the modules i have to
> change common "test.txt" file,here i use template (.erb) file to changing
> the contents.
> In both abc and xyz the contents of "test.txt"
On Friday, April 12, 2013 12:13:12 PM UTC+1, R.I. Pienaar wrote:
> ok - so if you did 'mco rpc puppet runonce -I training-node1' do you get
> the
> same timeout error?
>
Yes. Output:
root@training-puppetmaster:~# mco rpc puppet runonce -I training-node1
* [ ==
I use Subversion to maintain the $confdir of my puppet-masters and I just
discovered that when one does an upgrade, the entire tree is blown away and
replaced -- all my .svn directories are gone.
I see nothing in the documentation (man page and such) to address this.
Suggestions ?
“Sometimes I
- Original Message -
> From: "Josh"
> To: puppet-users@googlegroups.com
> Sent: Friday, April 12, 2013 12:11:36 PM
> Subject: Re: [Puppet Users] MCollective and Puppet with periodic runs disabled
>
> On Friday, April 12, 2013 11:44:44 AM UTC+1, R.I. Pienaar wrote:
>
> > OK - and on tra
On Friday, April 12, 2013 11:44:44 AM UTC+1, R.I. Pienaar wrote:
> OK - and on training-node1 what is in mcollective server.cfg and if you
> have in /etc/mcollective/plugin.d/puppet.cfg ?
>
The server.cfg (just password auth while I am testing):
topicprefix = /topic/
main_collective = mcollect
- Original Message -
> From: "Josh"
> To: puppet-users@googlegroups.com
> Sent: Friday, April 12, 2013 11:38:04 AM
> Subject: Re: [Puppet Users] MCollective and Puppet with periodic runs disabled
>
> Sorry, slack of me:
>
> *Running:*
> *
> *
> mco puppet -v runall 2
>
> *Agent Confi
Sorry, slack of me:
*Running:*
*
*
mco puppet -v runall 2
*Agent Config:*
*
*
[main]
logdir=/var/log/puppet
vardir=/var/lib/puppet
ssldir=/var/lib/puppet/ssl
rundir=/var/run/puppet
factpath=$vardir/lib/facter
templatedir=$confdir/templates
[agent]
server = puppetmaster
ca_s
- Original Message -
> From: "Josh"
> To: puppet-users@googlegroups.com
> Sent: Friday, April 12, 2013 10:33:17 AM
> Subject: Re: [Puppet Users] MCollective and Puppet with periodic runs disabled
>
> On Friday, April 12, 2013 10:13:28 AM UTC+1, R.I. Pienaar wrote:
>
> > you do not need
We are not using Hiera yet (but it seems that this is what we should do in
the close future ...)
At the moment the regexp expression is the simplest one.
Thank you :-)
On Friday, 12 April 2013 10:09:00 UTC+1, Josh wrote:
>
> On Friday, April 12, 2013 9:44:31 AM UTC+1, ForumUser wrote:
>
>> We hav
On Friday, April 12, 2013 10:13:28 AM UTC+1, R.I. Pienaar wrote:
> you do not need to have puppet running for the agent to work, just stop it
> entirely and then trigger runs through mcollective - in that setup it will
> happily pass custom arguments like --noop or --no-noop etc
>
Right, I was
- Original Message -
> From: "Josh"
> To: puppet-users@googlegroups.com
> Sent: Friday, April 12, 2013 10:01:13 AM
> Subject: [Puppet Users] MCollective and Puppet with periodic runs disabled
>
> Hi,
>
> I have looked all over the place and can't seem to find a complete answer
> to my
On Friday, April 12, 2013 9:44:31 AM UTC+1, ForumUser wrote:
> We have nodes in different networks - they use different DNS servers.
> I'd like to set up its /etc/resolv.conf dependent on network they are in.
>
Are you using Hiera? We run multiple datacentres that have different
management netwo
Hi,
I have looked all over the place and can't seem to find a complete answer
to my query
I am setting up MCollective to run alongside my puppet deployment and am
having some problems getting it to play as I want it to
Basically, I need to make sure that puppet NEVER makes any changes without
Hello,
I am a beginner in puppet so please excuse my lack of knowledge.
(I use puppet 3.1).
We have nodes in different networks - they use different DNS servers.
I'd like to set up its /etc/resolv.conf dependent on network they are in.
What approach would you recommend to solve the problem ?
Th
35 matches
Mail list logo