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
> <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?
> <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"?
--
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/
<email address hidden> <email address hidden>
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?
> <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?
> <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"?
-- www.debian. org/
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://
<email address hidden> <email address hidden>