[FFe]: improvements and fixes to cloud-init networking
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
cloud-init (Ubuntu) |
Fix Released
|
High
|
Unassigned |
Bug Description
Ubuntu cloud images have network information “hard coded” in /etc/network/
The ‘static’ nature of network configuration in these images makes the difficult to use for anything other than their original use case. It also makes specific images required simply for networking configuration.
Items to be fixed with in cloud-init are:
* remove need for xenial images to have persistent networking disabled via kernel command line
* allow easy disabling of cloud-init via kernel command line or file in filesystem
* Defined and sane behavior on re-writing ENI
* Support single and multi-nic network info from by openstack config-drive
* Support dynamic naming of single network device system
* MAAS / iscsi root with ip= but no symlink from ENI to /run/network/
* General Cloud-init ‘disable’ kernel command line.
* Cloud-localds support for configuring networking
Related branches
summary: |
- FFE: improvements and fixes to cloud-init networking + [FFe]: improvements and fixes to cloud-init networking |
description: | updated |
Changed in cloud-init (Ubuntu): | |
importance: | Undecided → High |
Many thanks for addressing this. Fixing this for an LTS is much appreciated indeed, as it will make the cloud images much more useful particularly for "real hardware" use cases, and also get rid of some gross hacks in e. g. autopkgtest, and fix the broken ppc64el images along the way (bug 1541757).
Do you have a plan how to test and roll this out? I can help testing this on various architectures and cloud+QEMU, but I think before this lands in the official cloud images this should be tested from a PPA (e. g. by running dist-upgrade on a current cloud image and removing the ifnames=0 hack from the grub config).
FF approved, thanks!