Re: [Puppet Users] How to use class in different place

2016-08-25 Thread Henrik Lindberg
On 25/08/16 22:40, Albert Shih wrote: Hi, I would like to known how can I use a class in different place. Let's take a example. I have a module who manage a CMS, let's say something like drupal (or whatever you want). So in this CMS I need to use apache class. So I get in my node.yaml

[Puppet Users] How to use class in different place

2016-08-25 Thread Albert Shih
Hi, I would like to known how can I use a class in different place. Let's take a example. I have a module who manage a CMS, let's say something like drupal (or whatever you want). So in this CMS I need to use apache class. So I get in my node.yaml something like classes : -

[Puppet Users] puppet ignores storeconfig_backend in puppet.conf

2016-08-25 Thread Joseph Lorenzini
Hi all, I am encountered an odd behavior when i revoke a certificate on the puppet master. I see this error. I am using puppet 3.7.4 on CentOS 7. Error: undefined method `verify_active_connections!' for ActiveRecord::Base:Class This leads me to think that when a revocation is happening, the

[Puppet Users] Announce: PuppetDB 4.2.2 is released!

2016-08-25 Thread Wyatt Alt
PuppetDB 4.2.2 - August 25, 2016 PuppetDB 4.2.2 Downloads Available in native package format as part of Puppet Collection 1 (PC1). More information on the PC1 repositories is available here: http://bit.ly/1HQJDNb Binary tarball:

Re: [Puppet Users] How to handle predictable network interface names

2016-08-25 Thread Luke Bigum
On Thursday, 25 August 2016 13:31:17 UTC+1, Marc Haber wrote: > > On Wed, Aug 24, 2016 at 09:03:16AM -0700, Luke Bigum wrote: > > The template will create udev rules from two sources. The first is > > @interfaces, which is the giant multi-level hash of network interfaces > that > > our old

[Puppet Users] Re: How to handle predictable network interface names

2016-08-25 Thread Luke Bigum
On Thursday, 25 August 2016 13:21:24 UTC+1, Marc Haber wrote: > > On Wed, Aug 24, 2016 at 08:36:49AM -0700, Luke Bigum wrote: > > Here we have very strict control over our hardware and what interface > goes > > where. We keep CentOS 6's naming scheme on Dell hardware, so p2p1 is PCI > > slot

Re: [Puppet Users] How to handle predictable network interface names

2016-08-25 Thread Rob Nelson
We are provisioning everything with vmxnet3 drivers, only weird old OVAs from vendors have non-vmxnet3, and we don't manage those with puppet. We are cloning from template and getting the same results on different vSphere/vCenter versions and instances. Not sure why they would come out different

[Puppet Users] Re: Key management with AWS S3

2016-08-25 Thread Joseph Lorenzini
Hi Mathew, I've actually been wrestling with a similar problem myself. So far the solution I like the best is the following: 1. use gpg encryption to encrypt the files on disk and then commit them into the VCS. 2. do NOT include the gpg private key or the passphrase for the key into

Re: [Puppet Users] How to handle predictable network interface names

2016-08-25 Thread Marc Haber
On Wed, Aug 24, 2016 at 09:03:16AM -0700, Luke Bigum wrote: > The template will create udev rules from two sources. The first is > @interfaces, which is the giant multi-level hash of network interfaces that > our old designs use. A VM might look like this in Hiera: > > networking::interfaces: >

Re: [Puppet Users] How to handle predictable network interface names

2016-08-25 Thread Marc Haber
Hi Rob, On Wed, Aug 24, 2016 at 10:30:20AM -0400, Rob Nelson wrote: > We use VMware's vSphere, which still results in "random" but predictable > interface names - eth0 is now eno16780032, eth1 is now eno3359296, etc. In my experience, the numbers are rather random, different on each VM. > We've

Re: [Puppet Users] How to handle predictable network interface names

2016-08-25 Thread Marc Haber
On Wed, Aug 24, 2016 at 09:20:56AM -0700, Luke Bigum wrote: > Now that I think about it, I might be able to post a sanitised version of > the module online with most of the internal stuff stripped out. It might > prove useful for educating our own staff in the concepts, as well as other >

[Puppet Users] Re: How to handle predictable network interface names

2016-08-25 Thread Marc Haber
On Wed, Aug 24, 2016 at 08:36:49AM -0700, Luke Bigum wrote: > Here we have very strict control over our hardware and what interface goes > where. We keep CentOS 6's naming scheme on Dell hardware, so p2p1 is PCI > slot 2, Port 1, and don't try rename it. Isn't CentOS 6 still using eth0, 1, 2,