Turn off client autoupdate

382 views
Skip to first unread message

Sergey V. Arlashin

unread,
Jun 24, 2011, 4:47:56 AM6/24/11
to Puppet Users
By default puppet node connects to server periodically and looks if
there is something execute. I'm wondering is it possible to make
puppet clients not connect to server themselves? So that it would be
possible to update a node only with puppetrun nodename.

---
WBR, Sergey

Sergey V. Arlashin

unread,
Jun 23, 2011, 5:47:20 PM6/23/11
to Puppet Users
Hello!

sergey

unread,
Jun 23, 2011, 6:07:47 PM6/23/11
to puppet...@googlegroups.com

Nathan Clemons

unread,
Jun 24, 2011, 10:10:38 AM6/24/11
to puppet...@googlegroups.com
Just disable the puppet agent / puppetd (depending on your version) in chkconfig / update-rc.d / etc.

Further runs would then be done via ssh, either manually or via a distributed ssh command like ralsh, pdsh, clusterssh, etc.

This is what we do at Livemocha; we're actually in the process of switching over to using MCollective to trigger Puppet runs.

--
Nathan Clemons
The worlds largest online language learning community




--
You received this message because you are subscribed to the Google Groups "Puppet Users" group.
To post to this group, send email to puppet...@googlegroups.com.
To unsubscribe from this group, send email to puppet-users...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.


sergey

unread,
Jun 24, 2011, 10:14:55 AM6/24/11
to puppet...@googlegroups.com
And how is it possible to connect to puppet client via ssh? I mean I usually issue puppetrun nodename and then puppetmaster  connects to puppet client on the client node. What should I do in case of ssh connect? 

---
WBR, Sergey

Daniel Maher

unread,
Jun 24, 2011, 10:31:19 AM6/24/11
to puppet...@googlegroups.com
On 06/24/2011 04:10 PM, Nathan Clemons wrote:
>
> This is what we do at Livemocha; we're actually in the process of
> switching over to using MCollective to trigger Puppet runs.

By way of a vote of confidence, we made the switch to MC-triggered
Puppet runs a few months ago and have been very happy with the result.
Implementing Puppet Commander[1] in order to manage the trigger events
was about as straightforward as it gets !

[1]
http://projects.puppetlabs.com/projects/mcollective-plugins/wiki/ToolPuppetcommander

--
Daniel Maher
� makin' plans now to live on Mars 'cuz I got Earth on lock. �

Ken Barber

unread,
Jun 24, 2011, 10:34:04 AM6/24/11
to puppet...@googlegroups.com
I concur. Using mcollective to trigger Puppet is sweet.

ken.

> « makin' plans now to live on Mars 'cuz I got Earth on lock. »

Nathan Clemons

unread,
Jun 24, 2011, 12:43:10 PM6/24/11
to puppet...@googlegroups.com
Under 0.25, we do "puppet --onetime --no-daemonize".

I'm not sure if that syntax changed in 2.6.x and above.

--
Nathan Clemons
The worlds largest online language learning community



jcbollinger

unread,
Jun 24, 2011, 2:29:04 PM6/24/11
to Puppet Users


On Jun 24, 9:14 am, sergey <sergey...@gmail.com> wrote:
> And how is it possible to connect to puppet client via ssh? I mean I usually issue puppetrun nodename and then puppetmaster  connects to puppet client on the client node. What should I do in case of ssh connect?

One does not connect to the puppet client *software*; rather, one
connectes to the puppet client *machine*. The software (puppetd or
puppet agent, depending on the version) is after all not running as a
daemon. Once connected, you execute a command such as "puppet agent --
onetime --no-daemonize".

If you wish to use it, command-line ssh clients typically provide a
means to specify a command to run on the remote machine instead of a
login shell (e.g. "puppet agent [...]"); this is convenient for
scripting.


John

sergey

unread,
Jun 24, 2011, 2:30:56 PM6/24/11
to puppet...@googlegroups.com
Thank you!

---
WBR, Sergey

Jacob Helwig

unread,
Jun 24, 2011, 2:39:20 PM6/24/11
to puppet...@googlegroups.com

You'd probably be interested in #4411[1] and #3313[2].

Specifically, it looks like the way you should be able to do this is by
specifying "listen=true" and "client=false", but there appears to be a
bug with the agent that makes "client=false" not actually work, but
("--no-client" on the command line does work). :-/

[1] http://projects.puppetlabs.com/issues/4411
[2] http://projects.puppetlabs.com/issues/3313

--
Jacob Helwig

signature.asc

sergey

unread,
Jun 24, 2011, 3:18:58 PM6/24/11
to puppet...@googlegroups.com
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Thank you! This is what I was looking for :) "--no-client" DOES work.
P.S. I should have read man puppetd before sending this message. :)

-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.17 (Darwin)
Comment: GPGTools - http://gpgtools.org

iQEcBAEBAgAGBQJOBOMiAAoJEPQ905NMSvKrpLsIAMD/sUsdJDCOW9L0WGXKjLFz
BQ9OFmReZx2MSDtXpgzhioOsJ0lMBeTlQ0RWEv5oEtz7senIwbWSyW9hGzHgpujW
nm0ZLk7bURW7Fn0z8zVw7ueS70RnMgq0MTeLNSQBZk/dCjBDxu72HSg2O9jAxW8x
z49AZVT9TWNjSMIaihF4V5GpbxdAKRb7iqbbNEJAYHRiGodgwjwJywQl8JWRBTg3
1dLzlAr24bzxusApMMNf+7aYPgYQSzyp2jfIpgx3HEp0D3tO3Wv4dmYqUf8YFWG7
Q+uYjnq+PiYeSNxTF2w/F9D5XU5wEbgnnV0r5TrLws5KsKrl4VZ3q4JEmPh0Zzg=
=nyL2
-----END PGP SIGNATURE-----

Denmat

unread,
Jun 24, 2011, 6:07:12 PM6/24/11
to puppet...@googlegroups.com
Hi,

You're looking for something like this.

http://docs.puppetlabs.com/mcollective/index.html

Reply all
Reply to author
Forward
0 new messages