Forge Home


Puppet module for setting up UMD and CMD repositories


5,901 latest version

1.3 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

  • 1.0.0 (latest)
released Feb 20th 2018
This version is compatible with:
  • Puppet 3.x
  • , ,

Start using this module

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

Add this module to your Puppetfile:

mod 'egiqc-umd', '1.0.0'
Learn more about managing modules with a Puppetfile

Add this module to your Bolt project:

bolt module add egiqc-umd
Learn more about using this module with an existing project

Manually install this module globally with Puppet module tool:

puppet module install egiqc-umd --version 1.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.



egiqc/umd — version 1.0.0 Feb 20th 2018


This Puppet module deploys EGI's UMD and/or CMD software distribution repositories, residing at


From PuppetForge

puppet module install egiqc/umd

With librarian-puppet tool

cat <<EOF >>Puppetfile
#!/usr/bin/env ruby
forge ""
mod "egiqc/umd"

or using the repository directly:

cat <<EOF >>Puppetfile
#!/usr/bin/env ruby
forge ""
mod "egi-qc/umd", :git => "git://"


Simplest-case scenario would be to provide the distribution parameter and leave anything else as defaults. This one-liner does the job:

puppet apply -e 'class {"umd": distribution => "umd"}'

The module will take the latest production release version for the selected distribution. Otherwise, the release version could be passed with the release variable:

class {
        distribution => "umd",
        release => 4,

Available repositories

The repositories enabled by default are:

  • base
  • updates

The rest of available repositories are:

  • testing
  • untested

which can be enabled with enable_testing_repoand enable_untested_repo, respectively.

Extra repositories (verification)

EGI Software Provisioning process uses this module for the software product's verification. Consequently, there is the possibility of providing extra repositories with verification_repofile parameter, as happen to be the verification one. Note that verification_repofile must point to a valid YUM or APT source file:

class {
        distribution => "umd",
        release => 4,
        verification_repofile => ""


This module is also able to deploy the EGI IGTF release, containing the trusted set of certification authorities in the EGI infrastructure. By default, the EGI IGTF repository is deployed and the trusted CAs are installed. To disable this feature:

class {
        distribution => "umd",
        igtf_repo => false,