[11:19] meena: and FreeBSd congratulation [12:07] faa: thank you! [12:46] So, I'm trying to implement an ifconfig parser for net/*bsd; and I'm trying to figure out where best to put it, because the equivalent of that thing would be all the `/sys` reading methods / functions in Linux land. in BSD, an ifconfig -a would give us all that info; and I'd like to put it into a structured form… a structured form already exists: [12:46] NetworkState but doesn't seem to be used for any such thing [14:42] cjp256: Morning! Thanks for the follup in #1725. [14:42] Do you think the potential work items there are release blockers, or is that work that could go into 22.4? [14:42] If not required in 22.3 I'll move forward with release, but I wanted to double check with you first :) [16:31] holman: i'd be more comfortable with the error handling addressed for the update_metadata_is_supported path + the instance id fix. I have the latter one in queue I'm less sure about the former. If we raise an exception instead of returning False, I assume cloud-init will exit/fail early and what state would we be in? I'll talk to Anh [19:11] cjp256: No problem, sounds good. I reviewed and merged the instance id fix. I'll let blackbox speak to the exception / false bit, seems like he had thoughts on that (blackbox isn't around today, so it will probably be tomorrow). [19:21] meena: yes parsing ifconfig is hard, some utils updated and now parsing friendly example netstat -A --libxo json [19:23] faa: I would like to add --libxo to ifconfig… but that will take a while to trickle down [19:24] faa, but it's not about how tricky it is, it's about where it structurally best fits these days [19:25] a lot has changed since i last worked on cloud-init [19:30] yes is old dream https://reviews.freebsd.org/D25447 but now early developed netlink https://reviews.freebsd.org/D33975 [20:07] faa: libifconfig via ffi was another idea suggested [20:07] i just feel for most admins, libxo is a lot more useful === gschanuel5 is now known as gschanuel