Public bug reported: See [1] for doc on cloud-initramfs-dyn-netconf.
cloud-initramfs-dyn-netconf takes klibc ipconfig output and writes /etc/network/interfaces (ENI) style file in /run/network/dynamic-interfaces. The goal is to have the user's provided 'ip=' kernel parameters be "sticky" and not have the network interface get bounced by normal post-initramfs networking bringup. Essentially kernel command line should override /etc/network/interfaces in a similar way to command line flags overriding environment or system configuration. As it is right now, we have to have ln -sf /etc/network/interfaces /run/network/dynamic-interfaces in order for this to work. That means: a.) if you've not done this, dyn-netconf isn't much use b.) if you *have* done this, but not provided ip= then you'll get you'll get no network configuration. In xenial, the one necessary change from a cloud image to maas image is this symlink, so that the image can work well with networking information being provided on the kernel command line via network boot. -- [1] http://bazaar.launchpad.net/~cloud-initramfs-tools/cloud-initramfs-tools/trunk/view/head:/dyn-netconf/doc/README.txt ** Affects: cloud-initramfs-tools (Ubuntu) Importance: High Status: Confirmed ** Changed in: cloud-initramfs-tools (Ubuntu) Status: New => Confirmed ** Changed in: cloud-initramfs-tools (Ubuntu) Importance: Undecided => High ** Description changed: See [1] for doc on cloud-initramfs-dyn-netconf. cloud-initramfs-dyn-netconf takes klibc ipconfig output and writes /etc/network/interfaces (ENI) style file in /run/network/dynamic-interfaces. The goal is to have the user's provided 'ip=' kernel parameters be "sticky" and not have the network interface get bounced by normal post-initramfs networking bringup. Essentially kernel command line should override /etc/network/interfaces in a similar way to command line flags overriding environment or system configuration. As it is right now, we have to have ln -sf /etc/network/interfaces /run/network/dynamic-interfaces in order for this to work. That means: - a.) if you've not done this, dyn-netconf isn't much use - b.) if you *have* done this, but not provided ip= then you'll get you'll get no network configuration. + a.) if you've not done this, dyn-netconf isn't much use + b.) if you *have* done this, but not provided ip= then you'll get you'll get no network configuration. + + In xenial, the one necessary change from a cloud image to maas image is + this symlink, so that the image can work well with networking + information being provided on the kernel command line via network boot. -- [1] http://bazaar.launchpad.net/~cloud-initramfs-tools/cloud-initramfs-tools/trunk/view/head:/dyn-netconf/doc/README.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1534205 Title: cloud-initramfs-dyn-netconf should work without /etc/network/interfaces symlink To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-initramfs-tools/+bug/1534205/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
