summaryrefslogtreecommitdiff
path: root/NEWS
diff options
context:
space:
mode:
authorLennart Poettering <lennart@poettering.net>2016-05-16 22:18:39 +0200
committerLennart Poettering <lennart@poettering.net>2016-05-16 22:18:39 +0200
commit25b0e6cb99c2a13c8f1ae9c5057f6941b722e764 (patch)
tree39e9dcb9a2fb7c2795e16f7be125f8ccf213c0a2 /NEWS
parent3103459e9083555d1b52fb6a212a5c6ad1f98b95 (diff)
update TODO
Diffstat (limited to 'NEWS')
-rw-r--r--NEWS17
1 files changed, 16 insertions, 1 deletions
diff --git a/NEWS b/NEWS
index b3e51877c9..6469074549 100644
--- a/NEWS
+++ b/NEWS
@@ -53,7 +53,9 @@ CHANGES WITH 230 in spe:
* The unified cgroup hierarchy added in Linux 4.5 is now supported.
Use systemd.unified_cgroup_hierarchy=1 on the kernel command line to
- enable.
+ enable. Also, support for the "io" cgroup controller in the unified
+ hierarchy has been added, so that the "memory", "pids" and "io" are
+ now the controllers that are supported on the unified hierarchy.
WARNING: it is not possible to use previous systemd versions with
systemd.unified_cgroup_hierarchy=1 and the new kernel. Therefore it
@@ -142,6 +144,19 @@ CHANGES WITH 230 in spe:
deployable. The systemd-nspaw@.service template unit file has been
changed to use this functionality by default.
+ * systemd-nspawn gained a new --network-zone= switch, that allows
+ creating ad-hoc virtual Ethernet links between multiple containers,
+ that only exist as long as at least one container referencing them is
+ running. This allows easy connecting of multiple containers with a
+ common link that implements an Ethernet broadcast domain. Each of
+ these network "zones" may be named relatively freely by the user, and
+ may be referenced by any number of containers, but each container may
+ only reference one of these "zones". On the lower level, this is
+ implemented by an automatically managed bridge network interface for
+ each zone, that is created when the first container referencing its
+ zone is created and removed when the last one referencing its zone
+ terminates.
+
* The default start timeout may now be configured on the kernel command
line via systemd.default_timeout_start_sec=. It was already
configurable via the DefaultTimeoutStartSec= option in