Skip to content
This repository has been archived by the owner on May 6, 2020. It is now read-only.

Remove socket activation & KSM features #176

Open
jodh-intel opened this issue Nov 30, 2017 · 0 comments
Open

Remove socket activation & KSM features #176

jodh-intel opened this issue Nov 30, 2017 · 0 comments
Assignees

Comments

@jodh-intel
Copy link
Contributor

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 clearcontainers/runtime#795 which covers what the KSM functionality in the proxy will be replaced by.

@jodh-intel jodh-intel self-assigned this Nov 30, 2017
jodh-intel added a commit to jodh-intel/proxy that referenced this issue Nov 30, 2017
The proxy should not (cannot) handle KSM now that an instance is being
launched per pod.

Partially fixes clearcontainers#176.

Signed-off-by: James O. D. Hunt <james.o.hunt@intel.com>
jodh-intel added a commit to jodh-intel/proxy that referenced this issue Nov 30, 2017
Socket activation is no longer required since a proxy instance
is launched by the runtime for each pod.

Fixes clearcontainers#176.

Signed-off-by: James O. D. Hunt <james.o.hunt@intel.com>
jodh-intel added a commit to jodh-intel/proxy that referenced this issue Dec 14, 2017
The proxy should not (cannot) handle KSM now that an instance is being
launched per pod.

Partially fixes clearcontainers#176.

Signed-off-by: James O. D. Hunt <james.o.hunt@intel.com>
jodh-intel added a commit to jodh-intel/proxy that referenced this issue Dec 14, 2017
Socket activation is no longer required since a proxy instance
is launched by the runtime for each pod.

Fixes clearcontainers#176.

Signed-off-by: James O. D. Hunt <james.o.hunt@intel.com>
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant