summaryrefslogtreecommitdiffstats
path: root/src/nspawn/nspawn-gperf.gperf
diff options
context:
space:
mode:
authorLennart Poettering <lennart@poettering.net>2016-05-06 21:00:27 +0200
committerLennart Poettering <lennart@poettering.net>2016-05-09 15:45:31 +0200
commit22b28dfdc78680a5c03e6af3b0ce6bc96f8174a1 (patch)
treede1324b7d10f1a27d73d5823187d4bcbf981a5ae /src/nspawn/nspawn-gperf.gperf
parentutil-lib: add new ifname_valid() call that validates interface names (diff)
downloadsystemd-22b28dfdc78680a5c03e6af3b0ce6bc96f8174a1.tar.xz
systemd-22b28dfdc78680a5c03e6af3b0ce6bc96f8174a1.zip
nspawn: add new --network-zone= switch for automatically managed bridge devices
This adds a new concept of network "zones", which are little more than bridge devices that are automatically managed by nspawn: when the first container referencing a bridge is started, the bridge device is created, when the last container referencing it is removed the bridge device is removed again. Besides this logic --network-zone= is pretty much identical to --network-bridge=. The usecase for this is to make it easy to run multiple related containers (think MySQL in one and Apache in another) in a common, named virtual Ethernet broadcast zone, that only exists as long as one of them is running, and fully automatically managed otherwise.
Diffstat (limited to 'src/nspawn/nspawn-gperf.gperf')
-rw-r--r--src/nspawn/nspawn-gperf.gperf1
1 files changed, 1 insertions, 0 deletions
diff --git a/src/nspawn/nspawn-gperf.gperf b/src/nspawn/nspawn-gperf.gperf
index 34e1310e29..1d3f0b40bf 100644
--- a/src/nspawn/nspawn-gperf.gperf
+++ b/src/nspawn/nspawn-gperf.gperf
@@ -40,4 +40,5 @@ Network.IPVLAN, config_parse_strv, 0, offsetof(Settings,
Network.VirtualEthernet, config_parse_tristate, 0, offsetof(Settings, network_veth)
Network.VirtualEthernetExtra, config_parse_veth_extra, 0, 0
Network.Bridge, config_parse_string, 0, offsetof(Settings, network_bridge)
+Network.Zone, config_parse_network_zone, 0, 0
Network.Port, config_parse_expose_port, 0, 0