Issue #7559 has been updated by Jeff McCune.
Unfortunately I still need validation of this on OpenStack. Apparently the "next gen" RackSpace cloud is based on OpenStack, but they're removed support for the metadata server at http://169.254.169.254 [1]. In the RackSpace next-generation cloud, the change set does return "xenu" so the metadata server at 169.254.169.254 is probed as expected. Unless there is additional information available from community members who run inside of OpenStack, I'm going to proceed as though the change set is behaving as expected. As previously noted, this change set is working as expected in Amazon EC2 VPC instances and public cloud instances, so we're good to go there. Finally, I've investigated the issue where the `virtual` fact is `xenu` when `virt-what` is _not_ installed and appears to be `xen` when virt-what _is_ installed. In the current master branch of Facter, which is slated to become Facter 2 this is not an issue. There is a case statement that matches the output of `virt-what` such that `xenu` is consistently returned. Please see <https://github.com/puppetlabs/facter/blob/cf43fc0092f0476d378ea05dd8e21fc170a51bdf/lib/facter/virtual.rb#L179-L180>. Unless there is additional information based on the pull request and not based on Facter 1.6.x, I'm going to proceed as though this change is behaving as expected. Please do exploratory testing against my `ec2_vpc_7559` branch and not against Facter 1.6.x since we've made a lot of improvements in this area already. [1] <http://feedback.rackspace.com/forums/71021-product-feedback/suggestions/3285653-bring-back-169-254-169-254-support> ---------------------------------------- Feature #7559: Fact for identifying Amazon VPC instances. https://projects.puppetlabs.com/issues/7559#change-82226 Author: Nigel Kersten Status: In Topic Branch Pending Review Priority: Normal Assignee: Martijn Heemels Category: cloud - ec2 Target version: 2.0.0 Keywords: vpc ec2 arp Branch: https://github.com/puppetlabs/facter/pull/387 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 unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/puppet-bugs?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
