On 9 May 2017 at 19:05, Ryan Harper <1689...@bugs.launchpad.net> wrote: > On Tue, May 9, 2017 at 11:23 AM, Steve Langasek < > steve.langa...@canonical.com> wrote: > > 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? >
My understanding was that cloud-init does not re-initialise the network for initialized instances, and thus an upgrade to cloud-init and/or installation of nplan will not switch one's existing instance to use nplan. The understanding I had was the idea is to have newly provisioned xenial instances to be nplan managed. -- Regards, Dimitri. -- 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
