On 3/4/2012 8:12 PM, Brian Troutwine wrote:
(First of all, sorry for the jumbled first paragraph. I was
trying to do two things at once).
An interesting thought. If you enable graph output in your puppet.conf
http://docs.puppetlabs.com/references/stable/configuration.html#graph
you can i
An interesting thought. If you enable graph output in your puppet.conf
http://docs.puppetlabs.com/references/stable/configuration.html#graph
you can identify those sub-graphs that could run in parallel pretty
easily, just by eyeballing it. Parallel execution is wonderful for an
optimizing com
As many learning Puppet for the first time, the fact that the
order of actions is undefined unless specific metaparameters
like 'require' are used. Fine.
This got me to thinking. The GNU make program has the "-j"
option, which allows make to start more than one action
in parallel if the actions a
On Sunday, 4 March 2012 at 20:49, Elias Abacioglu wrote:
> Dominik Zyla skrev 2012-03-04 17:04:
> > Hi,
> >
> > Just take a look into your logs. You'll see something like:
> >
> > (/Stage[main]/Mcollective::Server/Service[mcollective])
> >
> > where `Mcollective::Server' points to `mcollective::
Dominik Zyla skrev 2012-03-04 17:04:
Hi,
Just take a look into your logs. You'll see something like:
(/Stage[main]/Mcollective::Server/Service[mcollective])
where `Mcollective::Server' points to `mcollective::server' subclass in the
catalog. Just look for such log format and you'll know proce
I agree with Brian.. We have three main environments (development, staging,
production) for puppet master. All based on git branches. Having such setup
you can use small staging environment for tests and while everything looks fine
just merge it with your production. You can read more about suc
Hi,
Just take a look into your logs. You'll see something like:
(/Stage[main]/Mcollective::Server/Service[mcollective])
where `Mcollective::Server' points to `mcollective::server' subclass in the
catalog. Just look for such log format and you'll know processing which
manifest puppet-agent st
$replicas works now by replacing
<% if has_variable?(scope.lookupvar('class_name::params::replicas')) then %>
with
> <% if has_variable?("class_name::params::replicas") then %>
but the problem now with $dbhost variable "else condition"
i got that error after defining $mongodb variable instead
Hi everyone,
i'm trying to apply the fully qualified variables aspect in my puppet code
and one of variables i use is an array
in template file i wrote the following :
MONGO_DATABASE_NAME =
> '<%=scope.lookupvar('class_name::params::mongodb_dbname')%>'
> <% if has_variable?(scope.lookupvar('class
