trey85stang
2011-Apr-22 18:34 UTC
[Puppet Users] scheduling package installs - ignore schedule if not installed
Is there a way to override a schedule for a package if the package is
not installed?
class packages {
schedule { installs:
range => "2-4",
period => daily,
repeat => 1,
}
package { openssh:
ensure => latest,
schedule => installs,
}
}
I dont want to check if openssh is the latest package everytime puppet
runs; but I do want it installed if it is not already installed
regardless of the schedule.
Anyway to do this?
--
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.
Steven Acres
2011-Apr-23 02:01 UTC
Re: [Puppet Users] scheduling package installs - ignore schedule if not installed
On Fri, Apr 22, 2011 at 2:34 PM, trey85stang <trey85stang@gmail.com> wrote:> Is there a way to override a schedule for a package if the package is > not installed? > > class packages { > schedule { installs: > range => "2-4", > period => daily, > repeat => 1, > } > package { openssh: > ensure => latest, > schedule => installs, > } > } > > I dont want to check if openssh is the latest package everytime puppet > runs; but I do want it installed if it is not already installed > regardless of the schedule. > > Anyway to do this? > >Hi, Sure, there are many ways to achieve this. You would be better off defining which packages should be present on which nodes in another class. Then use an include in the node(s) definition (or whatever method you have defined for your architecture structure). BTW, if you''re using yum and you would like to keep pkgs. updated, you may want to look into yum-cron. -- Cheers, Steven ----------------------- Steven Acres UNIX/Linux System Administrator -- 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.
Felix Frank
2011-Apr-28 07:36 UTC
Re: [Puppet Users] scheduling package installs - ignore schedule if not installed
On 04/23/2011 04:01 AM, Steven Acres wrote:> On Fri, Apr 22, 2011 at 2:34 PM, trey85stang <trey85stang@gmail.com > <mailto:trey85stang@gmail.com>> wrote: > > Is there a way to override a schedule for a package if the package is > not installed? > > class packages { > schedule { installs: > range => "2-4", > period => daily, > repeat => 1, > } > package { openssh: > ensure => latest, > schedule => installs, > } > } > > I dont want to check if openssh is the latest package everytime puppet > runs; but I do want it installed if it is not already installed > regardless of the schedule. > > Anyway to do this? > > > Hi, > > Sure, there are many ways to achieve this. You would be better off > defining which packages should be present on which nodes in another > class. Then use an include in the node(s) definition (or whatever method > you have defined for your architecture structure). > > BTW, if you''re using yum and you would like to keep pkgs. updated, you > may want to look into yum-cron.Hi, I don''t agree. Telling puppet to "install at all times but update only on a specific schedule" is not trivial if at all possible. Doing the upgrades outside the package provider may indeed be a sensible workaround. Cheers, Felix -- 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.
Steven Acres
2011-May-06 02:51 UTC
Re: [Puppet Users] scheduling package installs - ignore schedule if not installed
On Thu, Apr 28, 2011 at 3:36 AM, Felix Frank < felix.frank@alumni.tu-berlin.de> wrote:> On 04/23/2011 04:01 AM, Steven Acres wrote: > > On Fri, Apr 22, 2011 at 2:34 PM, trey85stang <trey85stang@gmail.com > > <mailto:trey85stang@gmail.com>> wrote: > > > > Is there a way to override a schedule for a package if the package is > > not installed? > > > > class packages { > > schedule { installs: > > range => "2-4", > > period => daily, > > repeat => 1, > > } > > package { openssh: > > ensure => latest, > > schedule => installs, > > } > > } > > > > I dont want to check if openssh is the latest package everytime > puppet > > runs; but I do want it installed if it is not already installed > > regardless of the schedule. > > > > Anyway to do this? > > > > > > Hi, > > > > Sure, there are many ways to achieve this. You would be better off > > defining which packages should be present on which nodes in another > > class. Then use an include in the node(s) definition (or whatever method > > you have defined for your architecture structure). > > > > BTW, if you''re using yum and you would like to keep pkgs. updated, you > > may want to look into yum-cron. > > Hi, > > I don''t agree. Telling puppet to "install at all times but update only > on a specific schedule" is not trivial if at all possible. > > Doing the upgrades outside the package provider may indeed be a sensible > workaround. > > Cheers, > Felix > > -- > 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. > > Hi all,Easy as could be .. simple conditionals and cron, at .... if we''re in the ''old'' days .. but since we now have the ''magic'' of pkg. managers ... we manage this effortlessly now. Not only does this free time to catch up on BOFH ... it also ties into DR, auditing and compliance (i.e. PCI-DSS) which need to be included and documented in our architectural process/design. The most time is and should be spent on that design and the rest is primarily fine-tuning. -- Cheers, Steven ----------------------- Steven Acres UNIX/Linux System Administrator -- 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.
Martin Willemsma
2011-May-06 08:23 UTC
Re: [Puppet Users] scheduling package installs - ignore schedule if not installed
Hi Steven, Do you mind sharing how you manage this with us here or in some sort of a blog post? Martin 2011/5/6 Steven Acres <admin@swatteksystems.com>> On Thu, Apr 28, 2011 at 3:36 AM, Felix Frank < > felix.frank@alumni.tu-berlin.de> wrote: > >> On 04/23/2011 04:01 AM, Steven Acres wrote: >> > On Fri, Apr 22, 2011 at 2:34 PM, trey85stang <trey85stang@gmail.com >> > <mailto:trey85stang@gmail.com>> wrote: >> > >> > Is there a way to override a schedule for a package if the package >> is >> > not installed? >> > >> > class packages { >> > schedule { installs: >> > range => "2-4", >> > period => daily, >> > repeat => 1, >> > } >> > package { openssh: >> > ensure => latest, >> > schedule => installs, >> > } >> > } >> > >> > I dont want to check if openssh is the latest package everytime >> puppet >> > runs; but I do want it installed if it is not already installed >> > regardless of the schedule. >> > >> > Anyway to do this? >> > >> > >> > Hi, >> > >> > Sure, there are many ways to achieve this. You would be better off >> > defining which packages should be present on which nodes in another >> > class. Then use an include in the node(s) definition (or whatever method >> > you have defined for your architecture structure). >> > >> > BTW, if you''re using yum and you would like to keep pkgs. updated, you >> > may want to look into yum-cron. >> >> Hi, >> >> I don''t agree. Telling puppet to "install at all times but update only >> on a specific schedule" is not trivial if at all possible. >> >> Doing the upgrades outside the package provider may indeed be a sensible >> workaround. >> >> Cheers, >> Felix >> >> -- >> 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. >> >> Hi all, > > Easy as could be .. simple conditionals and cron, at .... if we''re in the > ''old'' days .. but since we now have the ''magic'' of pkg. managers ... we > manage this effortlessly now. Not only does this free time to catch up on > BOFH ... it also ties into DR, auditing and compliance (i.e. PCI-DSS) which > need to be included and documented in our architectural process/design. The > most time is and should be spent on that design and the rest is primarily > fine-tuning. > > > > -- > Cheers, > > Steven > ----------------------- > Steven Acres > UNIX/Linux System Administrator > > -- > 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. >-- Met vriendelijke groet, Martin Willemsma -- 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.
Steven Acres
2011-May-11 01:34 UTC
Re: [Puppet Users] scheduling package installs - ignore schedule if not installed
On Fri, May 6, 2011 at 4:23 AM, Martin Willemsma <mwillemsma@gmail.com>wrote:> Hi Steven, > > Do you mind sharing how you manage this with us here or in some sort of a > blog post? > > Martin > > > 2011/5/6 Steven Acres <admin@swatteksystems.com> > >> On Thu, Apr 28, 2011 at 3:36 AM, Felix Frank < >> felix.frank@alumni.tu-berlin.de> wrote: >> >>> On 04/23/2011 04:01 AM, Steven Acres wrote: >>> > On Fri, Apr 22, 2011 at 2:34 PM, trey85stang <trey85stang@gmail.com >>> > <mailto:trey85stang@gmail.com>> wrote: >>> > >>> > Is there a way to override a schedule for a package if the package >>> is >>> > not installed? >>> > >>> > class packages { >>> > schedule { installs: >>> > range => "2-4", >>> > period => daily, >>> > repeat => 1, >>> > } >>> > package { openssh: >>> > ensure => latest, >>> > schedule => installs, >>> > } >>> > } >>> > >>> > I dont want to check if openssh is the latest package everytime >>> puppet >>> > runs; but I do want it installed if it is not already installed >>> > regardless of the schedule. >>> > >>> > Anyway to do this? >>> > >>> > >>> > Hi, >>> > >>> > Sure, there are many ways to achieve this. You would be better off >>> > defining which packages should be present on which nodes in another >>> > class. Then use an include in the node(s) definition (or whatever >>> method >>> > you have defined for your architecture structure). >>> > >>> > BTW, if you''re using yum and you would like to keep pkgs. updated, you >>> > may want to look into yum-cron. >>> >>> Hi, >>> >>> I don''t agree. Telling puppet to "install at all times but update only >>> on a specific schedule" is not trivial if at all possible. >>> >>> Doing the upgrades outside the package provider may indeed be a sensible >>> workaround. >>> >>> Cheers, >>> Felix >>> >>> -- >>> 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. >>> >>> Hi all, >> >> Easy as could be .. simple conditionals and cron, at .... if we''re in the >> ''old'' days .. but since we now have the ''magic'' of pkg. managers ... we >> manage this effortlessly now. Not only does this free time to catch up on >> BOFH ... it also ties into DR, auditing and compliance (i.e. PCI-DSS) which >> need to be included and documented in our architectural process/design. The >> most time is and should be spent on that design and the rest is primarily >> fine-tuning. >> >> >> >> -- >> Cheers, >> >> Steven >> ----------------------- >> Steven Acres >> UNIX/Linux System Administrator >> >> -- >> 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. >> > > > > -- > Met vriendelijke groet, > > Martin Willemsma > > -- > 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. >Hi Martin, Sure, which process are you referring to? -- Cheers, Steven ----------------------- Steven Acres UNIX/Linux System Administrator -- 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.