ConfigDrive network configuration does not applied per boot

[r]

Hi,

I'm trying to boot Ubuntu Bionic image by config-drive provisioning, but network configuration will be applied just for first boot (per-instance). Adding EventType.BOOT to network's update_events made it work. Now, I wonder shouldn't it be set in ConfigDriveDataSource? I found no other way to update network configuration by config-drive and without metadata server.

Thanks

[Ryan Harper (raharper)]

Hi,

Thanks for reporting this.

DataSourceConfigDrive doesn't currently set this value, and likely won't by default. However, we do want to allow user-config to opt-in to this behavior.

This is a work-in-progress feature, currently here:

https://code.launchpad.net/~raharper/cloud-init/+git/cloud-init/+ref/feature/cloud-init-hotplug-handler

[r (ameretat-reith)]

Hi Rayn,

Thanks for your response. It looks that work intend to let user-config change modules frequency which is great. It's not clear to me how currently OpenStack applies network changing on next boots without that mechanism. Anyway, is anything missing in that branch making us wait to have it in mainline?

[r (ameretat-reith)]

And I think it would be useful to let in addition to user-config, vendor-data too change configuration frequency. Is it possible it you work? Do you agree with It usefulness?

[James Falcon (falcojr)]

The activity from SamKenXStream is not correct.

This was previously listed as In Progress, but it is not in progress and we have no intention of changing this behavior for ConfigDrive, so I changed it to Invalid. This works as expected, and if you prefer to apply network per boot, you can provide the yaml from this example in either user data or an /etc/cloud/cloud.cfg.d/ file:
https://cloudinit.readthedocs.io/en/latest/explanation/events.html#apply-network-config-every-boot