| 2016-02-24 17:41:26 |
Scott Moser |
bug |
|
|
added bug |
| 2016-02-25 16:01:34 |
Scott Moser |
summary |
FFE: improvements and fixes to cloud-init networking |
[FFe]: improvements and fixes to cloud-init networking |
|
| 2016-02-25 19:36:42 |
Scott Moser |
description |
Ubuntu cloud images have network information “hard coded” in /etc/network/interfaces (ENI). For cloud images, this configuration has always amounted to “dhcp on eth0”. For MAAS images /etc/network/interfaces is a symlink to /run/network/dynamic-interfaces which is populated from within the initramfs by the cloud-initramfs-dyn-netconf package based on the result of ‘ip=’ parameters on the kernel command line. Both of these networking configurations came from the initial use case for the image type. For cloud-images, this was EC2 and for maas-images, the maas ephemeral environment.
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
* allow easily disabling of cloud-init
* 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/dyn-interfaces
* General Cloud-init ‘disable’ kernel command line.
* Cloud-localds support for configuring networking |
Ubuntu cloud images have network information “hard coded” in /etc/network/interfaces (ENI). For cloud images, this configuration has always amounted to “dhcp on eth0”. For MAAS images /etc/network/interfaces is a symlink to /run/network/dynamic-interfaces which is populated from within the initramfs by the cloud-initramfs-dyn-netconf package based on the result of ‘ip=’ parameters on the kernel command line. Both of these networking configurations came from the initial use case for the image type. For cloud-images, this was EC2 and for maas-images, the maas ephemeral environment.
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/dyn-interfaces
* General Cloud-init ‘disable’ kernel command line.
* Cloud-localds support for configuring networking |
|
| 2016-02-29 21:27:12 |
Scott Moser |
bug |
|
|
added subscriber Ubuntu Release Team |
| 2016-03-03 11:45:28 |
Martin Pitt |
cloud-init (Ubuntu): status |
New |
Confirmed |
|
| 2016-03-08 20:08:43 |
Scott Moser |
cloud-init (Ubuntu): importance |
Undecided |
High |
|
| 2016-03-08 20:13:02 |
Surojit Pathak |
bug |
|
|
added subscriber Surojit Pathak |
| 2016-03-14 16:56:11 |
Launchpad Janitor |
branch linked |
|
lp:~smoser/ubuntu/xenial/cloud-utils/pkg |
|
| 2018-04-05 09:34:18 |
Iain Lane |
cloud-init (Ubuntu): status |
Confirmed |
Fix Released |
|
