Luke Kanies wrote:
> Appending and overriding attributes can only be done in subclasses,
> not in the same scope that the attribute is set.
>
> I'm not actually convinced this makes a ton of sense in the current
> parser, now that I think of it, though...
>
FWIW, the following does not appe
Hi.
I'm trying to create a bunch of types to manage an installation server
via cobbler. However, I don't really understand how to do it.
For example a cobbler repository is actually a record describing a YUM
repository. This could be a local mirror. So there are some
variables/properties describi
Sven Mueller schrieb:
> I did write a preliminary type, but it doesn't seem to work at all (see
> below). I put the attached file in
> /etc/puppet/modules/puppet/type/cobbler_repo.rb as per
> http://reductivelabs.com/trac/puppet/wiki/PluginsInModules, with
> effective puppetmasterd configuration c
Another reply to myself.
I also inverstigated using defines like in:
http://reductivelabs.com/trac/puppet/wiki/Recipes/AptKeys
Which resulted in this code:
define cobbler::repo($name, $source, $arch="", $ensure="present",
$local=1) {
case $ensure {
present: {
exec { "ensure_cobbler_
Could someone explain what the expected behavior of puppet is when
trying to mix external and internal nodes? The docs suggest you can
have both, but when I set node_terminus = exec, my internal (node
file) definitions don't seem to get picked up at all.
--
Eric
--~--~-~--~~--
2008/9/25 Luke Kanies <[EMAIL PROTECTED]>:
>
> On Sep 16, 2008, at 12:16 PM, Digant C Kasundra wrote:
>
>>
>> Hello everyone,
>>
>> My team and I have been mulling over the module standards that were
>> proposed (http://www.reductivelabs.com/trac/puppet/wiki/ModuleStandards
>> )
>>
>> Members of o
You created the type which provides an interface for something that you wish
to model.
The 'ensurable' call is going to do something very similar to the ensure
definition you defined with a block, but they can't both exists.
ensureable is going to look for an exists? method on the 'provider', and
Hi, I noticed the Documentation link in the page header is broken on all trac
instances. Please fix this, it will save a few clicks.
http://reductivelabs.com/trac/puppet
The doc link for the main puppet instance should point here:
http://reductivelabs.com/trac/puppet/wiki/DocumentationStart
On Sep 26, 2008, at 8:27 AM, Eric Moore wrote:
> Could someone explain what the expected behavior of puppet is when
> trying to mix external and internal nodes? The docs suggest you can
> have both, but when I set node_terminus = exec, my internal (node
> file) definitions don't seem to get pick
On Sep 26, 2008, at 3:35 PM, Eric Moore wrote:
>
> Luke Kanies <[EMAIL PROTECTED]> writes:
>
>> On Sep 26, 2008, at 8:27 AM, Eric Moore wrote:
>>
>>> Could someone explain what the expected behavior of puppet is when
>>> trying to mix external and internal nodes? The docs suggest you can
>>> hav
Luke Kanies <[EMAIL PROTECTED]> writes:
> On Sep 26, 2008, at 3:35 PM, Eric Moore wrote:
>
>>
>> Luke Kanies <[EMAIL PROTECTED]> writes:
>>
>>> On Sep 26, 2008, at 8:27 AM, Eric Moore wrote:
>>>
Could someone explain what the expected behavior of puppet is when
trying to mix external an
Luke Kanies <[EMAIL PROTECTED]> writes:
> On Sep 26, 2008, at 8:27 AM, Eric Moore wrote:
>
>> Could someone explain what the expected behavior of puppet is when
>> trying to mix external and internal nodes? The docs suggest you can
>> have both, but when I set node_terminus = exec, my internal (
On Sep 26, 2008, at 4:11 PM, Eric Moore wrote:
> When does the internal node definition get used, i.e. under what
> circumstances? What do the internal nodes do in combination with the
> external tool, and under what circumstances?
The internal and external node systems are essentially paralle
I'm trying to set up rrdgraph reporting:
I added report = true to the [puppetd] section on my clients and I
added reports = store,rrdgraph to the [puppetmasterd] section on my
puppet master. The YAML reports appear to be working and are getting
stored under /var/lib/puppet/reports, but the rrd gr
Robert,
The rrdtool-ruby package didn't work for me either I had to use the rubygems
version in order to have it start creating the rrd files. Took me a couple
of hours to figure that out since it didnt log anything that would give me
an idea of were to look.
--dn
On Fri, Sep 26, 2008 at 2:20 P
I am noticing some unexpected (to me) behavior; puppetd seems to
ignore changes to puppet.conf if it is running with --no-daemonize.
Is this a bug or a feature?
--Paul
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
John Philips wrote:
> Hi, I noticed the Documentation link in the page header is broken on all trac
> instances. Please fix this, it will save a few clicks.
>
> http://reductivelabs.com/trac/puppet
>
> The doc link for the main puppet instance sho
That worked!
Any clue on why the rrdtool-ruby doesn't work? Is it a puppet issue or
the way the rrdtool-ruby rpm was packaged? I tend to stick with rpm
packages when I can. I guess now I'll need to work on a rubygems
module for my puppet deployment.
Thanks.
On Fri, Sep 26, 2008 at 6:28 PM, Dave
Robert Foreman wrote:
> That worked!
>
There's rrdtool-ruby, which just isn't enough(TM), and then there's
ruby-rrdtool (in EPEL[1]), which is a package I own and maintain for EL5;
http://puppetmanaged.org/rrd/
Kind regards,
Jeroen van Meeuwen
-kanarip
[1] http://fedoraproject.org/wiki/EPEL
Robert Foreman wrote:
> That worked!
>
There's rrdtool-ruby, which just isn't enough(TM), and then there's
ruby-rrdtool (in EPEL[1]), which is a package I own and maintain for EL5;
http://puppetmanaged.org/rrd/
Kind regards,
Jeroen van Meeuwen
-kanarip
[1] http://fedoraproject.org/wiki/EPEL
James/Andrew,
I viewed the page source and found a hint to the problem.
http://reductivelabs.com/trac/puppet/wiki/GettingHelp";
title="Support">Support
Documentation
The Support link is correct, the Documentation link uses the 'selected' class
but has no href.
On another note, I see the
Interesting. I must be missing something. I see the rrdtool-ruby
package in epel, but I don't see ruby-rrdtool in epel.
On Fri, Sep 26, 2008 at 9:45 PM, Jeroen van Meeuwen (GMail)
<[EMAIL PROTECTED]> wrote:
>
> Robert Foreman wrote:
>> That worked!
>>
>
> There's rrdtool-ruby, which just isn't en
22 matches
Mail list logo
