Re: [Puppet Users] hosts update trouble

Ohad Levy
2010-01-26T01:51:58Z

I can offer two more options..

   1. I didn''t want to enable puppetd to start a whole webserver
(puppetd
   starts a webrick when listen=true) esp due to the amount of memory used, so
   I wrote puppetlisten and puppetrun - which is based on a smaller footprint
   daemon which does more or less the same as puppetrun - you might consider
   using it - its in the ext directory of puppet
   http://github.com/ohadlevy/puppet/tree/puppetlisten/ext/puppetlisten/
   2. Use foreman query interface to feed a ssh based script - see
   http://theforeman.org/wiki/foreman/Query_Interface ; this will allow you
   to define on which hosts you want to trigger an action (e.g. only hosts that
   has fact=value or based on classes etc).

cheers,
Ohad

On Mon, Jan 25, 2010 at 9:46 PM, Christopher Johnston
<chjohnst@gmail.com>wrote:

> I thought puppetrun _requires_ putting all your nodes into LDAP?  Is that
> not the case anymore? (I am using version 0.24.8-4 from Fedora 10)
>
> -Chris
>
>
> On Sun, Jan 24, 2010 at 8:28 PM, Carl Caum <carl.caum@gmail.com>
wrote:
>
>> Add:
>>
>> ignoreschedules = true
>>
>> to your puppet.conf.  I think you can also set
>>
>> listen = true
>>
>> and that will disable runs and just run when triggered by authorized
>> nodes.  Others will know more about that than me.  Anyone care to jump
in?
>>
>> On Jan 22, 2010, at 7:14 PM, Christopher Johnston wrote:
>>
>> > How do you disable autorun?
>> >
>> > Sent from my iPhone
>> >
>> > On Jan 22, 2010, at 3:29 PM, Carl Caum <carl.caum@gmail.com>
wrote:
>> >
>> >> I''ve run in to the same problem.  I''ve
started to solve this problem by
>> getting rid of puppetmasters and puppetd.  Instead I''m
building a new
>> management tool called Puppeteer.  I''m almost ready to begin
testing, but
>> it''s not ready for others to try yet.  I''ll post to
the list when it''s read
>> for others to try.
>> >>
>> >> In the mean time, look in to using puppetrun to trigger a run
on the
>> clients and set the clients to never autorun.  Then you build a quick
tool
>> that sends out puppetrun commands in a way you decide.  Of course, you
can
>> also trigger runs manually this way.  I know Reductive Lab''s
>> puppet-dashboard will support triggering client runs in the future.
Maybe
>> it''s better to wait for that or for Puppeteer.
>> >>
>> >> On Jan 13, 2010, at 7:52 AM, Arnauld wrote:
>> >>
>> >>> Hi,
>> >>>
>> >>> I do not know if it''s a bug, a feature or
something I didn''t
>> >>> understood, but it''s I can''t update my
clients hosts "synchronously".
>> >>> What I mean by "synchronously" is that when I
push a new configuration
>> >>> on my master server, I do not know when my clients will be
updated.
>> >>> And it also appears that some clients get their whole new
>> >>> configuration in less than 1 hour whereas some other
clients can get
>> >>> their new configuration in some few days.
>> >>>
>> >>> What I would like is to deploy automaticaly my new
configuration on
>> >>> all my clients at a given time (for example when I restart
the puppetd
>> >>> daemon).
>> >>>
>> >>> Is it possible ?
>> >>>
>> >>> Arnauld
>> >>> --
>> >>> You received this message because you are subscribed to
the Google
>> Groups "Puppet Users" group.
>> >>> To post to this group, send email to
puppet-users@googlegroups.com.
>> >>> To unsubscribe from this group, send email to
>>
puppet-users+unsubscribe@googlegroups.com<puppet-users%2Bunsubscribe@googlegroups.com>
>> .
>> >>> For more options, visit this group at
>> http://groups.google.com/group/puppet-users?hl=en.
>> >>>
>> >>>
>> >>
>> >> --
>> >> You received this message because you are subscribed to the
Google
>> Groups "Puppet Users" group.
>> >> To post to this group, send email to
puppet-users@googlegroups.com.
>> >> To unsubscribe from this group, send email to
>>
puppet-users+unsubscribe@googlegroups.com<puppet-users%2Bunsubscribe@googlegroups.com>
>> .
>> >> For more options, visit this group at
>> http://groups.google.com/group/puppet-users?hl=en.
>> >>
>> >
>> > --
>> > You received this message because you are subscribed to the Google
>> Groups "Puppet Users" group.
>> > To post to this group, send email to
puppet-users@googlegroups.com.
>> > To unsubscribe from this group, send email to
>>
puppet-users+unsubscribe@googlegroups.com<puppet-users%2Bunsubscribe@googlegroups.com>
>> .
>> > For more options, visit this group at
>> http://groups.google.com/group/puppet-users?hl=en.
>> >
>>
>> --
>> You received this message because you are subscribed to the Google
Groups
>> "Puppet Users" group.
>> To post to this group, send email to puppet-users@googlegroups.com.
>> To unsubscribe from this group, send email to
>>
puppet-users+unsubscribe@googlegroups.com<puppet-users%2Bunsubscribe@googlegroups.com>
>> .
>> For more options, visit this group at
>> http://groups.google.com/group/puppet-users?hl=en.
>>
>>
>  --
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To post to this group, send email to puppet-users@googlegroups.com.
> To unsubscribe from this group, send email to
>
puppet-users+unsubscribe@googlegroups.com<puppet-users%2Bunsubscribe@googlegroups.com>
> .
> For more options, visit this group at
> http://groups.google.com/group/puppet-users?hl=en.