Ubuntu
systemd package

FFE: integrate networkd with /etc/network/if-*.d/ scripts

Bug #1492129 reported by Martin Pitt
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
systemd (Ubuntu)
Fix Released
Wishlist
Martin Pitt

Bug Description

In https://blueprints.launchpad.net/ubuntu/+spec/foundations-w-networkd-vs-ifupdown we want to provide networkd as a viable option for Ubuntu, in particular server/cloud land. This requires some integration with existing packages, in particular calling the /etc/network/if-up.d/ and if-post-down.d/ scripts, similar to what NetworkManager does.

I would like to land this in wily still, so that people can experiment it and we still have some time to tweak it for 16.04 LTS:

    http://anonscm.debian.org/cgit/pkg-systemd/systemd.git/commit/?id=27f7cc9f9f32

As we don't currently use (or even advertise) networkd in Ubuntu, the risk of this is very low IMHO. The main regression risk is if that would somehow influence/break interfaces managed by ifupdown or NetworkManager, but the above changes test if the interface is managed by networkd.

We also want to provide integration with "resolvconf". This does not exist yet, but an FFE for this might come for wily as well.

See original description
Martin Pitt (pitti)
Changed in systemd (Ubuntu):
importance: Undecided → Wishlist
description: updated
summary: - FFE: integrate networkd with /etc/network/if-*.d/ scripts
+ FFE: integrate networkd with /etc/network/if-*.d/ scripts and resolvconf
Revision history for this message
Launchpad Janitor (janitor) wrote : Re: FFE: integrate networkd with /etc/network/if-*.d/ scripts and resolvconf

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in systemd (Ubuntu):
status: New → Confirmed
Martin Pitt (pitti)
description: updated
summary: - FFE: integrate networkd with /etc/network/if-*.d/ scripts and resolvconf
+ FFE: integrate networkd with /etc/network/if-*.d/ scripts
Revision history for this message
Iain Lane (laney) wrote :

As long as this is limited to opt-in configurations (ideally get some review to ensure there are no mistakes here; I'm not confident in doing that right myself), go ahead.

Changed in systemd (Ubuntu):
status: Confirmed → Triaged
Martin Pitt (pitti)
Changed in systemd (Ubuntu):
assignee: nobody → Martin Pitt (pitti)
status: Triaged → Fix Committed
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package systemd - 225-1ubuntu3

---------------
systemd (225-1ubuntu3) wily; urgency=medium

  * Enable libseccomp support for mips64, mips64el, and x32. (Closes: #797403)
  * debian/tests/networkd: Add hotplug tests.
  * Make networkd call if-up.d/ scripts when it brings up interfaces, to
    become compatible with ifupdown and NetworkManager for packages shipping
    hooks. (LP: #1492129)
    - Add debian/extra/units/networkd-if-up.d@.service: Wait for a particular
      interface to be up, and call if-up.d/ for it if it is managed by
      networkd. Correspondingly, call if-post-down.d/ scripts when stopping.
    - debian/extra/udev-helpers/net.agent: Start/stop
      networkd-if-up.d@.service when interfaces appear/go away.
    - debian/tests/networkd: Verify that if-up.d/ and if-post-down.d/ scripts
      get run for a networkd managed interface.
    - Note that if-pre-up.d/ and if-down.d/ scripts are *not* being called, as
      they are often not applicable for networkd (if-pre-up.d) and unreliable
      (if-down.d).
  * Drop udev-finish. We needed this for the autogenerated CD and network
    interface names, but both are gone now.
  * Drop debian/udev.udev-fallback-graphics.upstart. The vesafb module has
    been compiled into the kernel in both Debian and Ubuntu for a fair while,
    this never had a systemd equivalent, and Debian never shipped the
    accompanying rules for determining $PRIMARY_DEVICE_FOR_DISPLAY.
  * debian/control: Remove some boilerplate from the long descriptions, to
    more easily get to the point what a specific package actually does.
  * debian/README.Debian: As systemd is the default init now, replace the
    documentation how to switch to systemd with how to switch back
    (temporarily or permanently) to SysV init. Also move that paragraph to the
    bottom as it's now less important.
  * debian/README.Debian: Add a hint why you may want to enable persistent
    journal, and suggest to uninstall system-log-daemon to avoid duplicate
    logging.
  * debian/README.Debian: Add documentation about networkd integration.

 -- Martin Pitt <email address hidden> Wed, 09 Sep 2015 07:56:03 +0200

Changed in systemd (Ubuntu):
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.