Issue Type: | Improvement |
---|---|
Priority: | 3 - Elevated |
Status: | Resolved |
Created at: | 2018-04-20T15:13:42.804Z |
Updated at: | 2020-04-02T13:57:32.003Z |
Created by: | Former user |
---|---|
Reported by: | Former user |
Assigned to: | Former user |
Fixed: A fix for this issue is checked into the tree and tested.
(Resolution Date: 2020-04-02T13:57:31.992Z)
Due to kvm's use of dhcp, it has a way to automatically pick up network configuration on each boot. For feature parity in bhyve, cloud-init needs to be able to reconfigure the network on each boot.
Support for a boolean customer metadata property, maintain_network
will be added. If this is not present or set to any value other than false
, the network will be reconfigured on every boot.
This value has no impact on first boot.
This value is only respected by HVM images that contain and use a version of cloud-init that supports the maintain_network
metadata item. This is expected to first exist in an update to cloud-init 18.3 or later.
Legacy cloud-init found in debian 8 and centos 6 will not have the ability to control this setting - cloud-init will always be in control of network configuration.
The cloud-init changes are tracked at https://bugs.launchpad.net/cloud-init/+bug/1765801
This is currently in a holding pattern due to concern about how this fix will interact with eventual network hotplug. The hotplug proposal was written in January 2018 with no visible progress since then.
There seems to be agreement that this is worthwhile to approach while hotplug is fleshed out. I received review feedback and things are moving along again.
Bumped priority to match OS-6965, which was closed as a dup of this.
This work has been completed for all non-Ubuntu images.
For Ubuntu, the prerequisite work has just landed.
Merge request updated for cloud-init: https://code.launchpad.net/~mgerdts/cloud-init/+git/cloud-init/+merge/373171
This will eventually allow it to make its way into ubuntu certified images
This should make it into cloud-init 19.3.
https://git.launchpad.net/cloud-init/commit/?id=e81389592a67bb54b889512928dcdf65f87ad436
cloud-init 19.3 was released yesterday. History suggests that it will find its way into Ubuntu 18.04 updates soon.
Per the cloud-init mailing list:
Canonical has just finished Stable Release Update (SRU) validation of
cloud-init version 19.3.41 into Ubuntu Xenial, Bionic, Disco and Eoan. It is
currently available in the <ubuntu-series>-updates repositories and will
make it into certified cloud images in the next few days.The changelog provided in this update can be seen in the package changelog
or in the following process bug:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1854872Thank you all for your contributions to this version of cloud-init.
This means that apt update; apt-upgrade cloud-init
should allow existing and Ubuntu 16.04 and 18.40 instances to begin to use this feature.