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

Conversation

@jodh-intel
Copy link

Update the architecture document to reflect the new proxy behaviour
where there is a proxy instance per virtual machine rather than a
single host-level proxy instance.

This should strictly have been handled on #835.

Fixes #908.

Signed-off-by: James O. D. Hunt james.o.hunt@intel.com

@jodh-intel
Copy link
Author

Hi @sameo, @sboeuf, @grahamwhaley - could you take a look?

Note also: clearcontainers/proxy#193.

@clearcontainersbot
Copy link

kubernetes qa-passed 👍

@sboeuf
Copy link
Contributor

sboeuf commented Jan 9, 2018

LGTM

the `cc-agent`.

The `cc-proxy` API is available through a single socket for all `cc-shim` and
to a single `cc-shim` and `cc-runtime` client. Its main role is to route the
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

A single cc-shim?

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good catch! Branch updated.

@jodh-intel jodh-intel force-pushed the arch-doc-one-proxy-per-vm branch from 0d32593 to 8392219 Compare January 9, 2018 10:03
@jodh-intel
Copy link
Author

Hi @klynnrif - please could you my changes [*]?


[*] - If there are other parts of the doc that need altering, let's do that on a separate PR as this doc is a bit of a monster 😄

Copy link
Contributor

@grahamwhaley grahamwhaley left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for picking this up @jodh-intel Minor nits, but generally:
lgtm

6. The `cc-proxy` waits for the agent to signal that it is ready and then returns
5. Spawn the `cc-proxy` process providing a single argument:
`cc-proxy --uri $(uri)`
* A UNIX socket URI, which will be used by the `cc-shim` and `cc-agent` processes will use to pass information between them.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think s/will use// ?

a token. This token uniquely identifies a process within a container inside
the virtual machine.
7. Spawn the `cc-shim` process providing two arguments:
8. Spawn the `cc-shim` process providing two arguments:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Was surprised you did not change these all to (1.) items whilst here @jodh-intel:-)

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I considered it, but then decided to go for a minimal change "in line" with the current content to minimise the review cycle time ;)

4. `cc-runtime` sends an agent `EXECMD` command to start the command in the
right container. The command is sent to `cc-proxy` who forwards it to the right
agent instance running in the appropriate guest.
container. The command is sent to `cc-proxy` who forwards it to the
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

s/who/which/

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

However, branch updated 😄

@clearcontainersbot
Copy link

kubernetes qa-passed 👍

@jodh-intel jodh-intel force-pushed the arch-doc-one-proxy-per-vm branch from 8392219 to 87221dd Compare January 9, 2018 10:52
@clearcontainersbot
Copy link

kubernetes qa-passed 👍

Copy link

@klynnrif klynnrif left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

A couple suggested rewrites - @jodh-intel I believe I only commented on your changes this time :) Thanks!

6. The `cc-proxy` waits for the agent to signal that it is ready and then returns
5. Spawn the `cc-proxy` process providing a single argument:
`cc-proxy --uri $(uri)`
* A UNIX socket URI, which will be used by the `cc-shim` and `cc-agent` processes will use to pass information between them.
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Agree with @grahamwhaley here, to keep this active - suggested rewrite that may need adjusted for meaning: A UNIX socket URI used by the cc-shim and cc-agent processes is used to pass information between them.

4. `cc-runtime` sends an agent `EXECMD` command to start the command in the
right container. The command is sent to `cc-proxy` who forwards it to the right
agent instance running in the appropriate guest.
container. The command is sent to `cc-proxy` who forwards it to the
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested rewrite: the command is sent to cc-proxy, which forwards it to the

that the virtual machine that used to host the pod should no longer be used.
5. `cc-runtime` explicitly shuts the virtual machine down.
6. The host namespaces are cleaned up and destroyed. In particular, `cc-runtime`
5. The `cc-proxy` instance will then exit.
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The cc-proxy instance exits.

5. `cc-runtime` explicitly shuts the virtual machine down.
6. The host namespaces are cleaned up and destroyed. In particular, `cc-runtime`
5. The `cc-proxy` instance will then exit.
6. `cc-runtime` explicitly shuts the virtual machine down.
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

cc-runtime shuts the virtual machine down.

offloads the networking namespace cleanup path by calling into the specific
networking model (CNM or CNI) removal method.
7. All remaining pod related resources on the host are deleted.
8. All remaining pod related resources on the host are deleted.
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

All remaining pod-related resources...

Update the architecture document to reflect the new proxy behaviour
where there is a proxy instance per virtual machine rather than a
single host-level proxy instance.

This should strictly have been handled on clearcontainers#835.

Fixes clearcontainers#908.

Signed-off-by: James O. D. Hunt <james.o.hunt@intel.com>
@jodh-intel jodh-intel force-pushed the arch-doc-one-proxy-per-vm branch from 87221dd to 8062cb9 Compare January 10, 2018 08:37
@jodh-intel
Copy link
Author

Hi @klynnrif - thanks for reviewing - branch updated.

@clearcontainersbot
Copy link

kubernetes qa-passed 👍

@jodh-intel jodh-intel merged commit 8ababd7 into clearcontainers:master Jan 10, 2018
mcastelino pushed a commit to mcastelino/runtime that referenced this pull request Dec 6, 2018
…atFs

build: introduction of archConvertStatFs function
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants