Ohai 0.6.6.RC.1


#1

I’ve pushed out another release candidate for 0.6.6 with some
additional work for detecting Xen. Those of you using Chef/Ohai on Xen
should give 0.6.6.RC.1 a whirl.

http://tickets.opscode.com/browse/OHAI-253


Bryan McLellan | opscode | senior systems administrator
© 206.607.7108 | (t) @btmspox | (b) http://blog.loftninjas.org


#2

On Sep 26, 2011, at 1:50 PM, Bryan McLellan wrote:

I’ve pushed out another release candidate for 0.6.6 with some
additional work for detecting Xen. Those of you using Chef/Ohai on Xen
should give 0.6.6.RC.1 a whirl.

http://tickets.opscode.com/browse/OHAI-253

I haven’t seen any progress on OHAI-239. Any thoughts?


Brad Knowles bknowles@ihiji.com
SAGE Level IV, Chef Level 0.0.1


#3

On Thursday, September 29, 2011 at 4:17 PM, Brad Knowles wrote:

On Sep 26, 2011, at 1:50 PM, Bryan McLellan wrote:

I’ve pushed out another release candidate for 0.6.6 with some
additional work for detecting Xen. Those of you using Chef/Ohai on Xen
should give 0.6.6.RC.1 a whirl.

http://tickets.opscode.com/browse/OHAI-253

I haven’t seen any progress on OHAI-239. Any thoughts?


Brad Knowles <bknowles@ihiji.com (mailto:bknowles@ihiji.com)>
SAGE Level IV, Chef Level 0.0.1
There’s no patch, but this looks like a bug in the images–ohai is faithfully reporting what hostname says the hostname is. I’d be resistant to embedding a value judgement about hostnames into ohai. If you don’t like the hostnames, why not use chef to change them?


Dan DeLeo


#4

On Sep 29, 2011, at 6:33 PM, Daniel DeLeo wrote:

There’s no patch, but this looks like a bug in the images–ohai is faithfully reporting what hostname says the hostname is. I’d be resistant to embedding a value judgement about hostnames into ohai. If you don’t like the hostnames, why not use chef to change them?

Your comment has caused me to re-think the way we were approaching the FQDN issue, and I think I can actually use this to our advantage the way it is.

Now that I’ve figured this out, of course Rackspace will decide to put a proper FQDN into that value and break what we’re going to try to do, but I’ll at least keep an eye out for that.

Thanks!


Brad Knowles bknowles@ihiji.com
SAGE Level IV, Chef Level 0.0.1


#5

On Fri, Sep 30, 2011 at 10:01 AM, Brad Knowles bknowles@ihiji.com wrote:

Now that I’ve figured this out, of course Rackspace will decide to put a proper FQDN into that value and break what we’re going to try to do, but I’ll at least keep an eye out for that.

You could detect that and have it raise an exception when they do =D