[Puppet Users] puppet creating AWS EC instances
Hi, I have installed fog 0.7.2 on linux amazon ami. Created ~/.fog file and gave AWS credentials in the file. For verification i used >ruby -rubygems -e 'require "fog"' -e 'puts Fog::Compute.new(:provider => "AWS").servers.length >= 0' This returns true but with the following error. Excon requests with a block are deprecated, pass :response_block instead (/usr/lib/ruby/gems/1.8/gems/fog-0.7.2/lib/fog/core/connection.rb:20:in `request') true When i use puppet node_aws create --image ami-0011e069 --keyname puppet --type m1.large for creating an instance, the instance is created but it gets terminated. I get the following error in the console repeatedly Excon requests with a block are deprecated, pass :response_block instead (/usr/lib/ruby/gems/1.8/gems/fog-0.7.2/lib/fog/core/connection.rb:20:in `request') At end the instance will get created. In the console if i see the instance, the instance is terminated. Can any one say what would be the issue. Waiting for the response Regards Srinivas -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] Problems parsing array to a define in puppet manifest
I have searched wide and far for a solution to this issue, but didn't find
any real solution that I could use.
I am running puppet ver. 3.0.2, and my problem is when I try to parse an
array to a define in a manifest.
My code looks as the following:
$testaccess = hiera('testaccess')
define testdefine () {
notify{"Parsed following to define: ${name} : }
}
which gives the following output:
Parsed following to define: test1test2
It seems that the array is concatenated into one string, instead of parsing
each entry in the array to the define.
Can anyone shed some light into this issue, would be much appreciated :)
/Marc
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] Re: Problems parsing array to a define in puppet manifest
Sorry - forgot to supply the call to the define:
testdefine { "$testaccess": }
Again - any feedback on the usage here would be much appreciated.
/Marc
Den fredag den 1. februar 2013 11.19.51 UTC+1 skrev ma...@ml4.dk:
>
> I have searched wide and far for a solution to this issue, but didn't find
> any real solution that I could use.
>
> I am running puppet ver. 3.0.2, and my problem is when I try to parse an
> array to a define in a manifest.
>
> My code looks as the following:
>
> $testaccess = hiera('testaccess')
>
> define testdefine () {
> notify{"Parsed following to define: ${name} : }
> }
>
> which gives the following output:
> Parsed following to define: test1test2
>
> It seems that the array is concatenated into one string, instead of
> parsing each entry in the array to the define.
>
> Can anyone shed some light into this issue, would be much appreciated :)
>
> /Marc
>
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] Problems parsing array to a define in puppet manifest
- Original Message -
> From: m...@ml4.dk
> To: puppet-users@googlegroups.com
> Sent: Friday, February 1, 2013 11:19:51 AM
> Subject: [Puppet Users] Problems parsing array to a define in puppet manifest
>
> I have searched wide and far for a solution to this issue, but didn't find
> any real solution that I could use.
>
> I am running puppet ver. 3.0.2, and my problem is when I try to parse an
> array to a define in a manifest.
>
> My code looks as the following:
>
> $testaccess = hiera('testaccess')
>
> define testdefine () {
> notify{"Parsed following to define: ${name} : }
> }
>
> which gives the following output:
> Parsed following to define: test1test2
>
> It seems that the array is concatenated into one string, instead of parsing
> each entry in the array to the define.
>
> Can anyone shed some light into this issue, would be much appreciated :)
You're not showing how you pass the array to the define but I would guess
you're doing:
testdefine{"$testaccess": } this turns the array into a string, you probably
should just remove the "s and make it testdefine{$testaccess: }
>
> /Marc
>
> --
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to puppet-users+unsubscr...@googlegroups.com.
> To post to this group, send email to puppet-users@googlegroups.com.
> Visit this group at http://groups.google.com/group/puppet-users?hl=en.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>
>
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] Problems parsing array to a define in puppet manifest
Of course - why did I miss that?
Thanks for the resolution Pienaar, now I can move on with the manifest :)
/Marc
Den fredag den 1. februar 2013 11.28.33 UTC+1 skrev R.I. Pienaar:
>
>
>
> - Original Message -
> > From: ma...@ml4.dk
> > To: puppet...@googlegroups.com
> > Sent: Friday, February 1, 2013 11:19:51 AM
> > Subject: [Puppet Users] Problems parsing array to a define in puppet
> manifest
> >
> > I have searched wide and far for a solution to this issue, but didn't
> find
> > any real solution that I could use.
> >
> > I am running puppet ver. 3.0.2, and my problem is when I try to parse an
> > array to a define in a manifest.
> >
> > My code looks as the following:
> >
> > $testaccess = hiera('testaccess')
> >
> > define testdefine () {
> > notify{"Parsed following to define: ${name} : }
> > }
> >
> > which gives the following output:
> > Parsed following to define: test1test2
> >
> > It seems that the array is concatenated into one string, instead of
> parsing
> > each entry in the array to the define.
> >
> > Can anyone shed some light into this issue, would be much appreciated :)
>
> You're not showing how you pass the array to the define but I would guess
> you're doing:
>
> testdefine{"$testaccess": } this turns the array into a string, you
> probably
> should just remove the "s and make it testdefine{$testaccess: }
> >
> > /Marc
> >
> > --
> > You received this message because you are subscribed to the Google
> Groups
> > "Puppet Users" group.
> > To unsubscribe from this group and stop receiving emails from it, send
> an
> > email to puppet-users...@googlegroups.com .
> > To post to this group, send email to
> > puppet...@googlegroups.com.
>
> > Visit this group at http://groups.google.com/group/puppet-users?hl=en.
> > For more options, visit https://groups.google.com/groups/opt_out.
> >
> >
> >
>
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] Augeas and defvar --> regexp
Hallo,
I have a problem to include augeas...
I will to change a comment to a entry in /etc/default/tmpfs in Debian Wheezy.
The comment is
#RAMTMP=no
I try this on augtool und it is running:
augtool> defvar ramtmpcomment
/files/etc/default/tmpfs/#comment[.=~regexp('RAMTMP=no')]
augtool> ins RAMTMP after $ramtmpcomment
augtool> set /files/etc/default/tmpfs/RAMTMP yes
augtool> rm $ramtmpcomment
After I running this the entry is correct.
But, I try this on puppet:
augeas {"tmpfs":
context => "/files/etc/default/tmpfs",
changes => [
"defvar ramtmpcomment #comment[.=~regexp('RAMTMP=no')]",
"ins RAMTMP after $ramtmpcomment",
"set RAMTMP yes",
"rm $ramtmpcomment",
],
}
Error: /Stage[main]/Debian/Augeas[tmpfs]: Could not evaluate: Error sending
command 'ins' with params ["RAMTMP", "after",
"/files/etc/default/tmpfs/"]/Error sending command 'ins' with params ["RAMTMP",
"after", "/files/etc/default/tmpfs/"]
I believe the variable ramtmpcomment is not set
Puppet version 3.0.2 aureas 0.10.0
Any ideas?
Thx
Karsten
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] Re: mcollective puppetd plugin does not work
Hey i have installed mcollective server cleint and puppet master, agent successfully. I have also installed puppet agent plugin. But when i run mco puppet runonce * [ > ] 2 / 2 Finished processing 2 / 2 hosts in 1093.05 ms This command runs successfully for all nodes. But i want to run puppet agent for only the specified server. For this i m using .. mco puppet runonce --server puppet.example.net I m getting following error ===>> The puppet application failed to run, use -v for full error details: Cannot validate input server: Unknown validator: 'puppet_server_address'. I m unable to find put the issue. Please help me?? -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] Re: mcollective puppetd plugin does not work
I can't check at the moment but shouldn't that be 'mco puppet runonce fqdn= puppet.example.net' ? - Keith On 1 February 2013 11:23, wrote: > Hey i have installed mcollective server cleint and puppet master, agent > successfully. I have also installed puppet agent plugin. But when i run > mco puppet runonce > > * [ > ] 2 / 2 > > Finished processing 2 / 2 hosts in 1093.05 ms > This command runs successfully for all nodes. But i want to run puppet > agent for only the specified server. For this i m using .. > > mco puppet runonce --server puppet.example.net > I m getting following error ===>> > > The puppet application failed to run, use -v for full error details: > Cannot validate input server: Unknown validator: 'puppet_server_address'. > I m unable to find put the issue. Please help me?? > > -- > You received this message because you are subscribed to the Google Groups > "Puppet Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to puppet-users+unsubscr...@googlegroups.com. > To post to this group, send email to puppet-users@googlegroups.com. > Visit this group at http://groups.google.com/group/puppet-users?hl=en. > For more options, visit https://groups.google.com/groups/opt_out. > > > -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] Re: mcollective puppetd plugin does not work
- Original Message - > From: "Keith Burdis" > To: "puppet-users" > Sent: Friday, February 1, 2013 12:40:17 PM > Subject: Re: [Puppet Users] Re: mcollective puppetd plugin does not work > > I can't check at the moment but shouldn't that be 'mco puppet runonce fqdn= > puppet.example.net' ? > > - Keith > > > On 1 February 2013 11:23, wrote: > > > Hey i have installed mcollective server cleint and puppet master, agent > > successfully. I have also installed puppet agent plugin. But when i run > > mco puppet runonce > > > > * [ > ] 2 / 2 > > > > Finished processing 2 / 2 hosts in 1093.05 ms > > This command runs successfully for all nodes. But i want to run puppet > > agent for only the specified server. For this i m using .. > > > > mco puppet runonce --server puppet.example.net > > I m getting following error ===>> > > > > The puppet application failed to run, use -v for full error details: > > Cannot validate input server: Unknown validator: 'puppet_server_address'. > > I m unable to find put the issue. Please help me?? --server chooses a specific puppet master to run against, the error suggests you didnt install the plugin properly though The filtering and limiting of which nodes you run against is standard across all mcollective commands, plenty of examples over @ http://docs.puppetlabs.com/mcollective/reference/basic/basic_cli_usage.html -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] creating file locations from hiera
On Jan 25, 2013, at 9:25 AM, Peter De Cleyn wrote: > I ran again against a long standing bug / feature request but from a new > angle: creating directories with parents > (http://projects.puppetlabs.com/issues/86). I was blown away when I saw that issue. It's been open for 7 years and nobody can figure out how to create a directory tree? It's kinda mind-boggling. > I wanted to create a module, where a path could be supplied with a class > parameter. The path would be used in a rsync configuration, so I would like > to be sure the path exists. As I want the module to be general and completely > separate code and data, I didn't want to configure a "base path" in which all > rsync modules would need to live. But there is AFAIK no "mkdir -p" > alternative in puppet, unless I'd go with an ugly exec. > > Any ideas houw to realise this? I probably could define my path in hiera as > an hash and as such define all parent folders, but this is not that elegant. Short of writing a plugin, I do think the exec is your best bet. It's ugly but effective. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] Re: directory mode
On Thu, Jan 31, 2013 at 05:58:55AM -0800, jcbollinger wrote:
>
>
> On Thursday, January 31, 2013 1:11:25 AM UTC-6, Kubes wrote:
> >
> > Hello,
> >
> > I am trying to set all the directroes in the tree to 775 and files to 664
> > with Puppets fie resource.
> >
> > This woks fine with native chmod: # chmod -R a=r,ug+Xw,o+X
> >
> > But if I us this in puppet all is set to 775
> >
> > file { "/etc/puppet":
> > ensure => directory,
> > recurse => true,
> > ignore => ".git",
> > owner => $puppet::params::puppet_user,
> > group => $puppet::params::puppet_group,
> > mode => 'a=r,ug+Xw,o+X',
> > }
> > I have also tried mode => 'a=r,ug+X,ug+w,o+X', no luck either, same
> > result 775.
> >
> >
>
> Just use "mode=> '644'". Puppet will turn on the execute bits on the
> directories automatically.
>
>
> John
>
mode => '0644'
^
it is a good idea also write the 0 there just to make it clearer
--
Best, Nikola
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] Debugging a facter problem
Hello,
for the last couple of hours I've been trying to wrap my head around a
problem writing a custom facter plugin and I'm not getting it.
I'm trying to export LLDP neighbors as facter variables. I've already
found https://gist.github.com/1424959 and I'm quite happy with it, so
the issue is not pressing. But I'd like to understand it.
If the neighbor provides an ifAlias (like Cisco) I want to use this,
but if it doesn't I want to use description.
Sidenote: This is my first time with Ruby and it looks quite ugly
First try:
---
require 'facter/util/ip'
Facter::Util::IP.get_interfaces.each do |interface|
# Make a fact for each detail of each interface. Yay.
Facter.add("lldp_neighbor_" + Facter::Util::IP.alphafy(interface)) do
setcode do
device = Facter::Util::Resolution.exec("/usr/sbin/lldpctl -f keyvalue " +
interface + " | grep chassis.name | cut -d '=' -f 2")
ifdescr = Facter::Util::Resolution.exec("/usr/sbin/lldpctl -f keyvalue "
+ interface + " | grep port.descr | cut -d '=' -f 2")
ifalias = Facter::Util::Resolution.exec("/usr/sbin/lldpctl -f keyvalue "
+ interface + " | grep port.ifalias | cut -d '=' -f 2")
if device
if ifalias
device + " " + ifalias
else
device + " " + ifdescr
end
end
end
end
end
---
This is highly inefficient, but works
lldp_neighbor_eth0 => swg1-kic B23
lldp_neighbor_eth4 => csr1-kic Gi4/3
Next I wanted to try to parse the whole output to get rid of all the
spawning
---
require 'facter'
require 'facter/util/ip'
if not FileTest.exists?("/usr/sbin/lldpctl")
nil
end
config = Hash[]
output = Facter::Util::Resolution.exec("/usr/sbin/lldpctl -f keyvalue")
if output == ""
nil
end
for line in output.split("\n") do
# Drop Multiline
if line =~ /^lldp/
key, value = line.split('=')
prefix, int, key2 = key.split('.', 3)
if not config.has_key?(int)
config[int] = Hash[]
end
config[int][key2] = value
end
end
for interface in config.keys do
Facter.add("lldp_neighbor_" + Facter::Util::IP.alphafy(interface)) do
setcode do
device = config[interface].fetch('chassis.name', "")
ifdescr = config[interface].fetch('port.descr', "")
ifalias = config[interface].fetch('port.ifalias', "")
if device != ""
if ifalias != ""
device + " " + ifalias
else
device + " " + ifdescr
end
end
end
end
end
---
This errorneously reports the same neighbor for both interfaces
lldp_neighbor_eth0 => csr1-kic Gi4/3
lldp_neighbor_eth4 => csr1-kic Gi4/3
I somehow cannot execute the whole facter plugin using irb, but when I
replace the second part of the script with
---
for interface in config.keys do
device = config[interface].fetch('chassis.name', "")
ifdescr = config[interface].fetch('port.descr', "")
ifalias = config[interface].fetch('port.ifalias', "")
if device != ""
if ifalias != ""
puts interface + " " + device + " " + ifalias
else
puts interface + " " + device + " " + ifdescr
end
end
end
---
it does display the right information
eth0 swg1-kic B23
eth4 csr1-kic Gi4/3
Also, if I just open irb and run the first part of the script (the data
collection) the resulting hash looks fine
irb(main):030:0> pp config
{"eth0"=>
{"via"=>"LLDP",
"rid"=>"1",
"age"=>"0 day, 00:51:37",
"chassis.mac"=>"00:01:e7:df:df:00",
"chassis.name"=>"swg1-kic",
"chassis.descr"=>
"HP J4865A ProCurve Switch 4108GL, revision G.07.109, ROM G.05.02
(/sw/code/build/gamo(m03))",
"chassis.mgmt-ip"=>"",
"chassis.Bridge.enabled"=>"on",
"chassis.Router.enabled"=>"off",
"port.local"=>"47",
"port.descr"=>"B23"},
"eth4"=>
{"via"=>"LLDP",
"rid"=>"2",
"age"=>"0 day, 00:47:03",
"chassis.mac"=>"68:ef:bd:7e:ee:86",
"chassis.name"=>"csr1-kic",
"chassis.descr"=>
"Cisco IOS Software, s72033_rp Software (s72033_rp-ADVIPSERVICESK9_WAN-M),
Version 12.2(33)SXI2a, RELEASE SOFTWARE (fc2)",
"chassis.mgmt-ip"=>"xxx.xxx.xxx.xxx",
"chassis.Bridge.enabled"=>"off",
"chassis.Router.enabled"=>"on",
"port.ifalias"=>"Gi4/3",
"port.descr"=>"Mirror-Port, moni-kic",
"port.auto-negotiation.supported"=>"no",
"port.auto-negotiation.enabled"=>"yes",
"port.auto-negotiation.1000Base-T.hd"=>"no",
"port.auto-negotiation.1000Base-T.fd"=>"yes",
"port.auto-negotiation.current"=>"unknown"}}
So something is obviously wrong in my facter part, but I cannot find it.
I've tried several attempts (like explicitly resetting the variables
in the setcode block), but ...
Help! :-)
Bernhard
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
F
[Puppet Users] Re: Hyperic monitoring of Puppet master and nodes?
I don't see any thing relating to Hyperic in the Puppet Forge. I will need a Puppet module at some point to mange Hyperic but not sure what time frame I'll be working that yet. My main concern now is to determine how to properly have Hyperic monitor the health of the puppet master and agents. I'll look into Foreman and tagmail as you suggested. Thanks! Thomas On Wednesday, January 30, 2013 9:12:06 AM UTC-5, llowder wrote: > > > > On Wednesday, January 30, 2013 7:46:53 AM UTC-6, Thomas wrote: >> >> I'll be looking at having Hyperic monitor our Puppet master and nodes. >> >> Maybe I'm lucky but I've never found any thing errors in the puppet logs >> to indicate any problems. Are there any messages I should look for? Is >> there any information documented on best practices for assuring Puppet is >> running properly? >> >> So far I'm planning to have Hyperic monitor that the required services >> are running on all agents and the master. Is there any thing else I should >> consider having Hyperic monitor to assure my Puppet infrastructure is >> running properly? >> >> > You can have Hyperic monitor logs, but doing so tends to be very resource > intensive, and you can get the same results using The Foreman or tagmail. > > I use hyperic as well, and have been looking at a way to setup hyperic > monitoring on my nodes automatically via puppet. > > If this is something you would find useful, or would be interested in > working on with me, please let me know. > > >> Thanks! Thomas >> >> -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] All nodes are showing unresponsive
Hi Mamta, Are you using the learning puppet VM (I assume so because of the domain name)? That comes with Puppet Enterprise installed, which uses different paths and service names. In PE, the master and console run under the pe-httpd service, and the agent runs under pe-puppet. Are you able to run the following commands? If not, please copy/paste the error text. /sbin/service pe-httpd start /sbin/service pe-puppet start If you are not using the learning puppet VM, and are not using Puppet Enterprise, the above instructions will not apply, and we will need more information about how you installed dashboard to troubleshoot further. Thanks, - James On Thu, Jan 31, 2013 at 5:03 AM, Mamta Garg wrote: > Can anyone please help! > > > On Wed, Jan 30, 2013 at 6:58 AM, Mamta Garg wrote: > >> Hi , >> >> I have set the correct time on master and agent.But Not able to lauch >> puppet dashboard. >> Please guide? >> >> find attched screenshot. >> >> I thiugh because of servuce iam getting error ,I have tried to run below >> command ,getting error. >> >> puppet resource service puppet ensure=running enable=true >> >> Thanks, >> Mamta >> >> On Tue, Jan 29, 2013 at 11:38 PM, RAVI TEJ wrote: >> >>> Hi mamta, >>> >>> Could you please check the time on the server(which is hosting >>> puppet-dashboard) ?? Make sure it is sync with the puppet master. >>> >>> >>> -- >>> You received this message because you are subscribed to the Google >>> Groups "Puppet Users" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to puppet-users+unsubscr...@googlegroups.com. >>> >>> To post to this group, send email to puppet-users@googlegroups.com. >>> Visit this group at http://groups.google.com/group/puppet-users?hl=en. >>> For more options, visit https://groups.google.com/groups/opt_out. >>> >>> >>> >> >> >> >> -- >> Thanks and Regards, >> Mamta Garg >> > > > > -- > Thanks and Regards, > Mamta Garg > > -- > You received this message because you are subscribed to the Google Groups > "Puppet Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to puppet-users+unsubscr...@googlegroups.com. > To post to this group, send email to puppet-users@googlegroups.com. > Visit this group at http://groups.google.com/group/puppet-users?hl=en. > For more options, visit https://groups.google.com/groups/opt_out. > > > -- James Sweeny Professional Services http://puppetlabs.com/ -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] Change the location of puppet.conf
Hey Ramin,
Thanks for all of your help! I've tried that and it didn't work either. I'm
suspecting it might not be related to the syntax of my config.ru file
whatsoever. I'm going to do some digging elsewhere to see if I can track it
down
Jason
On Thursday, January 31, 2013 8:44:50 PM UTC-8, Ramin K wrote:
>
> I'm not sure your syntax is valid with that double <<. Try
>
> $0 = "master"
> ARGV << "--debug"
> ARGV << "--rack"
> ARGV << "--confdir=/opt/puppet"
> ARGV << "--vardir=/opt/puppet/var"
> ARGV << "--config=/opt/puppet/puppet.conf"
>
> require 'puppet/util/command_line'
> run Puppet::Util::CommandLine.new.execute
>
> Ramin
>
> On 1/31/2013 6:55 PM, Jason Knudsen wrote:
> > Just in case I'm missing something obvious, here's my entire config.rufile:
> >
> > # a config.ru, for use with every rack-compatible webserver.
> > # SSL needs to be handled outside this, though.
> > # if puppet is not in your RUBYLIB:
> > # $LOAD_PATH.unshift('/opt/puppet/lib')
> > $0 = "master"
> > # if you want debugging:
> > # ARGV << "--debug"
> > ARGV << "--rack"
> > # Rack applications typically don't start as root. Set --confdir
> > and --vardir
> > # to prevent reading configuration from ~puppet/.puppet/puppet.conf
> > and writing
> > # to ~puppet/.puppet
> > ARGV << "--confdir" << "/opt/puppet"
> > ARGV << "--vardir" << "/opt/puppet/var"
> > ARGV << "--config=/opt/puppet/puppet.conf"
> > # NOTE: it's unfortunate that we have to use the "CommandLine" class
> > # here to launch the app, but it contains some initialization logic
> > # (such as triggering the parsing of the config file) that is very
> > # important. We should do something less nasty here when we've
> > # gotten our API and settings initialization logic cleaned up.
> > #
> > # Also note that the "$0 = master" line up near the top here is
> > # the magic that allows the CommandLine class to know that it's
> > # supposed to be running master.
> > #
> > # --cprice 2012-05-22
> > require 'puppet/util/command_line'
> > # we're usually running inside a Rack::Builder.new {} block,
> > # therefore we need to call run *here*.
> > run Puppet::Util::CommandLine.new.execute
> >
> >
> >
> >
> > On Thursday, January 31, 2013 6:50:22 PM UTC-8, Jason Knudsen wrote:
> >
> > Yup, definitely apache:
> >
> > netstat:
> > tcp0 0 :::8140 :::*
> > LISTEN 21710/httpd
> >
> > rack is spawned:
> >
> > ps:
> > user 21877 1 0 18:26 ?00:00:00 Rack: /opt/puppet/rack
> >
> > I get nothing in my httpd log files.. error or access.log (this
> > feels weird..)
> >
> > Oh yeah and this is Puppet 3.0.2
> >
> > Jason
> >
> >
> > On Thursday, January 31, 2013 6:43:49 PM UTC-8, Ramin K wrote:
> >
> > Very strange, I've used the --config with the custom
> > conf file for
> > years though I'm still on 2.7.
> >
> > Are you sure you're running your Puppet master through
> > Apache/Passenger
> > and not running the puppetmaster script? For the hell of it
> > check to
> > make sure Apache has the port and that Rack processes have
> > spawned. Also
> > look at the logs to see if Passenger is kicking out errors.
> >
> > Ramin
> >
> > On 1/31/2013 6:28 PM, Jason Knudsen wrote:
> > > Hey Ramin,
> > >
> > > That sounded like an awesome idea! So I tried it out, updated
> > config.ru
> > > and bounced httpd
> > >
> > > ARGV << "--confdir" << "/opt/puppet/"
> > > ARGV << "--vardir" << "/opt/puppet/var"
> > > ARGV << "--config" << "/opt/puppet/puppet.conf"
> > >
> > > Doesn't fly.. it stil creates the .puppet directory and
> fails.
> > >
> > > I also tried with:
> > >
> > > ARGV << "--config=/opt/puppet/puppetmaster.conf"
> > >
> > > And that didn't work.
> > >
> > > Both syntaxes work from the shell tho. Just not through httpd
> > for some
> > > odd reason. I'll keep tinkering tho
> > >
> > > Thanks,
> > >
> > > Jason
> > >
> > > On Thursday, January 31, 2013 6:03:31 PM UTC-8, Ramin K
> wrote:
> > >
> > > On 1/31/2013 5:46 PM, Jason Knudsen wrote:
> > > > Yo,
> > > >
> > > > Thanks for the suggestion Chad. So actually a little
> > bit more
> > > background
> > > > from me would be useful:
> > > >
> > > > I'm running this in use
Re: [Puppet Users] All nodes are showing unresponsive
Mamta, I am no expert, but I think you need to acquaint yourself with the logfiles for the different elements of the system .. that way, when something is not working you can get a helpful feedback from the logs. I struggled for a while with puppet, until I learnt where all the logs would go for various things .. Perhaps, James can point you to the logfiles locations for puppet enterprise .. so, you can use them effectively in your learning .. On Friday, 1 February 2013 15:14:19 UTC, James Sweeny wrote: > > Hi Mamta, > > Are you using the learning puppet VM (I assume so because of the domain > name)? That comes with Puppet Enterprise installed, which uses different > paths and service names. > > In PE, the master and console run under the pe-httpd service, and the > agent runs under pe-puppet. Are you able to run the following commands? If > not, please copy/paste the error text. > > /sbin/service pe-httpd start > /sbin/service pe-puppet start > > If you are not using the learning puppet VM, and are not using Puppet > Enterprise, the above instructions will not apply, and we will need more > information about how you installed dashboard to troubleshoot further. > > Thanks, > > - James > > On Thu, Jan 31, 2013 at 5:03 AM, Mamta Garg > > wrote: > >> Can anyone please help! >> >> >> On Wed, Jan 30, 2013 at 6:58 AM, Mamta Garg >> > wrote: >> >>> Hi , >>> >>> I have set the correct time on master and agent.But Not able to lauch >>> puppet dashboard. >>> Please guide? >>> >>> find attched screenshot. >>> >>> I thiugh because of servuce iam getting error ,I have tried to run below >>> command ,getting error. >>> >>> puppet resource service puppet ensure=running enable=true >>> >>> Thanks, >>> Mamta >>> >>> On Tue, Jan 29, 2013 at 11:38 PM, RAVI TEJ >>> > wrote: >>> Hi mamta, Could you please check the time on the server(which is hosting puppet-dashboard) ?? Make sure it is sync with the puppet master. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users...@googlegroups.com . To post to this group, send email to puppet...@googlegroups.com . Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out. >>> >>> >>> >>> -- >>> Thanks and Regards, >>> Mamta Garg >>> >> >> >> >> -- >> Thanks and Regards, >> Mamta Garg >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Puppet Users" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to puppet-users...@googlegroups.com . >> To post to this group, send email to puppet...@googlegroups.com >> . >> Visit this group at http://groups.google.com/group/puppet-users?hl=en. >> For more options, visit https://groups.google.com/groups/opt_out. >> >> >> > > > > -- > > James Sweeny > Professional Services > http://puppetlabs.com/ > > -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] puppet client 0.22.1-1 unable to communicate with master on 3.0.2-1
Hi, I have a client that I cannot upgrade from ubuntu 6.06 (due to application dependency issues) ... I have been able to get puppet/facter installed on it, but it seems unable to make certificate requests .. #/usr/sbin/puppetd -d -t -v err: No certificate; running with reduced functionality. info: Creating a new certificate request for cofkedit.bodleian.ox.ac.uk info: Requesting certificate warning: peer certificate won't be verified in this SSL session err: Could not call puppetca.getcert: # err: Could not request certificate: Certificate retrieval failed: HTTP-Error: 400 Bad Request == I have seem a few admonitions against using clients that are old, but I have no choice in this one if I hope to deploy puppet on it .. or are there work arounds I can attempt ? -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] Re: puppet creating AWS EC instances
Upgrade to latest fog and the errors are gone. On Friday, February 1, 2013 1:34:50 AM UTC-8, PuppetUser wrote: > > Hi, > > I have installed fog 0.7.2 on linux amazon ami. Created ~/.fog file and > gave AWS credentials in the file. > For verification i used > > >ruby -rubygems -e 'require "fog"' -e 'puts Fog::Compute.new(:provider => > "AWS").servers.length >= 0' > This returns true but with the following error. > > Excon requests with a block are deprecated, pass :response_block instead > (/usr/lib/ruby/gems/1.8/gems/fog-0.7.2/lib/fog/core/connection.rb:20:in > `request') > true > When i use > puppet node_aws create --image ami-0011e069 --keyname puppet --type > m1.large for creating an instance, the instance is created but it gets > terminated. > > I get the following error in the console repeatedly > > Excon requests with a block are deprecated, pass :response_block instead > (/usr/lib/ruby/gems/1.8/gems/fog-0.7.2/lib/fog/core/connection.rb:20:in > `request') > > At end the instance will get created. > In the console if i see the instance, the instance is terminated. > > Can any one say what would be the issue. Waiting for the response > > Regards > > Srinivas > > -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] Cannot get puppetlabs-haproxy to do what I want
I've been having a mess of a time using this module, which stinks because
its behavior is EXACTLY what I am looking for... whenever I bootstrap new
rabbitMQ nodes I want to add them to our HAProxy instance.
Here's my relevant site.pp entries:
node /^rabbit.*/ inherits basenode {
@@haproxy::balancermember { $fqdn:
listening_service => 'messaging00',
server_names => $::hostname,
ipaddresses => $::ipaddress,
ports => ['55672', '5672'],
options => 'check'
}
include roles::rabbitmq::worker_broker
}
node thelonius inherits basenode {
Haproxy::Balancermember <<| listening_service == 'messaging00' |>>
class { 'haproxy': }
haproxy::listen { 'messaging00':
options => {
'mode' => 'tcp',
'balance' => 'roundrobin',
'option' => [
'tcplog',
'tcpka'
]
},
ipaddress => $::ipaddress,
ports => ['55672','5672'],
}
haproxy::listen { 'private_monitoring01':
options => {
'mode' => 'http',
'stats' => [
'enable',
'uri /',
'refresh 5s'
],
'option' => [
'httplog',
]
},
ipaddress => "",
ports => [80],
}
}
When these run, haproxy goes down because it puts the server entry under
defaults instead of messaging00:
defaults
log global
maxconn 8000
option redispatch
retries 3
stats enable
timeout http-request 10s
timeout queue 1m
timeout connect 10s
timeout client 1m
timeout server 1m
timeout check 10s
server rabbit01 10.0.2.15:55672,10.0.2.15:5672 check
listen messaging00 10.0.2.15:55672,10.0.2.15:5672
balance roundrobin
mode tcp
option tcplog
option tcpka
Any help would be GREATLY appreciated ... I've done much yak shaving to get
this far and this is the last piece to give me the sweet setup I am looking
for. :)
Thanks,
James
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] Mcollective
Hi Everyone; I am just starting with MCollective and I am struggling to find information about how to properly configure it. I have it installed but, I cannot seem to get mco facts working.. mco facts does not return the request information. Any help would be greatly appreciated! [root@mydev5 ~]# mco facts hostname mydev5 Report for fact: hostname Finished processing 1 / 1 hosts in 54.62 ms Thanks! Bee -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] Re: Cannot get puppetlabs-haproxy to do what I want
I don't get it... really I DON'T! :)
For reasons that makes absolutely no sense to me whatsoever, the following
works... if anyone could shed some light on why in the world this would
work I would love to hear it... I don't feel safe going forward with it
because it feels like it is working by coincidence and could simply break
at any time.
node /^rabbit.*/ inherits basenode {
@@haproxy::balancermember { $fqdn:
listening_service => 'puppet00',
server_names => $::hostname,
ipaddresses => $::ipaddress,
ports => ['55672', '5672'],
options => 'check'
}
include roles::rabbitmq::worker_broker
}
node thelonius inherits basenode {
Haproxy::Balancermember <<| listening_service == 'puppet00' |>>
class { 'haproxy': }
haproxy::listen { 'puppet55':
options => {
'mode' => 'tcp',
'balance' => 'roundrobin',
'option' => [
'tcplog',
'tcpka'
]
},
ipaddress => $::ipaddress,
ports => ['55672','5672'],
}
}
On Friday, February 1, 2013 2:32:43 PM UTC-6, James Carr wrote:
>
> I've been having a mess of a time using this module, which stinks because
> its behavior is EXACTLY what I am looking for... whenever I bootstrap new
> rabbitMQ nodes I want to add them to our HAProxy instance.
>
> Here's my relevant site.pp entries:
>
> node /^rabbit.*/ inherits basenode {
> @@haproxy::balancermember { $fqdn:
> listening_service => 'messaging00',
> server_names => $::hostname,
> ipaddresses => $::ipaddress,
> ports => ['55672', '5672'],
> options => 'check'
> }
>
> include roles::rabbitmq::worker_broker
> }
>
> node thelonius inherits basenode {
> Haproxy::Balancermember <<| listening_service == 'messaging00' |>>
> class { 'haproxy': }
> haproxy::listen { 'messaging00':
> options => {
> 'mode' => 'tcp',
> 'balance' => 'roundrobin',
> 'option' => [
> 'tcplog',
> 'tcpka'
> ]
> },
> ipaddress => $::ipaddress,
> ports => ['55672','5672'],
> }
>
> haproxy::listen { 'private_monitoring01':
> options => {
> 'mode' => 'http',
> 'stats' => [
> 'enable',
> 'uri /',
> 'refresh 5s'
> ],
> 'option' => [
> 'httplog',
> ]
> },
> ipaddress => "",
> ports => [80],
> }
> }
>
> When these run, haproxy goes down because it puts the server entry under
> defaults instead of messaging00:
>
> defaults
> log global
> maxconn 8000
> option redispatch
> retries 3
> stats enable
> timeout http-request 10s
> timeout queue 1m
> timeout connect 10s
> timeout client 1m
> timeout server 1m
> timeout check 10s
>
> server rabbit01 10.0.2.15:55672,10.0.2.15:5672 check
>
>
> listen messaging00 10.0.2.15:55672,10.0.2.15:5672
> balance roundrobin
> mode tcp
> option tcplog
> option tcpka
>
> Any help would be GREATLY appreciated ... I've done much yak shaving to
> get this far and this is the last piece to give me the sweet setup I am
> looking for. :)
>
>
> Thanks,
> James
>
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] Re: Mcollective
You've gotta: - Set a fact source - Configure that fact source - Make sure that fact source has access to good data By default, mcollective is using the 'yaml' fact source, which is looking for a file that may not exist and which may not have good data in it. Check the instructions here, they cover how to get that set up (assuming you're using Puppet): http://projects.puppetlabs.com/projects/mcollective-plugins/wiki/FactsFacterYAML On Friday, February 1, 2013 12:44:49 PM UTC-8, Worker Bee wrote: > > Hi Everyone; > > I am just starting with MCollective and I am struggling to find > information about how to properly configure it. > > I have it installed but, I cannot seem to get mco facts working.. mco > facts does not return the request information. > > Any help would be greatly appreciated! > > > > [root@mydev5 ~]# mco facts hostname mydev5 > Report for fact: hostname > > > Finished processing 1 / 1 hosts in 54.62 ms > > > Thanks! > Bee > -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] Re: Mcollective
Thanks, Nick! Worked perfectly! On Fri, Feb 1, 2013 at 4:32 PM, Nick Fagerlund < nick.fagerl...@puppetlabs.com> wrote: > You've gotta: > >- Set a fact source >- Configure that fact source >- Make sure that fact source has access to good data > > By default, mcollective is using the 'yaml' fact source, which is looking > for a file that may not exist and which may not have good data in it. > > Check the instructions here, they cover how to get that set up (assuming > you're using Puppet): > http://projects.puppetlabs.com/projects/mcollective-plugins/wiki/FactsFacterYAML > > > On Friday, February 1, 2013 12:44:49 PM UTC-8, Worker Bee wrote: >> >> Hi Everyone; >> >> I am just starting with MCollective and I am struggling to find >> information about how to properly configure it. >> >> I have it installed but, I cannot seem to get mco facts working.. mco >> facts does not return the request information. >> >> Any help would be greatly appreciated! >> >> >> >> [root@mydev5 ~]# mco facts hostname mydev5 >> Report for fact: hostname >> >> >> Finished processing 1 / 1 hosts in 54.62 ms >> >> >> Thanks! >> Bee >> > -- > You received this message because you are subscribed to the Google Groups > "Puppet Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to puppet-users+unsubscr...@googlegroups.com. > To post to this group, send email to puppet-users@googlegroups.com. > Visit this group at http://groups.google.com/group/puppet-users?hl=en. > For more options, visit https://groups.google.com/groups/opt_out. > > > -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] storeconfigs and exported resources?
On 01/19/2013 05:44 AM, Jakov Sosic wrote: > On 01/19/2013 05:35 AM, Jakov Sosic wrote: >> On 01/19/2013 04:26 AM, Ken Barber wrote: >> >>> Yes, if you want to use exported resource this is the current endorsed >>> path. >> >> Thank you for your answer. >> >> I did set up puppetdb as described in official documentation, and my >> puppet.conf now looks like: >> >> [puppetmasterd] >> storeconfigs = true >> thin_storeconfigs = false >> storeconfigs_backend = puppetdb >> ssl_client_header = SSL_CLIENT_S_DN >> ssl_client_verify_header = SSL_CLIENT_VERIFY >> >> But, I'm still getting one big zero from exported resources :( >> >> Looking at puppetdb.log, I see only "replacing facts" but never >> "replacing catalog"... So back to square one :-/ > > I've found this one googling around: > > http://www.mentby.com/Group/puppet-users/puppetdb-indicated-only-facts-were-replaced-no-sign-of-catalog.html > > > > But I don't see the solution... :) Still no help? :-/ Any idea how should I approach to debugging this ? -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] storeconfigs and exported resources?
On 02/01/2013 11:45 PM, Jakov Sosic wrote: >> But I don't see the solution... :) > > Still no help? :-/ Any idea how should I approach to debugging this ? OK, after i put this into my routes.yaml: catalog: cache: puppetdb lines in the puppetdb.log with "[replace catalog]" finally started to appear. But, still nothing with exported resources... they just don't get collected... -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] help with define
I would like some help trying to accomplish something. I have a user
define as shown in the first example. Each user with an SSH key needs 2 of
them though, one as a normal login key, and the other is the same key but
is for the "git" user (all ssh git access done via this "git" user). Is
there a way to do this in the same define? I'm thinking something along
the lines of example 2, but the concatenation doesn't seem to work.
Example 1
class user::shell_acct {
define acct
($name,$uid,$password='!!',$groups='',$shell='/bin/bash',$sshkey='',$keytype='dsa')
{
user { $title:
comment=> $name,
ensure => 'present',
uid=> $uid,
gid=> $uid,
managehome => 'true',
home => "/home/$title",
shell => $shell,
membership => 'inclusive',
groups => $groups,
password => $password,
}
group { $title:
ensure => 'present',
gid=> $uid,
}
if ( $sshkey != "" ) {
# login key
ssh_authorized_key { $title:
ensure => 'present',
user=> $title,
type=> $keytype,
key => $sshkey,
}
}
}
}
*Example 2*
if ( $sshkey != "" ) {
# login key
ssh_authorized_key { $title:
ensure => 'present',
user=> $title,
type=> $keytype,
key => $sshkey,
}
# git key
ssh_authorized_key { $title-git:
ensure => 'present',
user=> git,
type=> $keytype,
key => $sshkey,
}
}
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] Re: puppet client 0.22.1-1 unable to communicate with master on 3.0.2-1
You're in a gnarly situation. DistroWatch is telling me that you're probably running Ruby 1.8.4, which, damn. I think your best bet is: * Find or build a newer Ruby, preferably 1.8.7. * Either install Puppet from source (http://docs.puppetlabs.com/guides/from_source.html) or force apt to install a Puppet package meant for a newer distro. I... THINK the packages from the Puppet Labs repo ought to limp along just fine if the Ruby is new enough, but I've never heard of it being tried with Dapper. Good luck with that. On Friday, February 1, 2013 10:18:49 AM UTC-8, Chux wrote: > > Hi, > > I have a client that I cannot upgrade from ubuntu 6.06 (due to application > dependency issues) ... I have been able to get puppet/facter installed on > it, but it seems unable to make certificate requests .. > > > #/usr/sbin/puppetd -d -t -v > err: No certificate; running with reduced functionality. > info: Creating a new certificate request for cofkedit.bodleian.ox.ac.uk > info: Requesting certificate > warning: peer certificate won't be verified in this SSL session > err: Could not call puppetca.getcert: # Request> > err: Could not request certificate: Certificate retrieval failed: > HTTP-Error: 400 Bad Request > == > > I have seem a few admonitions against using clients that are old, but I > have no choice in this one if I hope to deploy puppet on it .. or are there > work arounds I can attempt ? > > > -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Re: [Puppet Users] Any way to "force" set the type provider? Problem with firewall module and iptables
Thank you! My vagrant box have 2.7.6 installed. Got to test with newer version. Chad: yes I know, but I hope that I don't need any pre-install step when I use Vagrant. Its easier if there is no multiple steps to get environment up and running. Thanks for help anyway! -Erno perjantai, 1. helmikuuta 2013 3.38.15 UTC+2 Nan Liu kirjoitti: > > On Wed, Jan 30, 2013 at 10:50 PM, Erno Aapa > > wrote: > >> Hi, >> I have tricky problem and I hope that someone could help me. >> I'm using puppetlabs-firewall module. My box doesn't have iptables >> pre-installed. And because there is no /sbin/iptables puppet don't find >> provider for firewall -type. I get error that no provider for firewall >> found. >> >> Does anyone have idea how to get around this? Even if I create stage >> which is before "main"-stage and install the iptables there I get errors. >> > > The issue should be fixed somewhere in 2.7.x where you can install > packages and have it satisfy provider requirements in a single puppet run. > See: http://projects.puppetlabs.com/issues/6907. > > Nan > -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
