I''m testing puppet 2.6.2 (debian) in ec2. I had two questions- 1. Does anyone know why I can''t see any ec2 variables from facter in my instance? I''m running facter --puppet in my instance 2. I''m using certname=webserver01 in my puppet.conf /w an external node classifier to distinguish nodes. I don''t seem to be able to use certname as a global scope variable: why doesn''t this work out of the box? and how can I get it into my manifests? (is re-parroting the certname as a variable in my ENC script the only way?) Thanks! I''m really loving puppet so far. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
On Wed, Dec 28, 2011 at 7:38 PM, seanm <reinvigorate@gmail.com> wrote:> I''m testing puppet 2.6.2 (debian) in ec2. I had two questions-> 2. I''m using certname=webserver01 in my puppet.conf /w an external > node classifier to distinguish nodes. I don''t seem to be able to use > certname as a global scope variable: why doesn''t this work out of the > box? and how can I get it into my manifests? (is re-parroting the > certname as a variable in my ENC script the only way?)This is available as $clientcert: http://docs.puppetlabs.com/guides/faq.html#are-there-variables-available-other-than-those-provided-by-facter Thanks, Nan -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Thank you! $clientcert works like a charm! I''m still unclear as to why I can''t see any of the ec2 variables in my ec2 instance. Is it because I''m running an old version of puppet or something? Sean On Dec 29, 10:21 am, Nan Liu <n...@puppetlabs.com> wrote:> On Wed, Dec 28, 2011 at 7:38 PM, seanm <reinvigor...@gmail.com> wrote: > > I''m testing puppet 2.6.2 (debian) in ec2. I had two questions- > > 2. I''m using certname=webserver01 in my puppet.conf /w an external > > node classifier to distinguish nodes. I don''t seem to be able to use > > certname as a global scope variable: why doesn''t this work out of the > > box? and how can I get it into my manifests? (is re-parroting the > > certname as a variable in my ENC script the only way?) > > This is available as $clientcert:http://docs.puppetlabs.com/guides/faq.html#are-there-variables-availa... > > Thanks, > > Nan-- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
On Thu, Dec 29, 2011 at 10:59 AM, seanm <reinvigorate@gmail.com> wrote:> Thank you! $clientcert works like a charm! > > I''m still unclear as to why I can''t see any of the ec2 variables in my > ec2 instance. Is it because I''m running an old version of puppet or > something? >If you''re running Puppet 2.6.2, I imagine the version of Facter is also quite old. EC2 facts have had some work done to them in the last few releases of Facter. What''s the version you are running?> Sean > > On Dec 29, 10:21 am, Nan Liu <n...@puppetlabs.com> wrote: >> On Wed, Dec 28, 2011 at 7:38 PM, seanm <reinvigor...@gmail.com> wrote: >> > I''m testing puppet 2.6.2 (debian) in ec2. I had two questions- >> > 2. I''m using certname=webserver01 in my puppet.conf /w an external >> > node classifier to distinguish nodes. I don''t seem to be able to use >> > certname as a global scope variable: why doesn''t this work out of the >> > box? and how can I get it into my manifests? (is re-parroting the >> > certname as a variable in my ENC script the only way?) >> >> This is available as $clientcert:http://docs.puppetlabs.com/guides/faq.html#are-there-variables-availa... >> >> Thanks, >> >> Nan > > -- > You received this message because you are subscribed to the Google Groups "Puppet Users" group. > To post to this group, send email to puppet-users@googlegroups.com. > To unsubscribe from this group, send email to puppet-users+unsubscribe@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-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
facter --version is showing: 1.5.7 On Dec 29, 4:11 pm, Michael Stahnke <stah...@puppetlabs.com> wrote:> On Thu, Dec 29, 2011 at 10:59 AM, seanm <reinvigor...@gmail.com> wrote: > > Thank you! $clientcert works like a charm! > > > I''m still unclear as to why I can''t see any of the ec2 variables in my > > ec2 instance. Is it because I''m running an old version of puppet or > > something? > > If you''re running Puppet 2.6.2, I imagine the version of Facter is > also quite old. EC2 facts have had some work done to them in the last > few releases of Facter. What''s the version you are running? > > > > > > > > > Sean > > > On Dec 29, 10:21 am, Nan Liu <n...@puppetlabs.com> wrote: > >> On Wed, Dec 28, 2011 at 7:38 PM, seanm <reinvigor...@gmail.com> wrote: > >> > I''m testing puppet 2.6.2 (debian) in ec2. I had two questions- > >> > 2. I''m using certname=webserver01 in my puppet.conf /w an external > >> > node classifier to distinguish nodes. I don''t seem to be able to use > >> > certname as a global scope variable: why doesn''t this work out of the > >> > box? and how can I get it into my manifests? (is re-parroting the > >> > certname as a variable in my ENC script the only way?) > > >> This is available as $clientcert:http://docs.puppetlabs.com/guides/faq.html#are-there-variables-availa... > > >> Thanks, > > >> Nan > > > -- > > You received this message because you are subscribed to the Google Groups "Puppet Users" group. > > To post to this group, send email to puppet-users@googlegroups.com. > > To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. > > For more options, visit this group athttp://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-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
On Thu, Dec 29, 2011 at 4:01 PM, seanm <reinvigorate@gmail.com> wrote:> facter --version is showing: 1.5.7It looks like there is have been quite a few ec2 fact improvements since 1.5.7. The current version of facter is 1.6.4. You could try that (download from apt.puppetlabs.com). I see five or six commits around ec2 facts since 1.5.9.> > > On Dec 29, 4:11 pm, Michael Stahnke <stah...@puppetlabs.com> wrote: >> On Thu, Dec 29, 2011 at 10:59 AM, seanm <reinvigor...@gmail.com> wrote: >> > Thank you! $clientcert works like a charm! >> >> > I''m still unclear as to why I can''t see any of the ec2 variables in my >> > ec2 instance. Is it because I''m running an old version of puppet or >> > something? >> >> If you''re running Puppet 2.6.2, I imagine the version of Facter is >> also quite old. EC2 facts have had some work done to them in the last >> few releases of Facter. What''s the version you are running? >> >> >> >> >> >> >> >> > Sean >> >> > On Dec 29, 10:21 am, Nan Liu <n...@puppetlabs.com> wrote: >> >> On Wed, Dec 28, 2011 at 7:38 PM, seanm <reinvigor...@gmail.com> wrote: >> >> > I''m testing puppet 2.6.2 (debian) in ec2. I had two questions- >> >> > 2. I''m using certname=webserver01 in my puppet.conf /w an external >> >> > node classifier to distinguish nodes. I don''t seem to be able to use >> >> > certname as a global scope variable: why doesn''t this work out of the >> >> > box? and how can I get it into my manifests? (is re-parroting the >> >> > certname as a variable in my ENC script the only way?) >> >> >> This is available as $clientcert:http://docs.puppetlabs.com/guides/faq.html#are-there-variables-availa... >> >> >> Thanks, >> >> >> Nan >> >> > -- >> > You received this message because you are subscribed to the Google Groups "Puppet Users" group. >> > To post to this group, send email to puppet-users@googlegroups.com. >> > To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. >> > For more options, visit this group athttp://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-users@googlegroups.com. > To unsubscribe from this group, send email to puppet-users+unsubscribe@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-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.