One of the things we started doing is:
1) running puppet via cron.
2) on critical production systems running with --dry-run enabled so that
NOTHING happens completely automatically.
3) emailing the output of the dry run if changes show up on a production
server.
We also have a script on an admini
Is there a way, in a puppet config, to query the current nodes config
elements and use them in a template? My specific case is a JBOSS
configuration with multiple instances on one server installation. I
have the server configured as a class (with unpacking the zip file and
making the server level
t; Hope others can also share their own info. :)
>
> Cheers,
> Rodney
>
>
>
> On Dec 5, 6:41 am, Jeffrey Hulten <[EMAIL PROTECTED]> wrote:
> > Is there a way, in a puppet config, to query the current nodes config
> > elements and use them in a template? My speci
So the way I have implemented it is that we have a basenode node with the
common elements that all nodes get. The basenode is then inherited by each
of the specific nodes, therefore you get something like:
import "foo"
import "httpd"
node basenode {
include foo
}
node webnode inherits basenode
For my money the best solution is to use Puppet to manage the yum.conf
files and put your excludes there... But that is me.
On Wed, Jan 7, 2009 at 8:06 AM, Arnau Bria wrote:
>
> Hi all,
>
> sorry for breaking the threat, I don't know where the OP is.
>
> anyway, Tim Harper provided yum_plus in
I would agree. With DRBD and uCARP almost any service can be made to
work as a active-passive cluster. It is not for the faint of heart
tho... Of course if you are managing systems with Puppet you probably
aren't faint of heart. ;)
Please note... This is not a solution for load balancing. Only
Instead of requiring the file, subscribe to it. Also, to only run when
the package changes set refreshonly to true.
file { "/test" :
source => "puppet:///test/testfile" }
exec { "run once on test file" :
cmd => "/bin/echo running",
refreshonly => true,
subscribe => File["/test"],
}
On Thu,
Another issue potentially in 0.25.5...
If I set a tag in an inherited node it is not present on directives
(files, etc.) run down the chain...
node foo {
tag(tagme)
}
node bar inherits foo {
rundefine { "no tag here" }
}
But it appears if you tag the node directly
node foo {}
node bar inher
DRBD is really intended for local networks.
Is there anything preventing a puppetmaster being a node of a
different puppetmaster? You could pass config that way.
On Thu, Jan 8, 2009 at 2:34 PM, Aaron Lippold wrote:
>
> Hi,
>
> Has anyone done this across multiple site, let's say, 13 sites, wi
If I understand the match function on strings properly you might want
to escape the periods in your logic:
10.1.1. matches 10.1.1.X and 10.101.X for instance.
On Wed, Jan 21, 2009 at 6:58 AM, wrote:
>
> Thank you for your input! I solved it like this in then end:
>
> Facter.add("netenv") do
>
Sourcing to a HTTP address works? Since when?
On Mon, Feb 23, 2009 at 4:45 PM, Peter Meier wrote:
>
> Hi
>
> > Make a regular http- or ftp-accessible repository (instead of using the
> > puppetmaster's file distribution facility), and use one of the
> > higher-level rpm-based package providers w
11 matches
Mail list logo
