=== Daniel is now known as toolz
=== cpaelzer_ is now known as cpaelzer
=== yjftsjthsd9 is now known as yjftsjthsd
[18:36] <rharper> lovely, https://bugs.launchpad.net/netplan/+bug/1756590  
[18:36] <ubottu> Launchpad bug 1756590 in netplan "'gateway4' is cumbersome" [Medium, Fix Released]
[18:36] <rharper> so, netplan renderer will need to adjust here 
[19:21] <falcojr> wheeee
[20:32] <chaos12> hey everyone. I was wondering if anyone with experience using the vmware datasource was around? Looking at using it with network profiles to assign an IP to the VM from a pool. Is this a supported use case or is there a way we can implement this?
[20:33] <chaos12> It is a feature from the older-vApp settings
[20:40] <falcojr> akutz: is ^ something you could answer?
[20:40] <akutz> chahos12: Will take a look in a bit.
[20:42] <akutz> chaos12: Will take a look in a bit.
[20:50] <chaos12> Thanks andrew. side question but is there a way to see a history in this chat? Might have to disconnect for a bit. Just using the libera chat website
[21:28] <falcojr> chaos12: https://irclogs.ubuntu.com/latest/%23cloud-init.html
[21:28] <chaos12> Perfect, thanks falcojr
[21:32] <chaos12> Context for when you get back akutz, Rancher has support for setting the vApp dynamic properties when provisioning VMs but these get ignored when using cloud-init instead (expected). But it would be great if vSphere populated guestinfo "extra-vars" that could be included in the instance metadata so you can configure networking. Currently I think
[21:32] <chaos12> you can hack around this by using a mix of vApp settings just to get these dynamic OVF properties, grabbing the values using `vmtoolsd`, then using cloud-init to write a netplan and apply it in the userdata (cant use the networking metadata module)
[21:33] <chaos12> I'll be back in an hour-ish but will read the history in case you replied. Thanks in advance
[22:21] <chaos89> back!