Issue #7559 has been updated by Jeff McCune. Status changed from Needs Decision to Accepted Assignee deleted (eric sorenson) Branch deleted (https://github.com/puppetlabs/facter/pull/290)
James Turnbull wrote: > It doesn't require installing Puppet and the stdlib module on a host. A lot > of our customers rely on Facter knowing it is AWS or a VPC during > provisioning before Puppet is to be deployed or they use the facts generated. > Razor is another example. If facter_dot_d shipped with Facter then I'd > probably say that'd be an okay work-around albeit we'd still need to add some > checking logic to the EC2 facts to check a file deployed via that mechanism. The equivalent functionality of the standard library's facter_dot_d fact is implemented in Facter core already and will be released with Facter 1.7.0. Please see related issue #2157 and the related commit at <https://github.com/puppetlabs/facter/commit/4e8fb4152491e9b8b4f332402f12b8ea608ed98d>. This issue remains accepted and open because we still need to address the root issue at hand; that we cannot reliably introspect the EC2 operating environment without explicit and manual end user involvement. Please let me know if the current Facter 1.7.x branch does not provide a sufficient work around to this issue. -Jeff ---------------------------------------- Feature #7559: Fact for identifying Amazon VPC instances. https://projects.puppetlabs.com/issues/7559#change-78167 Author: Nigel Kersten Status: Accepted Priority: Normal Assignee: Category: library Target version: Keywords: vpc ec2 arp Branch: Affected Facter version: 1.6.10 (From the list) I ran into a buglet in facter 1.5.9rc6 (from tmz repo). In normal AWS instances it works great. In VPC instances if doesn't work. This seems to be because VPC instances don't use the fe:ff:ff:... MAC addresses. <pre> /sbin/ifconfig eth0 Link encap:Ethernet HWaddr 02:67:4E:E1:26:30 inet addr:172.17.129.24 ... /sbin/arp Address HWtype HWaddress Flags Mask Iface 169.254.169.253 ether 02:67:4E:C0:00:01 C eth0 172.17.128.1 ether 02:67:4E:C0:00:01 C eth0 /sbin/ifconfig eth0 Link encap:Ethernet HWaddr 02:67:4E:DA:58:16 inet addr:172.17.128.126 /sbin/arp Address HWtype HWaddress Flags Mask Iface 169.254.169.253 ether 02:67:4E:C0:00:01 C eth0 172.17.128.1 ether 02:67:4E:C0:00:01 C eth0 </pre> Of the two VPC EC2 instances I've seen, the MAC address always start with 02:67:4E. I have only seen two instances, both in the same VPC, so I don't know if this holds for every VPC instance, YMMV. in ec2.rb , the following seemed to work: <pre> def has_euca_mac? !!(Facter.value(:macaddress) =~ %r{^02:67:4[eE]:}) end </pre> -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://projects.puppetlabs.com/my/account -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en.
