[09:20] <humain> Hello, what hypervisors are compatible with cloud-init ?
[09:38] <dalurka> you could run cloud-init on any hypervisor where a supported os runs
[09:46] <humain> Ok, thanks !
[09:50] <dalurka> and where no metadata service is available you can mount an iso containing your yaml
[10:12] <Janus8> Hi,
[10:13] <Janus8> I noticed that upgrading Python to 3.7 or 3.8 breaks cloud-init
[10:13] <Janus8> is this something anyone else observed?
[10:13] <Janus8> looks like upgrade breaks the module "netifaces" - this module is needed at the boot phase to bring the network interface up
[10:14] <Janus8> this happens with cloud-init v. 22.2
[10:59] <esv> it is best not to modify the stock python included in a distribution, there are multiple subsystems that have their dependencies included in the stock one library path
[10:59] <esv> not only cloud-init.
[15:55] <blackboxsw> falcojr: couple of comments on the Outscale 3DS datasource PR
[15:55] <falcojr> blackboxsw: yep, I saw already. Thanks!
[17:18] <blackboxsw> community-notice: release 22.3 is published to our COPR el-testing repo for those interested in rockylinux and other RPM-based distros https://copr.fedorainfracloud.org/coprs/g/cloud-init/el-testing/
[17:19] <blackboxsw> there was a unittest commit needed on top of the release 22.3 tag to ensure COPR built the release properly
[17:20] <blackboxsw> daily copr builds look like they are in good shape against tip of main https://copr.fedorainfracloud.org/coprs/g/cloud-init/el-testing
[17:22] <blackboxsw> wrong link: https://copr.fedorainfracloud.org/coprs/g/cloud-init/cloud-init-dev/