Server networking should be updated for systemd-networkd

Will look at updating:
https://help.ubuntu.com/lts/serverguide/network-configuration.html

@Doug - can we publish these fixes as the other bug I was working on (bug 1772514) is blocked by development work still.

@Josh: O.K. what I'll do it not bother with a translation delay, for now. Once the other one is done we'll do a full translation update delay (say 2 weeks after the MP is merged).

That works for me! Thank you!

There is an error in the bridging section. The config file needs to
include a definition for the adapter. Formatting may not look great in
email but the config file should look like this:

network:
  version: 2
  renderer: networkd
  ethernets:
    enp3s0:
      dhcp4: no
  bridges:
    br0:
      dhcp4: yes
      interfaces:
        - enp3s0

Also the usage of true/false and yes/no should probably stay consistent in
the documentation. The default config file has "dhcp4: yes" so my vote
would be stick with "yes" and "no" in the documentation. However the
documentation mostly uses "true" or "false" but has "dhcp4: yes" in the
bridging section. I think should either change that to "dhcp4: true" to
keep the documentation consistent, or switch all the documentation to using
"yes" and "no" to stay consistent with the default config file.

On Tue, Jun 5, 2018 at 9:09 AM, Doug Smythies <email address hidden>
wrote:

> ** Changed in: serverguide
> Status: Fix Committed => Fix Released
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1769007
>
> Title:
> Server networking should be updated for systemd-networkd
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/serverguide/+bug/1769007/+subscriptions
>

@Brazen: I confirm that bridging does not work as currently written. Furthermore, I confirm that it does work as you wrote.

While you have a good point with yes, no, true, false consistency, myself, I'll not deal with it at this time.

@Josh and/or David Britton: I'll do the edits and re-publication, if you're O.K. with the text the way it Brazen wrote it.

For dynamic and static IP address assignment, I do not understand why we say to create 99_config.yaml. Why not just edit the existing 01-netcfg.yaml file? Anyway, I edited, rather than create a new file.

@Brazen: Thanks for bringing this up and proposing a fix.

re: yes/no or true/false, being more consistent would be nice, something that we should update on the netplan.io examples too, but can be fixed in a different bug.

@Doug: That file is not always present so I did not want to hardcode it. If you boot on a cloud instance you will instead have 50-cloud-init.yaml and if you originally had a system that was installed based on network manager: 01-network-manager-all.yaml

I'm good with the edit and re-publication.