Re: [Puppet Users] Include class with parameters

Hi Harish, On 09 Jun 2016, at 06:49, Harish Kothuri wrote: > Hi, > > I have classA with parameter and i want to include this in another classB . I > expected to consider the default value defined in foreman for classA but it's > not happening. > > > class classA

[Puppet Users] Include class with parameters

Hi, I have classA with parameter and i want to include this in another classB . I expected to consider the default value defined in foreman for classA but it's not happening. class classA ($version) { Package { 'Package A' ensure => 'installed', source

Re: [Puppet Users] Run Puppet Class only once

Hey; I don't know if this matches the OP's scenario; but, I've been contemplating something similar during provisioning. To provide context, as you can probably tell from my other posts, I'm just rolling out puppet server after a long absence and even then wasn't exactly an expert. Like most

Re: [Puppet Users] Puppet 4.5 and git & R10K

Cool. spent the last week getting my head around git .. branching and such. On 9 June 2016 at 05:39, Rob Nelson wrote: > I do something similar with zack/r10k: > > #r10k_installation.pp > Package { > allow_virtual => true, > } > > sshkey { 'github.com': > type =>

[Puppet Users] High level module & hiera design

Hey; I'm planning out a module to handle syslog config in my environment. I know there are modules on puppet forge already but am interested in the learning opportunity. . Here's the scenario: * The syslog config files will all be the same except for forwarders. * We have three datacenters

Re: [Puppet Users] Puppet 4.5 and git & R10K

I do something similar with zack/r10k: #r10k_installation.pp Package { allow_virtual => true, } sshkey { 'github.com': type => 'ssh-rsa', key =>

Re: [Puppet Users] Puppet 4.5 and git & R10K

At least to answer the question of installing r10k tool for use with open source Puppetserver (or just puppet agent), I do this in a bootstrap script for my Puppetserver to install r10k from gem, and do the initial deployment of the control repo. This for directory-based environments. #

Re: [Puppet Users] Packaging scripts for Puppetlabs Vagrant images?

It is not urgent at all. Thank you. On Wednesday, June 8, 2016 at 12:57:16 PM UTC-5, LinuxDan wrote: > > Depending how time critical this is, I would be willing to help you whip > up an appropriate box. > Can it hold until the weekend ? > > Dan White | d_e_...@icloud.com >

Re: [Puppet Users] Packaging scripts for Puppetlabs Vagrant images?

Depending how time critical this is, I would be willing to help you whip up an appropriate box. Can it hold until the weekend ? Dan White | d_e_wh...@icloud.com “Sometimes I think the surest sign that intelligent life exists elsewhere in the

Re: [Puppet Users] Packaging scripts for Puppetlabs Vagrant images?

The reason for testing is due to breaking package dependency changes that appeared in v6.8, creating the need to test on as virgin a copy of CentOS v6.8 as I could find. The resulting image from upgrading v6.6 to v6.8 is somewhat different. Thanks for pointing me to the packer repo. On

[Puppet Users] Puppetlabs_Postgres Module: validate_postgresql_connection.sh fails

I have asked this question over at ask.puppet.com, but there has been no response at all. I did notice that there is a very old thread about this problem, but there was never any solution posted. I'm hoping that Ken Barber is still on this list and can remember if he was able to help resolve

Re: [Puppet Users] Packaging scripts for Puppetlabs Vagrant images?

Simple to update the VM (just did it) The obvious : yum -y update The not-so-obvious: VirtualBox uses kernel modules that need updating http://www.virtualbox.org/manual/ch02.html#externalkernelmodules and http://ulyssesonline.com/2011/08/30/fix-virtualbox-after-kernel-upgrade/ and

Re: [Puppet Users] Packaging scripts for Puppetlabs Vagrant images?

Ben, I think https://github.com/puppetlabs/puppetlabs-packer is what you are looking for. HTH On Wed, Jun 8, 2016 at 9:54 AM, Ben West wrote: > I was hoping to test out CentOS v6.8, but the Puppetlabs Vagrant images > published only go up to v6.6: >

[Puppet Users] Packaging scripts for Puppetlabs Vagrant images?

I was hoping to test out CentOS v6.8, but the Puppetlabs Vagrant images published only go up to v6.6: https://atlas.hashicorp.com/puppetlabs Is there a repo, or other such info somewhere, providing details about how these images are rolled? I.e. so I could create my own CentOS v6.8 image to

Re: [Puppet Users] Multiple CA setup.

@Dan White: that link was pretty much what I was looking for. I take it then you have openssl sign certs for each master (grand and remote) and configure Puppet to use those certs. The tricky part is going to be installing the new certs in production. Sorta like changing a tire when the car is

Re: [Puppet Users] Re: Hiera, define, class, putting all together

On Tuesday, June 7, 2016 at 8:02:24 AM UTC-5, Helmut Schneider wrote: > > jcbollinger wrote: > > Without the case statement, how can I make sure that ubuntu only > receives classes for ubuntu and not e.g. for Windows then? > > That is where your data hierarchy comes in. You have a level

Re: [Puppet Users] Trouble creating a release RPM from puppetlabs/puppet source repo

On Wednesday, June 8, 2016 at 4:06:10 AM UTC-5, Matt Larson wrote: > > I did try installing via the PC1 (AIO) repo, and it worked ok for me at > home. But like I said, can't do that at work. > > What is your main concern with AIO? I don't wanna make a bad step here. > At first, AIO sounded

Re: [Puppet Users] Multiple CA setup.

Could the regional masters be set up as intermediate certificate authorities ? I found a link that describes the basics. https://jamielinux.com/docs/openssl-certificate-authority/create-the-intermediate-pair.html Dan White | d_e_wh...@icloud.com

Re: [Puppet Users] Multiple CA setup.

I think the dated docs you are reading are probably it :-) Running very much on 6 year old memory here, when I tried it last... You create a new Puppet CA cert with multiple SANs on it for each of your Puppet Masters' hostnames, and distribute that to each Master. The agents can be signed by

[Puppet Users] Multiple CA setup.

In the puppet setup that I have where I work it has been increasingly more desirable if not required to have each of our data centers be able to operate standalone. Because of this I've been Googling around looking for a methodology to allow multiple certificate authorities in puppet. Currently we

Re: [Puppet Users] Trouble creating a release RPM from puppetlabs/puppet source repo

I believe most reason for concern with AIO is that it installs a separate version of ruby, openssl, and other applications and libraries on your system. These need upgrading, just like your system apps/libs, and Puppet may both expose you to different vulnerabilities, since their versions are

[Puppet Users] Re: Trouble creating a release RPM from puppetlabs/puppet source repo

On Wednesday, June 8, 2016 at 11:03:09 AM UTC+2, Matt Larson wrote: > > I tried this, but where are the puppet-agent source RPMs ? > Indeed they are not there anymore as discussed in [1] and [2] . [1] https://tickets.puppetlabs.com/browse/CPR-191 [2]

Re: [Puppet Users] Trouble creating a release RPM from puppetlabs/puppet source repo

I did try installing via the PC1 (AIO) repo, and it worked ok for me at home. But like I said, can't do that at work. What is your main concern with AIO? I don't wanna make a bad step here. At first, AIO sounded scary to me... like some alternative to rpm/yum (in case of rhel-based

[Puppet Users] Re: Trouble creating a release RPM from puppetlabs/puppet source repo

Thanks for helping with this, Stefan! I tried this, but where are the puppet-agent source RPMs ? On Friday, June 3, 2016 at 3:51:36 PM UTC-4, Stefan Heijmans wrote: > > Have you tried using the source RPMs from here; > > https://yum.puppetlabs.com/el/6/PC1/SRPMS/ > > > On Friday, June 3, 2016 at

Re: [Puppet Users] Trouble creating a release RPM from puppetlabs/puppet source repo

Sorry for not getting back soon, Dan. Good question. I work for a draconian company that only allows installing FOSS after our infosec team has vetted the source code and then built from source; an impossible hand-waving exercise, I know... but it is what it is. On Friday, June 3, 2016 at