Thanks Lukas: +1 on this changeset not degrading early boot install scenarios where systemd services are ordered After=systemd-networkd-wait-online.service
Preliminary testing on Azure platform look good with accelerated networking enabled have confirmed dual-nic tests correctly configure the primary network devices brought and blocking systemd-networkd-wait-online awaiting the matching hv_netsvc devices.
The tests confirm systemd-networkd-wait-online.service properly awaits the individual devices Also, initial cloud-init integration test runs on Azure noble w/ netplan.io v.1.0-2ubuntu1 do not seem to expose any regressions for our integration tests so far.
cloud-init Ec2 testing of this same proposed netplan.io package doesn't show any degradation of behavior in detecting Ec2's IMDS in early boot.
Thanks Lukas: +1 on this changeset not degrading early boot install scenarios where systemd services are ordered After=systemd- networkd- wait-online. service
Preliminary testing on Azure platform look good with accelerated networking enabled have confirmed dual-nic tests correctly configure the primary network devices brought and blocking systemd- networkd- wait-online awaiting the matching hv_netsvc devices. networkd- wait-online. service properly awaits the individual devices Also, initial cloud-init integration test runs on Azure noble w/ netplan.io v.1.0-2ubuntu1 do not seem to expose any regressions for our integration tests so far.
The tests confirm systemd-
cloud-init Ec2 testing of this same proposed netplan.io package doesn't show any degradation of behavior in detecting Ec2's IMDS in early boot.