cloud-images /etc/network/interfaces shoud source-directory interfaces.d
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| | cloud-images |
Medium
|
Ben Howard | ||
Bug Description
A cloud image /etc/network/
| # This file describes the network interfaces available on your system
| # and how to activate them. For more information, see interfaces(5).
|
| # The loopback network interface
| auto lo
| iface lo inet loopback
|
| # The primary network interface
| auto eth0
| iface eth0 inet dhcp
A better version might be:
| # interfaces(5) file used by ifup(8) and ifdown(8)
| # Include files from /etc/network/
| source-directory /etc/network/
|
| # The loopback network interface
| auto lo
|
| iface lo inet loopback
| auto eth0
We could possibly put 'eth0' inside /etc/network/
that might make it easier to remove/replace.
| Changed in ubuntu: | |
| milestone: | none → ubuntu-14.01 |
| Scott Moser (smoser) wrote : | #1 |
| Stéphane Graber (stgraber) wrote : | #2 |
So the blurb that ifupdown puts in /etc/network/
"""
# interfaces(5) file used by ifup(8) and ifdown(8)
# Include files from /etc/network/
source-directory /etc/network/
"""
The loopback interface entry is no longer required as it's assumed to always be present by ifupdown.
There isn't any naming convention for files under /etc/network/
Should you have to do any kind of migration, I'd suggest doing:
- Move /etc/network/
- Rewrite /etc/network/
- Add any new /etc/network/
| Ben Howard (utlemming) wrote : | #3 |
Moved eth0 configuration to /etc/network/
Marking fix commited pending builds through the Cloud Image build system.
| Changed in ubuntu: | |
| status: | Triaged → Fix Committed |
| Changed in ubuntu: | |
| status: | Fix Committed → Fix Released |
| Martin Pitt (pitti) wrote : | #4 |
This is incompatible with what Debian's ifupdown does: "source-directory /etc/network/
| affects: | ubuntu → cloud-images |
| Changed in cloud-images: | |
| milestone: | ubuntu-14.01 → none |


So, some thoughts on this that I'd like to get some feedback on (slangasek or stgraber).
a.) Should we put 'eth0' configuration into /etc/network/ interfaces. d?
my feeling is that we should. This is possible to cause some breakage, but its fine with me to have to fix things. I'd just rather do it earlier than later in case there is fallout.
b.) what should we name that file? Would convention be 'eth0' ?