Ohai on a AWS VPC instance

Edward · January 20, 2014, 7:39pm

Ohai Chefs!

I’m seeing an issue with running a AWS instance in a VPC that has an Elastic IP
associated to it, the issue that I see is that I’m expecting node[cloud] and
node[cloud][public_ipv4] and its not there on the VPC instance.

Here is what I’m running on the VPC node:
ii chef 11.8.2-1.ubuntu.12.04
amd64 The full stack of chef
root@ip-10-0-16-121:~# lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 12.10
Release: 12.10
Codename: quantal

Quick output from a host in a VPC w/EIP and a non-VPC host w/EIP:

VPC host:
ohai | grep cloud
"label": “cloudimg-rootfs”
"/dev/disk/by-label/cloudimg-rootfs": {

Non-VPC:
ohai | grep cloud
"cloud": {
“label”: “cloudimg-rootfs”
"/dev/disk/by-label/cloudimg-rootfs": {

As you can see the non-VPC host has node[cloud] and the non-vpc host does not.
Here is a full output of ohai on the VPC host

https://gist.github.com/edwardvfluke/8527113

Any Ideas on why this is happening?

Thanks,
ev-

Eric_Herot · January 20, 2014, 7:45pm

Hi Edward,

Afaik that attribute is created if there is an ohai hint called 'ec2.json'. The knife-ec2 plugin automatically sets this hint during bootstrap (if you use that bootstrap method). Is it possible that the VPC nodes were bootstrapped in a way that would have skipped this step?

The relevant codey bits...
Where knife-ec2 sets the hint:

github.com

chef/knife-ec2/blob/3ac33a5938c30002d06b3e1279ff2a660ea02897/lib/chef/knife/ec2_server_create.rb#L528


      
            bootstrap.config[:environment] = locate_config_value(:environment)
            bootstrap.config[:prerelease] = config[:prerelease]
            bootstrap.config[:first_boot_attributes] = locate_config_value(:json_attributes) || {}
            bootstrap.config[:encrypted_data_bag_secret] = locate_config_value(:encrypted_data_bag_secret)
            bootstrap.config[:encrypted_data_bag_secret_file] = locate_config_value(:encrypted_data_bag_secret_file)
            bootstrap.config[:secret] = locate_config_value(:secret)
            bootstrap.config[:secret_file] = locate_config_value(:secret_file)
            # Modify global configuration state to ensure hint gets set by
            # knife-bootstrap
            Chef::Config[:knife][:hints] ||= {}
            Chef::Config[:knife][:hints]["ec2"] ||= {}
            bootstrap
          end
          
          def fetch_server_fqdn(ip_addr)
              require 'resolv'
              Resolv.getname(ip_addr)
          end
          
          def bootstrap_for_windows_node(server, fqdn)
            if locate_config_value(:bootstrap_protocol) == 'winrm' || locate_config_value(:bootstrap_protocol) == nil

Where the bootstrap process drops it on the node:
https://github.com/opscode/chef/blob/master/lib/chef/knife/bootstrap/chef-full.erb#L54

Hope this helps…

Eric

On Jan 20, 2014, at 2:39 PM, Edward edward@digitalnetz.net wrote:

Ohai Chefs!

I'm seeing an issue with running a AWS instance in a VPC that has an Elastic IP
associated to it, the issue that I see is that I'm expecting node[cloud] and
node[cloud][public_ipv4] and its not there on the VPC instance.

Here is what I'm running on the VPC node:
ii chef 11.8.2-1.ubuntu.12.04
amd64 The full stack of chef
root@ip-10-0-16-121:~# lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 12.10
Release: 12.10
Codename: quantal

Quick output from a host in a VPC w/EIP and a non-VPC host w/EIP:

VPC host:
ohai | grep cloud
"label": "cloudimg-rootfs"
"/dev/disk/by-label/cloudimg-rootfs": {

Non-VPC:
ohai | grep cloud
"cloud": {
"label": "cloudimg-rootfs"
"/dev/disk/by-label/cloudimg-rootfs": {

As you can see the non-VPC host has node[cloud] and the non-vpc host does not.
Here is a full output of ohai on the VPC host

https://gist.github.com/edwardvfluke/8527113

Any Ideas on why this is happening?

Thanks,
ev-

kallistec · January 21, 2014, 6:21pm

For further explanation, VPC mode in EC2 breaks ohai’s auto detection of EC2. Ohai’s hint system is a workaround for cases where we can not reliably auto detect some feature of the platform we’re on, so you need to create a hint file as referenced in the previous post to tell ohai to gather EC2 data.

HTH,

--
Daniel DeLeo

On Monday, January 20, 2014 at 11:45 AM, Eric Herot wrote:

Hi Edward,

Afaik that attribute is created if there is an ohai hint called 'ec2.json'. The knife-ec2 plugin automatically sets this hint during bootstrap (if you use that bootstrap method). Is it possible that the VPC nodes were bootstrapped in a way that would have skipped this step?

The relevant codey bits...
Where knife-ec2 sets the hint:
https://github.com/opscode/knife-ec2/blob/3ac33a5938c30002d06b3e1279ff2a660ea02897/lib/chef/knife/ec2_server_create.rb#L528
Where the bootstrap process drops it on the node:
https://github.com/opscode/chef/blob/master/lib/chef/knife/bootstrap/chef-full.erb#L54

Hope this helps…

Eric

On Jan 20, 2014, at 2:39 PM, Edward <edward@digitalnetz.net (mailto:edward@digitalnetz.net)> wrote:

Ohai Chefs!

I'm seeing an issue with running a AWS instance in a VPC that has an Elastic IP
associated to it, the issue that I see is that I'm expecting node[cloud] and
node[cloud][public_ipv4] and its not there on the VPC instance.

Here is what I'm running on the VPC node:
ii chef 11.8.2-1.ubuntu.12.04
amd64 The full stack of chef
root@ip-10-0-16-121: (mailto:root@ip-10-0-16-121:)~# lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 12.10
Release: 12.10
Codename: quantal

Quick output from a host in a VPC w/EIP and a non-VPC host w/EIP:

VPC host:
ohai | grep cloud
"label": "cloudimg-rootfs"
"/dev/disk/by-label/cloudimg-rootfs": {

Non-VPC:
ohai | grep cloud
"cloud": {
"label": "cloudimg-rootfs"
"/dev/disk/by-label/cloudimg-rootfs": {

As you can see the non-VPC host has node[cloud] and the non-vpc host does not.
Here is a full output of ohai on the VPC host

https://gist.github.com/edwardvfluke/8527113

Any Ideas on why this is happening?

Thanks,
ev-

Topic		Replies	Views
Questions on chef server & VPC Chef Infra (archive)	3	468	February 11, 2014
Still necessary to hint Ohai on EC2 VPC? Chef Infra (archive)	4	424	August 12, 2014
Knife-ec2 0.6.0 released Chef Infra (archive)	0	371	October 16, 2012
Knife-ec2 0.6.4 Released Chef Infra (archive)	2	300	April 18, 2013
VPC woes Chef Infra (archive)	0	235	November 11, 2011

Ohai on a AWS VPC instance

Related Topics