Hi there,
I''m trying to use a fact to tell whether the machine is virtualised.
I found this and, in testing, its been ok:
http://reductivelabs.com/trac/puppet/wiki/Recipes/VirtualMachine
However, trying to roll this new fact out has been difficult.
1. Debian has got facter looking in /var/puppet/facts while the package
maintainer has other puppet var stuff in /var/lib/puppet/ I used puppet to
create a symlink to work around this.
2. Following the instructions in
http://reductivelabs.com/trac/puppet/wiki/AddingFacts
I can test this properly from the commandline by setting environment
variables etc so I know that the ruby code is working.
Ie:
mkdir -p ~/lib/ruby/facter
export RUBYLIB=~/lib/ruby
cp /var/lib/puppet/facts/virtual.rb $RUBYLIB/facter
facter virtual
does return the expected output.
3. When I run facter from the commandline, without directing $RUBYLIB to my
home directory, I don''t get the expected output.
When I run facter from strace I can see:
open("/var/puppet/facts/virtual.rb", O_RDONLY|O_LARGEFILE) = 4
close(4) = 0
sigprocmask(SIG_BLOCK, NULL, []) = 0
open("/var/puppet/facts/virtual.rb", O_RDONLY|O_LARGEFILE) = 4
close(4) = 0
open("/var/puppet/facts/virtual.rb", O_RDONLY|O_LARGEFILE) = 4
fstat64(4, {st_mode=S_IFREG|0755, st_size=1435, ...}) = 0
mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0xb7f67000
read(4, "Facter.add(\"virtual\") do\n confi"..., 4096) =
1435
so I can tell that facter is reading this new fact file.
But when, from the commandline, I run "facter" or "facter
virtual" I don''t
get the expected output.
--
Please remember that an email is just like a postcard; it is not
confidential nor private nor secure and can be read by many other people
than the intended recipient. A postcard can be read by anyone at the mail
sorting office and expecting what is written on it to be private and secret
is not realistic. Please hold no higher expectation of email.
If you need to send confidential information in an email you need to use
encryption. PGP is Pretty good for this.
--~--~---------~--~----~------------~-------~--~----~
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 have to run facter with the "-p" argument if you want to see facts distributed by Puppet. -Josh On Mar 9, 2009, at 1:50 PM, Steve Wray wrote:> > Hi there, > > I''m trying to use a fact to tell whether the machine is virtualised. > > I found this and, in testing, its been ok: > http://reductivelabs.com/trac/puppet/wiki/Recipes/VirtualMachine > > However, trying to roll this new fact out has been difficult. > > 1. Debian has got facter looking in /var/puppet/facts while the > package > maintainer has other puppet var stuff in /var/lib/puppet/ I used > puppet to > create a symlink to work around this. > > 2. Following the instructions in > http://reductivelabs.com/trac/puppet/wiki/AddingFacts > I can test this properly from the commandline by setting environment > variables etc so I know that the ruby code is working. > > Ie: > mkdir -p ~/lib/ruby/facter > export RUBYLIB=~/lib/ruby > cp /var/lib/puppet/facts/virtual.rb $RUBYLIB/facter > facter virtual > > does return the expected output. > > > 3. When I run facter from the commandline, without directing > $RUBYLIB to my > home directory, I don''t get the expected output. > > When I run facter from strace I can see: > > open("/var/puppet/facts/virtual.rb", O_RDONLY|O_LARGEFILE) = 4 > close(4) = 0 > sigprocmask(SIG_BLOCK, NULL, []) = 0 > open("/var/puppet/facts/virtual.rb", O_RDONLY|O_LARGEFILE) = 4 > close(4) = 0 > open("/var/puppet/facts/virtual.rb", O_RDONLY|O_LARGEFILE) = 4 > fstat64(4, {st_mode=S_IFREG|0755, st_size=1435, ...}) = 0 > mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, > -1, 0) > 0xb7f67000 > read(4, "Facter.add(\"virtual\") do\n confi"..., 4096) = 1435 > > so I can tell that facter is reading this new fact file. > > But when, from the commandline, I run "facter" or "facter virtual" I > don''t > get the expected output. > > > > -- > Please remember that an email is just like a postcard; it is not > confidential nor private nor secure and can be read by many other > people > than the intended recipient. A postcard can be read by anyone at the > mail > sorting office and expecting what is written on it to be private and > secret > is not realistic. Please hold no higher expectation of email. > > If you need to send confidential information in an email you need to > use > encryption. PGP is Pretty good for this. > > >--~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
Joshua Anderson wrote:> You have to run facter with the "-p" argument if you want to see facts > distributed by Puppet.facter -p /usr/bin/facter: invalid option -- p /usr/lib/ruby/1.8/getoptlong.rb:265:in `set_error'': invalid option -- p (GetoptLong::InvalidOption) from /usr/lib/ruby/1.8/getoptlong.rb:434:in `get_option'' from /usr/lib/ruby/1.8/getoptlong.rb:458:in `each'' from /usr/lib/ruby/1.8/getoptlong.rb:457:in `loop'' from /usr/lib/ruby/1.8/getoptlong.rb:457:in `each'' from /usr/bin/facter:70 facter -v 1.3.5 This is Debian Etch and Sarge. The -p works fine in Lenny with facter 1.5.1> -Josh > > On Mar 9, 2009, at 1:50 PM, Steve Wray wrote: > >> Hi there, >> >> I''m trying to use a fact to tell whether the machine is virtualised. >> >> I found this and, in testing, its been ok: >> http://reductivelabs.com/trac/puppet/wiki/Recipes/VirtualMachine >> >> However, trying to roll this new fact out has been difficult. >> >> 1. Debian has got facter looking in /var/puppet/facts while the >> package >> maintainer has other puppet var stuff in /var/lib/puppet/ I used >> puppet to >> create a symlink to work around this. >> >> 2. Following the instructions in >> http://reductivelabs.com/trac/puppet/wiki/AddingFacts >> I can test this properly from the commandline by setting environment >> variables etc so I know that the ruby code is working. >> >> Ie: >> mkdir -p ~/lib/ruby/facter >> export RUBYLIB=~/lib/ruby >> cp /var/lib/puppet/facts/virtual.rb $RUBYLIB/facter >> facter virtual >> >> does return the expected output. >> >> >> 3. When I run facter from the commandline, without directing >> $RUBYLIB to my >> home directory, I don''t get the expected output. >> >> When I run facter from strace I can see: >> >> open("/var/puppet/facts/virtual.rb", O_RDONLY|O_LARGEFILE) = 4 >> close(4) = 0 >> sigprocmask(SIG_BLOCK, NULL, []) = 0 >> open("/var/puppet/facts/virtual.rb", O_RDONLY|O_LARGEFILE) = 4 >> close(4) = 0 >> open("/var/puppet/facts/virtual.rb", O_RDONLY|O_LARGEFILE) = 4 >> fstat64(4, {st_mode=S_IFREG|0755, st_size=1435, ...}) = 0 >> mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, >> -1, 0) >> 0xb7f67000 >> read(4, "Facter.add(\"virtual\") do\n confi"..., 4096) = 1435 >> >> so I can tell that facter is reading this new fact file. >> >> But when, from the commandline, I run "facter" or "facter virtual" I >> don''t >> get the expected output. >> >> >> >> -- >> Please remember that an email is just like a postcard; it is not >> confidential nor private nor secure and can be read by many other >> people >> than the intended recipient. A postcard can be read by anyone at the >> mail >> sorting office and expecting what is written on it to be private and >> secret >> is not realistic. Please hold no higher expectation of email. >> >> If you need to send confidential information in an email you need to >> use >> encryption. PGP is Pretty good for this. >> > > > >-- Please remember that an email is just like a postcard; it is not confidential nor private nor secure and can be read by many other people than the intended recipient. A postcard can be read by anyone at the mail sorting office and expecting what is written on it to be private and secret is not realistic. Please hold no higher expectation of email. If you need to send confidential information in an email you need to use encryption. PGP is Pretty good for this. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
FYI I''ve butchered this into place now by dropping my custom facts into /usr/lib/ruby/1.8/facter/ Obviously this isn''t ideal but its all I''ve found that works. :( Joshua Anderson wrote:> You have to run facter with the "-p" argument if you want to see facts > distributed by Puppet. > > -Josh > > On Mar 9, 2009, at 1:50 PM, Steve Wray wrote: > >> Hi there, >> >> I''m trying to use a fact to tell whether the machine is virtualised. >> >> I found this and, in testing, its been ok: >> http://reductivelabs.com/trac/puppet/wiki/Recipes/VirtualMachine >> >> However, trying to roll this new fact out has been difficult. >> >> 1. Debian has got facter looking in /var/puppet/facts while the >> package >> maintainer has other puppet var stuff in /var/lib/puppet/ I used >> puppet to >> create a symlink to work around this. >> >> 2. Following the instructions in >> http://reductivelabs.com/trac/puppet/wiki/AddingFacts >> I can test this properly from the commandline by setting environment >> variables etc so I know that the ruby code is working. >> >> Ie: >> mkdir -p ~/lib/ruby/facter >> export RUBYLIB=~/lib/ruby >> cp /var/lib/puppet/facts/virtual.rb $RUBYLIB/facter >> facter virtual >> >> does return the expected output. >> >> >> 3. When I run facter from the commandline, without directing >> $RUBYLIB to my >> home directory, I don''t get the expected output. >> >> When I run facter from strace I can see: >> >> open("/var/puppet/facts/virtual.rb", O_RDONLY|O_LARGEFILE) = 4 >> close(4) = 0 >> sigprocmask(SIG_BLOCK, NULL, []) = 0 >> open("/var/puppet/facts/virtual.rb", O_RDONLY|O_LARGEFILE) = 4 >> close(4) = 0 >> open("/var/puppet/facts/virtual.rb", O_RDONLY|O_LARGEFILE) = 4 >> fstat64(4, {st_mode=S_IFREG|0755, st_size=1435, ...}) = 0 >> mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, >> -1, 0) >> 0xb7f67000 >> read(4, "Facter.add(\"virtual\") do\n confi"..., 4096) = 1435 >> >> so I can tell that facter is reading this new fact file. >> >> But when, from the commandline, I run "facter" or "facter virtual" I >> don''t >> get the expected output. >> >> >> >> -- >> Please remember that an email is just like a postcard; it is not >> confidential nor private nor secure and can be read by many other >> people >> than the intended recipient. A postcard can be read by anyone at the >> mail >> sorting office and expecting what is written on it to be private and >> secret >> is not realistic. Please hold no higher expectation of email. >> >> If you need to send confidential information in an email you need to >> use >> encryption. PGP is Pretty good for this. >> > > > >-- Please remember that an email is just like a postcard; it is not confidential nor private nor secure and can be read by many other people than the intended recipient. A postcard can be read by anyone at the mail sorting office and expecting what is written on it to be private and secret is not realistic. Please hold no higher expectation of email. If you need to send confidential information in an email you need to use encryption. PGP is Pretty good for this. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
I think your facter version is rather old. On facter 1.5.4 (and probably before), as long as I have dmidecode installed, facter presents several variables that can be used to identify VM''s without any coding. manufacturer => VMware, Inc. virtual => vmware manufacturer => Xen virtual => physical It appears that $virtual doesn''t work on Xen :( Steve Wray wrote:> FYI I''ve butchered this into place now by dropping my custom facts into > /usr/lib/ruby/1.8/facter/ > > Obviously this isn''t ideal but its all I''ve found that works. > :( > > Joshua Anderson wrote: > >> You have to run facter with the "-p" argument if you want to see facts >> distributed by Puppet. >> >> -Josh >> >> On Mar 9, 2009, at 1:50 PM, Steve Wray wrote: >> >> >>> Hi there, >>> >>> I''m trying to use a fact to tell whether the machine is virtualised. >>> >>> I found this and, in testing, its been ok: >>> http://reductivelabs.com/trac/puppet/wiki/Recipes/VirtualMachine >>> >>> However, trying to roll this new fact out has been difficult. >>> >>> 1. Debian has got facter looking in /var/puppet/facts while the >>> package >>> maintainer has other puppet var stuff in /var/lib/puppet/ I used >>> puppet to >>> create a symlink to work around this. >>> >>> 2. Following the instructions in >>> http://reductivelabs.com/trac/puppet/wiki/AddingFacts >>> I can test this properly from the commandline by setting environment >>> variables etc so I know that the ruby code is working. >>> >>> Ie: >>> mkdir -p ~/lib/ruby/facter >>> export RUBYLIB=~/lib/ruby >>> cp /var/lib/puppet/facts/virtual.rb $RUBYLIB/facter >>> facter virtual >>> >>> does return the expected output. >>> >>> >>> 3. When I run facter from the commandline, without directing >>> $RUBYLIB to my >>> home directory, I don''t get the expected output. >>> >>> When I run facter from strace I can see: >>> >>> open("/var/puppet/facts/virtual.rb", O_RDONLY|O_LARGEFILE) = 4 >>> close(4) = 0 >>> sigprocmask(SIG_BLOCK, NULL, []) = 0 >>> open("/var/puppet/facts/virtual.rb", O_RDONLY|O_LARGEFILE) = 4 >>> close(4) = 0 >>> open("/var/puppet/facts/virtual.rb", O_RDONLY|O_LARGEFILE) = 4 >>> fstat64(4, {st_mode=S_IFREG|0755, st_size=1435, ...}) = 0 >>> mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, >>> -1, 0) >>> 0xb7f67000 >>> read(4, "Facter.add(\"virtual\") do\n confi"..., 4096) = 1435 >>> >>> so I can tell that facter is reading this new fact file. >>> >>> But when, from the commandline, I run "facter" or "facter virtual" I >>> don''t >>> get the expected output. >>> >>> >>> >>> -- >>> Please remember that an email is just like a postcard; it is not >>> confidential nor private nor secure and can be read by many other >>> people >>> than the intended recipient. A postcard can be read by anyone at the >>> mail >>> sorting office and expecting what is written on it to be private and >>> secret >>> is not realistic. Please hold no higher expectation of email. >>> >>> If you need to send confidential information in an email you need to >>> use >>> encryption. PGP is Pretty good for this. >>> >>> >> > > >-- Trevor Hemsley Infrastructure Engineer ................................................. * C A L Y P S O * 4th Floor, Tower Point, 44 North Road, Brighton, BN1 1YR, UK OFFICE +44 (0) 1273 666 350 FAX +44 (0) 1273 666 351 ................................................. www.calypso.com This electronic-mail might contain confidential information intended only for the use by the entity named. If the reader of this message is not the intended recipient, the reader is hereby notified that any dissemination, distribution or copying is strictly prohibited. * P * /*/ Please consider the environment before printing this e-mail /*/ --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
Trevor Hemsley wrote:> I think your facter version is rather old. On facter 1.5.4 (and probably > before), as long as I have dmidecode installed, facter presents several > variables that can be used to identify VM''s without any coding.yeah I know its kind of old. Eventually when we have converged on the latest stable release it''ll be fine. Until then I have to work with what I''ve got. I suspect that its a problem with the package maintainer having forgotten to configure facter to look in the right place, although strace seems to show it looking at the ruby code, it just doesn''t seem to do anything interesting with it.> > manufacturer => VMware, Inc. > virtual => vmware > > manufacturer => Xen > virtual => physical > > It appears that $virtual doesn''t work on Xen :( > > Steve Wray wrote: >> FYI I''ve butchered this into place now by dropping my custom facts into >> /usr/lib/ruby/1.8/facter/ >> >> Obviously this isn''t ideal but its all I''ve found that works. >> :( >> >> Joshua Anderson wrote: >> >>> You have to run facter with the "-p" argument if you want to see facts >>> distributed by Puppet. >>> >>> -Josh >>> >>> On Mar 9, 2009, at 1:50 PM, Steve Wray wrote: >>> >>> >>>> Hi there, >>>> >>>> I''m trying to use a fact to tell whether the machine is virtualised. >>>> >>>> I found this and, in testing, its been ok: >>>> http://reductivelabs.com/trac/puppet/wiki/Recipes/VirtualMachine >>>> >>>> However, trying to roll this new fact out has been difficult. >>>> >>>> 1. Debian has got facter looking in /var/puppet/facts while the >>>> package >>>> maintainer has other puppet var stuff in /var/lib/puppet/ I used >>>> puppet to >>>> create a symlink to work around this. >>>> >>>> 2. Following the instructions in >>>> http://reductivelabs.com/trac/puppet/wiki/AddingFacts >>>> I can test this properly from the commandline by setting environment >>>> variables etc so I know that the ruby code is working. >>>> >>>> Ie: >>>> mkdir -p ~/lib/ruby/facter >>>> export RUBYLIB=~/lib/ruby >>>> cp /var/lib/puppet/facts/virtual.rb $RUBYLIB/facter >>>> facter virtual >>>> >>>> does return the expected output. >>>> >>>> >>>> 3. When I run facter from the commandline, without directing >>>> $RUBYLIB to my >>>> home directory, I don''t get the expected output. >>>> >>>> When I run facter from strace I can see: >>>> >>>> open("/var/puppet/facts/virtual.rb", O_RDONLY|O_LARGEFILE) = 4 >>>> close(4) = 0 >>>> sigprocmask(SIG_BLOCK, NULL, []) = 0 >>>> open("/var/puppet/facts/virtual.rb", O_RDONLY|O_LARGEFILE) = 4 >>>> close(4) = 0 >>>> open("/var/puppet/facts/virtual.rb", O_RDONLY|O_LARGEFILE) = 4 >>>> fstat64(4, {st_mode=S_IFREG|0755, st_size=1435, ...}) = 0 >>>> mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, >>>> -1, 0) >>>> 0xb7f67000 >>>> read(4, "Facter.add(\"virtual\") do\n confi"..., 4096) = 1435 >>>> >>>> so I can tell that facter is reading this new fact file. >>>> >>>> But when, from the commandline, I run "facter" or "facter virtual" I >>>> don''t >>>> get the expected output. >>>> >>>> >>>> >>>> -- >>>> Please remember that an email is just like a postcard; it is not >>>> confidential nor private nor secure and can be read by many other >>>> people >>>> than the intended recipient. A postcard can be read by anyone at the >>>> mail >>>> sorting office and expecting what is written on it to be private and >>>> secret >>>> is not realistic. Please hold no higher expectation of email. >>>> >>>> If you need to send confidential information in an email you need to >>>> use >>>> encryption. PGP is Pretty good for this. >>>> >>>> >>> >> >> >-- Please remember that an email is just like a postcard; it is not confidential nor private nor secure and can be read by many other people than the intended recipient. A postcard can be read by anyone at the mail sorting office and expecting what is written on it to be private and secret is not realistic. Please hold no higher expectation of email. If you need to send confidential information in an email you need to use encryption. PGP is Pretty good for this. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
Le mardi 10 mars 2009 à 09:50 +1300, Steve Wray a écrit :> Hi there, > > I''m trying to use a fact to tell whether the machine is virtualised. > > I found this and, in testing, its been ok: > http://reductivelabs.com/trac/puppet/wiki/Recipes/VirtualMachine > > However, trying to roll this new fact out has been difficult. > > 1. Debian has got facter looking in /var/puppet/facts while the package > maintainer has other puppet var stuff in /var/lib/puppet/ I used puppet to > create a symlink to work around this. > > 2. Following the instructions in > http://reductivelabs.com/trac/puppet/wiki/AddingFacts > I can test this properly from the commandline by setting environment > variables etc so I know that the ruby code is working. > > Ie: > mkdir -p ~/lib/ruby/facter > export RUBYLIB=~/lib/ruby > cp /var/lib/puppet/facts/virtual.rb $RUBYLIB/facter > facter virtual > > does return the expected output. > > > 3. When I run facter from the commandline, without directing $RUBYLIB to my > home directory, I don''t get the expected output. > > When I run facter from strace I can see: > > open("/var/puppet/facts/virtual.rb", O_RDONLY|O_LARGEFILE) = 4 > close(4) = 0 > sigprocmask(SIG_BLOCK, NULL, []) = 0 > open("/var/puppet/facts/virtual.rb", O_RDONLY|O_LARGEFILE) = 4 > close(4) = 0 > open("/var/puppet/facts/virtual.rb", O_RDONLY|O_LARGEFILE) = 4 > fstat64(4, {st_mode=S_IFREG|0755, st_size=1435, ...}) = 0 > mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = > 0xb7f67000 > read(4, "Facter.add(\"virtual\") do\n confi"..., 4096) = 1435 > > so I can tell that facter is reading this new fact file. > > But when, from the commandline, I run "facter" or "facter virtual" I don''t > get the expected output.I''ve ran into the same problem, which is quite simple : facter 1.5.x already provides a fact named "virtual", rename your fact to "custom_virtual" (or whatever) and you''ll be OK. Nicolas. -- Nicolas Szalay Administrateur systèmes & réseaux -- _ ASCII ribbon campaign ( ) - against HTML email X & vCards / \
2009/3/9 Trevor Hemsley <trevor.hemsley@codefarm.com>> > I think your facter version is rather old. On facter 1.5.4 (and probably > before), as long as I have dmidecode installed, facter presents several > variables that can be used to identify VM''s without any coding. > > manufacturer => VMware, Inc. > virtual => vmware > > manufacturer => Xen > virtual => physical > > It appears that $virtual doesn''t work on Xen :( >It appears it doesn'' work under Debian/Windows HyperV either:- glaw@dv01:~ $ sudo facter virtual physical glaw@dv01:~ $ sudo facter -v 1.5.1 glaw@dv01:~ $ sudo facter operatingsystem Debian glaw@dv01:~ $ I may raise a bug. Gary -- Gary Law Email: garylaw@garylaw.net Chat googletalk/messenger: gary.law@gmail.com iChat/jabber/AIM: gary.law@mac.com --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---
Trevor Hemsley wrote:> It appears that $virtual doesn''t work on Xen :(It does for me. I get $virtual = xenu or xen0 on my boxes. Will have to check the exact Facter version, but I can tell you it''s whatever''s in EPEL. cYa, Avi --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
2009/3/11 Avi Miller <avi.miller@gmail.com>> > Trevor Hemsley wrote: > > It appears that $virtual doesn''t work on Xen :( > > It does for me. I get $virtual = xenu or xen0 on my boxes. Will have to > check the exact Facter version, but I can tell you it''s whatever''s in EPEL. >I''ve raised this ticket:- http://projects.reductivelabs.com/issues/2067 I''ll update with what you say. I''ve no Xen box to test on, but ''virtual'' doesn''t work for me on HyperV or Solaris Zones. Gary -- Gary Law Email: garylaw@garylaw.net Chat googletalk/messenger: gary.law@gmail.com iChat/jabber/AIM: gary.law@mac.com --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---
Avi Miller wrote:> Trevor Hemsley wrote: > >> It appears that $virtual doesn''t work on Xen :( >> > > It does for me. I get $virtual = xenu or xen0 on my boxes. Will have to > check the exact Facter version, but I can tell you it''s whatever''s in EPEL. >I just installed 1.5.4 from epel-testing on my VM and still get virtual => physical. Maybe it''s because I am running RHEL4 on my VM? Or because my VM is fully virt? It''s not important to me because there are other ways to get the same info - $manufacturer looks like the best to me -- Trevor Hemsley Infrastructure Engineer ................................................. * C A L Y P S O * Brighton, UK OFFICE +44 (0) 1273 666 350 FAX +44 (0) 1273 666 351 ................................................. www.calypso.com This electronic-mail might contain confidential information intended only for the use by the entity named. If the reader of this message is not the intended recipient, the reader is hereby notified that any dissemination, distribution or copying is strictly prohibited. * P * /*/ Please consider the environment before printing this e-mail /*/ --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
Hello, Am 11.03.2009 um 11:22 schrieb Gary Law:> I''ve raised this ticket:- > > http://projects.reductivelabs.com/issues/2067 > > I''ll update with what you say. I''ve no Xen box to test on, but > ''virtual'' doesn''t work for me on HyperV or Solaris Zones.KVM doesn''t seem to be recognised correctly either, I''ll update the ticket in Redmine. Felix Schäfer ------------- Cyprès IT Solutions GmbH Löwenstr. 11a, D-44135 Dortmund Tel.: +49 231 576 2678 Fax.: +49 231 576 2676 Cyprès IT-Solutions GmbH / private limited company Geschäftsführer / General Manager: Martin Heitmann – Zahra Salimi Sitz der Gesellschaft / registered office: Dortmund Registergericht / commercial office Dortmund: HRB 20853 Steuernummer / Tax ID: 314/57711/1333 Umsatzsteuer-Identnr / VAT ident. No.: DE257871146 --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
Trevor Hemsley wrote:> I just installed 1.5.4 from epel-testing on my VM and still get virtual > => physical. Maybe it''s because I am running RHEL4 on my VM? Or because > my VM is fully virt?I would guess the latter -- my EL4 and EL5 paravirt guests both report xenu, as they are running xenU kernels. The HVM guests run unmodified kernels, so Facter obviously can''t tell it''s a guest. cYa, Avi --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
I have noticed the same thing on CentOS with facter-1.5.2-1.el5.
# puppetd --configprint libdir
/var/lib/puppet/lib
# ls -l /var/lib/puppet/lib/facter/releasever.rb
-rw-r--r-- 1 root root 219 Feb 18 20:02
/var/lib/puppet/lib/facter/releasever.rb
#
Yet an strace shows that `facter -p releasever'' only looks under
/usr/lib and
for /var/puppet/lib/facter/releasever{,.rb} or
/var/puppet/facts/releasever{,.rb}.
Iow, `facter -p'' doesn''t seem to be honoring Puppet''s
$libdir, evidenced by
the fact that the same strace doesn''t show /etc/puppet/puppet.conf
being read.
--
Jos Backus
jos at catnook.com
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en
-~----------~----~----~----~------~----~------~--~---