Anil Madhavapeddy 2da4aefb37 projects/miragesdk: add a frontend yaml format for dhcp-client ... The intention with the yaml fragment is that it specifies the set of processes that form the daemon, with minimal privileges for each component and each running inside a separate container. In addition to the normal container capabilities, there is also a new field which lets a startup process establish an RPC channel, based on a Capnp specification. This allows for extremely unprivileged components to be started, such as the `dhcp-engine` in this example which can only communicate with the outside world via the `dhcp-network` (to transmit) or `dhcp-actuator` (to alter the state of the local Linux distribution). This is a first cut at the yaml interface and the capnp, with the intention to refine it as we combine it with the rest of the existing prototype (which currently doesnt have an RPC layer). Expect more changes... Signed-off-by: Anil Madhavapeddy <anil@docker.com>		2017-06-05 16:49:54 +01:00
..
dhcp-client.yml	projects/miragesdk: add a frontend yaml format for dhcp-client	2017-06-05 16:49:54 +01:00
dhcp.capnp	projects/miragesdk: add a frontend yaml format for dhcp-client	2017-06-05 16:49:54 +01:00