-
Notifications
You must be signed in to change notification settings - Fork 70
docs: Update arch doc for one proxy / VM #909
docs: Update arch doc for one proxy / VM #909
Conversation
|
Hi @sameo, @sboeuf, @grahamwhaley - could you take a look? Note also: clearcontainers/proxy#193. |
|
kubernetes qa-passed 👍 |
|
LGTM |
docs/architecture/architecture.md
Outdated
| 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 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A single cc-shim?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good catch! Branch updated.
0d32593 to
8392219
Compare
|
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 😄 |
grahamwhaley
left a comment
There was a problem hiding this 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
docs/architecture/architecture.md
Outdated
| 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. |
There was a problem hiding this comment.
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: |
There was a problem hiding this comment.
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:-)
There was a problem hiding this comment.
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 ;)
docs/architecture/architecture.md
Outdated
| 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 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
s/who/which/
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
However, branch updated 😄
|
kubernetes qa-passed 👍 |
8392219 to
87221dd
Compare
|
kubernetes qa-passed 👍 |
klynnrif
left a comment
There was a problem hiding this 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!
docs/architecture/architecture.md
Outdated
| 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. |
There was a problem hiding this comment.
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.
docs/architecture/architecture.md
Outdated
| 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 |
There was a problem hiding this comment.
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
docs/architecture/architecture.md
Outdated
| 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. |
There was a problem hiding this comment.
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.
docs/architecture/architecture.md
Outdated
| 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. |
There was a problem hiding this comment.
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.
docs/architecture/architecture.md
Outdated
| 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. |
There was a problem hiding this comment.
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>
87221dd to
8062cb9
Compare
|
Hi @klynnrif - thanks for reviewing - branch updated. |
|
kubernetes qa-passed 👍 |
…atFs build: introduction of archConvertStatFs function
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