[Puppet Users] Strategies for Source Control with Puppet 4

2015-07-05 Thread Rachel Andrew
Hi all just wondering how you are all managing source control. I’m setting up a new Puppet Master and migrating my nodes to it (I’ve only got 7 servers so we’re small fry). I only have need for the default production environment right now and I like to keep simple things simple as we’re not

Re: [Puppet Users] How to use multiple versions of same module

2015-07-05 Thread Peter Meier
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Ultimately, it seems that we should move to librarian puppet, but I'm not sure that that solves the basic problem, which is that I need to have multiple versions of the same modules. How do I accomplish this? At the moment the best thing is:

[Puppet Users] Re: How to use multiple versions of same module

2015-07-05 Thread Corey Osman
So the end goal would be to use r10k. However, in the midterm you need to do a few things. 1. Create a roles and profiles pattern for your business logic 2. version your modules inside your VCS. So basically you can create a nginx_profile1_2, nginx_profile_1_3, ... as well as a nginx_1_1 and

Re: [Puppet Users] Strategies for Source Control with Puppet 4

2015-07-05 Thread Gareth Rushgrove
Hi Rachel I'd probably take at least a look at r10k, which is an opinionated deployment tool for the problem you describe. https://github.com/puppetlabs/r10k The official documentation covers Puppet Enterprise but I think the majority of it will be applicable, especially in terms of getting a

Re: [Puppet Users] where is PC1 for Debian Jessie?

2015-07-05 Thread Felix Frank
Hi, has anyone tried the PC1 on jessie yet? I just did the following: wget http://apt.puppetlabs.com/puppetlabs-release-pc1-jessie.deb dpkg -i puppetlabs-release-pc1-jessie.deb apt-get update but I get ... W: Failed to fetch http://apt.puppetlabs.com/dists/jessie/Release Unable to find