Re: [Puppet Users] Re: London meetup during Training days
On 28 March 2010 13:11, Al @ Lab42 wrote: > London is calling, wednesday 31 is approaching... where and at what > hour are we going to meet up? > Londoners decide... possibly not too far from County House, Conway > Mews. I recommend Mason's Arms, 8 Devonshire Street, W1W 5EA, which I think was the scene of a previous meet. May not be able to make it myself though... :( HTH Gary -- Gary Law -- 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...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Passenger Apache2 Certificates
Hi Grifith, Puppet includes by default a CA, therefor if you had puppet working before (with a puppetmaster) then all you need to do is to find the relevant fines in your /var/lib/puppet/ssl dir :) something in the spirit of http://github.com/ohadlevy/puppet-multipuppetmaster/blob/master/templates/puppetmaster-vhost.confshould work. Ohad On Tue, Mar 30, 2010 at 1:46 PM, Smain Kahlouch wrote: > Hi everyone, > > I'm trying to migrate my puppetmaster to Passenger and i was wondering > how can i generate the following lines in apache2 configuration : > > ... > SSLCertificateFile /var/lib/puppet/ssl/certs/puppet.koumbit.net.pem > SSLCertificateKeyFile > /var/lib/puppet/ssl/private_keys/puppet.koumbit.net.pem > SSLCertificateChainFile /var/lib/puppet/ssl/ca/ca_crt.pem > SSLCACertificateFile/var/lib/puppet/ssl/ca/ca_crt.pem > ... > > I already know how to generate an autosigned certificate but i don't have a > certificate autority. > > How did you managed that ? > > Thanks for your help. > > Regards > Grifith > > -- > 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...@googlegroups.com > . > For more options, visit this group at > http://groups.google.com/group/puppet-users?hl=en. > > -- 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...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Passenger Apache2 Certificates
Hi everyone, I'm trying to migrate my puppetmaster to Passenger and i was wondering how can i generate the following lines in apache2 configuration : ... SSLCertificateFile /var/lib/puppet/ssl/certs/puppet.koumbit.net.pem SSLCertificateKeyFile /var/lib/puppet/ssl/private_keys/puppet.koumbit.net.pem SSLCertificateChainFile /var/lib/puppet/ssl/ca/ca_crt.pem SSLCACertificateFile/var/lib/puppet/ssl/ca/ca_crt.pem ... I already know how to generate an autosigned certificate but i don't have a certificate autority. How did you managed that ? Thanks for your help. Regards Grifith -- 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...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Puppet Labs is hiring...
...and you are just the kind of people want to hire. http://www.puppetlabs.com/company/jobs/ Cheers, Teyo -- 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...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Re: facter or ifconfig to find hosts with ip on certain subnet
On Mar 28, 8:47 pm, deet wrote: > I like the idea of accessing this information through facter instead > of needlessly running ifconfig again. Indeed. Take a look at the facter libraries, they're quite readable overall. Plenty of good bits in 'facter/util' that you can use also. > Is their any "standard" location to put a config.yml file like in > your above example? Or just where ever I happen to store config files > at my location? I think i'll extend your example for default gateway > lookups. I think /usr/local/etc/ is pretty standard for configs that aren't supplied by the base os. If they're specific to a single program you could also see "/usr/local/$program/". Check 'man hier' of your platform of choice for more info. In my case we're using config.yml to store all those site common settings that usually get embedded into 10 different scripts and then forgotten. Ive done similar facts for providing gateway & broadcast addresses based on existing facts. Those were used for dhcp servers to automagically build dhcp.conf settings for attached networks. Let me know if you have any questions. -- 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...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Source and Template file defaults
On Tue, Mar 23, 2010 at 4:00 AM, Thomas Bellman wrote:
> Douglas Garstang wrote:
>
>> On Mon, Mar 22, 2010 at 7:15 PM, Ohad Levy wrote:
>
>>> Hmm.. Puppet does not support going over multiple templates like it does
>>> in
>>> plain files.
>>>
>>> maybe there is even a feature request for it ;)
>>
>> Aw crap. I've been told that twice in the last few days. Is there
>> another way I could emulate this functionality, because I really
>> really need it.
>
> You could do it like this:
>
> $templ = file("/config/foo/xyzzy.$fqdn.erb",
> "/config/foo/xyzzy.default.erb")
> $content = inline_template($templ)
> file {
> "/my/file": content => $content;
> }
>
> Unfortunately, the file() function requires paths to be specified with
> an absolute path, and doesn't look up paths either via the fileserver.conf
> modules (like puppet:/// URLs do), or modules in your manifests (like the
> template() function do). So, it can be done, but it's not very nice.
Is this supported in puppet 0.24.x or is it a 0.25 thing? The docs
don't say what version of the puppet they refer to.
Doug.
--
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...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Adding System Account
What option I need to use to create a system account with "Puppet"? Like the bellow command: useradd -r nagios -s /sbin/nologin -d /var/lib/nagios -m nagios Sorry for this newbie question, I'm new in Puppet configuration :) Thanks ! -- 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...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Re: err: Got an uncaught exception of type ArgumentError: Field 'value' is required
Changed. Same error.
But if I add
:optional => %w{value}
into record_line this seems to fix the issue - and seems to work and I
am not really sure why because I did not find anywhere a complete
documentation on parsed file ( May be someone know where to get it -
without reading sources)
Thank you.
--
Maxim Ianoglo
On Mar 29, 9:54 pm, Dan Bode wrote:
> I just saw the mistake.
>
> The fields for parsedfile need to be properties, not parameters.
>
> change
>
> newparam(:value) do
> desc "The value to set"
> end
>
> to
>
> newproperty(:value) do
> desc "The value to set"
> end
>
> and it should work.
>
> On Mon, Mar 29, 2010 at 11:36 AM, .Nox wrote:
> > Hello,
>
> > [r...@vps1 ~]$ puppetd --server test --waitforcert 60 --test --trace
> > info: Retrieving plugin
> > warning: newstate() has been deprecrated; use newproperty(value)
> > info: Caching catalog for vps1.srv171.rackco.com
> > info: Applying configuration version '1269887449'
> > notice: //r::ssh/Ssh::Set_value[PermitRootLogin]/
> > Sshd_param[PermitRootLogin]/ensure: created
> > /usr/lib/ruby/site_ruby/1.8/puppet/util/fileparsing.rb:95:in `join'
> > /usr/lib/ruby/site_ruby/1.8/puppet/util/fileparsing.rb:89:in `collect'
> > /usr/lib/ruby/site_ruby/1.8/puppet/util/fileparsing.rb:89:in `join'
> > /usr/lib/ruby/site_ruby/1.8/puppet/util/fileparsing.rb:341:in
> > `to_line'
> > /usr/lib/ruby/site_ruby/1.8/puppet/util/fileparsing.rb:314:in
> > `to_file'
> > /usr/lib/ruby/site_ruby/1.8/puppet/util/fileparsing.rb:314:in
> > `collect'
> > /usr/lib/ruby/site_ruby/1.8/puppet/util/fileparsing.rb:314:in
> > `to_file'
> > /usr/lib/ruby/site_ruby/1.8/puppet/provider/parsedfile.rb:316:in
> > `to_file'
> > /usr/lib/ruby/site_ruby/1.8/puppet/provider/parsedfile.rb:102:in
> > `flush_target'
> > /usr/lib/ruby/site_ruby/1.8/puppet/provider/parsedfile.rb:74:in
> > `flush'
> > /usr/lib/ruby/site_ruby/1.8/puppet/provider/parsedfile.rb:72:in `each'
> > /usr/lib/ruby/site_ruby/1.8/puppet/provider/parsedfile.rb:72:in
> > `flush'
> > /usr/lib/ruby/site_ruby/1.8/puppet/provider/parsedfile.rb:356:in
> > `flush'
> > /usr/lib/ruby/site_ruby/1.8/puppet/type.rb:752:in `flush'
> > /usr/lib/ruby/site_ruby/1.8/puppet/transaction.rb:94:in `apply'
> > /usr/lib/ruby/site_ruby/1.8/puppet/transaction.rb:251:in
> > `eval_children_and_apply_resource'
> > /usr/lib/ruby/site_ruby/1.8/puppet/util.rb:418:in `thinmark'
> > /usr/lib/ruby/1.8/benchmark.rb:293:in `measure'
> > /usr/lib/ruby/1.8/benchmark.rb:307:in `realtime'
> > /usr/lib/ruby/site_ruby/1.8/puppet/util.rb:417:in `thinmark'
> > /usr/lib/ruby/site_ruby/1.8/puppet/transaction.rb:250:in
> > `eval_children_and_apply_resource'
> > /usr/lib/ruby/site_ruby/1.8/puppet/transaction.rb:207:in
> > `eval_resource'
> > /usr/lib/ruby/site_ruby/1.8/puppet/transaction.rb:296:in `evaluate'
> > /usr/lib/ruby/site_ruby/1.8/puppet/util.rb:418:in `thinmark'
> > /usr/lib/ruby/1.8/benchmark.rb:293:in `measure'
> > /usr/lib/ruby/1.8/benchmark.rb:307:in `realtime'
> > /usr/lib/ruby/site_ruby/1.8/puppet/util.rb:417:in `thinmark'
> > /usr/lib/ruby/site_ruby/1.8/puppet/transaction.rb:295:in `evaluate'
> > /usr/lib/ruby/site_ruby/1.8/puppet/transaction.rb:289:in `collect'
> > /usr/lib/ruby/site_ruby/1.8/puppet/transaction.rb:289:in `evaluate'
> > /usr/lib/ruby/site_ruby/1.8/puppet/resource/catalog.rb:142:in `apply'
> > /usr/lib/ruby/site_ruby/1.8/puppet/configurer.rb:169:in `run'
> > /usr/lib/ruby/site_ruby/1.8/puppet/util.rb:178:in `benchmark'
> > /usr/lib/ruby/1.8/benchmark.rb:293:in `measure'
> > /usr/lib/ruby/1.8/benchmark.rb:307:in `realtime'
> > /usr/lib/ruby/site_ruby/1.8/puppet/util.rb:177:in `benchmark'
> > /usr/lib/ruby/site_ruby/1.8/puppet/configurer.rb:168:in `run'
> > /usr/lib/ruby/site_ruby/1.8/puppet/agent.rb:53:in `run'
> > /usr/lib/ruby/site_ruby/1.8/puppet/agent/locker.rb:21:in `lock'
> > /usr/lib/ruby/site_ruby/1.8/puppet/agent.rb:53:in `run'
> > /usr/lib/ruby/1.8/sync.rb:229:in `synchronize'
> > /usr/lib/ruby/site_ruby/1.8/puppet/agent.rb:53:in `run'
> > /usr/lib/ruby/site_ruby/1.8/puppet/agent.rb:134:in `with_client'
> > /usr/lib/ruby/site_ruby/1.8/puppet/agent.rb:51:in `run'
> > /usr/lib/ruby/site_ruby/1.8/puppet/application/puppetd.rb:103:in
> > `onetime'
> > /usr/lib/ruby/site_ruby/1.8/puppet/application.rb:226:in `send'
> > /usr/lib/ruby/site_ruby/1.8/puppet/application.rb:226:in `run_command'
> > /usr/lib/ruby/site_ruby/1.8/puppet/application.rb:217:in `run'
> > /usr/lib/ruby/site_ruby/1.8/puppet/application.rb:306:in
> > `exit_on_fail'
> > /usr/lib/ruby/site_ruby/1.8/puppet/application.rb:217:in `run'
> > /usr/sbin/puppetd:159
> > err: Got an uncaught exception of type ArgumentError: Field 'value' is
> > required
> > warning: Value of 'preferred_serialization_format' (pson) is invalid
> > for report, using default (marshal)
> > notice: Finished catalog run in 3.01 seconds
>
> > Thank you.
> > --
> > Maxim Ianoglo
>
> > On Mar 29, 8:04 pm, Dan Bode wrote:
> > > On Sun, Mar 28, 2010 at 2:
Re: [Puppet Users] Re: err: Got an uncaught exception of type ArgumentError: Field 'value' is required
I just saw the mistake. The fields for parsedfile need to be properties, not parameters. change newparam(:value) do desc "The value to set" end to newproperty(:value) do desc "The value to set" end and it should work. On Mon, Mar 29, 2010 at 11:36 AM, .Nox wrote: > Hello, > > [r...@vps1 ~]$ puppetd --server test --waitforcert 60 --test --trace > info: Retrieving plugin > warning: newstate() has been deprecrated; use newproperty(value) > info: Caching catalog for vps1.srv171.rackco.com > info: Applying configuration version '1269887449' > notice: //r::ssh/Ssh::Set_value[PermitRootLogin]/ > Sshd_param[PermitRootLogin]/ensure: created > /usr/lib/ruby/site_ruby/1.8/puppet/util/fileparsing.rb:95:in `join' > /usr/lib/ruby/site_ruby/1.8/puppet/util/fileparsing.rb:89:in `collect' > /usr/lib/ruby/site_ruby/1.8/puppet/util/fileparsing.rb:89:in `join' > /usr/lib/ruby/site_ruby/1.8/puppet/util/fileparsing.rb:341:in > `to_line' > /usr/lib/ruby/site_ruby/1.8/puppet/util/fileparsing.rb:314:in > `to_file' > /usr/lib/ruby/site_ruby/1.8/puppet/util/fileparsing.rb:314:in > `collect' > /usr/lib/ruby/site_ruby/1.8/puppet/util/fileparsing.rb:314:in > `to_file' > /usr/lib/ruby/site_ruby/1.8/puppet/provider/parsedfile.rb:316:in > `to_file' > /usr/lib/ruby/site_ruby/1.8/puppet/provider/parsedfile.rb:102:in > `flush_target' > /usr/lib/ruby/site_ruby/1.8/puppet/provider/parsedfile.rb:74:in > `flush' > /usr/lib/ruby/site_ruby/1.8/puppet/provider/parsedfile.rb:72:in `each' > /usr/lib/ruby/site_ruby/1.8/puppet/provider/parsedfile.rb:72:in > `flush' > /usr/lib/ruby/site_ruby/1.8/puppet/provider/parsedfile.rb:356:in > `flush' > /usr/lib/ruby/site_ruby/1.8/puppet/type.rb:752:in `flush' > /usr/lib/ruby/site_ruby/1.8/puppet/transaction.rb:94:in `apply' > /usr/lib/ruby/site_ruby/1.8/puppet/transaction.rb:251:in > `eval_children_and_apply_resource' > /usr/lib/ruby/site_ruby/1.8/puppet/util.rb:418:in `thinmark' > /usr/lib/ruby/1.8/benchmark.rb:293:in `measure' > /usr/lib/ruby/1.8/benchmark.rb:307:in `realtime' > /usr/lib/ruby/site_ruby/1.8/puppet/util.rb:417:in `thinmark' > /usr/lib/ruby/site_ruby/1.8/puppet/transaction.rb:250:in > `eval_children_and_apply_resource' > /usr/lib/ruby/site_ruby/1.8/puppet/transaction.rb:207:in > `eval_resource' > /usr/lib/ruby/site_ruby/1.8/puppet/transaction.rb:296:in `evaluate' > /usr/lib/ruby/site_ruby/1.8/puppet/util.rb:418:in `thinmark' > /usr/lib/ruby/1.8/benchmark.rb:293:in `measure' > /usr/lib/ruby/1.8/benchmark.rb:307:in `realtime' > /usr/lib/ruby/site_ruby/1.8/puppet/util.rb:417:in `thinmark' > /usr/lib/ruby/site_ruby/1.8/puppet/transaction.rb:295:in `evaluate' > /usr/lib/ruby/site_ruby/1.8/puppet/transaction.rb:289:in `collect' > /usr/lib/ruby/site_ruby/1.8/puppet/transaction.rb:289:in `evaluate' > /usr/lib/ruby/site_ruby/1.8/puppet/resource/catalog.rb:142:in `apply' > /usr/lib/ruby/site_ruby/1.8/puppet/configurer.rb:169:in `run' > /usr/lib/ruby/site_ruby/1.8/puppet/util.rb:178:in `benchmark' > /usr/lib/ruby/1.8/benchmark.rb:293:in `measure' > /usr/lib/ruby/1.8/benchmark.rb:307:in `realtime' > /usr/lib/ruby/site_ruby/1.8/puppet/util.rb:177:in `benchmark' > /usr/lib/ruby/site_ruby/1.8/puppet/configurer.rb:168:in `run' > /usr/lib/ruby/site_ruby/1.8/puppet/agent.rb:53:in `run' > /usr/lib/ruby/site_ruby/1.8/puppet/agent/locker.rb:21:in `lock' > /usr/lib/ruby/site_ruby/1.8/puppet/agent.rb:53:in `run' > /usr/lib/ruby/1.8/sync.rb:229:in `synchronize' > /usr/lib/ruby/site_ruby/1.8/puppet/agent.rb:53:in `run' > /usr/lib/ruby/site_ruby/1.8/puppet/agent.rb:134:in `with_client' > /usr/lib/ruby/site_ruby/1.8/puppet/agent.rb:51:in `run' > /usr/lib/ruby/site_ruby/1.8/puppet/application/puppetd.rb:103:in > `onetime' > /usr/lib/ruby/site_ruby/1.8/puppet/application.rb:226:in `send' > /usr/lib/ruby/site_ruby/1.8/puppet/application.rb:226:in `run_command' > /usr/lib/ruby/site_ruby/1.8/puppet/application.rb:217:in `run' > /usr/lib/ruby/site_ruby/1.8/puppet/application.rb:306:in > `exit_on_fail' > /usr/lib/ruby/site_ruby/1.8/puppet/application.rb:217:in `run' > /usr/sbin/puppetd:159 > err: Got an uncaught exception of type ArgumentError: Field 'value' is > required > warning: Value of 'preferred_serialization_format' (pson) is invalid > for report, using default (marshal) > notice: Finished catalog run in 3.01 seconds > > Thank you. > -- > Maxim Ianoglo > > On Mar 29, 8:04 pm, Dan Bode wrote: > > On Sun, Mar 28, 2010 at 2:09 AM, .Nox wrote: > > > Hello, > > > > > I wrote a custom type for managing sshd configuration file > > > > > Type: > > > > > > module Puppet > > >newtype(:sshd_param) do > > >@doc = "Manages parameters of sshd" > > > > >ensurable > > > > >newparam(:name) do > > >desc "The name of the parameter." > > >isnamevar > > >end > > > > >newproperty(:target) do > > >desc "Location of sshd configuration file" > > > > >
[Puppet Users] Re: err: Got an uncaught exception of type ArgumentError: Field 'value' is required
Hello,
[r...@vps1 ~]$ puppetd --server test --waitforcert 60 --test --trace
info: Retrieving plugin
warning: newstate() has been deprecrated; use newproperty(value)
info: Caching catalog for vps1.srv171.rackco.com
info: Applying configuration version '1269887449'
notice: //r::ssh/Ssh::Set_value[PermitRootLogin]/
Sshd_param[PermitRootLogin]/ensure: created
/usr/lib/ruby/site_ruby/1.8/puppet/util/fileparsing.rb:95:in `join'
/usr/lib/ruby/site_ruby/1.8/puppet/util/fileparsing.rb:89:in `collect'
/usr/lib/ruby/site_ruby/1.8/puppet/util/fileparsing.rb:89:in `join'
/usr/lib/ruby/site_ruby/1.8/puppet/util/fileparsing.rb:341:in
`to_line'
/usr/lib/ruby/site_ruby/1.8/puppet/util/fileparsing.rb:314:in
`to_file'
/usr/lib/ruby/site_ruby/1.8/puppet/util/fileparsing.rb:314:in
`collect'
/usr/lib/ruby/site_ruby/1.8/puppet/util/fileparsing.rb:314:in
`to_file'
/usr/lib/ruby/site_ruby/1.8/puppet/provider/parsedfile.rb:316:in
`to_file'
/usr/lib/ruby/site_ruby/1.8/puppet/provider/parsedfile.rb:102:in
`flush_target'
/usr/lib/ruby/site_ruby/1.8/puppet/provider/parsedfile.rb:74:in
`flush'
/usr/lib/ruby/site_ruby/1.8/puppet/provider/parsedfile.rb:72:in `each'
/usr/lib/ruby/site_ruby/1.8/puppet/provider/parsedfile.rb:72:in
`flush'
/usr/lib/ruby/site_ruby/1.8/puppet/provider/parsedfile.rb:356:in
`flush'
/usr/lib/ruby/site_ruby/1.8/puppet/type.rb:752:in `flush'
/usr/lib/ruby/site_ruby/1.8/puppet/transaction.rb:94:in `apply'
/usr/lib/ruby/site_ruby/1.8/puppet/transaction.rb:251:in
`eval_children_and_apply_resource'
/usr/lib/ruby/site_ruby/1.8/puppet/util.rb:418:in `thinmark'
/usr/lib/ruby/1.8/benchmark.rb:293:in `measure'
/usr/lib/ruby/1.8/benchmark.rb:307:in `realtime'
/usr/lib/ruby/site_ruby/1.8/puppet/util.rb:417:in `thinmark'
/usr/lib/ruby/site_ruby/1.8/puppet/transaction.rb:250:in
`eval_children_and_apply_resource'
/usr/lib/ruby/site_ruby/1.8/puppet/transaction.rb:207:in
`eval_resource'
/usr/lib/ruby/site_ruby/1.8/puppet/transaction.rb:296:in `evaluate'
/usr/lib/ruby/site_ruby/1.8/puppet/util.rb:418:in `thinmark'
/usr/lib/ruby/1.8/benchmark.rb:293:in `measure'
/usr/lib/ruby/1.8/benchmark.rb:307:in `realtime'
/usr/lib/ruby/site_ruby/1.8/puppet/util.rb:417:in `thinmark'
/usr/lib/ruby/site_ruby/1.8/puppet/transaction.rb:295:in `evaluate'
/usr/lib/ruby/site_ruby/1.8/puppet/transaction.rb:289:in `collect'
/usr/lib/ruby/site_ruby/1.8/puppet/transaction.rb:289:in `evaluate'
/usr/lib/ruby/site_ruby/1.8/puppet/resource/catalog.rb:142:in `apply'
/usr/lib/ruby/site_ruby/1.8/puppet/configurer.rb:169:in `run'
/usr/lib/ruby/site_ruby/1.8/puppet/util.rb:178:in `benchmark'
/usr/lib/ruby/1.8/benchmark.rb:293:in `measure'
/usr/lib/ruby/1.8/benchmark.rb:307:in `realtime'
/usr/lib/ruby/site_ruby/1.8/puppet/util.rb:177:in `benchmark'
/usr/lib/ruby/site_ruby/1.8/puppet/configurer.rb:168:in `run'
/usr/lib/ruby/site_ruby/1.8/puppet/agent.rb:53:in `run'
/usr/lib/ruby/site_ruby/1.8/puppet/agent/locker.rb:21:in `lock'
/usr/lib/ruby/site_ruby/1.8/puppet/agent.rb:53:in `run'
/usr/lib/ruby/1.8/sync.rb:229:in `synchronize'
/usr/lib/ruby/site_ruby/1.8/puppet/agent.rb:53:in `run'
/usr/lib/ruby/site_ruby/1.8/puppet/agent.rb:134:in `with_client'
/usr/lib/ruby/site_ruby/1.8/puppet/agent.rb:51:in `run'
/usr/lib/ruby/site_ruby/1.8/puppet/application/puppetd.rb:103:in
`onetime'
/usr/lib/ruby/site_ruby/1.8/puppet/application.rb:226:in `send'
/usr/lib/ruby/site_ruby/1.8/puppet/application.rb:226:in `run_command'
/usr/lib/ruby/site_ruby/1.8/puppet/application.rb:217:in `run'
/usr/lib/ruby/site_ruby/1.8/puppet/application.rb:306:in
`exit_on_fail'
/usr/lib/ruby/site_ruby/1.8/puppet/application.rb:217:in `run'
/usr/sbin/puppetd:159
err: Got an uncaught exception of type ArgumentError: Field 'value' is
required
warning: Value of 'preferred_serialization_format' (pson) is invalid
for report, using default (marshal)
notice: Finished catalog run in 3.01 seconds
Thank you.
--
Maxim Ianoglo
On Mar 29, 8:04 pm, Dan Bode wrote:
> On Sun, Mar 28, 2010 at 2:09 AM, .Nox wrote:
> > Hello,
>
> > I wrote a custom type for managing sshd configuration file
>
> > Type:
> >
> > module Puppet
> > newtype(:sshd_param) do
> > �...@doc = "Manages parameters of sshd"
>
> > ensurable
>
> > newparam(:name) do
> > desc "The name of the parameter."
> > isnamevar
> > end
>
> > newproperty(:target) do
> > desc "Location of sshd configuration file"
>
> > defaultto {
> > if
> > �...@resource.class.defaultprovider.ancestors.include?
> > Puppet::Provider::ParsedFile
> > �...@resource.class.defaultprovider.default_target
> > else
> > nil
> > end
> > }
> > end
>
> > newparam(:value) do
> > desc "The value to set"
> > end
> > end
> > end
>
> > Provider:
> >
> > require 'p
Re: [Puppet Users] err: Got an uncaught exception of type ArgumentError: Field 'value' is required
On Sun, Mar 28, 2010 at 2:09 AM, .Nox wrote:
> Hello,
>
> I wrote a custom type for managing sshd configuration file
>
> Type:
>
> module Puppet
>newtype(:sshd_param) do
>@doc = "Manages parameters of sshd"
>
>ensurable
>
>newparam(:name) do
>desc "The name of the parameter."
>isnamevar
>end
>
>newproperty(:target) do
>desc "Location of sshd configuration file"
>
>defaultto {
>if
>@resource.class.defaultprovider.ancestors.include?
> Puppet::Provider::ParsedFile
>@resource.class.defaultprovider.default_target
>else
>nil
>end
>}
>end
>
>newparam(:value) do
>desc "The value to set"
>end
>end
> end
>
>
>
> Provider:
>
> require 'puppet/provider/parsedfile'
>
> conf = "/etc/ssh/sshd_config"
>
> Puppet::Type.type(:sshd_param).provide(
>:parsed,
>:parent => Puppet::Provider::ParsedFile,
>:default_target => conf,
>:filetype => :flat
> ) do
>
>confine :exists => conf
>
>text_line :comment,
> :match => /^#/
>text_line :blank,
> :match => /^\s*$/
>record_line :parsed,
>:fields => %w{name value},
>:separator => /\s*\ \s*|#.*|\s*$/,
>:joiner => ' '
> end
>
> Define:
>
> define ssh::set_value($value,
> $target = "/etc/ssh/sshd_config")
> {
>include ssh::server
>
>sshd_param
>{
>$name:
>value => $value,
>target => $target,
>notify => Service[sshd_server],
>require => Package[sshd_package]
>}
> }
>
> Package sshd_package and Service sshd_server are defined in
> ssh::server
>
> In manifest file I have:
> ssh::set_value
> {
> "PermitRootLogin":
> value => "yes",
> target => "/etc/ssh/sshd_config"
> }
>
>
> And at every run I get:
> err: Got an uncaught exception of type ArgumentError: Field 'value' is
> required
>
can you reproduce with with --trace.
> Does anyone know how to fix this issue ?
>
> OS: RHEL 5.4
> PUPPET_VER: 0.25.4
> PUPPET_MASTER_VER: 0.25.4
>
> Thank you.
> --
> Maxim Ianoglo
>
> --
> 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...@googlegroups.com
> .
> For more options, visit this group at
> http://groups.google.com/group/puppet-users?hl=en.
>
>
--
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...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Re: London meetup during Training days
On Mon, Mar 29, 2010 at 9:35 AM, Paul Nasrat wrote: > On 29 March 2010 15:18, scramble wrote: > > The class will end around 5pm on Wednesday, so a meet-up around 6 or > > 6:30 would be great. Open to suggestions from Paul or others... > > Posted in another thread - who from PuppetLabs is over? > > I (dan) am(is), also Scott and Bruce. > Paul > > -- > 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...@googlegroups.com > . > For more options, visit this group at > http://groups.google.com/group/puppet-users?hl=en. > > -- 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...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Re: London meetup during Training days
On 29 March 2010 15:18, scramble wrote: > The class will end around 5pm on Wednesday, so a meet-up around 6 or > 6:30 would be great. Open to suggestions from Paul or others... Posted in another thread - who from PuppetLabs is over? Paul -- 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...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Re: London meetup during Training days
On 29 March 2010 15:18, scramble wrote: > The class will end around 5pm on Wednesday, so a meet-up around 6 or > 6:30 would be great. Open to suggestions from Paul or others... > > I double-booked this with my other half, so if I can make this it will be for a /very/ swift drink. Is anyone around on Thursday evening as well? I imagine some might have travel plans ... J. -- 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...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Excluding a host
Hi Brice,
That is the first thing I tried, but unfortunately that isn't working. I
tried something like this,
node "hst26.domainname inherits commonnode{
*specific to this host*
}
node " /^hst[0-9]+\.domainname/" inherits commonnode{
*everthing else*
}
I was also under the impression that the exclusive node definition takes
precedence over regex matches, but guess I was wrong.
-LOhit
On Mon, Mar 29, 2010 at 7:23 PM, Brice Figureau <
brice-pup...@daysofwonder.com> wrote:
> Hi,
>
> On Mon, 2010-03-29 at 14:05 +0530, LOhit wrote:
> > Hi,
> >
> >
> > Sorry if this question has been answered before (Could not find the
> > answer, Google didn't help either :) ).
> >
> >
> > While specifying hosts I have used a regexp like this.
> > " /^hst[0-9]+.domainname/ " I have about 300+ hosts matching this
> > regexp and is working pretty well, so far. However, I have 2 hosts in
> > this list which have to be excluded. But, I don't know how to do
> > that.
> >
> >
> > Can anyone please provide some pointers/ tips to fix this?
> >
>
> Normal node syntax (ie by hostname/fqdn instead of regex) takes
> precedence over the regex nodes.
>
> Depending on what you mean by excluding (I assumed you meant that those
> host should have their own manifests) you can do:
>
> node "host321.domainname", "host644.domainname" {
> .. specific config
> }
>
> node /^hst[0-9]+.domainname/ {
> ... regular config...
> }
>
> --
> Brice Figureau
> Follow the latest Puppet Community evolutions on www.planetpuppet.org!
>
> --
> 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...@googlegroups.com
> .
> For more options, visit this group at
> http://groups.google.com/group/puppet-users?hl=en.
>
>
--
LOhit
--
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...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] New York Training - April 12-16th
Quick reminder here that Puppet Training is coming to New York April 12-16th. You can register and get more information here: http://reductivelabs.com/training/. Location: Downtown Conference Center 212-618-6997 157 William Street New York, NY 10038 Puppet Master Training: April 12-14 Puppet Developer Curriculum: April 15 & 16 We're about 3/4 full at this point so reserve your spot soon... If you have any questions contact me, Scott Campbell @ 503.805.9065 or sc...@puppetlabs.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-us...@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: London meetup during Training days
The class will end around 5pm on Wednesday, so a meet-up around 6 or 6:30 would be great. Open to suggestions from Paul or others... On Mar 28, 5:11 am, "Al @ Lab42" wrote: > London is calling, wednesday 31 is approaching... where and at what > hour are we going to meet up? > Londoners decide... possibly not too far from County House, Conway > Mews. > Looking forward to live the feeling of a british pub :-) > > On 3 Mar, 21:46, Julian Simpson wrote: > > > The Green Man was our local until I left $DAYJOB last Friday. Should be > > fine on a Wednesday unless we have a huge group. > > > On 3 March 2010 17:21, Paul Nasrat wrote: > > > > On 3 March 2010 17:11, Dan Bode wrote: > > > > > On Wed, Mar 3, 2010 at 2:37 AM, Al @ Lab42 wrote: > > > > >> Hei all, > > > >> In London, UK from March 29 to April 2 there are 2 Puppet training > > > >> classes: > > > >http://reductivelabs.com/training/london-puppet-training/?x_lf_kt=2&_... > > > > >> I'm personally seriously evaluating the possibility to attend the > > > >> developer one, the 1st and 2nd, but in any case considering the active > > > >> Puppet London scene and this specific occasion, it would be nice to > > > >> organize a meetup in those days. > > > >> The idea has been raised on IRC and can be better discussed here... > > > >> Who is interested? > > > > > I'm in. > > > > You're only invited if you come bearing goodies ;) > > > > > Wednesday is good for me. > > > > Fine, Wednesday it is. Guess that's the end of the one course and pre > > > developer course. I'll have to go scouting. ISTR us doing The Green > > > Man, Riding House St which is a Cider pub before. Else can find some > > > decent real ale pubs in the area that have space. > > > > Paul > > > > -- > > > 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...@googlegroups.com > > > . > > > For more options, visit this group at > > >http://groups.google.com/group/puppet-users?hl=en. > > > -- > > Julian Simpson > > Software Build and > > Deploymenthttp://www.build-doctor.comhttp://twitter.com/builddoctor -- 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...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Excluding a host
Hi,
On Mon, 2010-03-29 at 14:05 +0530, LOhit wrote:
> Hi,
>
>
> Sorry if this question has been answered before (Could not find the
> answer, Google didn't help either :) ).
>
>
> While specifying hosts I have used a regexp like this.
> " /^hst[0-9]+.domainname/ " I have about 300+ hosts matching this
> regexp and is working pretty well, so far. However, I have 2 hosts in
> this list which have to be excluded. But, I don't know how to do
> that.
>
>
> Can anyone please provide some pointers/ tips to fix this?
>
Normal node syntax (ie by hostname/fqdn instead of regex) takes
precedence over the regex nodes.
Depending on what you mean by excluding (I assumed you meant that those
host should have their own manifests) you can do:
node "host321.domainname", "host644.domainname" {
.. specific config
}
node /^hst[0-9]+.domainname/ {
... regular config...
}
--
Brice Figureau
Follow the latest Puppet Community evolutions on www.planetpuppet.org!
--
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...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] Re: Excluding a host
Thanks, in fact, I was going to use that if nothing else worked. It would be
nice to have a exclude list though.
Best Regards,
-LOhit
On Mon, Mar 29, 2010 at 5:59 PM, christian wrote:
> If you don't want to edit your regexp, a simple solution could be
> adding something like this to the beginning of your manifests :
>
> if $hostname == "host-that-should-be-excluded" {}
> else { your actual manifest }
>
> At least that worked for me as I just tested it.
>
> christian
>
>
> On 29 Mrz., 10:35, LOhit wrote:
> > Hi,
> >
> > Sorry if this question has been answered before (Could not find the
> answer,
> > Google didn't help either :) ).
> >
> > While specifying hosts I have used a regexp like this. " *
> > /^hst[0-9]+.domainname/* " I have about 300+ hosts matching this regexp
> and
> > is working pretty well, so far. However, I have 2 hosts in this list
> which
> > have to be excluded. But, I don't know how to do that.
> >
> > Can anyone please provide some pointers/ tips to fix this?
> >
> > Thanks in advance.
> >
> > --
> > LOhit
>
> --
> 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...@googlegroups.com
> .
> For more options, visit this group at
> http://groups.google.com/group/puppet-users?hl=en.
>
>
--
LOhit
--
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...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Re: Excluding a host
If you don't want to edit your regexp, a simple solution could be
adding something like this to the beginning of your manifests :
if $hostname == "host-that-should-be-excluded" {}
else { your actual manifest }
At least that worked for me as I just tested it.
christian
On 29 Mrz., 10:35, LOhit wrote:
> Hi,
>
> Sorry if this question has been answered before (Could not find the answer,
> Google didn't help either :) ).
>
> While specifying hosts I have used a regexp like this. " *
> /^hst[0-9]+.domainname/* " I have about 300+ hosts matching this regexp and
> is working pretty well, so far. However, I have 2 hosts in this list which
> have to be excluded. But, I don't know how to do that.
>
> Can anyone please provide some pointers/ tips to fix this?
>
> Thanks in advance.
>
> --
> LOhit
--
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...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
Re: [Puppet Users] London Puppet Meet - Wednesday 31 March
I'll be there from about 7pm I imagine, unless I can get out of work early. On 29 Mar 2010, at 12:33, Paul Nasrat wrote: > Meet up following training, open to all, we'll meet at The Green Man > pub again, I get off about 18h so probably there about 18:30 but feel > free to get there earlier if the class finishes up. > > Green Man > 36 Riding Hood St > London > W1W 7EP > > http://www.thegreenmanw1.co.uk/ > > It's 4 mins by google maps walking: > > http://maps.google.co.uk/maps?f=d&source=s_d&saddr=W1T+6AA&daddr=London+W1W+7EP,+UK&hl=en&geocode=%3BCZjVj3tY2guRFbodEgMdO9_9_yn_wAtAKht2SDHiFtk1jMkS7w&mra=ls&dirflg=w&sll=51.518906,-0.139461&sspn=0.010909,0.027874&g=w1w+7ep&ie=UTF8&z=18 > > http://maps.google.co.uk/maps?f=q&source=s_q&hl=en&geocode=&q=w1w+7ep&sll=53.800651,-4.064941&sspn=21.297675,57.084961&ie=UTF8&hq=&hnear=London+W1W+7EP,+United+Kingdom&z=16 > > I've not booked space but Julian thought it'd be quiet on Weds. I'll > be in my Puppet Camp T-Shirt. > > Paul > > -- > 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...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/puppet-users?hl=en. > -- 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...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] London Puppet Meet - Wednesday 31 March
Meet up following training, open to all, we'll meet at The Green Man pub again, I get off about 18h so probably there about 18:30 but feel free to get there earlier if the class finishes up. Green Man 36 Riding Hood St London W1W 7EP http://www.thegreenmanw1.co.uk/ It's 4 mins by google maps walking: http://maps.google.co.uk/maps?f=d&source=s_d&saddr=W1T+6AA&daddr=London+W1W+7EP,+UK&hl=en&geocode=%3BCZjVj3tY2guRFbodEgMdO9_9_yn_wAtAKht2SDHiFtk1jMkS7w&mra=ls&dirflg=w&sll=51.518906,-0.139461&sspn=0.010909,0.027874&g=w1w+7ep&ie=UTF8&z=18 http://maps.google.co.uk/maps?f=q&source=s_q&hl=en&geocode=&q=w1w+7ep&sll=53.800651,-4.064941&sspn=21.297675,57.084961&ie=UTF8&hq=&hnear=London+W1W+7EP,+United+Kingdom&z=16 I've not booked space but Julian thought it'd be quiet on Weds. I'll be in my Puppet Camp T-Shirt. Paul -- 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...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Excluding a host
Hi, Sorry if this question has been answered before (Could not find the answer, Google didn't help either :) ). While specifying hosts I have used a regexp like this. " * /^hst[0-9]+.domainname/* " I have about 300+ hosts matching this regexp and is working pretty well, so far. However, I have 2 hosts in this list which have to be excluded. But, I don't know how to do that. Can anyone please provide some pointers/ tips to fix this? Thanks in advance. -- LOhit -- 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...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
[Puppet Users] Re: Using ssh::auth for root
Well, thanks for the late answer.
> you shouldn't need to set home again in ::server and ::client, although I
> guess you
> only added those when the first didn't work.
That's right
In the meantime I made a little workaround and edited the following:
define ssh_auth_key_client ($ensure, $filename, $group, $home, $user)
{
File {
owner => $user,
group => $group,
mode=> 600,
require => [ User[$user], File[$home]],
}
Now it looks like this:
define ssh_auth_key_client ($ensure, $filename, $group, $home, $user)
{
File {
owner => $user,
group => $group,
mode=> 600,
require => $user ? {
"root" => [ User[$user], File["$home/.ssh"] ],
default => [ User[$user], File[$home]],
}
}
Together with file {"/root/.ssh"} this works now for me...but I don't
think that's a pretty solution ;)
During the last days I came across another problem. Something like
this doesn't seem to be possible:
ssh::auth::server { "user1":
user=> [ "user1", "user2"],
require => [ File["/home/user1"],
File["/home/user2"] ]
}
Explanation: User1 should be able to ssh as user1 and user2 but arrays
apparently don't work with the "user" parameter. When I run this
manifest puppet gives me always something like this: "directory /home/
user1user2 doesn't exist"
Is there way to realize this? I couldn't figure a way out, as defining
ssh::auth::server {"user1"} twice isn't allowed either.
By the way your documentation looks pretty messed up now after the
wiki change. I already fixed the link form the module overview and
reuploaded the auth.pp file, but I couldn't figure out how to fix the
relative links in the document itself. Although I have to admit that I
didn't really spend that much time on this issue...
christian
On 27 Mrz., 23:43, Andrew Schulman wrote:
> > Hey there,
>
> > I'm playing around with the ssh::auth module and right now I want to
> > create the authorized_keys file for root. But it doesn't seem to work
> > as I always get this error:
>
> > puppetd[2579]: Could not apply complete catalog:
> > Puppet::Util::FileType::FileTypeFlat could not write /home/root/.ssh/
> > authorized_keys: No such file or directory - /home/root/.ssh/
> > authorized_keys
>
> > Obviously puppet tries to write to the wrong directory. For other
> > users who really live in /home/$user the module works.
> > If I create a link /root/.ssh -> /home/root/.ssh puppet creates the
> > authorized_keys file.
>
> > My manifests look like this:
> > #site.pp
> > include ssh::auth
> > ssh::auth::key { "root":
> > ensure => "present",
> > keytype => "dsa",
> > home => "/root",
> > }
>
> > #nodes.pp
> > node sshserver {
> > ssh::auth::server { "root":
> > home => "/root", }
> > ssh::auth::client { "root":
> > home => "/root", }
>
> > }
>
> > As you can see I added always the home-parameter but still puppet
> > tries to write to /home/root.
> > I'm using puppet 0.25.4.
> > So where did I do the mistake?
>
> Christian, I'm sorry for my delayed reply. I've been offline for a while.
>
> Your manifests look right to me. This looks like a bug in ssh::auth. Setting
> ssh::auth::key { root: home => "/root" } should be all you'd have to do; you
> shouldn't need to set home again in ::server and ::client, although I guess
> you
> only added those when the first didn't work.
>
> Let me look into this and I'll see what I can figure out.
> Andrew.
--
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...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
