Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Team 5 Translation Doc #40

Closed
wants to merge 1 commit into from
Closed

Team 5 Translation Doc #40

wants to merge 1 commit into from

Conversation

zshi01
Copy link

@zshi01 zshi01 commented Jul 24, 2018

Includes translation for PouchContainer volume Mechanism and fourth paragraph of Design and Realization of PouchContainer CRI from Team 5
fix #24

In fact, all of the above features can be implemented as long as one set of containers share some Linux Namespaces and mount the same volume. Below, we will analyze how the CRI Manager in PouchContainer implements the Pod model by creating a Pod:

1. When Kubelet creating a Pod, the CRI `RunPodSandbox` would be called first. The implementation of the interface by CRI Manager is to create a special container, called "infra container".
From the point of view of the container implementation, it is not special, it is nothing but call the Container Manager and create a normal container with image named `pause-amd64:3.0`. But form the perspective of the whole Pod container group, it has special role, which contributes its own Linux Namespace as Linux shared namespace of the container mentioned above, connecting all containers in the container group. It is more like a carrier that carries all the other containers in the Pod and provides the infrastructure for their operation. In general, we also use an infra container to represent a Pod.

Choose a reason for hiding this comment

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

line 8: it is nothing but call --> it is nothing but calling

@@ -0,0 +1,16 @@
### 4. Realization of Pod Model

In the world of Kubernetes, Pod is the smallest scheduling deployment unit. In brief, a Pod is a container group composed of relavent container. As a whole, these "intimate" containers will share something to make their interaction more efficient. For example, for network, containers within same Pod will share same IP address and port, so that they can access eachother through localhost. For storage, volume defined in Pod will mount to every container, so that every container can access it.

Choose a reason for hiding this comment

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

paragraph 1 : eachother --> each other

@zshi01 zshi01 closed this Jul 24, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[Blog] Add translation doc in English for PouchContainer technology blogs
2 participants