=== harlowja is now known as harlowja_away === harlowja_away is now known as harlowja === harlowja is now known as harlowja_away [16:12] harlowja_away, bah to pylint. new version in ubuntu now at 1.X, spews warnings about everything. [16:12] :-( [16:15] http://paste.ubuntu.com/6768706/ === harlowja_away is now known as harlowja [17:52] smoser arg, stupid pylint [17:52] logging-not-lazy [17:52] lol [17:52] jeez, when did pylint get so crzy [17:53] harlowja_away, https://code.launchpad.net/~utlemming/cloud-init/vendor_data/+merge/201033 your thoughts there would be appreciated also [17:53] sure boss [17:53] :) [17:53] some of those things its seeing are reasonable. [17:53] but some (unused-argument or unused-variable) [17:53] ya [17:53] we named them with _ to specify that! [17:54] nutty [17:54] which afaik is convention [18:25] k, scott, seems ok to me [18:34] smoser harmw ok, tested basic freebsd (basics), seems to be starting fine and finding the distro and all [18:35] i'll submit up the rc.d files that sean made [18:42] https://code.launchpad.net/~harlowja/cloud-init/freebsd-rc.d/+merge/202155 [18:42] harmw ^ [18:43] compare lines 25,26 with 33 ;) [18:44] ya, sean and his '{' [18:44] :-P [18:44] will fix this for him, lol [18:45] (lines 50,51 in cloudfinal.. 2 blanc lines, instead of just 1) [18:46] and more like that as well :p [18:46] hmmm, all fixed, lol [18:46] hm, what could/would cloudinit_override() do anyway? [18:47] not sure, let me ask him why [18:47] ah great :) annoying stuff to bitch about, those whitelines, I know :p [18:48] harmw thats just reflecting the same thing in the other sysvinit scripts [18:48] its the precmd, though I dont know what sourcing that specific file would accomplish [18:48] ah ok [18:49] http://bazaar.launchpad.net/~cloud-init-dev/cloud-init/trunk/view/head:/sysvinit/redhat/cloud-init#L61 [18:49] i guess just reflecting that functionality [18:50] indeed [18:50] though CLOUDINITARGS is specified in one of the files in L62 or L63 [18:51] and the freebsd script doesn't use anything that could've been specified in a sysconfig file, hence my question :) [18:52] sure sure, understood, maybe for future use then :-P [18:53] ofc, while that could be an argument to completely drop that part for now as well :p [18:53] either or [18:57] harmw so i think sean will packge up any missing dependencies and get those shoved up to freebsd ports also [18:57] cool, I posted the pkg stuff already didn't I [18:58] think so, but might just be good to make sure we have a good list [18:58] known ones i had to install [configobj, jsonpatch, Cheetah, argparse] [18:58] [pyserial, oauth] probably also? [18:59] ^ those 2 are datasource usage dependent [18:59] pkg install python27 py27-yaml py27-requests py27-prettytable py27-cheetah py27-boto dmidecode e2fsprogs gpart sudo [18:59] and jsonpatch, manually [19:00] k [19:00] though those could've brought in some of the ones you just mentioned aswell :) [19:01] np, will make sure sean has a good list [19:01] great [19:04] harlowja, you have a thought ? [19:04] i'm looking to put vendor-data into nocloud [19:04] that would seem pretty easy [19:04] but it uses read_seeded [19:05] which looks for user-data and meta-data [19:05] both of which are "required" [19:05] but vendor-data would be optional [19:05] thats easy peasy for "file://" [19:05] but not for http:// [19:06] as we have retries built in. (and at the moment it doens't look like we have support in 'read_file_or_url' for returning None on 404) [19:07] u should be able to check the status code of the response right? [19:07] http://bazaar.launchpad.net/~cloud-init-dev/cloud-init/trunk/view/head:/cloudinit/url_helper.py#L86 ? [19:07] which in the case of a file 'response' is always 200 [19:09] how do u want it to work i guess [19:09] is the question :-P [19:30] harlowja, http://paste.ubuntu.com/6769790/ [19:30] what do yo uthink of that ? [19:30] none_on not the best of variable names, but a list of status_codes that should return None without retry [19:31] hmmm, what about a stop_retry_callback ? [19:32] then u can pass that callback the last request, and it can stop the retry if it wants [19:32] ? [19:34] what do u think smoser ? [19:36] hm.. [19:36] so you would just pass the exception [19:36] the UrlError ? [19:36] what is check_status ? [19:37] i think i can acutally just use that. [19:38] ya [19:38] there u go [19:38] seems like a good usage [19:38] k [20:08] ok. utlemming i think i'm gonna merge the vendordata stuff now. [20:09] and then i'll merge some other thigns that i think halrow had suggested [20:09] smoser: ack [20:09] and then i'm going to work to make NoCloud take vendordata [20:10] utlemming, i think that 'mergedvendoruser' is vestigial [20:10] right? [20:12] like my third baby arm [20:12] errr [20:12] haha [20:13] yeah, i've never really understood why you have 3 arms [20:14] wierd [20:28] lol [20:29] not my fault at summits that the 3rd baby arm hits u in face, lol [20:29] *mind of its own and all [21:31] harlowja, you there? [21:31] your added tests/unittests/test_ec2_util.py [21:31] has 2 test_metadata_fetch_key [21:47] jeeze harlowja . [21:47] now i have to fiddle wit hthis biuld-depends thingy httpretty [21:49] lol [21:49] smoser well its a nice http testing library [21:49] it should hopefully already exist [21:49] yeah. but lots of fallout [21:50] bddeb now busted [21:50] (due to version) [21:50] hmmm [21:50] and the version you depend on is > what we have in trusty [21:50] (but you work on trusty) [21:50] so i'm dropping that to 0.7.0 [21:50] k [21:50] i think thats fine [21:50] i can alter it if we really need [21:50] and drop it [21:53] ithink th eeasies tthign right now is to drop it as a 'Requires' [21:53] but i guess i'd like a BuildRequires or somthin and put that in [21:53] but we have to plumb that into the ./packages [21:54] ya, typically test-requires right? [21:55] and thats only used for testing [21:55] is it. [21:55] so then it doesn't need to be in buildrequires either [21:55] ? [21:55] ya, from what i've seen at least [21:55] well in ubunt packaing i'm running the tests [21:55] kk [21:55] so a file 'test-requires' ? [21:58] sureee [21:59] at least thats how openstack projects do it, maybe there is a different way [22:02] yeah. thats fine. [22:02] i'm gonna commit something really quick here to just drop tha tfor now [22:02] could you try to do a test-requires ? [22:03] err.. i'll handle that [22:11] ok. well, just pushed. './tools/bddeb -us -uc' works again [22:11] i can [22:11] shall i? [22:11] i added test-requires [22:11] kk [22:11] but tidoesnt get used anywhere really. [22:11] can probably add it to the makefile when make test is ran [22:12] alright. i have to run. [22:12] have a nice weekend all. [22:12] thanks for work. [22:12] byeeeeeeeee! [22:12] i'll do more cloud-init work monday i hope [22:12] *waves 3rd arm [22:12] and vendordata support for openstack (through the ec2metadata service) [22:13] ya, i gotta work more on my openstackdatasource [22:13] and then when we get that Openstack datasource (that harlowja) was going to add... [22:13] :) [22:13] night night [22:13] later. [22:13] lata [23:20] morning [23:21] cloud-init query --name instance_id gives me NotImplementedError: Action 'query' is not currently implemented [23:22] which makes me a sad panda. using the package from debian backports, 0.7.2 Is this expected, anything i can do t ofix it? [23:29] hmmmm, i still think its not fully implemented (unless i forget) [23:29] https://code.launchpad.net/~harlowja/cloud-init/query-back-duo [23:29] kwadronaut ^ [23:29] 'Integrate a slightly cleaner query tool, bring it back to life!' [23:29] lol [23:30] heh [23:31] it's i think good to have, especially for beginners trying to debug. [23:33] agreed [23:33] most of the data though is at /var/lib/cloud/ though [23:33] http://cloudinit.readthedocs.org/en/latest/topics/dir_layout.html [23:34] but not so easy as just using that tool [23:41] yep