[chef] RE: Re: Re: Re: aws and chef do not play nice

[POULAIN Dominique < >]

Hi,

I assume the ohai resource is what you had in mind:

http://docs.opscode.com/chef/resources.html#ohai

Cheers,

dsp
________________________________________
From: Torben Knerr 

 
Sent: 21 November 2013 09:08
To: 

 
Subject: [chef] Re: Re: Re: aws and chef do not play nice

Wasn't there a way to reload ohai during a Chef run, e.g. after the hints 
file has been placed?

I have seen this somewhere, but can't find it right now...

Cheers, Torben

On Nov 21, 2013 5:31 AM, "Daniel DeLeo" 
<
 <mailto:
 >>
 wrote:


On Wednesday, November 20, 2013 at 8:24 PM, Morgan Blackthorne wrote:

Speaking of this, I noticed that private VPC nodes don't seem to have 
node['cloud'] or node['ec2'] defined. Is there a good workaround for this, to 
always force these attributes to get loaded on those nodes? I bake my own 
AMIs so if that helps, I'm fine with it.
The hints file Julian describes below takes care of this


On Wednesday, November 20, 2013, Julian C. Dunn wrote:
Part of the issue is that we have not yet found a reliable way in Ohai
to detect whether a machine is running in EC2. Hence the hints file.
However, creating the hints file in recipe code is not sufficient to
populate node['ec2'] because by that point, Ohai has already run.

You can create the hints file *before* you run Chef in a number of
ways, one of which is that "knife ec2 server create" will take a
--hint parameter.

- Julian



--
Daniel DeLeo