On Wed, Jan 5, 2022 at 9:46 AM Neal Gompa <ngompa13@xxxxxxxxx> wrote: > That is not Ignition configuring the network, that is *you* knowing > what an NM file looks like and dropping it in. With cloud-init, it > knows how to access cloud provider data sources to get configuration > information and translate it into machine network configuration > automatically. For cloud-specific network configuration, we've been steering towards nm-cloud-setup. We do ship it in FCOS, but it's currently disabled by default pending more CI coverage and investigation: https://github.com/coreos/fedora-coreos-tracker/issues/320#issuecomment-791492732 So in theory, we could drop support for ifcfg as this Change is proposing and add nm-cloud-setup. (And that'd take us closer to being able to move from cloud-init to Ignition, which would have lots of benefits too.) I'm not sure how wide the gap between nm-cloud-setup and cloud-init is today though. _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
