[01:31] <cabazon> hi, can I do cloud-init with unikernel (like Nanos) ? 
[08:55] <meena> cabazon: if Nanos is POSIX based, has python3 support, then you could use it to bootstrap your Nanos VM with cloud-init
[08:57] <meena> however, you'd need to add support for Nanos as a distro: https://github.com/canonical/cloud-init/tree/main/cloudinit/distros
[08:58] <meena> and the equivalent for networking… which should become easier, once I'm done refactoring cloudinit.net
[09:25] <aciba> Does anybody know whether the machine-id of an instance is generated by sysvinit or not and if so, where could I find documentation about it? I have been trying to find doc about it in the context of https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1563951
[10:13] <meena> aciba: not by FreeBSD sysvinit
[10:14] <meena> aciba: https://wiki.debian.org/MachineId seems to be how it's done
[10:15] <meena> aciba: so it seems to be a dbus thing then?
[10:18] <aciba> meena: systemd ultimately generates via dbus if not provided by other means, I was wondering if sysvinit does something similar, but didn't find info about it
[10:19] <meena> aciba: it might, on some Linux distros, if you have dbus installed, link it in place
[10:29] <aciba> meena: so it is distro dependent. Thanks!
[10:30] <meena> aciba: most likely, i have no time to go poking
[10:31] <aciba> meena: no worries, thanks a lot
[20:54] <meena> do we have types for IPv4/IPv6?
[20:56] <meena> there's a module, ipaddress
[22:17] <meena> here's a prototype for the ifconfig parser: https://gist.github.com/igalic/0b326b003b31650f8dda05b5f09aa5a5
[22:17] <meena> the emphasis, I suppose, is on "type"
[22:18] <meena> tomorrow I'm gonna write some unit tests with some of the pastes I've gotten, and then start writing actual code.
[22:20] <meena> a lot of questions can be answered from this datastructure… is_physical() for example is an interface that's got a sensible media type, a mac address, and *no* groups.
[22:23] <meena> but it makes me think i should attach our cloudinit.net methods to the IfConfig class, just so I'm not constantly shelling out to `ifconfig -a`, and parsing it again… because I don't know how sensible caching is here…