diff options
author | Lennart Poettering <lennart@poettering.net> | 2016-05-06 21:00:27 +0200 |
---|---|---|
committer | Lennart Poettering <lennart@poettering.net> | 2016-05-09 15:45:31 +0200 |
commit | 22b28dfdc78680a5c03e6af3b0ce6bc96f8174a1 (patch) | |
tree | de1324b7d10f1a27d73d5823187d4bcbf981a5ae /shell-completion | |
parent | ef76dff225a00008fe0edd1f528c9096f1a91179 (diff) |
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 'shell-completion')
0 files changed, 0 insertions, 0 deletions