On Tue, May 9, 2017 at 11:23 AM, Steve Langasek < steve.langa...@canonical.com> wrote:
> Hi Ryan, > > On Tue, May 09, 2017 at 02:20:17PM -0000, Dimitri John Ledkov wrote: > > > <rharper> it does create the yaml and call generate, but it's not > > sufficient to create the symlink IIRC due to the code in netplan which > > doesn't generate the symlinks in /run if it;s not invoked as a genartor > > There is no bug report at https://bugs.launchpad.net/ubuntu/+source/nplan > for this. Is there one on cloud-init? > I did not file a bug against netplan for that; it's not clear to me that it's a bug in netplan, but I can and we can discuss the "late" cloud-init call to netplan generate for the netplan rendere. > > > <rharper> I've picked this apart too many times; we've got the set of > > changes needed documented and staged for ubuntu-core > > Where are these staged? > https://github.com/snapcore/core/pull/30 https://github.com/snapcore/core-build/pull/5 https://github.com/raharper/snapd/commit/3e83b3aa281f02bce9a230a812ad4f02d0d66c22 > > > <rharper> but it's not landed in xenial for cloud-init proper due to not > > wanting to foist networkd onto xenial users at this time > > I don't understand this. Why would any of these staged changes not be > conditional on use of nplan, thus avoiding any "foisting"? > Maybe we can; I don't think we can change the default network renderer in Xenial by default, that has upgrade implications; I don't think we want to switch existing users over to netplan by an upgrade to cloud-init. I'm hesitant to say apt-get install nplan implies that you want cloud-init to use netplan to rendering things as well. So what remains is some unit changes (ensure that network-online.target depends on systemd-networkd-wait-online.service) and cloud-config change (cloud-init's network renderer should be netplan over eni). How would those changes get introduced when a user wants to try netplan on xenial? > > -- > Steve Langasek Give me a lever long enough and a Free OS > Debian Developer to set it on, and I can move the world. > Ubuntu Developer http://www.debian.org/ > slanga...@ubuntu.com vor...@debian.org > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1689410 > > Title: > nplan with networkd + resolvconf without resolved, results in no DNS > resolution > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1689 > 410/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ifupdown in Ubuntu. https://bugs.launchpad.net/bugs/1689410 Title: nplan with networkd + resolvconf without resolved, results in no DNS resolution Status in ifupdown package in Ubuntu: Invalid Status in nplan package in Ubuntu: Invalid Status in resolvconf package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Incomplete Bug description: if nplan yaml specifies nameservers which are passed onto networkd, they will never take effect on systems that do not use systemd- resolved. This is because there is no integration between nplan and resolvconf, either directly; via networkd; via NetworkManager. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1689410/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
