Forge Home

mrepo

Configures and manages mrepo mirrors

19,720 downloads

67 latest version

5.0 quality score

We run a couple of automated
scans to help you access a
module's quality. Each module is
given a score based on how well
the author has formatted their
code and documentation and
modules are also checked for
malware using VirusTotal.

Please note, the information below
is for guidance only and neither of
these methods should be considered
an endorsement by Puppet.

Version information

  • 5.0.0 (latest)
  • 4.1.0
  • 4.0.0
  • 3.1.1
  • 3.1.0
  • 3.0.0
  • 2.1.0
  • 2.0.1
released Aug 19th 2024
This version is compatible with:
  • Puppet Enterprise 2023.8.x, 2023.7.x, 2023.6.x, 2023.5.x, 2023.4.x, 2023.3.x, 2023.2.x, 2023.1.x, 2023.0.x, 2021.7.x, 2021.6.x, 2021.5.x, 2021.4.x, 2021.3.x, 2021.2.x, 2021.1.x, 2021.0.x
  • Puppet >= 7.0.0 < 9.0.0
  • , ,

Start using this module

  • r10k or Code Manager
  • Bolt
  • Manual installation
  • Direct download

Add this module to your Puppetfile:

mod 'puppet-mrepo', '5.0.0'
Learn more about managing modules with a Puppetfile

Add this module to your Bolt project:

bolt module add puppet-mrepo
Learn more about using this module with an existing project

Manually install this module globally with Puppet module tool:

puppet module install puppet-mrepo --version 5.0.0

Direct download is not typically how you would use a Puppet module to manage your infrastructure, but you may want to download the module in order to inspect the code.

Download

Documentation

puppet/mrepo — version 5.0.0 Aug 19th 2024

Puppet Mrepo

Build Status Release Puppet Forge Puppet Forge - downloads Puppet Forge - endorsement Puppet Forge - scores puppetmodule.info docs Apache-2.0 License Donated by Puppet

Transfer Notice

This module creates and synchronizes rpm based repositories by managing mrepo. It is maintained by Vox Pupuli having kindly been migrated from Puppet Inc.

Synopsis

Install and configure a basic mrepo installation

node default {
  class { 'mrepo': }
}

Override default values and enable redhat network support for use in other classes

class { 'mrepo':
  selinux       => true,
  rhn           => true,
  rhn_username  => 'user',
  rhn_password  => 'pass',
}

Or using Hiera for parameters (same example)

code: class { 'mrepo': }

Hiera: mrepo::selinux: true mrepo::rhn: true mrepo::rhn_username: user mrepo::rhn_password: pass

Mirror multiple centos 5 repositories

mrepo::repo { 'centos5-x86_64':
  ensure    => present,
  update    => 'nightly',
  repotitle => 'CentOS 5.6 64 bit',
  arch      => 'x86_64',
  release   => '5.6',
  urls      => {
    addons      => 'rsync://mirrors.kernel.org/centos/$release/addons/$arch/',
    centosplus  => 'rsync://mirrors.kernel.org/centos/$release/centosplus/$arch/',
    updates     => 'rsync://mirrors.kernel.org/centos/$release/updates/$arch/',
  }
}

mrepo::repo { 'centos5-i386':
  ensure    => present,
  update    => 'nightly',
  repotitle => 'CentOS 5.6 64 bit',
  arch      => 'i386',
  release   => '5.6',
  urls      => {
    addons      => 'rsync://mirrors.kernel.org/centos/$release/addons/$arch/',
    centosplus  => 'rsync://mirrors.kernel.org/centos/$release/centosplus/$arch/',
    updates     => 'rsync://mirrors.kernel.org/centos/$release/updates/$arch/',
  }
}

Mirror multiple rhel channels

mrepo::repo { 'rhel6server-x86_64':
  ensure      => present,
  update      => 'nightly',
  repotitle   => 'Red Hat Enterprise Linux Server $release ($arch)',
  rhn         => true,
  type        => 'rhn',
  arch        => 'x86_64',
  release     => '6',
  typerelease => '6Server',
  iso         => 'rhel-server-6.0-$arch-dvd.iso',
  urls        => {
    updates       => 'rhns:///rhel-$arch-server-$release',
    vt            => 'rhns:///rhel-$arch-server-vt-$release',
    supplementary => 'rhns:///rhel-$arch-server-supplementary-$release',
    fasttrack     => 'rhns:///rhel-$arch-server-fasttrack-$release',
    hts           => 'rhns:///rhel-$arch-server-hts-$release',
    rhn-tools     => 'rhns:///rhn-tools-rhel-$arch-server-$release',
  }
}

Fetch and place an ISO file for the above rhel6server-x86_64 repo

mrepo::iso { 'rhel-server-6.0-$arch-dvd.iso':
  source_url => 'http://some.domain.tld/path/to/isodir',
  repo       => 'rhel6server-x86_64',
}

Usage

If you need to customize the mrepo default settings, include the mrepo class and include the appropriate variables. Else, you should be able to use the mrepo::repo by itself to instantiate repositories.

For class/define specific documentation, view the puppet doc in the given file.

Prerequisites

This module expects the following modules to be available:

  • puppetlabs-apache
  • puppetlabs-stdlib
  • puppetlabs-vcsrepo

It also is configured for a redhat derived system and makes assumptions about the available users and groups. Alternate parameters may override these assumptions.

Mirror data can grow extremely large, so you will want to ensure that src_root is located on a large volume.

If you are planning on using ISOs, you will also need fuse-iso.

Repository URL formatting

You can take advantage of the variables that mrepo itself supports when defining a repository or ISO to mirror. Mrepo uses the following variables:

  • $dist is set to the title of the resource
  • $arch is set to the arch parameter
  • $nick is set to $dist-$arch
  • $repo is set to the key of the specific repository
  • $release is set to the release parameter

Note that these are variables within mrepo; if you are using them, make sure to surround the string in single quotes so puppet doesn't try to expand them.

So this:

mrepo::repo { 'centos5-x86_64':
  ensure    => present,
  update    => 'nightly',
  repotitle => 'CentOS 5.6 64 bit',
  arch      => 'x86_64',
  release   => '5.6',
  urls      => {
    addons      => 'rsync://mirrors.kernel.org/centos/$release/$repo/$arch/',
    centosplus  => 'rsync://mirrors.kernel.org/centos/$release/$repo/$arch/',
    updates     => 'rsync://mirrors.kernel.org/centos/$release/$repo/$arch/',
  }
}

Is equivalent to this:

mrepo::repo { 'centos5-x86_64':
  ensure    => present,
  update    => 'nightly',
  repotitle => 'CentOS 5.6 64 bit',
  arch      => 'x86_64',
  release   => '5.6',
  urls      => {
    addons      => 'rsync://mirrors.kernel.org/centos/5.6/addons/x86_64/',
    centosplus  => 'rsync://mirrors.kernel.org/centos/5.6/centosplus/x86_64/',
    updates     => 'rsync://mirrors.kernel.org/centos/5.6/updates/x86_64/',
  }
}

Be warned that you can make a repository with the name of 'release'; however, this will overwrite the actual release variable. If you have a repository with a name of release, change the key to something else, and explicitly define the url instead of using a variable.

For full details on how mrepo is used, see the mrepo usage page.

Caveats

Params Pattern

This module was previously using a design where the params class was used as the main class and included in other classes.

It now follows the params pattern, where parameters are set in the params class as default, inherited, then overwritten as needed when calling the base class.

Before:

Using classes

class { 'mrepo::params':
  selinux       => true,
  rhn           => true,
  rhn_username  => 'user',
  rhn_password  => 'pass',
}

After:

class { 'mrepo':
  selinux       => true,
  rhn           => true,
  rhn_username  => 'user',
  rhn_password  => 'pass',
}

SELinux

Default SELinux policy prevents the httpd context from manipulating loopback devices without having an explicit httpd context. This can be corrected by changing the context as a mount option for a regular mount. However, fuseiso does not have the capability to change selinux contexts. If you are planning on mounting ISOs, either do so as root, change the httpd context to permit fuseiso to run using audit2allow, or disable SELinux. If neither of these are viable options, you can locate and mirror an outside repository of the ISO data.

Further clarification of this issue can be found on the repoforge tools list.

Fuse ISO

Fuse iso is not available in any yum repository. You will need to locate an RPM or source file and install it for yourself. In addition, if you are using a non-root user to mount the ISOs, you will need to ensure that the user is in the 'fuse' group.