[Puppet Users] Re: stored ressources and file creation
node A:
@@file{'/tmp/foo': tag = $fqdnofothernode }
other node:
File| tag == $fqdn |
cheers pete
for me this fails with:
err: Could not retrieve catalog: Puppet::Parser::Compiler failed with
error NameError: uninitialized constant ParamValue on node x
class mybackup::server inherits mybackup {
File | tag == $fqdn |
}
class mybackup::client inherits mybackup {
@@file{/tmp/$fqdn:content = $fqdn,tag
= 'backup01.myserver.net';}
}
i include the mybackup::client on one node, mybackup::server on the node
'backup01.myserver.net' and it fails with:
err: Could not retrieve catalog: Puppet::Parser::Compiler failed with
error NameError: uninitialized constant ParamValue on node x
Even with direct config in the nodes:
node 'main-1' {
@@file{/tmp/$fqdn:content = $fqdn,tag =
'backup01';}
}
node 'backup01' {
File | tag == 'backup01' |
}
regards,
Jean.
--~--~-~--~~~---~--~~
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 email to
puppet-users+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en
-~--~~~~--~~--~--~---
[Puppet Users] Re: stored ressources and file creation
Hi puppet version? Did you turn stored configs on? etc. I assume you have followed http://reductivelabs.com/trac/puppet/wiki/ExportedResources ? cheers pete --~--~-~--~~~---~--~~ 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 email to puppet-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~--~~~~--~~--~--~---
[Puppet Users] Re: Help with Passenger-based puppetmaster....
Hi Nigel Thank you for answering. I'm running Passenger 2.1.2 installed as a gem, on Debian Lenny. I'm using the Apache worker mpm. I've tried to get a Passenger setup running once before, around new year, and I couldn't get it to work then either. I don't recall what version of Passenger I used unfortunately... Should I try to downgrade my passenger...? All I get in the apache error log right now is: [ pid=6521 file=ApplicationPoolServerExecutable.cpp:392 time=2009-05-11 13:13:13.934 ]: Client 0x8096ec0: SpawnException occured (with error page) And if I visit https://puppet:8140/ manually I get: Error message:private method `warn' called for Puppet:ModuleException class:NoMethodErrorApplication root:/srv/www/puppet.fab-it.dkBacktrace: # FileLineLocation 0 /usr/lib/ruby/1.8/puppet/network/http_server/rack.rb62 in `initialize' 1 config.ru 32 in `new' 2 config.ru 32 3 /var/lib/gems/1.8/gems/passenger-2.1.2/vendor/rack-0.9.1/lib/rack/ builder.rb 29 in `instance_eval' 4 /var/lib/gems/1.8/gems/passenger-2.1.2/vendor/rack-0.9.1/lib/rack/ builder.rb 29 in `initialize' 5 config.ru 1 in `new' 6 config.ru It seems like Passenger can't spawn the Rack application. I'm using rack v. 0.4.0 as described in the UsingPassenger doc. My config.ru is exactly the same as in the doc, so I won't bother pasting it in here. Do you have any clue to what's wrong or can you give me some troubleshooting hints...? Thanks in advance. On May 11, 2009, at 01:15 , Nigel Kersten wrote: How did you install Passenger? What Debian based OS are you on? Are you running Apache worker or prefork mpm? I've had some issues getting Passenger 2.1.2 to work with some of these variants where 2.1.1 worked fine. I've yet to have time to dig into it properly though. -- Med venlig hilsen/Best regards Juri Rischel Jensen Fab:IT ApS Vesterbrogade 50 DK-1620 København Tlf: +45 70 202 407 www.fab-it.dk --~--~-~--~~~---~--~~ 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 email to puppet-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~--~~~~--~~--~--~---
[Puppet Users] Re: stored ressources and file creation
Peter Meier a écrit :
Hi
puppet version? Did you turn stored configs on? etc.
I assume you have followed
http://reductivelabs.com/trac/puppet/wiki/ExportedResources ?
cheers pete
yes,
i have the lenny puppet package running on both and yes i have stored
config running i see mysql query being done :)
facterversion = 1.5.1
puppetversion = 0.24.5
(root) mysql -V
mysql Ver 14.12 Distrib 5.0.51a, for debian-linux-gnu (i486) using
readline 5.2
if i just invert the nodes i have the very same error on the other node:
node 'main-1' {
File | tag == 'backup01' |
}
node 'backup01' {
@@file{/tmp/$fqdn:content = $fqdn,tag
= 'backup01';}
}
err: Could not retrieve catalog: Puppet::Parser::Compiler failed with
error NameError: uninitialized constant ParamValue on node main-1
regards,
Jean
--~--~-~--~~~---~--~~
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 email to
puppet-users+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en
-~--~~~~--~~--~--~---
[Puppet Users] Re: stored ressources and file creation
Jean Spirat a écrit : Peter Meier a écrit : Hi puppet version? Did you turn stored configs on? etc. I assume you have followed http://reductivelabs.com/trac/puppet/wiki/ExportedResources ? cheers pete :) when i put: File | tag == $fqdn | or File | tag == $fqdn | then it fails with err: Could not retrieve catalog: Puppet::Parser::Compiler failed with error NameError: uninitialized constant ParamValue on node backup01 If i put: File | tag == testme | i just do nothing (obviously) but if i change the file tag to : tag= testme then i got the same error. , emptying the tables of the puppetd server do not change the behavior :( If i put: File | | then the files are created... :( so there is an issue i cannot see here in the tag == part of the thing ... Jean. --~--~-~--~~~---~--~~ 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 email to puppet-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~--~~~~--~~--~--~---
[Puppet Users] Re: Tips for a new puppet setup
Hey Alan,
On Fri, May 8, 2009 at 9:11 AM, Trevor Vaughan peiriann...@gmail.com wrote:
Hi,
I would say that this is a good idea except for the custom fact part.
Since these are not items that you will 'discover' from the system, a
custom function that looks up items in a table/LDAP server/whatever
would be more appropriate.
I agree with Trevor. It really is about whether or not you are
talking about assignment or discovery. If you are discovering
intrinsic qualities of a node then a custom fact makes sense. If you
are assigning a value to a node or your provisioning tool is assigning
that value then a function makes sense. Obviously, there is a gray
area here. Alternatively, you could use an external nodes to tool.
Currently, LDAP functions as a external nodes terminus,
http://reductivelabs.com/trac/puppet/wiki/LDAPNodes.
This reduces the load on both your clients and your network. Yes, not
by much for only two facts but, once you start down this path, you
will rapidly have a glut of facts that could more easily be discovered
by the server.
Trevor
On Wed, May 6, 2009 at 03:26, Greg greg.b...@gmail.com wrote:
Alan,
One thing I found handy was to build up 2 custom facts to add into
facter: defaultroute and site.
defaultroute is used to determine which site a host is in...
Personally I found the class heirarchy
too limited since you can't inherit from multiple places... So you
would need classes like site1-webserver,
site2-webserver, site1-database, site2-database and so on... Too
annoying.
Adding in these custom facts allows you to add in config files based
on which site the node lives.
For example:
file { /etc/resolv.conf:
source = puppet:///network/resolv.conf-$site
owner = root, group = root, mode = 644
}
Heres the custom facts I added.
(Note: the default route is Solaris specific as I don't need to manage
any Linux boxes at my site)
(Also note: My knowledge of Ruby is *really* basic at this stage,
apologies if this code is bad)
defaultroute.rb:
Facter.add(defaultroute) do
setcode do
defroutefh = File.open(/etc/defaultrouter)
defroutefh.readline.chomp
end
end
site.rb:
Facter.add(site) do
setcode do
case Facter.value('defaultroute')
when 10.0.0.1
site1
when 10.0.0.2, 10.0.0.3
site2
else
unknown
end
end
end
Now, this makes the answer to q1 a bit easier... I have mine
modularised into groups based on what the config is about. Networking
config is in one module, sudo management in another and so on. That
way its (hopefully) more sane when you come to make changes. I guess
the granularity that you put this on is up to you.
2. I will leave this one to someone more experienced with Puppet than
me, but I use modules to group similar classes
together - kind of like a library. Its probably a very simplistic view
of things, but so far it has worked well for me...
3. My svn repository is set up as follows:
- baseline/
Main trunk - This is where most of the work gets done... Keep
your live Puppet Master config tree here...
- tags/
Contains discrete release views.
- branches/
Haven't used this yet, but I'm planning on using this for
larger changes, development work and so forth...
I'm sure I have missed out something that I'm going to need later on,
but figure its a reasonable starting point...
--
Teyo Tyree :: www.reductivelabs.com :: +1.615.275.5066
--~--~-~--~~~---~--~~
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 email to
puppet-users+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en
-~--~~~~--~~--~--~---
[Puppet Users] Re: Need to use base.rb and parsedfile.rb in a new resource type.
On May 7, 2009, at 5:54 AM, Manish Chakravarty wrote: Hello Everyone, First, let me describe what I plan to do: I want to write monit provider which a) populates the configuration file b) restarts monit I have written the two pieces separately. The first piece inherits from parsedfile and does the configuration file properly The second piece inherits from base.rb and provides commands to stop/start/restart service. I want to combine them into one piece for a complete monit resource type. How do you suggest I go about doing it? I'm not sure that's actually what you want. You need a resource type that manages monit configuration files, but the resource type that manages the monit service should probably just be a normal service resource. You could have your resource automatically notify the monit resource (there's no hook for that, but you can just add the relationship in the initialize method or something). -- The trouble with the rat race is that even if you win, you're still a rat. -- Lily Tomlin - Luke Kanies | http://reductivelabs.com | http://madstop.com --~--~-~--~~~---~--~~ 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 email to puppet-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~--~~~~--~~--~--~---
[Puppet Users] cron type autorequire?
Just ran into a dependency issue with 0.24.8. The system was trying to add a crontab entry for a user it had not yet created. I do have the user being created with the user type. I started to look into the code and it seems the user is not setup with autorequire. My question is should it? If so, I can file a bug. If not, I would be interested in the reasoning behind it. Thanks - JimP --- @(#) $Id: dot.signature,v 1.15 2007/12/27 15:06:13 pirzyk Exp $ __o j...@pirzyk.org --- _'\,_ (*)/ (*) I'd rather be out biking. PGP.sig Description: This is a digitally signed message part
[Puppet Users] Re: Help with Passenger-based puppetmaster....
Juri, On May 11, 1:20 pm, Juri Rischel Jensen j...@fab-it.dk wrote: And if I visithttps://puppet:8140/manually I get: Error message:private method `warn' called for Puppet:ModuleException class:NoMethodErrorApplication root:/srv/www/puppet.fab-it.dkBacktrace: # File Line Location 0 /usr/lib/ruby/1.8/puppet/network/http_server/rack.rb 62 in `initialize' 1 config.ru 32 in `new' 2 config.ru 32 3 /var/lib/gems/1.8/gems/passenger-2.1.2/vendor/rack-0.9.1/lib/rack/ builder.rb 29 in `instance_eval' 4 /var/lib/gems/1.8/gems/passenger-2.1.2/vendor/rack-0.9.1/lib/rack/ builder.rb 29 in `initialize' 5 config.ru 1 in `new' 6 config.ru Seems like you've triggered a bug here. Puppet is trying to tell you that the puppetmaster process is not called puppetmasterd, but printing the warning fails (because of the bug). You should probably rename the directory which contains config.ru to puppetmasterd. Christian --~--~-~--~~~---~--~~ 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 email to puppet-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~--~~~~--~~--~--~---
[Puppet Users] Re: Help with Passenger-based puppetmaster....
Thank you, Christian - that did it! How the h**l did you guess that, out of that vague error message..? Thanks again, man. Now I can get on with my new setup... On May 12, 2009, at 24:03 , ch+...@zeha.at wrote: Seems like you've triggered a bug here. Puppet is trying to tell you that the puppetmaster process is not called puppetmasterd, but printing the warning fails (because of the bug). You should probably rename the directory which contains config.ru to puppetmasterd. -- Med venlig hilsen/Best regards Juri Rischel Jensen Fab:IT ApS Vesterbrogade 50 DK-1620 København Tlf: +45 70 202 407 www.fab-it.dk --~--~-~--~~~---~--~~ 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 email to puppet-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~--~~~~--~~--~--~---
[Puppet Users] Re: stored/virtual ressources
On May 7, 2009, at 2:42 PM, Jean Spirat wrote:
For the stored config i use this:
in the client node i do :
include backupset::client
backupset::client::backupme{ 'mybackup': }
inside the backupset::client class i have:
define backupme( $periode='1',
$rsyncversion='29+',
$serveur='backup01.myserver.com'){
@@file { /etc/BackupPC/serveurs/$fqdn:
content =
template(backupset/hostfile.erb),
tag = $serveur;
}
}
in the server node i got:
include backupset::server
inside the backupset::server class i have :
File | tag == $fqdn |
but this never create any files on the server side :(
i got :
err: Could not retrieve catalog: Puppet::Parser::Compiler failed with
error NameError: uninitialized constant ParamValue on node
backup01.myserver.com
i am kind of lost here on why it does not work:)
This is a problem with our Rails integration. Modify your lib/puppet/
rails/resource.rb file to have this at the top:
has_many :param_values, :dependent = :destroy, :class_name =
Puppet::Rails::ParamValue
has_many :param_names, :through = :param_values, :class_name =
Puppet::Rails::ParamName
has_many :resource_tags, :dependent = :destroy, :class_name =
Puppet::Rails::ResourceTag
has_many :puppet_tags, :through = :resource_tags, :class_name =
Puppet::Rails::PuppetTag
Replacing the existing code, of course.
--
Charm is a way of getting the answer yes without asking a clear
question. -- Albert Camus
-
Luke Kanies | http://reductivelabs.com | http://madstop.com
--~--~-~--~~~---~--~~
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 email to
puppet-users+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en
-~--~~~~--~~--~--~---
[Puppet Users] Re: FreeBSD pw user provider password management
On May 8, 2009, at 3:55 AM, Andrew Wasilczuk wrote: Peter Burkholder wrote: Is it this issue? http://projects.reductivelabs.com/issues/1511 You need to have ruby-shadow library and restart puppetd. Thanks for your reply Peter. Unfortunately this issue is talking about the useradd provider and I was asking about pw (which is the only option on FreeBSD). As far as I can tell the pw provider for the user type doesn't support the password management feature at the moment and I was wandering why. Is it because of a technical issue or it just hasn't been done yet? Just hasn't been done, apparently. -- The trouble with the rat race is that even if you win, you're still a rat. -- Lily Tomlin - Luke Kanies | http://reductivelabs.com | http://madstop.com --~--~-~--~~~---~--~~ 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 email to puppet-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~--~~~~--~~--~--~---
[Puppet Users] Re: SystemStackError
On May 8, 2009, at 7:08 PM, phynias wrote: I have puppet installed on 15 identical CentOS 5.2 systems and it runs perfectly on all of them but 2. i get the following different one from each. the same version of ruby, facter, and puppet are on all machines using yum: Installed: ruby - 1.8.5-5.el5_2.6.x86_64 Installed: facter - 1.3.7-1.el5.rf.x86_64 Installed: puppet - 0.22.4-1.el5.rf.x86_64 debug: puppet: Setting vardir to '/var/lib/puppet' debug: puppet: Setting logdir to '/var/log/puppet' debug: puppet: Setting rundir to '/var/run/puppet' debug: puppet: Setting ssldir to '$vardir/ssl' debug: puppetd: Setting classfile to '$vardir/classes.txt' debug: puppetd: Setting localconfig to '$vardir/localconfig' debug: puppetd: Setting server to 'cacti.hautelook.com' /usr/lib/ruby/site_ruby/1.8/puppet/util/classgen.rb:157:in `initclass': stack level too deep (SystemStackError) from /usr/lib/ruby/site_ruby/1.8/puppet/util/classgen.rb: 156:in `each' from /usr/lib/ruby/site_ruby/1.8/puppet/util/classgen.rb: 156:in `initclass' from /usr/lib/ruby/site_ruby/1.8/puppet/util/classgen.rb: 111:in `genthing' from /usr/lib/ruby/site_ruby/1.8/puppet/util/classgen.rb:28:in `genclass' from /usr/lib/ruby/site_ruby/1.8/puppet/metatype/attributes.rb: 240:in `newparam' from /usr/lib/ruby/site_ruby/1.8/puppet/type/schedule.rb:63 from /usr/lib/ruby/site_ruby/1.8/puppet/util/classgen.rb: 118:in `class_eval' from /usr/lib/ruby/site_ruby/1.8/puppet/util/classgen.rb: 118:in `send' ... 26 levels... from /usr/lib/ruby/site_ruby/1.8/puppet/util/config.rb:588:in `use' from /usr/lib/ruby/site_ruby/1.8/puppet/network/client/ master.rb:241:in `initialize' from /usr/sbin/puppetd:308:in `new' from /usr/sbin/puppetd:308 #puppetd --debug --test /usr/lib/ruby/site_ruby/1.8/facter.rb:255:in `each_with_index': stack level too deep (SystemStackError) from /usr/lib/ruby/site_ruby/1.8/facter.rb:255:in `add' from /usr/lib/ruby/site_ruby/1.8/facter.rb:89:in `add' from /usr/lib/ruby/site_ruby/1.8/facter.rb:627:in `loadfacts' from /usr/lib/ruby/site_ruby/1.8/facter.rb:626:in `each' from /usr/lib/ruby/site_ruby/1.8/facter.rb:626:in `loadfacts' from /usr/lib/ruby/site_ruby/1.8/facter.rb:1071 from /usr/lib/ruby/site_ruby/1.8/puppet.rb:3:in `require' from /usr/lib/ruby/site_ruby/1.8/puppet.rb:3 from /usr/sbin/puppetd:157:in `require' from /usr/sbin/puppetd:157 if anyone can help me even begin to look for something that might be causing this i appreciate it so much. i have no idea how to even begin solving this. Hrm, that's a doozy, but that version of Puppet is quite old. I can't guarantee that upgrading would result in no bugs, but I'm quite confident it would result in different bugs. :) Really, though, I recommend upgrading. -- Yesterday upon the stair I met a man who wasn't there. He wasn't there again today -- I think he's from the CIA. - Luke Kanies | http://reductivelabs.com | http://madstop.com --~--~-~--~~~---~--~~ 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 email to puppet-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~--~~~~--~~--~--~---
[Puppet Users] Re: exported res with multiple tags not working
On May 10, 2009, at 6:48 PM, Ben wrote:
Luke Kanies wrote:
On May 6, 2009, at 7:36 PM, Ben wrote:
I am creating a define to manage cups printers on many servers and
would like to export the necessary 'file' and 'exec' resources with
multiple tags so i can be selective about what is realized on what
servers but i don't seem to be able to get it working with multiple
tags.
The following examples do not work and i would expect them too.
example 1:
# Export resource test w/ mulitple tags.
@@file { /tmp/test-${fqdn}: content = test ${fqdn},
tag = [ exp-res-test-${fqdn},
exp-res-test-${domain}, exp-res-test-all ];
}
File| tag == exp-res-test-${fqdn} |
On examining the database the resource is created and exported but
non
of the requested tags are created, only the autotags.
example 2:
# Export resource test w/ mulitple tags using a define.
define exp-res-test () {
tag(exp-res-test-${fqdn})
tag(exp-res-test-${domain})
tag(exp-res-test-all)
@@file { /tmp/test-${fqdn}: content = test ${fqdn}; }
}
exp-res-test { testing: }
File| tag == exp-res-test-${fqdn} |
Looking at the database for this one things are looking better, the
resource is created, exported and all the requested tags are
associated
with it but the resource is not realized by the 'File| tag ==
exp-res-test-${fqdn} |' and the file is never created.
I have tried a number of other configurations with no success. Am i
missing something or is this a bug?
What version are you using?
The tagging is a bit weird when searching for resources, because
Puppet tries to match against any item in a list, but this should
work
for the most recent versions.
Luke,
I am using the latest.
# rpm -q puppet
puppet-0.24.8-1.el5.1
Then I guess it's a bug. Please file it, and I'll try to make sure it
works in 0.25.
--
It's not that I'm afraid to die. I just don't want to be there when it
happens. -- Woody Allen
-
Luke Kanies | http://reductivelabs.com | http://madstop.com
--~--~-~--~~~---~--~~
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 email to
puppet-users+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en
-~--~~~~--~~--~--~---
[Puppet Users] Re: stored ressources and file creation
On May 11, 2009, at 6:38 AM, Jean Spirat wrote:
Peter Meier a écrit :
Hi
puppet version? Did you turn stored configs on? etc.
I assume you have followed
http://reductivelabs.com/trac/puppet/wiki/ExportedResources ?
cheers pete
yes,
i have the lenny puppet package running on both and yes i have stored
config running i see mysql query being done :)
facterversion = 1.5.1
puppetversion = 0.24.5
This is likely your problem. The bug you're encountering didn't hit
everyone, but it basically is a Rails constant lookup issue. You can
add some lines to your rails/resource.rb file, something like:
has_many :param_values, :dependent = :destroy, :class_name =
Puppet::Rails::ParamValue
has_many :param_names, :through = :param_values, :class_name =
Puppet::Rails::ParamName
has_many :resource_tags, :dependent = :destroy, :class_name =
Puppet::Rails::ResourceTag
has_many :puppet_tags, :through = :resource_tags, :class_name =
Puppet::Rails::PuppetTag
Or you can upgrade. :)
(root) mysql -V
mysql Ver 14.12 Distrib 5.0.51a, for debian-linux-gnu (i486) using
readline 5.2
if i just invert the nodes i have the very same error on the other
node:
node 'main-1' {
File | tag == 'backup01' |
}
node 'backup01' {
@@file{/tmp/$fqdn:content = $fqdn,tag
= 'backup01';}
}
err: Could not retrieve catalog: Puppet::Parser::Compiler failed with
error NameError: uninitialized constant ParamValue on node main-1
regards,
Jean
--
Talent hits a target no one else can hit; Genius hits a target no one
else can see. -- Arthur Schopenhauer
-
Luke Kanies | http://reductivelabs.com | http://madstop.com
--~--~-~--~~~---~--~~
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 email to
puppet-users+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en
-~--~~~~--~~--~--~---
[Puppet Users] Making an entire class depend on something...
Hi guys,
Is it currently possible to do something along the lines of:
class accounts {
require = Fact[blah]
...
}
Reason I ask is that I have a custom fact for the directory to use as
the base home directory
(it varies based on OS, etc.) for user accounts. The problem I have is
that when I jumpstart
a new server and put Puppet on it, the first run doesn't know about
the home directory fact
(it gets grabbed in from a different class - customfacts) and as a
result all the home directories
get created in the root directory, not in /home (or /export/home)
Now I can put in a require = Fact[blah] for every user, but that
seems somewhat excessive.
It means that for every fact that I include, I need to require that
fact for every object I use it in...
At least at a class level I can tell it what I need for that class...
Or does anyone have any other ideas on how I can tackle this?
thanks,
Greg
--~--~-~--~~~---~--~~
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 email to
puppet-users+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en
-~--~~~~--~~--~--~---
[Puppet Users] Ruby EE vs Ruby 1.8.4 results.
This was: ruby 1.8.4 (2005-12-24) [x86_64-linux] vs ruby 1.8.6 (2008-08-11 patchlevel 287) [x86_64-linux] Ruby Enterprise Edition 20090421 on Ubuntu Dapper, using Passenger with Apache. I used the puppet-test script in the ext/ directory to simulate 50 simultaneous runs with a repeat of 10. Both runs ran from the same clean state. I measured peak memory usage and total catalog compilation time (ie adding up the compiled catalog in xxx.x seconds output) with our actual Puppet configuration. Ruby 1.8.4: peak memory consumption: 2686 MB total catalog compilation time: 26632 seconds Ruby EE 20090421: peak memory consumption: 1462 MB total catalog compilation time: 13693.5 seconds wow. -- Nigel Kersten nig...@google.com System Administrator Google, Inc. --~--~-~--~~~---~--~~ 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 email to puppet-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~--~~~~--~~--~--~---
[Puppet Users] Re: Ruby EE vs Ruby 1.8.4 results.
On Mon, May 11, 2009 at 6:40 PM, Arjuna Christensen a...@junglist.gen.nz wrote: Hey, On 12/05/2009, at 1:35 PM, Nigel Kersten wrote: This was: ruby 1.8.4 (2005-12-24) [x86_64-linux] vs ruby 1.8.6 (2008-08-11 patchlevel 287) [x86_64-linux] Ruby Enterprise Edition 20090421 Might I recommend also testing the MBARI[1] patches[2] for Ruby 1.8.6/1.8.7? I've seen massive reductions (-30% real memory, 2-3x req/ s) across a variety of applications. http://wiki.github.com/brentr/matzruby http://github.com/brentr/matzruby/tree/v1_8_7_72-mbari Yep. That's next on my list. -- Nigel Kersten nig...@google.com System Administrator Google, Inc. --~--~-~--~~~---~--~~ 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 email to puppet-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~--~~~~--~~--~--~---
[Puppet Users] Re: Making an entire class depend on something...
2009/5/11 Greg greg.b...@gmail.com:
Hi guys,
Is it currently possible to do something along the lines of:
class accounts {
require = Fact[blah]
...
}
Reason I ask is that I have a custom fact for the directory to use as
the base home directory
(it varies based on OS, etc.) for user accounts. The problem I have is
that when I jumpstart
a new server and put Puppet on it, the first run doesn't know about
the home directory fact
(it gets grabbed in from a different class - customfacts) and as a
result all the home directories
get created in the root directory, not in /home (or /export/home)
Now I can put in a require = Fact[blah] for every user, but that
seems somewhat excessive.
It means that for every fact that I include, I need to require that
fact for every object I use it in...
At least at a class level I can tell it what I need for that class...
Or does anyone have any other ideas on how I can tackle this?
thanks,
Greg
To the best of my knowledge this is still something that cannot be
done. It did come up exactly one year ago in the somewhat infamous
thread Philosophical Differences[1]. You might search the
bugs/feature requests on the Reductive Labs site and if you don't find
it you should request it, as I'm pretty sure this would be a useful
thing to have.
Cheers,
.r'
[1]:
http://groups.google.com/group/puppet-users/browse_thread/thread/476957cb16b30986/cc0b79b6a1047a8c?hl=enq=class+dependencylnk=ol;
--~--~-~--~~~---~--~~
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 email to
puppet-users+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en
-~--~~~~--~~--~--~---
[Puppet Users] logging to a file
Is it possible to completely disable logging to syslog and only log to a file? --~--~-~--~~~---~--~~ 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 email to puppet-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~--~~~~--~~--~--~---
[Puppet Users] Re: logging to a file
On May 12, 3:41 pm, James Turnbull ja...@lovedthanlost.net wrote: Have a look at thehttp://reductivelabs.com/trac/puppet/wiki/ConfigurationReferencepage and the various log options. I've looked there. I've got sensible values set for all of the log related config. The closest I could find to an answer was: masterlog -- Where puppetmasterd logs. This is generally not used, since syslog is the default log destination. I can't find any mention of how to change the log destination though. --~--~-~--~~~---~--~~ 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 email to puppet-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~--~~~~--~~--~--~---
