not that I'm aware of, but a poor mans solution would be to run puppet via
cron, and check which server can be used at that time.
e.g. get load of all puppet servers, and use the least busy one
it would be nice to have a DNS SRV record for puppet.
Ohad
On Fri, May 14, 2010 at 1:53 PM, Abhishek
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 14/05/10 4:14 PM, Ohad Levy wrote:
not that I'm aware of, but a poor mans solution would be to run puppet
via cron, and check which server can be used at that time.
e.g. get load of all puppet servers, and use the least busy one
it would be
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Welcome back to the Puppet release cycle for the third outing of
0.25.5 - release candidate number 3.
The 0.25.5 release is a maintenance release in the
0.25.x branch. It contains a number of bug fixes but also
performance enhancements including
On 5/12/2010 2:15 AM, Paul Lathrop wrote:
Hey all,
I've open-sources Digg's apache module:
http://github.com/plathrop/puppet-module-apache
I know this isn't much more advanced than what I've seen a lot of
people using. Here's my proposition, though. Let's get all the
disparate apache modules
On Thu, 2010-05-13 at 22:53 -0700, Abhishek wrote:
Hi,
Is there any way to define multiple puppet servers in client
configuration so that if my one puppet server is down then my
production config changes can be applied from other puppet server. I
am using apache and Mongrel for puppet load
On 12 May 2010 16:13, Thomas Bellman bell...@nsc.liu.se wrote:
[..]
I don't create the logical volumes automatically, nor do I
partition or create filesystems on them automatically, to lessen
the risk of destroying important data.
Good info. I do much the same - logical vols are managed by
On Thu, May 13, 2010 at 7:55 PM, josbal joshua.bald...@gmail.com wrote:
Have you found a solution to this problem? I am having the same issue
after upgrading to puppet 0.25.4 and passenger.
The error message im getting is: Error 400 on SERVER: Not authorized
to call find on
James Turnbull wrote:
The release candidate is available at:
http://puppetlabs.com/downloads/puppet/puppet-0.25.5rc3.tar.gz
For thoae using Fedora or RHEL/CentOS, I've updated the yum repos at:
http://tmz.fedorapeople.org/repo/puppet/
Packages for EL 4 - 6 and Fedora 11 - 13 are
On May 13, 10:53 pm, Abhishek abhishek.r...@gmail.com wrote:
Hi,
Is there any way to define multiple puppet servers in client
configuration so that if my one puppet server is down then my
production config changes can be applied from other puppet server. I
am using apache and Mongrel for
On May 12, 1:03 am, Rohan McGovern rohan.mcgov...@nokia.com wrote:
I've been doing it like this, for an example module
named baselayout:
modules/baselayout/manifests/init.pp:
import *
class baselayout {
case $operatingsystem {
Darwin: { include baselayout::mac }
The afternoon during the USENIX Configuration Management workshop is
going to be for set user talks + a barcamp format.
Currently the organizers are looking for folks to do some user topics,
such as How I used X to do Foo, or Automating a Blarg or ... maybe
you've got something more exciting :)
On 05/14/2010 01:21 PM, Michael DeHaan wrote:
The afternoon during the USENIX Configuration Management workshop is
going to be for set user talks + a barcamp format.
Currently the organizers are looking for folks to do some user topics,
such as How I used X to do Foo, or Automating a Blarg or
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/02/10 23:40, Taylor wrote:
Hi All,
I'm reading the docs and various references available for Puppet but
can't seem to find a better way of accomplishing my goal of binding my
Linux Servers to Active Directory. (Please don't berate me for
(As there is no puppet-jobs list)
TomTom Services Delivery is currently looking for new staff with
Puppet experience at all levels from operations to architecture. Our
Technical Operations team is based in Amsterdam in the Netherlands and
manages a large environment of Red Hat servers.
A
Just to put my $0.02 in... the 'exec' command is similar in my setup -
but I do a little bit of maintenance as well (like a customized
lsassd.conf file) - Note I also unwrapped the .rpm files so I could
put them in a serviced repo... :
class likewise {
$rpmlist = [ likewise-lwio,
Hi,
Is there any way to define multiple puppet servers in client
configuration so that if my one puppet server is down then my
production config changes can be applied from other puppet server. I
am using apache and Mongrel for puppet load balancing.
Shouldn't your load balancing take care of
On Fri, May 14, 2010 at 2:26 PM, Kinzel, David david.kin...@encana.com wrote:
Hi,
Is there any way to define multiple puppet servers in client
configuration so that if my one puppet server is down then my
production config changes can be applied from other puppet server. I
am using apache and
Somewhere in the 20-40 minute range. I don't think it's been quite
decided yet.
On Fri, May 14, 2010 at 1:49 PM, Joe McDonagh
joseph.e.mcdon...@gmail.com wrote:
On 05/14/2010 01:21 PM, Michael DeHaan wrote:
The afternoon during the USENIX Configuration Management workshop is
going to be for
Hmm
Does this thread help you? We should fix the error message, also, IMHO.
http://markmail.org/message/aydpf243lu6uub5a#query:uninitialized%20constant%20Puppet%3A%3ANetwork%3A%3AAuthStore+page:1+mid:lelvuzkis2xzruyc+state:results
--Michael
On Thu, May 13, 2010 at 7:15 PM, Eric
You are getting a bunch of misguided answers to this. I'm also
perplexed by your assertion that external nodes requires you to write
custom scripts to parse node manifests.
No, you cannot put resources directly into nodes when you are using
external nodes. In practice, this hasn't mattered; you
I've been waiting forhttp://projects.puppetlabs.com/issues/1866
(Support for specification of multiple servers). 3669 looks to
duplicate a lot of the functionality. The obvious difference being
static config or SRV records providing the list of available hosts.
Personally I'd be pleased with
Assuming the client has puppeted at least once against that server. This
won't work for bootstrapping a client though will it?
it does, the facts yaml file is created before the external node
classifier is called ;)
Whoa. This should be called out in the external node docs, as I simply
What you gain is truly node-scoped variables (AWESOME). Contrary to
Ken's assertion about global variables, instead you have your external
node script place variables into the output YAML; these variables are
then available to all the classes and resources that apply to that
node.
I
Speaking of external nodes..
Any decent tutorials out there for someone that has no idea where to start? ;)
-Original Message-
From: puppet-users@googlegroups.com [mailto:puppet-us...@googlegroups.com] On
Behalf Of Ken
Sent: Friday, May 14, 2010 4:28 PM
To: Puppet Users
Subject: [Puppet
On May 14, 1:39 pm, Ken k...@bob.sh wrote:
Also I just realised - if the client does it using SRV with weights
and priorities - you get global server load balancing built in. Cool
bananas.
ken.
That exact functionality is actually a big benefit to me. As an
example we have multiple geo
Ok, I may got what went wrong. Since I'm using puppet in a ubuntu
distro, I installed it from repositories, which setup everything to
run with puppet user, including file permissions. But after installing
it, I only run the puppetmaster it with sudo and --no-daemonize to see
messages and stuff.
Hi Nigel,
Yes i am using environments. I have a production (default)
environement and a testing environment.
All my hosts us the production environment currently.
Here is what my puppetmasterd puppet.conf file looks like:
[main]
# Where Puppet stores dynamic and growing data.
# The
On Fri, May 14, 2010 at 1:42 PM, Paul Lathrop paul.lath...@gmail.comwrote:
Assuming the client has puppeted at least once against that server.
This
won't work for bootstrapping a client though will it?
it does, the facts yaml file is created before the external node
classifier is
On Fri, May 14, 2010 at 5:11 PM, josbal joshua.bald...@gmail.com wrote:
Hi Nigel,
Yes i am using environments. I have a production (default)
environement and a testing environment.
All my hosts us the production environment currently.
Here is what my puppetmasterd puppet.conf file looks
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 15/05/10 6:42 AM, Paul Lathrop wrote:
Assuming the client has puppeted at least once against that server. This
won't work for bootstrapping a client though will it?
it does, the facts yaml file is created before the external node
classifier is
On Fri, May 14, 2010 at 6:01 PM, Nigel Kersten nig...@google.com wrote:
On Fri, May 14, 2010 at 1:42 PM, Paul Lathrop paul.lath...@gmail.comwrote:
Assuming the client has puppeted at least once against that server.
This
won't work for bootstrapping a client though will it?
it does,
31 matches
Mail list logo
