[01:04] alevy, running 'single' doesn't actually hit the datasource. [01:04] harlowja, [01:04] it just uses what it already found [01:04] you have to re run 'cloud-init init' to have it search [01:04] ya, moving /var/lib/cloud should make that work out right [01:08] single wont re-run the search though [01:08] so it wont have pulled the data. [01:08] i dont think [01:08] this use case is one i want to solve with 'ci-tool' [01:08] ya, k, i think alevy was running init also === harlowja is now known as harlowja_away === harlowja_away is now known as harlowja === harlowja is now known as harlowja_away === medberry is now known as med_ === harlowja_away is now known as harlowja [18:16] harlowja: hey man if you have time I am going to roll a new instance and try to finish debugging this?your input is appreciated. [18:17] sure, i'll have a little time today, today i have more meetings (which sux) [18:17] smoser can probably also jump in to (or others) [18:17] ha ha [18:17] yeah understood [18:17] thx [18:17] i can help. sure. [18:18] all smoser fault anyway alevy , lol [18:18] :-P [18:18] ha [18:18] thanks guys [18:18] let me get it up and see where i am at [19:12] smoser: I assume i need console=ttyS0 to make sure I can see cloud-iit output at boot? [19:13] ubuntu? [19:13] smoser: centos [19:13] i don tknwo fo sure, but quite possibly. [19:13] it depends on the sysvinit scripts [19:14] if they send output to their stdout (which i'd expect them to do) [19:14] so yeah, you probably should have that. and should log thta serial console [19:22] ok [21:23] smoser: have you been following the systemd-networkd work? They kinda have a proposal rolling for network config files. [21:23] smoser: ps sorry i'm bad at bzr; made it a new merge proposal :-/ [21:25] pquerna, no. not at all. network config files ? [21:29] smoser: http://lists.freedesktop.org/archives/systemd-devel/2013-November/014077.html was the first patch, trying to find the bigger spec doc on the .network and .link file formats. [21:37] smoser: i know the CoreOS guys are interested in getting the .link and .network files onto a ConfigDrive, rather than having to parse out the interface file. Not sure in the end its much different though. [21:39] well, i think thats wrong. [21:39] network/interfaces format is equally wrong [21:39] but openstack is stuck with it for legacy [21:39] they shouldn't go inserting some other arbitrary format in. [21:39] i'm all for something better. [21:39] instead use something like the netcfg format or somethign. [21:40] is anyone actually adopting netcfg though? [21:40] picking up a "standard" that is all of 2 months old isn't a good idea.