On 16/04/12 21:08, puppetguest wrote:
Hi,
if possible can someone post a working example please ?
I am using hiera = puppet = augeas.
cat myserver.yaml
---
myserver:
Birthday: '1'
Debug: '5'
The no. of settings will change, so i would like to use a hash here.
The hiera
Hi Steve,
This is a long standing 'chicken and egg' situation with Puppet
installing dependencies for it's own providers. There was an issue I
thought I was watching, but I can't find it now to quote it to you.
People do different things: they either put up with the 2 pass approach,
or for
Overdue,
Walter is right in that you will need to look to another tool, such as
MCollective. Puppet is not the best at orchestrating operations across
multiple servers. It can reacting to things on one machine, like an
Apache servers' config file updating, but there's nothing in core Puppet
Just in case you haven't seen it, RIP's original concat module:
https://github.com/ripienaar/puppet-concat
It hides a lot of the concatenation implementation detail in defined
types and the temporary file fragments are stored under /var/lib/puppet/.
On 17/04/12 06:46, Wil Cooley wrote:
On
On Tuesday, April 17, 2012 8:46:33 AM UTC+3, Wil Cooley wrote:
Have you considered instead using something like the file fragment
pattern? Basically, you add 'notifiy' to sysctl::variable resources
to notify an exec that rebuilds sysctl.conf [...]
Yeah, that's what we're already doing. I
On Mon, Apr 16, 2012 at 4:55 PM, Steve Roberts strob...@strobe.net wrote:
But since the provider has already clipped the attributes they don't
get set in the first run.
when run a second time the attributes do get set correctly, but that
seems a bit kludgy to have to run puppet twice to get
Hi All,
can we use puppet dashboard for following requirements.
1. List all the nodes with the role they play.
2. View the binary versions on the nodes and also the node
status.
3. Ability to start / stop a node.
4. Have an interface to view logs from all nodes - Logs
Thanks guys that was really very helpful and did clear lots of concepts in
my mind for puppet. Absolutely brilliant that means that with collective I
can even launch the instances on EC2 aswel and can even run the required
services on demand within the boxs.
One thing I also like to know say
Yes, your Puppet Master can be an Agent, it just talks to itself. Most
people manage Puppet Agent and Master configuration with Puppet itself -
get it to manage it's own config and restart itself when it changes.
This means you only need a bunch of text files - your modules and
manifests - to
On 04/17/2012 07:14 AM, Wil Cooley wrote:
On Apr 16, 2:39 pm, Boudewijn Ector boudew...@boudewijnector.nl
wrote:
Very very simple, except for the fact that I want to add the
dependency for the mysql::database too. I'm using this excellent
module for managing
On Tuesday, April 17, 2012 11:14:15 AM UTC+3, Luke Bigum wrote:
Just in case you haven't seen it, RIP's original concat module:
https://github.com/ripienaar/puppet-concat
I hadn't seen it. Thank you for the pointer. Like I said, this is
basically what we're doing now; but It's probably
On Apr 16, 10:03 pm, Steve Roberts strob...@strobe.net wrote:
I'm hoping I'm just missing something simple.
I ran across this in my deployment setup and have replicated in a
simple set of manifests. command output and the manifests below.
basically start with a user/group name but it had
On Mon, Apr 16, 2012 at 9:52 PM, Paul Hinze paul.t.hi...@gmail.com wrote:
On Mon, Apr 16, 2012 at 4:55 PM, Steve Roberts strob...@strobe.net wrote:
But since the provider has already clipped the attributes they don't
get set in the first run.
when run a second time the attributes do get set
I think I've hit a minor permissions bug using
puppet-2.6.13-2.el6.noarch from EPEL on CentOS 6. In order to
reproduce production bugs on a test environment, I use puppet to copy
the latest backup to a test server, followed by the remainder of the
puppet-driven configuration necessary. I just
On Tue, Apr 17, 2012 at 3:52 AM, Afroz Hussain hussainaph...@gmail.com wrote:
Thanks a lot Jeff,
yes, It is an warning but still I am not able to access the dashboard,
Pasted the error:
I'm unable to decode this message in a timely manner. =)
Could you please paste the details of the
In regard to: Re: [Puppet-dev] Re: [Puppet Users] Telly: Nagios types...:
Todd, welcome and I feel your pain. Trust me, I pushed every way I
could to use native packages as our module deliver mechanism. However
we have some odd requirements that make things not work as well with
RPM (or deb,
On Tue, Apr 17, 2012 at 10:34 AM, Tim Mooney tim.moo...@ndsu.edu wrote:
In regard to: Re: [Puppet-dev] Re: [Puppet Users] Telly: Nagios types...:
Todd, welcome and I feel your pain. Trust me, I pushed every way I
could to use native packages as our module deliver mechanism. However
we
Puppet 2.7.14rc1 is a maintenance release candidate for Puppet in the
2.7.x series.
This release is on the heels of Puppet 2.7.13 because our regular
monthly release for April got preempted by our security release.
Downloads are available:
* Source
I'm doing some work on module development inside of a Vagrant VM of CentOS 6.2.
This VM has the community version of Puppet installed (2.7.13 I think), but
that doesn't include Hiera by default.
My module is dependent on Nan Liu's puppet-staging module, which requires
hiera. This puts me into
On Tue, Apr 17, 2012 at 11:08 AM, Geoff Davis gada...@ucsd.edu wrote:
I'm doing some work on module development inside of a Vagrant VM of CentOS
6.2. This VM has the community version of Puppet installed (2.7.13 I
think), but that doesn't include Hiera by default.
My module is dependent on
On Apr 18, 2012 1:39 AM, Nigel Kersten ni...@puppetlabs.com wrote:
Absolutely. This is the functionality we'll have available in Puppet.
# puppet module list
/etc/puppetlabs/puppet/production/modules
└── nigelkersten-testmac (v0.0.2)
/opt/puppet/share/puppet/modules
├──
On Tue, Apr 17, 2012 at 2:19 PM, Walter Heck walterh...@gmail.com wrote:
On Apr 18, 2012 1:39 AM, Nigel Kersten ni...@puppetlabs.com wrote:
Absolutely. This is the functionality we'll have available in Puppet.
# puppet module list
/etc/puppetlabs/puppet/production/modules
└──
Yeah, right after that email I saw the 2.7.14rc1 release notes and
answered my own question, my apologies :)
On Wed, Apr 18, 2012 at 02:26, Kelsey Hightower kel...@puppetlabs.com wrote:
On Tue, Apr 17, 2012 at 2:19 PM, Walter Heck walterh...@gmail.com wrote:
On Apr 18, 2012 1:39 AM, Nigel
That's what I'm looking for. I'll fold in that branch into my testing until it
goes mainline.
Any ETA on it going mainline?
On Apr 17, 2012, at 11:14 AM, Nigel Kersten wrote:
On Tue, Apr 17, 2012 at 11:08 AM, Geoff Davis gada...@ucsd.edu wrote:
I'm doing some work on module development
On Tue, Apr 17, 2012 at 2:28 PM, Walter Heck walterh...@gmail.com wrote:
Yeah, right after that email I saw the 2.7.14rc1 release notes and
answered my own question, my apologies :)
No worries, we're here to help.
--
You received this message because you are subscribed to the Google Groups
I'm going to review this now. Its destined for master, so someone from
the release team can probably comment on the next major release
schedule for stdlib.
On Tue, Apr 17, 2012 at 7:35 PM, Geoff Davis gada...@ucsd.edu wrote:
That's what I'm looking for. I'll fold in that branch into my testing
So.. I am evaluating Puppet Enterprise 2.5. I was messing with Live
Management and I cloned a user account to all my nodes instead of just
one. This overwrote the account settings on all my Solaris and SUSE with
the account data from a RHEL server. I'd like to know how I would undo
this,
I've found a potential issue, but I'm not sure if this is within the scope of
function_available or not.
The vagrant basebox I'm using actually does ship with puppet-hiera, but there's
no /etc/puppet/hiera.yaml
Thus, even though function_available('hiera') returns true, the function isn't
Hey Geoff,
I see that as two separate steps (Is Hiera enabled and is Hiera
configured). I think the function satisfies the former, but you might want
to write your own check for the latter (as each person probably interprets
'configured' differently). You could do a check like:
if
Alas that doesn't work as the manifest fails to compile properly without the
/etc/puppet/hiera.yaml file being there.
Nan's code does provide defaults for the hiera lookups similar to what you are
doing below, but the compiler balks before they are even evaluated.
Here's the version of
Hi,
What will be the option(s) for Puppet users with no internet connection
(not allowed), if things start to depend more on PMT and Puppet Forge?
Will we be able to make a local repo and do something like a 'puppet module
localinstall' ?
--
You received this message because you are
Hey Geoff,
We actually had a talk about this. There is this code that will help catch
that scenario FOR NOW --
https://github.com/puppetlabs/hiera-puppet/pull/23
I believe this is a bug and should DEFINITELY be fixed in source. Until
then, the 'safe_hiera()' function allows you to make this
As a +1 on this (and as the guy who wrote safe_hiera) --
It shouldn't be a function, the safety should be wrapped into hiera. But yes,
this will get you the right syntax so you can just search/replace safe_hiera
for hiera once it's fixed.
-Eric
--
Eric Shamow
Professional Services
Thank you, I appreciate it.Still learning all the interesting
nuances of this syntax. I'm not yet familiar with this $::
--
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
And here's the bug to track -- http://projects.puppetlabs.com/issues/10367
On Tue, Apr 17, 2012 at 12:31 PM, Eric Shamow e...@puppetlabs.com wrote:
As a +1 on this (and as the guy who wrote safe_hiera) --
It shouldn't be a function, the safety should be wrapped into hiera. But
yes, this
Cool, thanks for the quick response.
In the meantime, it might be helpful to ship a default hiera.yaml in the
PuppetLabs packages.
I'm using the Vagrant boxes from vstone.eu [1], and he's just pulling your
Puppet packages from yum.puppetlabs.com. [2]
Version in my VM is:
puppet.noarch
The $:: business is to force the variable look up to be in the top scope. It
didn't fix have anything to do with the conditional, I just put it there for
correctness.
In this case, you are using a variable that is set by facter, so it appears in
the top scope. Variables that you set yourself
On Tuesday, April 17, 2012 1:34:02 AM UTC-4, Wil Cooley wrote:
On Apr 15, 4:44 pm, Jesse anonym...@gmail.com wrote:
case $operatingsystem {
centos, redhat: { $ntp = ntp }
debain, ubuntu: { $ntp = ntpd }
This is backwards; centos/redhat should be 'ntpd' and debian/ubuntu
Ooops, forgot the default page:
file { 'default.html':
path = ${docu_root}/default.html,
source = puppet:///modules/apache2/default.html,
ensure = file,
require = Package[$webservice_name],
--
You received this message because you are subscribed to the Google
On Apr 17, 7:08 am, Michael Stahnke stah...@puppetlabs.com wrote:
Much of this depends on *how* you install puppet. If you use yum or
apt, I think shadow is pulled in as a dep (I know it is for rpm). If
you use gems, I'm quite sure it's not. If you're on mac or Windows you
can use the native
On Apr 16, 9:52 pm, Paul Hinze paul.t.hi...@gmail.com wrote:
I've run into this too, and worked around it by considering
ruby-shadow as a prerequisite for puppet, and therefore taking
responsibility for that package up to my bootstrapping scripts. IOW,
it is one of the short list of packages
Hi everyone,
I am using puppet setup with gem:
--
root@linux-install:/tmp# facter |egrep -i pupp|lsbdistdescription
lsbdistdescription = Debian GNU/Linux 6.0.4 (squeeze)
puppetversion = 2.7.9
root@linux-install:/tmp# gem list puppet
***
On Apr 17, 6:25 am, jcbollinger john.bollin...@stjude.org wrote:
On Apr 16, 10:03 pm, Steve Roberts strob...@strobe.net wrote:
I thought one of the key ideas for puppet was the ability to define a
manifest and puppet would make the machine look like that manifest.
That is correct. Another
So, it's choking on this still at the line with the conditional:
Apr 17 18:58:17 test-system puppet-agent[7590]: Could not retrieve
catalog from remote server: Error 400 on SERVER: Could not parse for
environment production: Syntax error at '{'; expected '}' at /etc/
/(i386|i586|i686/) =
should be
/(i386|i586|i686)/ =
shouldn't it?
Den
On 18/04/2012, at 9:01, Forrie for...@gmail.com wrote:
So, it's choking on this still at the line with the conditional:
Apr 17 18:58:17 test-system puppet-agent[7590]: Could not retrieve
Looks like you're missing a question mark in the selector in your source
parameter. It should look like this:
source = $::architecture ? {
/(i386|i586|i686)/ = puppet:///files/32/usr/local/nagios/libexec,
x86_64 = puppet:///files/64/usr/local/nagios/libexec,
}
--
Peter
On
46 matches
Mail list logo
