Configure EPEL (Extra Repository for Enterprise Linux)
This module basically just mimics the epel-release rpm. The same repos are enabled/disabled and the GPG key is imported. In the end you will end up with the EPEL repos configured.
The following Repos will be setup and enabled by default:
Other repositories that will setup but disabled (as per the epel-release setup)
In nearly all cases, you can simply include epel or classify your nodes with the epel class. There are quite a few paramters available if you need to modify the default settings for the epel repository such having your own mirror, an http proxy, disable gpg checking.
You can also use a puppet one-liner to get epel onto a system.
puppet apply -e 'include epel'
If you have an http proxy required to access the internet, you can use either a class parameter in the epel class, or edit the $proxy variable in the params.pp file. By default no proxy is assumed.
I am a big fan of EPEL. I actually was one of the people who helped get it going. I am also the owner of the epel-release package, so in general this module should stay fairly up to date with the official upstream package.
I just got sick of coding Puppet modules and basically having an assumption that EPEL was setup or installed. I can now depend on this module instead.
I realize it is fairly trivial to get EPEL setup. Every now-and-then however the path to epel-release changes because something changes in the package (mass rebuild, rpm build macros updates, etc). This module will bypass the changing URL and just setup the package mirrors.
This does mean that if you are looking for RPM macros that are normally included with EPEL release, this will not have them.
- Update README with usage section.
- Fix regression when os_maj_version fact was required
- Ready for 1.0 - replace Modulefile with metadata.json
- Replace os_maj_version custom fact with operatingsystemmajrelease
- Works for EPEL7 now as well.
- This is commonly used on Puppet Enterprise 3.x
- This was tested using Puppet 3.3.0 on Centos5/6
- This was tested using Puppet 3.1.1 on Amazon's AWS Linux
- I assume it will work on any RHEL variant (Amazon Linux is debatable as a variant)
- Amazon Linux compatability not promised, as EPEL doesn't always work with it.
- No functionality has been introduced that should break Puppet 2.6 or 2.7, but I am no longer testing these versions of Puppet as they are end-of-lifed from Puppet Labs.
- This also assumes a facter of greater than 1.7.0 -- at least from a testing perspective.
Install the necessary gems
Run the RSpec and puppet-lint tests
bundle exec rake ci
If you have Vagrant >=1.1.0 you can also run system tests:
RSPEC_SET=centos-64-x64 bundle exec rake spec:system
Available RSPEC_SET options are in .nodeset.yml
Apache Software License 2.0
- Aaron firstname.lastname@example.org
- Chad Metcalf email@example.com
- Ewoud Kohl van Wijngaarden firstname.lastname@example.org
- Joseph Swick email@example.com
- Matthaus Owens firstname.lastname@example.org
- Michael Stahnke email@example.com
- Michael Stahnke firstname.lastname@example.org
- Pro Cabales email@example.com
- Proletaryo Cabales firstname.lastname@example.org
- Stefan Goethals email@example.com
- Tim Rupp firstname.lastname@example.org
- Trey Dockendorf email@example.com
- Troy Bollinger firstname.lastname@example.org
- Vlastimil Holer email@example.com