On 01/04/2012 04:18 AM, Dan White wrote:
Have you tried importing that very file instead of *.pp?
I could, but I plan to add more node files.
I'd still like you to try. Moreover, what does a
'grep -r ^node manifests/' yield?
It appears as though your puppt apply was using an empty node
Good luck in your new position! I think the FOSS version of puppet is
very important for the spreading of puppet technology (I know small
shops like mine couldn't use it if it wasn't FOSS).
Have fun with the Puppet Platform team!
On Tue, Jan 3, 2012 at 20:41, Daniel Pittman dan...@puppetlabs.com
Hello.
In testing a potential upgrade from 2.6.7 - 2.7.9 I ran across the following
'interesting' behaviour:
The relevant section of manifest (postfixconf::generic) looks like this:
file { /etc/aliases:
mode = 444,
source = [
Hi,
On 12/28/2011 02:26 PM, sanjiv singh wrote:
If i trigger puppet client, than i will fetches all from puppet
master and deploy on it.
the complete catalog is fetched, that is true. However, the agent will
only touch resources that *do* need a change due running in your
development
Hi,
On 12/29/2011 11:29 PM, Ola wrote:
Hello
So i used this guide
http://itand.me/using-puppet-to-manage-users-passwords-and-ss
to set it up similar. Now want to do small modification. What i want
is to have all the users defined in a speciall file or a folder where
all the users are
On Jan 4, 12:48 am, Gonzalo Servat gser...@gmail.com wrote:
Hi All,
I have a particular requirement where a Puppet managed group needs to have
several members that are either local and not managed by Puppet (e.g.
mysql) or they reside in LDAP.
Apart from running an exec call to groupmems,
On Thu, Jan 5, 2012 at 1:00 AM, jcbollinger john.bollin...@stjude.orgwrote:
It depends on the Group provider, which usually depends on operating
system. If you are using the default Group provider for AIX, OS X, or
Windows, then group membership is managed as an attribute of the group
Puppet dev can help? I modified auth.conf and it did not seem to help.
On Tue, Jan 3, 2012 at 1:54 PM, Christopher Johnston chjoh...@gmail.comwrote:
I have multiple masters (40+) that reside in remote locations, I want to
have them send puppet inventory data to a central inventory with mysql.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2011-11-28 16:01, Dan White wrote:
In my users class, I want to be able to push out custom dot-files when
the user account is first created.
Unfortunately, if one sets user:managehome = true, the dotfiles are
created by default and the custom
Hi,
On Wed, 2012-01-04 at 11:51 +, John Hawkes-Reed wrote:
Hello.
In testing a potential upgrade from 2.6.7 - 2.7.9 I ran across the following
'interesting' behaviour:
The relevant section of manifest (postfixconf::generic) looks like this:
file { /etc/aliases:
mode
On 4 Jan 2012, at 16:31, Brice Figureau wrote:
Hi,
On Wed, 2012-01-04 at 11:51 +, John Hawkes-Reed wrote:
Hello.
In testing a potential upgrade from 2.6.7 - 2.7.9 I ran across the
following 'interesting' behaviour:
The relevant section of manifest (postfixconf::generic) looks
On Wed, Jan 4, 2012 at 6:00 AM, jcbollinger john.bollin...@stjude.orgwrote:
If you are using the default Group provider for AIX, OS X, or
Windows, then group membership is managed as an attribute of the group
instead of the user.
Windows can actually manage 'members' as an attribute of the
On Tue, Jan 3, 2012 at 10:54 AM, Christopher Johnston
chjoh...@gmail.com wrote:
I have multiple masters (40+) that reside in remote locations, I want to
have them send puppet inventory data to a central inventory with mysql.
Once the data is there I would like puppet dashboard installation use
On Tue, Jan 3, 2012 at 18:31, Russell Van Tassell russel...@gmail.com wrote:
On Tue, Jan 3, 2012 at 4:30 PM, Daniel Pittman dan...@puppetlabs.com wrote:
On Tue, Jan 3, 2012 at 16:01, Russell Van Tassell russel...@gmail.com
wrote:
For completeness sake, the subsequent error (with trace) is
On Wed, Jan 4, 2012 at 11:31 AM, Christopher Johnston
chjoh...@gmail.com wrote:
If it is a requirement that I have a signed CA, that could be an issue as I
have two puppet masters in each datacenter that has its own shared CA across
those two puppet masters only (certname = puppet). I don't
My inventory server is a puppetmaster, but its master of itself and is only
being using for inventory services. If I point new clients to it will work
fine.
So think of my setup like this:
puppet1.company.com and puppet2.company.com are two dedicated servers in
each datacenter that handle local
On Wed, Jan 4, 2012 at 12:12 PM, Christopher Johnston
chjoh...@gmail.com wrote:
My inventory server is a puppetmaster, but its master of itself and is only
being using for inventory services. If I point new clients to it will work
fine.
So think of my setup like this:
puppet1.company.com
That could get ugly, so I would have to create one CA, sign it then
distribute it to all of my masters. Then also delete my certs on the
clients and re-issue new ones.
Is my thinking correct here?
-Chris
On Wed, Jan 4, 2012 at 3:31 PM, Nan Liu n...@puppetlabs.com wrote:
On Wed, Jan 4, 2012
I'm trying to debug an issue I'm noticing on RHEL 6.1 puppet clients
and reporting. I've got dashboard v1.1.0 running under apache
passenger with 26 nodes.It's been pretty good for reporting status
and this is the first time i've come across an issue. The issue
appears to be cropping up
The way I've done it in the past is that you have one Puppet instance
dedicated to the initial Puppet run.. It handles the CA plus farms out
a puppet.conf which contains the local server info.
The main issue I found is that Puppet doesn't seem to change masters
without a restart even though it
Hi Vorik,
Did you solve your problem? I'm having the same issue with the 2.7.9 on
CentOS and Amazon Linux.
Puppet agent stops polling for configs and it tells me it's in progress
when I run it manually.
--
Radek
--
You received this message because you are subscribed to the Google Groups
NOTE: this is a draft document, just because there are some things here that
I'd really like to improve. Please let me know if you have a better way to do
these things. There's also a few issues with Puppet Dashboard that appear to
be bugs that need either improved documentation or changes to
As far as control of software package versions,
I would think you could use the ensure metaparameter for the package type
package { foo:
...
ensure = 1.2.3.4.5-1,
...
}
as opposed to
package { foo:
...
ensure = latest,
...
}
The first one would give you more control -
Very nice write-up, Jo. Thanks.
On Wed, Jan 4, 2012 at 5:04 PM, Jo Rhett jrh...@netconsonance.com wrote:
NOTE: this is a draft document, just because there are some things here
that I'd really like to improve. Please let me know if you have a better
way to do these things. There's also a
On Thu, Jan 5, 2012 at 3:04 AM, Jo Rhett jrh...@netconsonance.com wrote:
First many thanks for your efforts!
3. Foreman requires Ruby 1.8.7
Just wanted to correct that, the upcoming version would, but we
still maintain a supported version 0.4.x that works on RHEL5 with no issues.
Thanks,
Got nearly 300 servers in RHEL 6.0, 6.1 and 6.2 all managed by puppet and
20 of them got that behavior.
It's not related to the RHEL version neither the kernel version.
Still digging on my side, if anyone find a solution please post.
--
You received this message because you are subscribed to
I try to downgrade the puppet client and after that it still hang. All
puppet software with the same version but the problem still there.
2012/1/5 Nicolas Aizier nicolas.aiz...@googlemail.com
Got nearly 300 servers in RHEL 6.0, 6.1 and 6.2 all managed by puppet and
20 of them got that
27 matches
Mail list logo
