[11:04] blackboxsw, I need a help on one of the issue I am facing on RHEL 8.1 env with cloudinit 18.5. I have ds-identify.cfg set as below(notfound=disabled), When no datasource is found ideally cloudinit suppose get disabled but what I see on my env is cloudinit continues to run and configures fallback network dhcp. Just trying to understand if I am missing something here? Do you any scenario where ds-identify.cfg is not honoured ? [root@rhel-26-analys [11:04] is cloud-init]# cat /etc/cloud/ds-identify.cfg policy: search,found=all,maybe=all,notfound=disabled [15:49] Hi, I got a question about cloud-init and can't find the answer in the documentation [15:49] At my work, we've got a custom linux distrib made with Yocto [15:50] And we wanted to add cloud-init support, what is the appropriate way to do it ? [15:50] Write an new OS file and create a PR on github ? [15:50] Or maintain a "private" patch with our specific OS ? [15:54] Some platform specific Agent like WALinuxAgent (for Azure) accept PR for custom OSes https://github.com/remip2/WALinuxAgent/blob/master/azurelinuxagent/common/osutil/factory.py === hjensas is now known as hjensas|afk [15:58] Sorry wrong link : https://github.com/Azure/WALinuxAgent/blob/develop/azurelinuxagent/common/osutil/factory.py [15:58] You can see that there is sevral custom OSes in the list like : GaiaOS, NSBSD, marner, iosxe... [21:28] I guess it depends on what you mean by "add cloud-init support". There's a distro class here: https://github.com/canonical/cloud-init/blob/master/cloudinit/distros/__init__.py#L66 and we have distro-specific differences in their respective files here: https://github.com/canonical/cloud-init/tree/master/cloudinit/distros