Hello fellow puppeteers :) I was just wondering: would anyone benefit from puppet''s abitity to only do partial catalog runs? Additional explanation: As you manage your hosts with puppet, your catalog tends to grow and puppet runs are becoming longer. If you manage some overseas servers, runtime is even longer. What I was thinking about is being able to run just part of your catalog, for example just one stage, or just one module. This way one could trigger puppet run via mcollective, and only for run stage called "appconfig". This would check and/or modify only a dozen resources across clustered application setup, instead of doing the whole catalog run with thousands of resources. What do you guys think? Should I be looking into app deployment tools instead? A separate installation of dedicated puppet for this objective is also an option... Best regards, b. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/H_EXKAgASdwJ. 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 could also do this with Tags from the command line (https://puppetlabs.com/references/0.25.3/metaparameter.html#tag). If you run puppet agent -t --tags apache it will only declare the resources that are tagged with the ''apache'' tag. Tags are implicitly set through major scope levels (i.e. anything inside class ''ntp'' gets a tag of ''ntp'') but can also be set with the tag() function or the tag metaparameter. -- Gary Larizza Sent with Sparrow (http://www.sparrowmailapp.com/?sig) On Wednesday, May 9, 2012 at 4:45 PM, Bostjan Skufca wrote:> Hello fellow puppeteers :) > > I was just wondering: would anyone benefit from puppet''s abitity to only do partial catalog runs? > > Additional explanation: > As you manage your hosts with puppet, your catalog tends to grow and puppet runs are becoming longer. If you manage some overseas servers, runtime is even longer. > What I was thinking about is being able to run just part of your catalog, for example just one stage, or just one module. This way one could trigger puppet run via mcollective, and only for run stage called "appconfig". This would check and/or modify only a dozen resources across clustered application setup, instead of doing the whole catalog run with thousands of resources. > > What do you guys think? Should I be looking into app deployment tools instead? A separate installation of dedicated puppet for this objective is also an option... > > Best regards, > b. > > > -- > You received this message because you are subscribed to the Google Groups "Puppet Users" group. > To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/H_EXKAgASdwJ. > To post to this group, send email to puppet-users@googlegroups.com (mailto:puppet-users@googlegroups.com). > To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com (mailto: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.
Just realized I grabbed an OOOOOLD version of the docs. Here''s the latest --> https://puppetlabs.com/references/latest/metaparameter.html#tag -- Gary Larizza Sent with Sparrow (http://www.sparrowmailapp.com/?sig) On Wednesday, May 9, 2012 at 4:45 PM, Bostjan Skufca wrote:> Hello fellow puppeteers :) > > I was just wondering: would anyone benefit from puppet''s abitity to only do partial catalog runs? > > Additional explanation: > As you manage your hosts with puppet, your catalog tends to grow and puppet runs are becoming longer. If you manage some overseas servers, runtime is even longer. > What I was thinking about is being able to run just part of your catalog, for example just one stage, or just one module. This way one could trigger puppet run via mcollective, and only for run stage called "appconfig". This would check and/or modify only a dozen resources across clustered application setup, instead of doing the whole catalog run with thousands of resources. > > What do you guys think? Should I be looking into app deployment tools instead? A separate installation of dedicated puppet for this objective is also an option... > > Best regards, > b. > > > -- > You received this message because you are subscribed to the Google Groups "Puppet Users" group. > To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/H_EXKAgASdwJ. > To post to this group, send email to puppet-users@googlegroups.com (mailto:puppet-users@googlegroups.com). > To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com (mailto: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.
Aaah, that''s useful. I guess I''ve been searching for the wrong keywords (partial catalog run != tags). Thank you very much! b. On Thursday, 10 May 2012 01:45:24 UTC+2, Bostjan Skufca wrote:> > Hello fellow puppeteers :) > > I was just wondering: would anyone benefit from puppet''s abitity to only > do partial catalog runs? > > Additional explanation: > As you manage your hosts with puppet, your catalog tends to grow and > puppet runs are becoming longer. If you manage some overseas servers, > runtime is even longer. > What I was thinking about is being able to run just part of your catalog, > for example just one stage, or just one module. This way one could trigger > puppet run via mcollective, and only for run stage called "appconfig". This > would check and/or modify only a dozen resources across clustered > application setup, instead of doing the whole catalog run with thousands of > resources. > > What do you guys think? Should I be looking into app deployment tools > instead? A separate installation of dedicated puppet for this objective is > also an option... > > Best regards, > b. > > >-- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/eECavyRwSnwJ. 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.