On Thu, 2009-04-30 at 14:19 -0700, Brandon Evans wrote:
> I prefer copying the repos over using a template. This way all my
> CentOS boxes have the same repos. If I were to add any Fedora boxes to
> the mix I'd add the repos to the Fedora {} block.
Instead of using a template, you can also us
Hi Tim,
> I don't have a yum module, but I have a yum.pp in /etc/puppet/
> manifests/classes which tells the puppetmaster to distribute a
> yum.conf and a repos.repo (a list of all local Fedora and CentOS
> repos) to the puppet clients.
Managing yum is a good place to start with puppet. It's s
Hi Brandon, thanks for this. I'm new to puppet and I have also
inherited a setup from a consultant who was at Kew before me.
I don't have a yum module, but I have a yum.pp in /etc/puppet/
manifests/classes which tells the puppetmaster to distribute a
yum.conf and a repos.repo (a list of all loca
Hi Brandon, thanks for this. I'm new to puppet and I have also
inherited a setup from a consultant who was at Kew before me.
I don't have a yum module, but I have a yum.pp in /etc/puppet/
manifests/classes which tells the puppetmaster to distribute a
yum.conf and a repos.repo (a list of all loca
I prefer copying the repos over using a template. This way all my
CentOS boxes have the same repos. If I were to add any Fedora boxes to
the mix I'd add the repos to the Fedora {} block.
case $operatingsystem {
CentOS : {
file { "epel" :
path => "/etc/yum.repo
The first thing I would do; split the repositories up. In your case I
would have only the CentOS specific repositories available under "/etc/
yum.repos.d/" for CentOS. servers.
There are several ways to achieve this.
- During the Kickstart process add a repository specifically for
CentOS or Fedo
I administer both RHEL4 and 5 with puppet, and all the software is on
a local yum mirror.
I use the yumrepo type in my base class, which all others depend on,
and use some facts from facter to generate a uniq repo path based on
both the version and architecture. I use something like this;
baseurl
