[11:04] <vijayendra> 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] <vijayendra> is cloud-init]# cat /etc/cloud/ds-identify.cfg policy: search,found=all,maybe=all,notfound=disabled
[15:49] <dedesite> Hi, I got a question about cloud-init and can't find the answer in the documentation
[15:49] <dedesite> At my work, we've got a custom linux distrib made with Yocto
[15:50] <dedesite> And we wanted to add cloud-init support, what is the appropriate way to do it ?
[15:50] <dedesite> Write an new OS file and create a PR on github ?
[15:50] <dedesite> Or maintain a "private" patch with our specific OS ?
[15:54] <dedesite> 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
[15:58] <dedesite> Sorry wrong link : https://github.com/Azure/WALinuxAgent/blob/develop/azurelinuxagent/common/osutil/factory.py
[15:58] <dedesite> You can see that there is sevral custom OSes in the list like : GaiaOS, NSBSD, marner, iosxe...
[21:28] <falcojr> 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