[01:13] <phunyguy> holmanb: just saw the email, I'll get it tested as soon as I can tonight.
[01:13] <phunyguy> thanks for taking a look.
[02:14] <phunyguy> holmanb: looks like that got it farther, but it probably needs more work.  It's not producing a working network config in /etc/conf.d/net
[02:15] <phunyguy> Also I had to hack in that patch manually, it wasn't applying to the git pulld sources.
[02:15] <phunyguy> pulled*
[03:08] <holmanb> phunyguy: that patch was based on the latest commit on main this afternoon, I should have mentioned that sorry. Glad you got that part figured out.
[03:08] <holmanb> phunyguy: anything interesting in the logfile after applying the patch?
[03:10] <holmanb> I'll often do a `grep -i -e warn -e error -e traceback /var/log/cloud-init.log`, which should be empty on a healthy system.
[03:11] <phunyguy> I will try this again soon and let you know.  I actually didn't realize it was going to create net.eth0, which I didn't look for before, so I wiped and reloaded to see the old behavior to make sure.
[03:11] <phunyguy> usually it's just /etc/conf.d/net that gets created so /etc/conf.d/net.eth0 threw me for a loop.
[03:12] <phunyguy> holmanb: also, the way I patched it with yours was against main... gentoo has a built in method to patch packages, and I instructed it to pull the cloud-init-9999 version which pulls direct from git, and applies the patches specified in /etc/portage/patches.  It still failed.
[03:43] <holmanb> phunyguy: agreed, that patch got mangled sorry
[03:44] <holmanb> phunyguy: That should probably be in version control anyways, here's a branch in case it helps: https://github.com/holmanb/cloud-init/tree/holmanb/phunyguy
[04:04] <phunyguy> Yeah that gives me something I can pip install as you need me to test things
[04:05] <phunyguy> It's late here, I will get back to testing tomorrow afternoon.
[04:05] <phunyguy> thanks holmanb 
[13:00] <holmanb> phunyguy: sounds good :)
[20:05] <holmanb> blackboxsw: I forgot to drop a message earlier, but the Ansible PR is ready for review. I'm much happier with the test coverage now.
[20:06] <blackboxsw> awesome holmanb I forgot to mention as well I'm peeking over meena's freebsd work breakdown for networking to see if it can be captured as more manageable work items
[20:06] <blackboxsw> a la, "Network refactor for BSD" is sort of big
[20:07] <blackboxsw> because it ties into a lot of the https://github.com/canonical/cloud-init/blob/main/WIP-ONGOING-REFACTORIZATION.rst  we have
[20:08] <blackboxsw> ... and initial discussions on that front is sort of one of the major reasons we have some of that networking refactor work in the first place
[20:08] <blackboxsw> to try to support some of this BSD work
[20:09] <blackboxsw> +1 holmanb I'll get through your integration test adds for LXD storage config options so we can mark that Roadmap item "done" and then onto ansible
[20:09] <holmanb> Have I seen this already? I saw mention of the Freebsd networking work yesterday, but is there something more detailed I haven't already seen?
[20:11] <blackboxsw> I think it's work in progress trying to get a commitment for some BSD  networking improvements in cloud-init
[20:11] <blackboxsw> s/a commitment/additional firm commitment/
[20:11] <holmanb> +1 thanks for taking a look at those, network is still down here, unfortunately. I think I'll have to relocate so I can get back online and get in some reviews.
[20:11] <blackboxsw> +1 yeah bummer on that. 
[20:11] <holmanb> Gotcha, I see
[20:11] <blackboxsw> coffee shop in your fugture
[20:12] <holmanb> Indeed. 
[21:50] <holmanb> minimal: does alpine provide systemd-detect-virt for use in cloud-init?
[22:00] <holmanb> I assume not, but looks like the LXD data source fallback config uses eth0 for the interface name inside of VMs that don't have detect-virt, which I didn't think was init-specific?
=== dalurka is now known as dal
=== dal is now known as dalurka