[13:21] <harmw_> meh, still no openstack community newsletter
[20:14] <smathews> hey guys, im using 0.7.4 and noticed that with the config drive source that when it checks the uuid for previous installs it fails because the length of the uuids differ (extra white space) so it runs on_first_boot everytime, is this a known bug (maybe fixed already)
[20:14] <smathews> ?
[20:27] <smathews_> example http://pastie.org/8769066
[20:36] <smathews> apologies if I missed a responce, the web client keeps disconnecting me
[21:08] <smoser> smathews, why does it find different content in the uuid ?
[21:09] <smoser> smathews, ie, that doesn't look like insane behavior from cloud-init's perspective. why should it be expected to trim data ?
[21:09] <smathews> my guess is that when it writes there is an extra white space at the end of the uuid in the file
[21:12] <smathews> I dont think the logic here is incorrect, or that it should have to trim
[21:12] <smathews> maybe the write of the uuid is incorrect
[21:14] <smathews> also I think this is related, since if the uuids were matching it wouldnt run the network config https://bugs.launchpad.net/cloud-init/+bug/1275098
[21:15] <smathews> on subsequent launches that is
[21:29] <smathews>         util.write_file(iid_fn, "%s\n" % iid)
[21:29] <smathews> looks like its from the newline
[21:29] <smathews> thoughts?
[22:20] <smoser> smathews, it looks like you're right.
[22:20] <smoser> harlowja, ^
[22:21] <harlowja> hmmm, newlnes!
[22:22] <smathews> heh
[22:25] <harlowja> https://code.launchpad.net/~harlowja/cloud-init/strip-iid-newline/+merge/208028 
[22:25] <smathews> so, while we are on the topic of config drives, can I make a request for in on_first_boot to write the files before applying the network config?
[22:25] <smathews> this would be helpful for when writing static routes
[22:26] <harlowja> seems fair
[22:26] <harlowja> any objections smathews ?
[22:26] <harlowja> smoser ^
[22:26] <harlowja> lol
[22:26] <smathews> heh
[22:26] <harlowja> i assume smathews  doesn't have objects :-P
[22:27] <smathews> hmmm I generally dont object with myself... 
[22:27] <smathews> although lol
[22:28] <harlowja> :)
[22:28] <smoser> is it not easy to not write the carraige return?
[22:28] <smoser> clearly strip() should be safe
[22:28] <smoser> but we shoud just not write baad data
[22:28] <smoser> or even bad data
[22:28] <smoser> harlowja, one othe rhting i meant to mention to you.
[22:28] <harlowja> smoser likely it already exists out there with "\n" for quite a few versions, so better to just strip?
[22:28] <smoser> the datasource for openstack right now reads from "latest"
[22:28] <smoser> which is imo wrong
[22:28] <harlowja> ?
[22:29] <smoser> i'm pretty sure it tries "latest" in the metadata service.
[22:29] <smoser> this is somewhat memeory, but there were 2 things i wanted to fix there.
[22:29] <harlowja> k
[22:29] <harlowja> ya, which version to use?
[22:29] <smoser> a.) i thought it was reading from "latest" by default. as opposed to GRIZZLY or HAVANA (their YYYY-MM-DD respectively)
[22:29] <harlowja> sure, seems so
[22:30] <smoser> b.) it was warning when it tried one. warn goes to stdout, which goes to console and log as a warn
[22:30] <smoser> and that wasn't really a failure case.
[22:30] <harlowja> agreed
[22:30] <harlowja> repairing
[22:32] <smathews> smoser, thoughts on writing files before apply network in on_first_boot?
[22:38] <smoser> smathews, i dont follow
[22:38] <smoser> writing files as in 'write_files' ?
[22:39] <smathews> yeah, in on_first_boot apply_network happens before write_files
[22:39] <smathews> Id like to switch that
[22:40] <smathews> it'd be handy for writing static routes and such
[22:42] <smoser> smathews, i have to thikn about it. sorry . have to run right now
[22:42] <smathews> no worries
[22:43] <smathews> thanks for your help!
[22:43] <harlowja> smoser https://code.launchpad.net/~harlowja/cloud-init/ds-os-adjust/+merge/208031
[22:43] <harlowja> whenver u get free