Hi all, I''m runnign debian lenny and that has puppet 0.24.5 in it. Lenny- backports ahs Puppet 2.6.2 in it, which is what I want. How do I make puppet update itself through puppet recipes? I already had it create an /etc/apt/preferences, where I pin backports at 900 and lenny stable at 700. Is that correct? I don''t want to have to run apt-get update / apt-get upgrade / any other command on the nodes at all, but I don''t know how :) Walter -- 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.
On Fri, Nov 5, 2010 at 9:52 AM, Walter Heck <walterheck@gmail.com> wrote:> Hi all, > > I''m runnign debian lenny and that has puppet 0.24.5 in it. Lenny- > backports ahs Puppet 2.6.2 in it, which is what I want. How do I make > puppet update itself through puppet recipes? I already had it create > an /etc/apt/preferences, where I pin backports at 900 and lenny stable > at 700. Is that correct? I don''t want to have to run apt-get update / > apt-get upgrade / any other command on the nodes at all, but I don''t > know how :)You can''t get around running an `apt-get update` but you can do that from an exec resource in an earlier run stage. stage { pre: before => Stage["main"] } exec { "apt-get update": stage => "pre" } You''ll probably want to do your backports setup before the `apt-get update` in your early run stage, too. Richard -- 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.
On Nov 5, 2010, at 9:52 AM, Walter Heck wrote:> Hi all, > > I''m runnign debian lenny and that has puppet 0.24.5 in it. Lenny- > backports ahs Puppet 2.6.2 in it, which is what I want. How do I make > puppet update itself through puppet recipes? I already had it create > an /etc/apt/preferences, where I pin backports at 900 and lenny stable > at 700. Is that correct? I don''t want to have to run apt-get update / > apt-get upgrade / any other command on the nodes at all, but I don''t > know how :) > > WalterFirst, if you update puppet, it''s probably a good idea to update facter. Second, are you trying to use lenny-backports for everything or just puppet and related stuff? Are you using apache for anything other than puppet? Are you using ruby for more than just puppet? -- 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 Patrick, On Nov 6, 1:25 am, Patrick <kc7...@gmail.com> wrote:> First, if you update puppet, it''s probably a good idea to update facter.I thought that would be done by dependencies? If not, yes that is also what I need :)> Second, are you trying to use lenny-backports for everything or just puppet and related stuff?I think ''the official debian way'' is to only use backports for packages that you choose, not for everything, right?> Are you using apache for anything other than puppet?Not yet, but I will be. It''s going to be a setup used for shared hosting, and I haven''t found a more secure way to do that then apache + mod_fcgid> Are you using ruby for more than just puppet?Only on the puppetmaster, it will be running redmine. cheers, Walter -- 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 Richard, On Nov 6, 12:59 am, Richard Crowley <r...@rcrowley.org> wrote:> You can''t get around running an `apt-get update` but you can do that > from an exec resource in an earlier run stage. > > stage { pre: before => Stage["main"] } > exec { "apt-get update": stage => "pre" } > > You''ll probably want to do your backports setup before the `apt-get > update` in your early run stage, too.Hmm, i haven''t even seen that ''stage'' type before, guess it''s time to hit the manual on that one :) Walter -- 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 Walter,
How are you managing your sources file? If you are simply managing the
sources.list with a file resource, you can "notify" an exec that would
run
the apt-get update when a change is detected, such as:
file { "/etc/apt/sources.list":
source => "puppet:///modules/source.list",
notify => Exec["apt-update"];
}
exec { "apt-update":
command => "/usr/bin/apt-get update",
}
This should help when you make changes to the sources.list file.
Another option is to use an apt pattern like the one here:
http://projects.puppetlabs.com/projects/puppet/wiki/Apt_Repositories_Patterns
This will remove your sources.list and instead create individual source
files in your /etc/apt/sources.list.d directory. It sounds like you have
pinning setup, but I am not sure that I would want everything in my
backports to be installed at a higher priority. Something like this might
be more appropriate:
Package: puppet
Pin: release a=backports
Pin-Priority: 900
Package: facter
Pin: release a=backports
Pin-Priority: 900
The above may need some tweaking, but should get you started. Hope this
helps.
Zach
On Fri, Nov 5, 2010 at 9:52 AM, Walter Heck <walterheck@gmail.com> wrote:
> Hi all,
>
> I''m runnign debian lenny and that has puppet 0.24.5 in it. Lenny-
> backports ahs Puppet 2.6.2 in it, which is what I want. How do I make
> puppet update itself through puppet recipes? I already had it create
> an /etc/apt/preferences, where I pin backports at 900 and lenny stable
> at 700. Is that correct? I don''t want to have to run apt-get
update /
> apt-get upgrade / any other command on the nodes at all, but I
don''t
> know how :)
>
> Walter
>
> --
> 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.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
I get around this issue by installing Puppet as a gem. -- 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.
Which isn''t terrible, but you loose init scripts and the like. Zach On Tue, Nov 9, 2010 at 4:43 PM, bobics <bobics@gmail.com> wrote:> I get around this issue by installing Puppet as a gem. > > -- > 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. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.