proxy
proxy copied to clipboard
clearcontainers
Hypervisor based containers proxy
From #196, we started getting k8s issues. cc-runtime start gets hanged: ``` fuentess@k8s-latest:~/go/src/github.com/clearcontainers/tests/integration/kubernetes$ ps -ef | grep cc- root 26106 1 0 15:29 ? 00:00:03 /usr/bin/dockerd -D --add-runtime cc-runtime=/usr/local/bin/cc-runtime --default-runtime=cc-runtime...
Last revendoring make K8s stop working because cc-runtime gets hanged starting pods. Will open another issue with more details.
## Definition [Kernel Same-page Merging](https://www.kernel.org/doc/Documentation/vm/ksm.txt) (KSM) throttling is the process of regulating the KSM daemon by dynamically modifying the KSM sysfs entries, in order to minimize memory duplication as fast...
Now that the proxy can be run on a per pod/VM basis rather than as a host-level daemon service, we don't need socket activation or KSM. See https://github.com/clearcontainers/runtime/issues/795 which covers...
Introduce the high availability feature of cc-proxy by implementing store/restore of proxy's state to/from disk. This feature depends on the ability of shim to reconnect to cc-proxy if connection is...
The proxy is the only component running on the host for all the containers/VM that are started. This is an issue since a crash would lead to the lost of...
_From @sameo on December 2, 2016 17:36_ If cc-proxy crashes: 1. all cc-shim instances terminate. 2. cc-proxy will not be able to restore its internal state after restarting. We need...
update the diagram: it shows hyperstart instead of cc-agent
