Kevin Carter 6285b6c638 Build out the PrivateNetwork function for services ... This change adds the ability to effectively use the PrivateNetwork functionality systemd provides for services. Now, if enabled, services can be created in a network namespace which isolates it from the reset of the host. Additional options have been added allowing access into the network namespace over ephemeral devices as needed. Highlights: * Isolated private networking for services will sandbox using a stand alone namespace which has no access to anything via the network. * Access into a private namespace can be provided over a single network interface which can be IP'd via local DHCP + NAT or using an upstream DHCP server. * Tests have been added to exercise the new functionality. All of the funcality has been documented in the defaults of this role. Change-Id: I6751765131f32393a1605eb2100bec46199d980a Signed-off-by: Kevin Carter <kevin@cloudnull.com>		2019-02-09 04:06:44 +00:00
..
group_vars	Set container_name as host_var in test inventory	2018-10-22 11:09:50 +00:00
host_vars	Initial Commit	2017-05-19 10:24:55 -05:00
ansible-role-requirements.yaml	include built docs	2017-05-22 23:46:39 -05:00
inventory	Initial Commit	2017-05-19 10:24:55 -05:00
systemd_init-overrides.yml	Initial Commit	2017-05-19 10:24:55 -05:00
test.yml	Build out the PrivateNetwork function for services	2019-02-09 04:06:44 +00:00