Hi Moty,
Note that variables in node scopes (and also true for classes) could be very
confusing and are usually the main reason to move to external nodes..
Ohad
On Wed, Sep 2, 2009 at 2:32 PM, Moty wrote:
> Hi,
>
> I like Lab42 example. I understand what you saying about sticking to
> somethin
Well,
As you said earlier I will need to customize external node script.
I need to classify my nodes and I don't like the idea of using customized
external node script to
read extra database such as csv file for example.
I thought of an idea to parse yaml output of external node script, look for
swygue wrote:
> I trying to get puppet to add an entry to /etc/hosts, but I can't get
> it to work. I have a class file host.pp with the following content:
>
> class host {
> host { "${fqdn}":
> ensure => present,
> ip => $ipaddress,
> alias =>
On 02/09/2009, at 5:43 PM, David Schmitt wrote:
>> alias => ["$fqdn", "$hostname"]
>
> yes, but you have to "include host" somewhere in the node.
Also, don't put the $fqdn into the alias field. It is automatically
added by the host provider. You just need the $hostname.
cYa,
A
On Wed, Sep 2, 2009 at 3:28 PM, Moty wrote:
> ...
> Does node classification planned for gni ? I mean the ability to define a
> group of nodes with some variables that all nodes
> in the group will inherits.
>
Sure, GNI is a node classifier solution.
I will implement two options:
1.host name bas
gr8 news :-)
On Wed, Sep 2, 2009 at 10:51 AM, Ohad Levy wrote:
> On Wed, Sep 2, 2009 at 3:28 PM, Moty wrote:
>
>> ...
>> Does node classification planned for gni ? I mean the ability to define a
>> group of nodes with some variables that all nodes
>> in the group will inherits.
>>
>
> Sure, G
btw: I myself don't use it, I use normal puppet classes instead, e.g.:
- have a default/common class which includes all the classes that I want to
be there by default.
- have a class for each host type - e.g. ,my host function is a X server, so
I have a class X which bundles all of the requirement
Hi all,
I have encountered some that I dont quite understand.
I am trying to parse log messages to create summaries, and I have seen an
event that I do not understand.
(//Node[default]/base/syslog/syslog::base/File[syslog.conf]/content) is
{md5}549c6de7a94e882b19f98ec953c8604a, should be
{md5}dd
I am attempting to set up file serving in a testing environment. I
currently have puppet/puppetmaster running "successfully" in that I
have users and hosts updating correctly across all clients, but when I
try to source /etc/sudoers, I am getting the following errors on my
client:
Sep 2 08:30:5
> Any ideas? This configuration seems pretty dead simple and it is half
> working, it's just not serving files. I am using puppet 0.24.8-1 on
> CentOS 5.3 from the epel yum repository.
Do you have a CNAME record for "puppet" in DNS? If not, try adding a
hosts entry called "puppet" to your host
I added puppet to my hosts.pp file and the change was picked up by the
client, but I still get the following errors:
Sep 2 09:26:19 vm1 puppetd[22296]: Certificate validation failed;
consider using the certname configuration option
Sep 2 09:26:19 vm1 puppetd[22296]: (//Node[default]/baseclass/s
I'm trying to use a snapshot of the upcoming 0.25 release on nontrivial
manifests for the first time, and I'm having some problems. Specifically,
I'm using the stand-alone 'puppet' executable, and find that it seems to
ignore the --modulepath option. Or, for that matter, the modulepath
setting i
> Looks like it's retrieving and diff'ing the file, but not writing it.
That's probably because the certificate is not trusted. Can you try
the following (in this order):
on the client:
rm -rf /var/lib/puppet/ssl/*
on the server:
puppetca --clean vm2.guilty.com
on the client:
/usr/sbin/puppet
Dear Puppet users and developers,
We're Solaris 10/X86 users, enjoying ZFS and Solaris
containers. In my first effort to configure a host without ever
logging in after launching Puppet, I've tried to remove a ZFS filesystem:
zfs { "rpool/export/home":
ensure => absent;
I want to have a look at Naginator. Where is the best place to start
the link from the Type reference is a dead link
http://reductivelabs.com/trac/naginator
I downloaded the project from gitrepo and had a glance, but the first thing
that I saw said that its an integration with CFEngine (in the R
So, I tried a random file in another directory and guess what, it
worked
class testfile {
file { "/tmp/testfile.txt":
source => "puppet:///files/testfile.txt"
}
}
The file ended up in /tmp/testfile.txt.
sudoers still doesn't work - thinking it was permissions based (I had
it set
No, it seems to have everything to do with replacing an existing
file. I changed the file on the server and it couldn't update it. I
remove the file on the client and it updated fine.
It happens after the puppetbuck.addfile, as shown in the debug dump
above.
I added replace => true, and it did
Ok - so the error occurs if the file already exists. I modified my
test file, restarted, and I now get the same error:
Sep 2 15:20:09 vm1 puppetd[3205]: (//Node[default]/baseclass/testfile/
File[/tmp/testfile.txt]/source) change from {md5}
f47c75614087a8dd938ba4acff252494 to puppet:///files/test
Dan,
Note that the next line says:
"Would have triggered refresh from 1 dependencies"
--Paul
On Wed, Sep 2, 2009 at 3:55 AM, Dan Bode wrote:
> Hi all,
>
> I have encountered some that I dont quite understand.
>
> I am trying to parse log messages to create summaries, and I have seen an
> event
Booyah! That was it. I had the hostname set without the fqdn there.
Thank you very much for sticking with me today.
Aaron
On Sep 2, 4:21 pm, Justin Kinney wrote:
> > Ok - so the error occurs if the file already exists. I modified my
> > test file, restarted, and I now get the same error:
> >
On Wed, Sep 2, 2009 at 2:11 PM, Dan Bode wrote:
> I want to have a look at Naginator. Where is the best place to start
>
> the link from the Type reference is a dead link
>
> http://reductivelabs.com/trac/naginator
>
> I downloaded the project from gitrepo and had a glance, but the first thing
>
This is exactly the sequence of steps that I have been doing over and
over like an insane person :). The certificate gets signed fine, and
puppet scripts are running, but serving files is failing with the
errors above. Just to be sure, I tried exactly your steps and got the
same results.
Thank
> Ok - so the error occurs if the file already exists. I modified my
> test file, restarted, and I now get the same error:
> Sep 2 15:20:09 vm1 puppetd[3205]: (//Node[default]/baseclass/testfile/
> File[/tmp/testfile.txt]/source) change from {md5}
> f47c75614087a8dd938ba4acff252494 to puppet:///
thanks, I got the idea from somewhere that naginator was a module or
something using those types for automated nagios configuration. Now its all
clear.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Puppet Users" gr
A question:
I want to make a class to delete all lines (if any) in /etc/hosts and
add this two new lines:
class hosts {
host { "$hostname":
ensure => present,
ip => "$ipaddress",
alias => ["$hostname"],
name => ["$fqdn"],
}
host { "localhost":
ensure =>
On Wed, Sep 2, 2009 at 12:15 PM, ABrown wrote:
>
> So, I tried a random file in another directory and guess what, it
> worked
>
> class testfile {
> file { "/tmp/testfile.txt":
> source => "puppet:///files/testfile.txt"
> }
> }
Did this work because you switched from:
source => "pup
Umm...thanks joseph, but I see things begins to complicate because I
don't know how to make this template :-(
I though I'd resolve my problem with some resources.
regards,
Israel.
On Sep 2, 8:50 pm, joseph.e.mcdon...@gmail.com wrote:
> You'd want to change your idea into a file resource with th
Hi,
I've just been hit by a real annoying bug with passenger:
I've changed some manifest, and some of the passenger processes picked op
the change, while others didn't, this resulted in many nodes toggling
between the old and new configuration every puppet run.
the only way to fix it eventually w
What version? Sounds like a bug to me to submit.
-L
--
Larry Ludwig
Reductive Labs
--~--~-~--~~~---~--~~
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@googlegro
Do you mean if any of init.pp files of any module change, puppetmaster
gets the change and reload?
regards,
Israel.
On Sep 1, 12:31 pm, Paul Lathrop wrote:
> Why would you want to do this? puppetmaster will notice changes to
> these files without needing to be restarted.
>
> --Paul
>
> On Sun,
You'd want to change your idea into a file resource with the content parameter
set to a template. In the template you can access the variables to set up that
line properly. Of course if you need to add more hosts to a system it will be
sort of a pita.
Sent from my Verizon Wireless BlackBerry
--
You can use:
resources{host: purge => true}
HOWEVER! this will delete any non manged resource in your /etc/hosts! handle
with care.
Ohad
On Thu, Sep 3, 2009 at 10:07 AM, ELTigre wrote:
>
> Umm...thanks joseph, but I see things begins to complicate because I
> don't know how to make this templ
puppet 0.24-8, passenger 2.2.2-1
Thanks,
Ohad
On Thu, Sep 3, 2009 at 10:11 AM, Larry Ludwig wrote:
>
> What version? Sounds like a bug to me to submit.
>
> -L
>
> --
> Larry Ludwig
> Reductive Labs
>
>
> >
>
--~--~-~--~~~---~--~~
You received this message becaus
:-) Hi Ohad, and thanks for your soon answer..
Umm, I did'nt know purge can be used in hosts resource... is purge a
global parameter others resources can use?
So, in my configuration do I have to put 3 purge => true in my 2
entries?
class hosts {
host { "$hostname":
ensure => present,
you cant use purge in the host type it self (its not support)
you can tell puppet to purge all non managed host(or cron or any other
supported resource) entries, by the line I provided before.
in general you need to put it somewhere in your manifest, I would put it in
the same place I define my ho
If you install puppet from the ubuntu 9.04 repositories (apt-get
install puppet) it sets up puppet differently than the gem. The
differences are obvious from the /etc/puppet/puppet.conf which looks
like this
[main]
logdir=/var/log/puppet
vardir=/var/lib/puppet
ssldir=/var/lib/puppet/ssl
rundir=/v
On Wed, Sep 2, 2009 at 10:32 PM, timu wrote:
>
> If you install puppet from the ubuntu 9.04 repositories (apt-get
> install puppet) it sets up puppet differently than the gem. The
> differences are obvious from the /etc/puppet/puppet.conf which looks
> like this
>
> [main]
> logdir=/var/log/puppet
2009/9/3 Thomas Bellman :
>
> I'm trying to use a snapshot of the upcoming 0.25 release on nontrivial
> manifests for the first time, and I'm having some problems. Specifically,
> I'm using the stand-alone 'puppet' executable, and find that it seems to
> ignore the --modulepath option. Or, for t
38 matches
Mail list logo
