Theoretically that's the way to do it in Puppet, but as other people
point out it would be much simpler to block things from being installed
in the first place. ensure = purged might get you better results from
providers that handle dependencies, however I have mixed results with
yum when
Ah, exactly what I needed!
Thanks!
On Monday, April 30, 2012 5:32:26 PM UTC+2, R.I. Pienaar wrote:
- Original Message -
From: Andreas Paul xorp...@googlemail.com
To: puppet-users@googlegroups.com
Sent: Monday, April 30, 2012 2:52:00 PM
Subject: [Puppet Users] querying
Cool thx Den, undef worked like a charm.
much appriciated!
On 2 May 2012 01:24, denmat tu2bg...@gmail.com wrote:
Hi Peter,
take a look at this:
class testme {
define vhost ($servername = ${hostname}.${domain}, $serveralias =
[ www.${hostname}.${domain} ], $inorout = 1, $owner = root,
We have a custom fact that we wrote to determine which (business)
environment a specific server belongs to (test, stage, production).
We want to set up puppet environments (again, test, stage, and production).
Is it possible to use our custom fact to set which environment a node
belongs to?
- Original Message -
From: John Kennedy skeb...@gmail.com
To: puppet-users@googlegroups.com
Sent: Wednesday, May 2, 2012 11:59:49 AM
Subject: [Puppet Users] Using fact to determine node environment
We have a custom fact that we wrote to determine which (business)
environment a
On 2 May 2012 12:19, R.I.Pienaar r...@devco.net wrote:
your only option at present is to write out puppet.conf using a template
with your fact
We use this approach. The very first run gets called with --environment
foo and it sticks. --environment can then be called again if it needs to
move
On May 2, 3:02 am, Luke Bigum luke.bi...@lmax.com wrote:
Theoretically that's the way to do it in Puppet,
I missed your referent. Are you talking about Brian's suggestion of a
controlled repository?
but as other people
point out it would be much simpler to block things from being
On May 1, 11:24 am, Philip Brown p...@bolthole.com wrote:
On Tue, May 1, 2012 at 6:58 AM, jcbollinger john.bollin...@stjude.org wrote:
But that requires the files be hosted on the puppet master.
What if the conf files are still rdisted out under /rdist/base instead?
What does that look
For folks with multiple Puppet Masters, how are you pushing out
manifest and module updates to them?
We intend to use Subversion for our version control. Obviously one
option would be to have each Puppet Master perform a checkout of the
svn repo. We could schedule periodic updates via cron. Or we
Team,
Is there any way where we can exclude certain module from the inherited
list
Thanks,
Munna
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group,
I use a combination of git and puppet itself to push to productions, but
git for dev/qa puppet masters. Puppet Pro has nice examples of git with
environments but here is a link also.
http://puppetlabs.com/blog/git-workflow-and-puppet-environments/
On Wed, May 2, 2012 at 10:18 AM, Scott Merrill
On Wed, May 2, 2012 at 4:19 AM, R.I.Pienaar r...@devco.net wrote:
- Original Message -
From: John Kennedy skeb...@gmail.com
To: puppet-users@googlegroups.com
Sent: Wednesday, May 2, 2012 11:59:49 AM
Subject: [Puppet Users] Using fact to determine node environment
We have a
Fellow Puppet Users!
I have a continually growing list of 600 remote users that I need to ensure
exist across 3 web servers. I only need to ensure these users exist, and
that the password is set with the what they provide via a secure web
interface. Within my puppet configuration, I don't
Many people I talk to prefer postcommit hooks to do this work. We had an
on-site engagement where we wrote an MCollective agent that would do all
the heavy Git lifting, and the postcommit would call the MCollective agent.
This also let you quickly move your Masters to different commits as-needed
On Wed, May 2, 2012 at 11:10 AM, Nigel Kersten ni...@puppetlabs.com wrote:
On Wed, May 2, 2012 at 4:19 AM, R.I.Pienaar r...@devco.net wrote:
- Original Message -
From: John Kennedy skeb...@gmail.com
To: puppet-users@googlegroups.com
Sent: Wednesday, May 2, 2012 11:59:49 AM
- Original Message -
From: Nigel Kersten ni...@puppetlabs.com
To: puppet-users@googlegroups.com
Sent: Wednesday, May 2, 2012 4:10:16 PM
Subject: Re: [Puppet Users] Using fact to determine node environment
On Wed, May 2, 2012 at 4:19 AM, R.I.Pienaar r...@devco.net wrote:
My experience managing only home directories (and even fewer than yours) is
that tossing hundreds of i/o-sensitive resources (nfs mounts, directories) at a
puppet agent guarantees slow agent runs. You're also not going to scale way up
with local users across a growing number of servers.
My way
On Wed, May 2, 2012 at 8:18 AM, R.I.Pienaar r...@devco.net wrote:
- Original Message -
From: Nigel Kersten ni...@puppetlabs.com
To: puppet-users@googlegroups.com
Sent: Wednesday, May 2, 2012 4:10:16 PM
Subject: Re: [Puppet Users] Using fact to determine node environment
- Original Message -
From: Nigel Kersten ni...@puppetlabs.com
To: puppet-users@googlegroups.com
Sent: Wednesday, May 2, 2012 4:24:06 PM
Subject: Re: [Puppet Users] Using fact to determine node environment
On Wed, May 2, 2012 at 8:18 AM, R.I.Pienaar r...@devco.net wrote:
On Wed, May 2, 2012 at 8:37 AM, R.I.Pienaar r...@devco.net wrote:
Unless something broke it recently, I ran for years with a fact
that
returned :environment and didn't set it in puppet.conf at all.
yes, it broke. You'll get a mix of files from one environment and
classes
from
- Original Message -
From: Nigel Kersten ni...@puppetlabs.com
To: puppet-users@googlegroups.com
Sent: Wednesday, May 2, 2012 4:38:38 PM
Subject: Re: [Puppet Users] Using fact to determine node environment
On Wed, May 2, 2012 at 8:37 AM, R.I.Pienaar r...@devco.net wrote:
- Original Message -
From: R.I.Pienaar r...@devco.net
To: puppet-users@googlegroups.com
Sent: Wednesday, May 2, 2012 4:46:24 PM
Subject: Re: [Puppet Users] Using fact to determine node environment
- Original Message -
From: Nigel Kersten ni...@puppetlabs.com
To:
Team,
Any help?
Thanks,
Jeeva
On Wed, May 2, 2012 at 9:24 AM, Munna S 19.mu...@gmail.com wrote:
Team,
Is there any way where we can exclude certain module from the inherited
list
Thanks,
Munna
--
You received this message because you are subscribed to the Google Groups
Puppet Users
Our SVN repo box is shared with some other projects so I haven't
implemented a post-commit hook at this point. We used to have Puppet
perform the checkouts, but since a commit may break Puppet's ability to
run it didn't seem like the best way. For now we're doing it via
MCollective.
On
Hi,
I don't understand what you mean by inherit list. Module inheritance
is like this:
class woof inherits meow { ... }
... and there's no list, it's a single class. Are you talking about
pluginsync and defined modules on a Puppet Master?
Can you describe your problem in another way or
- Munna S 19.mu...@gmail.com wrote:
Team,
Any help?
Thanks,
Jeeva
On Wed, May 2, 2012 at 9:24 AM, Munna S 19.mu...@gmail.com wrote:
Team,
Is there any way where we can exclude certain module from the inherited
list
Thanks,
Munna
Hi,
Regarding this issue of $1 not working have you made sure that the DNS
reverse for your server are right? Because puppet master seems to identify
the 'allow' from the reverse of the IP resolution...
Regards,
JM
On Tue, Apr 24, 2012 at 11:52 AM, Luke Bigum luke.bi...@lmax.com wrote:
Not
Hello all,
I am trying to write a script that will check logs for puppet errors to use
in a nagios check. I am checking /var/log/messages (RHEL6) but when puppet
runs on its 30 minute interval, nothing gets written to messages. I have
also looked at /var/log/puppet/puppet.log but that does not
Do you have reports=log in your puppet.conf?
On Wed, May 2, 2012 at 12:49 PM, John Kennedy skeb...@gmail.com wrote:
Hello all,
I am trying to write a script that will check logs for puppet errors to
use in a nagios check. I am checking /var/log/messages (RHEL6) but when
puppet runs on its 30
All-
We're using puppet 2.7.11.
Our custom firewall module currently builds the RHEL
/etc/sysconfig/iptables (and ip6tables) from multiple fragments using
concat::fragment.
The base part of the firewall is constructed like this:
class firewall {
include concat::setup
$firewall_config =
I vaguely recall some kind of reference mentioning that as a fallback,
puppet master would attempt to load host.fqdn.pp to find a node
definition. Is that a false memory?
In practice, it does not seem to do that.
Along those lines, is it possible to MAKE it do that?
I've tried
import
At the bottom of my site.pp I have:
import nodes/*
I haven't heard of this autoload thing, but then I'm newish.
On Wed, May 02, 2012 at 11:06:17AM -0700, Philip Brown wrote:
I vaguely recall some kind of reference mentioning that as a fallback,
puppet master would attempt to load
On Wed, May 2, 2012 at 8:53 AM, R.I.Pienaar r...@devco.net wrote:
I think you're thinking of the ENC setting the environment, not a
fact called 'environment' RI?
nope.
Anyone got a bug # for this?
pretty sure there was one but couldnt find it so I just knocked up a
So having an internal debate on whether to use puppet managed debian
preseed files to configure packages prior to installation or
installing with no-config and using puppet to manage the config files
after the fact.
The end of the discussion is that ideally one would use both, but if
one had to
- Original Message -
From: Tim Mooney tim.moo...@ndsu.edu
To: puppet-users@googlegroups.com
Sent: Wednesday, May 2, 2012 7:00:30 PM
Subject: [Puppet Users] mixing source content (templates) in
concat::fragment
All-
We're using puppet 2.7.11.
Our custom firewall module
Hi All,
I recently added the puppet-concat module in order to implement the
example motd use case. Now our motd includes a list of modules being
used on the server, which is awesome.
All the modules define an motd::register so they expect that the motd
module was included. When a node does not
Hi! I am using environments in my puppet setup, and would like to do the
same for hiera. I used to have this sort of hierarchy:
:hierarchy: - hosts/%{fqdn}
- domain/%{domain}
- whatever/%{some_fact}
- common
with a yaml datadir:
:yaml:
On 5/2/2012 1:57 PM, Guy Matz wrote:
Hi! I am using environments in my puppet setup, and would like to do
the same for hiera. I used to have this sort of hierarchy:
:hierarchy: - hosts/%{fqdn}
- domain/%{domain}
- whatever/%{some_fact}
-
On Wed, May 2, 2012 at 2:03 PM, Ramin K ramin-l...@badapple.net wrote:
On 5/2/2012 1:57 PM, Guy Matz wrote:
Hi! I am using environments in my puppet setup, and would like to do
the same for hiera. I used to have this sort of hierarchy:
:hierarchy: - hosts/%{fqdn}
-
I can attest to the fact that it works fine here is my:
:yaml:
:datadir: '/etc/puppet/env/%{environment}/hieradata'
I am having no issues with that.
On Wed, May 2, 2012 at 2:57 PM, Guy Matz gm...@matz.org wrote:
Hi! I am using environments in my puppet setup, and would like to do
I'm currently prototyping with Puppet Enterprise 2.5 and I was
wondering if compliance workflow is only in PE or if is also available
in the open source dashboard?
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To post to this group, send email
Looks like it is an Enterprise only feature:
http://puppetlabs.com/puppet/enterprise-vs-open-source/
-Brian
On Wed, May 2, 2012 at 5:26 PM, Thomas thomas.e.ke...@gmail.com wrote:
I'm currently prototyping with Puppet Enterprise 2.5 and I was
wondering if compliance workflow is only in PE or
In regard to: Re: [Puppet Users] mixing source content (templates) in...:
All-
We're using puppet 2.7.11.
Our custom firewall module currently builds the RHEL
/etc/sysconfig/iptables (and ip6tables) from multiple fragments using
concat::fragment.
The base part of the firewall is constructed
- Original Message -
From: Tim Mooney tim.moo...@ndsu.edu
To: puppet-users@googlegroups.com
Sent: Wednesday, May 2, 2012 10:39:08 PM
Subject: Re: [Puppet Users] mixing source content (templates) in
concat::fragment
In regard to: Re: [Puppet Users] mixing source content
On 5/2/2012 2:16 PM, Gary Larizza wrote:
I'm using the following which I copied from somewhere. Quotes might
be part of the missing magic. Also I'm not sure you'd want a - in
there either.
:yaml:
:datadir: '/home/puppet/environments/%{environment}/hieradata'
I would
- Original Message -
From: Ramin K ramin-l...@badapple.net
To: puppet-users@googlegroups.com
Sent: Wednesday, May 2, 2012 10:51:56 PM
Subject: Re: [Puppet Users] hiera environmentss question
On 5/2/2012 2:16 PM, Gary Larizza wrote:
I'm using the following which I copied from
I just became the Linux Admin for a large company's development team. There
are about 6 servers (ubuntu on HP) and roughly 35 people who all have
ubuntu workstations and laptops (dual boot). I have heard of puppet and
have tried to wrap my head around what it might be good for in the
On Wed, May 2, 2012 at 2:51 PM, Ramin K ramin-l...@badapple.net wrote:
On 5/2/2012 2:16 PM, Gary Larizza wrote:
I'm using the following which I copied from somewhere. Quotes might
be part of the missing magic. Also I'm not sure you'd want a - in
there either.
:yaml:
for reasons probably not important to the discussion, I am trying to transition
my Ubuntu setups from using libnss-ldap / libpam-ldap over to the libnss-ldapd
/ libpam-ldapd. There some files that have minor differences such as
/etc/pam.d/common-session.
So I have my ldap module which manages
That said, it is build on top of Puppet's puppet inspect subcommand,
so theoretically one could build an open source extension to do the
same thing.
Puppet inspect was introduced in 2.6.5:
http://projects.puppetlabs.com/issues/4943
Read here for more information:
On Wed, May 2, 2012 at 6:51 AM, jcbollinger john.bollin...@stjude.org wrote:
Yes, I understand the normal puppet way of doing things, is to have
those conf files inside the puppet tree, but it is more maintainable
*for us*, to have all multi-host related stuff, in the single rdist
directory
I've done this sort of thing (upgrading puppetmasters in my case) by having one
class (thing::mainclass) manage all the resources of the new one and depend on
another class (otherthing:removeclass) which restored/defaulted/removed
everything that shouldn't be there.
You might need to be more
Hi,
load host.fqdn.pp to find a node
it will search hostname and fqdn but not hostname.fqdn.
This all sounds like a lot of work to me. How do you intend to manage changes
that effect 300 nodes?
What I do is that I create a custom that assigns a role to certain node types.
I then have a
53 matches
Mail list logo
