support cloud-init networking with snappy
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Snappy |
Fix Released
|
Undecided
|
Unassigned | ||
cloud-init (Ubuntu) |
Fix Released
|
Medium
|
Unassigned | ||
livecd-rootfs (Ubuntu) |
Fix Released
|
High
|
Oliver Grawert |
Bug Description
snappy configures /etc/network/
with version 0.7.7~bzr1189-
ubuntu@localhost:~$ ls -l /etc/network/
total 8
-rw-r--r-- 1 root root 64 Mar 28 09:23 50-cloud-init.cfg
-rw-r--r-- 1 root root 40 Mar 28 09:19 eth0
ubuntu@localhost:~$ cat /etc/network/
auto lo
iface lo inet loopback
auto eth0
iface eth0 inet dhcp
ubuntu@localhost:~$ cat /etc/network/
allow-hotplug eth0
iface eth0 inet dhcp
Changed in livecd-rootfs (Ubuntu): | |
status: | New → Confirmed |
importance: | Undecided → High |
assignee: | nobody → Oliver Grawert (ogra) |
summary: |
- cloud-init 0.7.7~bzr1189-0ubuntu1 adds duplicated network config in - /etc/network/interfaces.d/ in snappy leaving the boot completely - network-less + support cloud-init networking with snappy |
Changed in cloud-init (Ubuntu): | |
importance: | High → Medium |
Changed in snappy: | |
status: | New → Fix Released |
Changed in cloud-init (Ubuntu): | |
status: | Confirmed → Fix Released |
Hmm. cloud.cfg. d/ that says
You can disable cloud-init writing network config by putting config in /etc/cloud/
network:
config: disabled
However, that will entirely disable cloud init writing networking information that the data source provided it with.
Currently that is openstack config drive or NoCloud.
But in the future it will be other sources. Basically, the cloud can provide the intended networking to the instance, and the instance should apply it.
2 options I can think of are
1 adding function for cloud-init to not write 'fallback' networking config but still write carapace provided config
2 having cloud init read and render the snappy provided config