On Tue, Nov 23, 2010 at 6:26 PM, Daniel Pittman wrote:
> tu2bg...@gmail.com writes:
>
> [...]
>
>> Apart from the node declaration (declaring in the inherited node as opposed
>> to the node itself) the concept is the same.
>>
>> What am I missing?
>
> Variables in the parent node are *not* visible
tu2bg...@gmail.com writes:
[...]
> Apart from the node declaration (declaring in the inherited node as opposed
> to the node itself) the concept is the same.
>
> What am I missing?
Variables in the parent node are *not* visible in the child node when you use
inheritance. Seems crazy, I know, bu
Hi all,
I run the test.pp on the master host and the notify supplies the correct
variables in the class notify and define notify.
node default {
$puppet_master = "hitw-cn-master-1"
include cn
}
node f13guest inherits default {
include test
test::thistest{"aname":}
}
notify{"outside class: $pu
Ashley Penney writes:
> We've been having some internal discussions about the best way to handle
> certain cases and I thought I'd turn to the list to solicit opinions on how
> other people have solved this issue (or don't, as the case may be). The
> issue is that we would like our modules to, w
Russell Perkins writes:
> Well It started working. I think the storeconfigs = false fixed the
> issue temporarily. I also noticed ruby-mysql was not installed, so
> that could have been causing issues.
...I see you arrived at the solution before I got there, but yes:
The error you are seeing co
On Tue, Nov 23, 2010 at 12:07 PM, Stefan Schulte
wrote:
> I think thats near to impossible.
I agree.
This kind of information needs to be collected *outside* the puppet run.
You could have a fact that reported the number of classes used in the
previous puppet run, but that's about it.
--
You
in retrospect, it might be very presumptuous of me to assume that this use
case is covered under futures.
On Tue, Nov 23, 2010 at 12:19 PM, Dan Bode wrote:
> that's is an interesting example. If we actually did implement futures in
> puppet, I would expect that to result in an error.
>
>
> On Tu
Hello,
I'm trying to establish a simple inheritance
all_hosts > all_redhat > DNS Master
DNS Slaves
Oracle RAC Nodes
Web Nodes
all_hosts > all_solaris > Web Nodes
that's is an interesting example. If we actually did implement futures in
puppet, I would expect that to result in an error.
On Tue, Nov 23, 2010 at 12:07 PM, Stefan Schulte <
stefan.schu...@taunusstein.net> wrote:
> On Tue, Nov 23, 2010 at 11:27:58AM -0800, Dan Bode wrote:
> > Hi,
> >
> > On Tue
Well It started working. I think the storeconfigs = false fixed the
issue temporarily. I also noticed ruby-mysql was not installed, so
that could have been causing issues.
Russell Perkins wrote:
> my node sets the variables to be used in my puppet.conf here is the
> puppetmasterd section of my /et
On Tue, Nov 23, 2010 at 11:27:58AM -0800, Dan Bode wrote:
> Hi,
>
> On Tue, Nov 23, 2010 at 11:21 AM, Alaric wrote:
>
> > Hi all! I've been trying to work with classes in my templates, it seems
> > like a really useful feature. I'm running on puppet .25.5 from EPEL and
> > really wanted to sta
my node sets the variables to be used in my puppet.conf here is the
puppetmasterd section of my /etc/puppet/puppet.conf. I use version
0.25.5 of puppet.
[puppetmasterd]
# autosign = true
# Storeconfigs activated
storeconfigs = true
thin_storeconfigs = true
# Sets MySQL database backend
dbadapter
Bummer! Would anyone mind if I updated to wiki to reflect that?
Thanks again for the help!
-a
On Nov 23, 2:27 pm, Dan Bode wrote:
> Hi,
>
>
>
>
>
>
>
>
>
> On Tue, Nov 23, 2010 at 11:21 AM, Alaric wrote:
> > Hi all! I've been trying to work with classes in my templates, it seems
> > like a r
On Tue, Nov 23, 2010 at 11:26:36AM -0800, Russell Perkins wrote:
> I get this error when I run puppet site.pp --noop
>
> warning: You cannot collect without storeconfigs being set on line 31
> in file /etc/puppet/modules/puppet/manifests/server/mysql.pp
>
> Storeconfigs IS set on...in like line 2
On Nov 23, 2010, at 11:26 AM, Russell Perkins wrote:
> I get this error when I run puppet site.pp --noop
>
> warning: You cannot collect without storeconfigs being set on line 31
> in file /etc/puppet/modules/puppet/manifests/server/mysql.pp
>
What's on line 31 of /etc/puppet/modules/puppet/ma
On Nov 23, 2010, at 6:45 AM, Ashley Penney wrote:
> Hi,
>
> We've been having some internal discussions about the best way to handle
> certain cases and I thought I'd turn to the list to solicit opinions on how
> other people have solved this issue (or don't, as the case may be). The
> issue
Hi,
On Tue, Nov 23, 2010 at 11:21 AM, Alaric wrote:
> Hi all! I've been trying to work with classes in my templates, it seems
> like a really useful feature. I'm running on puppet .25.5 from EPEL and
> really wanted to start making use of the ability to pivot on classes that
> have been includ
I get this error when I run puppet site.pp --noop
warning: You cannot collect without storeconfigs being set on line 31
in file /etc/puppet/modules/puppet/manifests/server/mysql.pp
Storeconfigs IS set on...in like line 22 of my node file. I modified
to the line to read $puppet_storeconfigs = "no
Hi all! I've been trying to work with classes in my templates, it seems
like a really useful feature. I'm running on puppet .25.5 from EPEL and
really wanted to start making use of the ability to pivot on classes that
have been included in the catalog. It *seems* as though the templates are
only
Thanks Dan. This was very helpful.
Regards,
Thomas Hallgren
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-us...@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr
Hi Thomas,
I don't know the docs as well as I should: I found a detailed description of
the process of compiling catalogs.
http://projects.puppetlabs.com/projects/1/wiki/Puppet_Internals
The model in puppet is implemented as a directed acyclic graph (DAG). The
vertices of the graph are resoures,
Hi,
I'm trying to find a formal description of the "Graph based model"
that puppet uses but so far I have not been able to find it. Can
someone please tell me where to look?
Thanks,
Thomas Hallgren
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" grou
So I got puppet working the way I want in a single client environment.
Now I have a puppetmaster and I'm trying to get it to setup a test VM
Centos box. I started out with the example42 configs and modified them
to fit my environment if that helps any.
I'm running into the following error -
Nov 22
On Tue, Nov 23, 2010 at 12:26 AM, donavan wrote:
> On Nov 22, 3:21 pm, "russell.fulton" wrote:
>> Over the last few weeks I have several times felt the need to test out
>> some small snippets of puppet code without having to have them in my
>> live system.
>>
>> At the moment I am doing all my te
Hi,
We've been having some internal discussions about the best way to handle
certain cases and I thought I'd turn to the list to solicit opinions on how
other people have solved this issue (or don't, as the case may be). The
issue is that we would like our modules to, where possible, check for th
>> Just a quick warning, I've found that 2.6.0 is too buggy to be useful, but
>> anything higher worked well for me.
>
> Yes, I'd say the 2.6 branch is looking pretty good. I've been on 2.6.2
> + some HEAD patches in production with no real issues. Haven't looked
> at 2.6.3 yet, but I expect that
On Nov 19, 10:56 am, Felix Frank
wrote:
> On 11/19/2010 10:15 AM, luke.bigum wrote:
>
> > Felix,
>
> > That fixes the problem, my remote file bucket now works. I'll raise a
> > bug for this.
Fixes it for me as well, thanks!
--
Mikael
--
You received this message because you are subscribed to t
On Nov 22, 3:21 pm, "russell.fulton" wrote:
> Over the last few weeks I have several times felt the need to test out
> some small snippets of puppet code without having to have them in my
> live system.
>
> At the moment I am doing all my testing by fiddling with file on the
> puppet master and th
On Nov 22, 10:51 am, Patrick wrote:
> Just a quick warning, I've found that 2.6.0 is too buggy to be useful, but
> anything higher worked well for me.
Yes, I'd say the 2.6 branch is looking pretty good. I've been on 2.6.2
+ some HEAD patches in production with no real issues. Haven't looked
at 2
On Nov 21, 6:12 pm, 張旭 wrote:
> I'm a newbie in Puppet.
> I had googled for a while,
> I just wonder if those work ? (syntax below)
There are a couple of points here. If you want to set a default
paramters for a resource[1]:
Package{ provider => yum }
I think 'allowcdrom' parameter is only for '
30 matches
Mail list logo
