Puppet users - Jun 2011 - Make puppet automatically recognize new files in nodes directory?

So, instead of defining all my nodes in one file, I use what seems to
be a fairly common practice, from site.pp I do:

import ''nodes/*''

Then I have a nodes directory containing a .pp file for each node.
The only problem with this setup is that puppet seems oblivious to new
node files in the nodes directory until you do a "service puppetmaster
restart".  Is there any way to have puppet automatically find those
new files without restarting?  Alternately, does anyone have a good
method for automating the necessary restart?  Thanks.

-- 
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.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

touch site.pp?
On Jun 23, 2011 1:01 PM, "Pheran" <pheran@gmail.com>
wrote:
> So, instead of defining all my nodes in one file, I use what seems to
> be a fairly common practice, from site.pp I do:
>
> import ''nodes/*''
>
> Then I have a nodes directory containing a .pp file for each node.
> The only problem with this setup is that puppet seems oblivious to new
> node files in the nodes directory until you do a "service puppetmaster
> restart". Is there any way to have puppet automatically find those
> new files without restarting? Alternately, does anyone have a good
> method for automating the necessary restart? Thanks.
>
> --
> 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.
> 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.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

Hmm, if that''s enough to make it reread all the nodes, then I suppose
I could have my git hook scripts that syncs the puppet manifests from
my git repo always touch the site.pp file after it fires.  Any other
good methods for handling this?

On Jun 23, 4:05 pm, Aaron Grewell <aaron.grew...@gmail.com>
wrote:
> touch site.pp?
> On Jun 23, 2011 1:01 PM, "Pheran" <phe...@gmail.com>
wrote:> So, instead of defining all my nodes in one file, I use what seems to
> > be a fairly common practice, from site.pp I do:
>
> > import ''nodes/*''
>
> > Then I have a nodes directory containing a .pp file for each node.
> > The only problem with this setup is that puppet seems oblivious to new
> > node files in the nodes directory until you do a "service
puppetmaster
> > restart". Is there any way to have puppet automatically find
those
> > new files without restarting? Alternately, does anyone have a good
> > method for automating the necessary restart? Thanks.
>
> > --
> > 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.> 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.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

I don''t believe so.  I don''t have time to dig deeply into the
code and
confirm right now, but I believe we don''t model include operations as
a glob, just as the resultant set of files to watch.  Touching site.pp
will trigger it to reparse, which will re-run the import operation and
watch those files for changes.

So, I think this is the only present solution for the issue; you might
want to find the existing bug (which I bet there is, but file a new
one if you can''t turn it up) and add your voice to those asking that
it get fixed. :)

Regards,
    Daniel

On Thu, Jun 23, 2011 at 13:10, Pheran <pheran@gmail.com>
wrote:
> Hmm, if that''s enough to make it reread all the nodes, then I
suppose
> I could have my git hook scripts that syncs the puppet manifests from
> my git repo always touch the site.pp file after it fires.  Any other
> good methods for handling this?
>
> On Jun 23, 4:05 pm, Aaron Grewell <aaron.grew...@gmail.com> wrote:
>> touch site.pp?
>> On Jun 23, 2011 1:01 PM, "Pheran" <phe...@gmail.com>
wrote:> So, instead of defining all my nodes in one file, I use what seems to
>> > be a fairly common practice, from site.pp I do:
>>
>> > import ''nodes/*''
>>
>> > Then I have a nodes directory containing a .pp file for each node.
>> > The only problem with this setup is that puppet seems oblivious to
new
>> > node files in the nodes directory until you do a "service
puppetmaster
>> > restart". Is there any way to have puppet automatically find
those
>> > new files without restarting? Alternately, does anyone have a good
>> > method for automating the necessary restart? Thanks.
>>
>> > --
>> > 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.> 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.
> For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
>
>


-- 
⎋ Puppet Labs Developer – http://puppetlabs.com
✉ Daniel Pittman <daniel@puppetlabs.com>
✆ Contact me via gtalk, email, or phone: +1 (877) 575-9775
♲ Made with 100 percent post-consumer electrons

-- 
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.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

I have a similar command in my svn post-commit.  It works well for
convincing Puppet that something has happened.

On Thu, Jun 23, 2011 at 1:10 PM, Pheran <pheran@gmail.com> wrote:
> Hmm, if that''s enough to make it reread all the nodes, then I
suppose
> I could have my git hook scripts that syncs the puppet manifests from
> my git repo always touch the site.pp file after it fires.  Any other
> good methods for handling this?
>
> On Jun 23, 4:05 pm, Aaron Grewell <aaron.grew...@gmail.com> wrote:
> > touch site.pp?
> > On Jun 23, 2011 1:01 PM, "Pheran" <phe...@gmail.com>
wrote:> So, instead
> of defining all my nodes in one file, I use what seems to
> > > be a fairly common practice, from site.pp I do:
> >
> > > import ''nodes/*''
> >
> > > Then I have a nodes directory containing a .pp file for each
node.
> > > The only problem with this setup is that puppet seems oblivious
to new
> > > node files in the nodes directory until you do a "service
puppetmaster
> > > restart". Is there any way to have puppet automatically find
those
> > > new files without restarting? Alternately, does anyone have a
good
> > > method for automating the necessary restart? Thanks.
> >
> > > --
> > > 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.> 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.
> 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.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.