I use a separate module for the repositories (
https://forge.puppetlabs.com/thbe/yum) and require them during startup like
here (https://forge.puppetlabs.com/thbe/ssmtp). So Puppet is doing the work
to get everything in place in the correct order.
Regards Thomas
2014-07-07 17:35 GMT+02:00 Andrei
Yanis, Doug, thank you very much.
Max
On 2014-07-07 17:49:44 +, Yanis Guenane said:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
To second Doug, I also uses a module for each repo I want to add.
This way you can probably have a base profile, like the following :
class profile::base {
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
To second Doug, I also uses a module for each repo I want to add.
This way you can probably have a base profile, like the following :
class profile::base {
resources { 'yumrepo' :
purge => true,
}
include ::epel
include ::nginx
include
Max,
I do a single module for each repo that I want added. In some cases I
combine it with a repo to manage the service. IE mysql* repos would be
managed via the mysql module.
As for making sure they are all up to date I might just create an
exec {my_check_update:
refreshonly => true,
command
Hi,
I've been looking into Puppet recently and I'm trying to setup a couple
of virtual machines that should mimick what's in production. I'm pretty
much a developer trying to lean towards DevOps :-)
Locally, I'm using Vagrant and the CentOS 6.5 64-bit box with Puppet
3.4.3 that was published
