[00:06] smoser the conversion of that json into network config, looking into that, is that network config yaml made by juju somewhere at some point? and thats why the translation? [00:06] or maas [00:07] seems like https://raw.githubusercontent.com/mgagne/cloud-init-fedora-pkg/epel7/cloud-init-0.7.5-network-info-support.patch isn't really needed (or a large part of it goes away) due to that conversion and stuffs [00:09] * harlowja wonders why the network json stuff wasn't == this network yaml stuff ? [00:27] harlowja: I would like to make clear that I'm not the original author of this patch. The original version can be found here: https://github.com/jayofdoom/cloud-init-fedora-pkg/blob/master/cloud-init-0.7.5-onmetal-configdrive.patch I adapted it to support the "real" network_data.json location instead of loading it from vendor_data.json [00:27] jayofdoom, lol [00:27] nice [00:28] mgagne np, there exists some kind of ubuntu network yaml stuff that the current code in cloud-init is converting network json into [00:28] and i'm more or less trying to figure out what that yaml thing is, ha [00:28] never heard of such yaml [00:29] cause it appears to convert network_data.json ---> in memory format closer to network yaml format --> then this gets turned into a yaml file (that then gets processed by?) [00:29] aka http://bazaar.launchpad.net/~cloud-init-dev/cloud-init/trunk/view/head:/cloudinit/net/network_state.py (this thing) [00:30] the end result of that thing seems to be a yaml file that is written out (which is different from the other yaml file?) that something then processes [00:31] just not quite sure that that thing is, ha [00:31] (and maybe that thing is already in rhel/fedora?) [00:34] or maybe its just a ubuntu thing [00:36] but i'm guessing smoser knows [00:37] I'm not sure why YAML is needed. I think it's only for debug purposes. [00:40] possibly [00:40] commit message doesn't tell much about it which is unfortunate [00:41] ya, so there is a conversion into a in-memory format, which then gets processed @ http://bazaar.launchpad.net/~cloud-init-dev/cloud-init/trunk/view/head:/cloudinit/stages.py#L596 [00:41] which then activates a bunch of debian(?) specific output [00:41] it doesn't use the yaml [00:41] http://bazaar.launchpad.net/~cloud-init-dev/cloud-init/trunk/view/head:/cloudinit/net/network_state.py#L120 [00:41] debug [00:41] right, so maybe just for debug [00:42] and test http://bazaar.launchpad.net/~cloud-init-dev/cloud-init/trunk/view/head:/cloudinit/net/network_state.py#L391 [00:42] so from the looks of it, http://bazaar.launchpad.net/~cloud-init-dev/cloud-init/trunk/view/head:/cloudinit/net/__init__.py#L590 then does all the 'rendering' [00:42] but it sort of looks like debian network style rendering [00:42] which is oddly not in the debian.py distro file, lol [00:42] I guess you are looking for rhel support? [00:43] well https://raw.githubusercontent.com/mgagne/cloud-init-fedora-pkg/epel7/cloud-init-0.7.5-network-info-support.patch has some of that :-P [00:43] just there is a bunch of work that exists to do stuff with this format for ubuntu, just need to figure out where the rhel stuff goes in [00:43] yea, but actually implementation changed a lot in upstream and looks to have made it much more debian specific than needed. [00:43] yup [00:43] i blame smoser [00:43] lol [00:44] now something hacky looks much more appealing ;) [00:44] lol [00:44] or refactor time [00:44] i'll bug smoser when he gets back [00:44] * harlowja unsure how much of http://bazaar.launchpad.net/~cloud-init-dev/cloud-init/trunk/view/head:/cloudinit/net/__init__.py is really debian specific [00:44] seems like a larger part of it [00:45] why can't the distros just agree on a network format, lol [00:46] harlowja: I'm not sure why *anything* distro specific is in that file. should be in distro [13:08] harlowja: I can get you a Mitaka config drive if you'd like (for rhel networking support) === rangerpbzzzz is now known as rangerpb [16:30] dmsimard that'd be sweet [16:31] i can prob get one, but gotta check if the openstack we have is making that network json file [16:31] more samples i have the better :) [16:32] harlowja: https://dmsimard.com/disk.config [16:34] thx [16:34] i gotta start ripping apart the cloud-init net stuff soon [16:35] (cause it seems ubuntu specific) [16:35] i mean debian [16:55] harlowja, it does not have a rh renderer [16:55] but we want one [16:56] smoser ya :-P [16:56] and i have some other changes tat are voing to be necessary [16:56] just unsure what is debian specific and what isn't, ha [16:56] relly need to change some things more to do this right. [16:56] ?? [16:57] the datasource searching needs to chnage some really. [16:57] :) [16:57] here. i'll point you at a branch in a bit with some docs on what i want to change. [16:58] cool [17:01] smoser but ya, datasources are ummm, interesting [17:01] ha [17:23] smoser do u want parallel searching, multiple datasource merging, something else :-P [17:26] or just redo the whole thing, lol [17:29] smoser whats up with the net stuff having references to 'Curtin' ? [17:29] whats 'Curtin'? [17:40] curtin is the curt installer [17:40] harlowja, [17:40] is curt a person? [17:40] lol [17:40] curt cobain [17:40] curtin (the curt installer) is a "fast path" installer designed to install Ubuntu quickly. [17:40] It is blunt, brief, snappish, snippety and unceremonious. [17:41] are u in marketing now? [17:41] lol [17:41] harlowja, the goal is to move all that network stuff out into its own library [17:41] that'd be nice [17:41] but under time pressure we just copied from curtin to cloud-init [17:41] has time pressure been fixed? [17:41] like if i do some rhel stuff, should i just put it in curtin? [17:42] (or maybe i can find someone from RH, lol) [17:47] harlowja, heres a crappy dump of my thoughts http://paste.ubuntu.com/16222645/ [17:57] smoser: FYI, I opened the bug: https://bugs.launchpad.net/cloud-init/+bug/1577982 [17:57] mgagne, yea, i saw. i reproduced . [18:13] smoser: let me know if you need access to a test instance [18:13] I can find a way to make that happen [18:31] harlowja, if you do rh stuff do it in cloud-init [18:31] and then we can move it there. [18:31] k [18:31] did you read that paste above ? [18:31] ya, looked over a little :-P [18:32] what do you think ? [18:32] i think the consolidation of dsmode (basically making it go away) is a big simplification [18:33] and also then a network datasource (such as openstack metadata) can look locally and say "yes, i'm the datasource". [18:33] (by looking at something in dmi information) [18:33] even though it does not have access to the network net. [18:35] ya, seems fair to me [18:44] oh, and when you do that "rh stuff", let me know and I can test it :p === rangerpb is now known as rangerpbzzzz