Hello Puppeteers,
We currently have implemented a nodeless (role base using LDAP) and
masterless (git pulls) puppet infrastructure at work. This aspect seems to
work just fine. We also have puppetdb setup to manage reports and
storeconfigs. There is plenty of data being written to the PostgreSQ
hey John,
You are rock!
The codes is working as expected. Should have pick up some ruby books and
start understanding it
thanks a lot...
On Thursday, March 19, 2015 at 8:52:12 PM UTC+7, jcbollinger wrote:
>
>
>
> On Wednesday, March 18, 2015 at 8:45:58 PM UTC-5, Hiu wrote:
>>
>> hi all,
>>
PuppetDB 2.3.0 - March 19, 2015
PuppetDB 2.3.0 Downloads
Available in native package format in the release repositories at:
http://yum.puppetlabs.com and http://apt.puppetlabs.com
For information on how to enable the Puppet Labs repos, see:
http://docs.puppetlabs.com/gui
Hi Garrett et all.
Thanks for your thoughts and examples. I forgot to mention and I have
in my top level site.pp only
hiera_include('classes')
and the rest it's in the hiera.yaml mentioned above and so far so good.
I was just wondering if it's one way to go and it seems to be right.
I love Puppe
We have about a dozen CentOS 6 servers being managed by puppet 3.7.4, using
puppet
apply with locally stored modules and node definition.
Recently, performance on one of them has collapsed to hopeless levels, and
I really don't know how to diagnose the problem.
Puppet used to take 5 - 10 min
Many of you probably saw this on The Twitternets but I figured I would post
here as well: There are now release candidate builds of Puppet 4 and
Puppet-Server 2 available for EL7. The long-form writeup is at
bit.ly/1FBUJUN or you can jump straight to the installation
instructions: http://docs.p
does anyone has a manifest I can use to:
1. Create an account for Mary, maryjane on all systems
2. Create a specific user on just a specific system (For example, create
account john.doe on puppet-domain but not on puppetagent)
--
You received this message because you are subscribed to the Goog
Hi,
I've been wondering about what to do when configuration files change on
services that I don't want to automatically restart. It's simple enough to
make it automatically restart by having the file notify the service, but
for important services I thought it would be good to have a module that
Just figured this out this morning. It was the $::role. It's a variable
declared in site.pp inside a node block. ( poor man's role classification)
$role seems to have fixed things
Hopefully this release is smooth now!
Thanks
Brett
Sent from my iPhone
> On Mar 19, 2015, at 07:30, jcbo
On 3/19/15 12:07 AM, Alfredo De Luca wrote:
> Hi all.
> I am testing hiera in our enviroment and I wonder if I can manage
> everything from hiera without using the main site.pp.
>
> Do you think is the right way? or I should use site.pp as well?
>
>
> Here is what I am testing and so far so good
From this example:
package { 'foo':
ensure => '1.0.0',
}
package { 'foo':
ensure => '1.0.1',
}
package { 'foo':
ensure => 'latest',
}
Which one wins? Since resources can be evaluated and applied in any
order (barring dependencies), you could end up in a situation where a
package
I've encountered the problem where 2 modules declare the identical package.
I wonder why package { .. } doesn't check if the package is already
declared, and the redundant declaration can be ignored.
Will it be a nice improvement? If not, why not?
Thank you,
Tanin
--
You received this messag
On Wednesday, March 18, 2015 at 8:45:58 PM UTC-5, Hiu wrote:
>
> hi all,
>
> I am wondering if I would like to retrieve the mount points values from
> the facter. From the facter -p, I can see that I do have the information.
> e.g.
>
> partitions => {
> "sda1"=>{
> "mount"=>"/boot",
> "uuid"=>
On Wednesday, March 18, 2015 at 4:40:38 PM UTC-5, Brett Swift wrote:
>
> I've found the time to deliver a multiple hiera backend for our ops guys,
> and I'm seeing some weird behaviour.
>
> With a single backend, it works great - add host level configs in the host
> hierarchy, and common stuff
On Wednesday, March 18, 2015 at 6:07:15 PM UTC-5, Alfredo De Luca wrote:
>
> Hi all.
> I am testing hiera in our enviroment and I wonder if I can manage
> everything from hiera without using the main site.pp.
>
> Do you think is the right way? or I should use site.pp as well?
>
Hiera does n
Yes, I think it's a good way to go, Alfredo.
I would normally have a hierarchy like the following.
- secrets (e-yaml-gpg)
- nodes
- environment
- roles
- common
Gets by in most setups. You'll still need a site.pp file but in can just have:
hiera_include('classes') (pretty sure that's the call, n
My current site.pp sets a few global level variables and then all I need is :
node default {
hiera_include('classes')
}
I am not sure what kind of response you are looking for.
“Sometimes I think the surest sign that intelligent life exists elsewhere in the
universe is that none of it
Hi all.
Anyone on this question?
On Thu, Mar 19, 2015 at 10:07 AM, Alfredo De Luca
wrote:
> Hi all.
> I am testing hiera in our enviroment and I wonder if I can manage
> everything from hiera without using the main site.pp.
>
> Do you think is the right way? or I should use site.pp as well?
>
>
Hullo
I've been a casual puppet user for some time and I'm struggling with the
different lifespans and innovation rates of the different components in my
environment. In order to trial new distro versions with new puppet clients,
I need my puppet master to be on a newish distro, and probably pro
Thank you very much, Guys. I've converted file to array using SED, but it
is nice idea with hiera. I have never used hiera before, it was not
necessary, but maybe it is time to start thinking in that direction.
On Wednesday, 18 March 2015 13:18:13 UTC, Garrett Honeycutt wrote:
> On 3/13/15 10:
On 3/18/15 10:02 PM, Johan De Wit wrote:
> Hi all,
>
> Looking for some best practice, guideline, documentation puppet testing
> in all its aspect, sometimes I try to figure out the following :
>
> How does one tests roles and profiles ?
>
> Do we still write rspec-puppet for profiles ? Since w
21 matches
Mail list logo
