On Tue, 2011-10-25 at 12:31 +0200, Davide Ferrari wrote:
> Hi
>
> I have wrote these classes
>
> http://pastebin.com/WKbUurt4
>
Forget it, it was simply a typo :/ (a missing /)
Sorry for the noise
--
Davide Ferrari
Senior System Administrator
Atrapalo S.L.
--
You rec
ppet 2.6.2
Thanks
--
Davide Ferrari
Senior System Administrator
Atrapalo S.L.
--
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 unsubscribe from this group, send em
o the
same with my own defines, is it possible?
I'm using Debian Squeeze Puppet (2.6.2) on both agent and server.
TIA
--
Davide Ferrari
Senior System Administrator
Atrapalo S.L.
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To p
On Thu, 2011-11-10 at 11:09 +0100, Davide Ferrari wrote:
> I mean, with File if you set path to a value, the path has value, but if
> you don't set a value, then it uses the "name" value. I'd like to do the
> same with my own defines, is it possible?
I'll
the dynamic scope.
Now that we are on topic: what is the fully-qualified name for node
variables? Reading the doc I guessed, seems wrongly, that they were
top-scope variables...
TIA
--
Davide Ferrari
Senior System Administrator
Atrapalo S.L.
--
You received this message because you are subsc
the
third point is a bit harder for me.
TIA
[1] I thought about a custom facter detecting if it's an
active/passivehost or no HB cluster at all, but I'd like some other
opinions.
--
Davide Ferrari
Senior System Administrator
Atrapalo S.L.
--
You received this message because you
d not by hand.
Just for the sake of curiosity: why don't you just prepare your puppet
conf to be like the default conf for that package? It's easier and saner
IMO.
--
Davide Ferrari
Senior System Administrator
Trovit Search http://www.trovit.com
--
You received this message
mess, and
then puppet it's not what you want. You probably want some system deploy
application like FAI and then manual resource management.
--
Davide Ferrari
Senior System Administrator
Trovit Search http://www.trovit.com
--
You received this message because you are subscribed to the G
readability and personally
I hate using global variables and passing parameters (but it's just a
matter of taste).
But hey, if there's any technical reason in Puppet that makes
inheritance bad, I'm all ears and happy to change my mind about it :)
[1] https://projects.puppetl
Hi
I'm trying to override a fact from facter 2.3, called "partitions"
with a custom version of this fact, via pluginsync.
The problem is that the base file in
/var/lib/puppet/lib/facter/partitions.rb, just like it's facter
brother in /usr/lib/ruby/vendor_ruby/facter/partitions.rb has a
require '
:37:in `block in run'
/usr/lib/ruby/vendor_ruby/facter/application.rb:35:in `each'
/usr/lib/ruby/vendor_ruby/facter/application.rb:35:in `run'
/usr/bin/facter:20:in `'
Anyway I'm attaching the fact that is giving me this error. The error
is thrown by
# facter -p --yaml
Ok, I'll try to see if I can find a solution by myself meanwhile.
Maybe the override should be done as you say, so, in a different
fashion than the upstream patch.
Cheers
On Mon, Jan 12, 2015 at 3:55 PM, Felix Frank
wrote:
> On 01/12/2015 01:22 PM, Davide Ferrari wrote:
>> Hello!
Mmmh it still doesn't work for me :( As a workaround, I created
another fact which just executes the "partitions" fact and then add
the labels to the appropriate partions. My PR was accepted :) so I've
just to wait a new upstream version to remove the workaround. Anyway
if you (or anybody) find som
13 matches
Mail list logo
