Group 1 add the long passage translation and the short passage translation with the first paragraph #27
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
this is for #24 |
RuiteGuo
reviewed
Jul 24, 2018
|
|
||
| PouchContainer is an efficient, open-source, lightweight Enterprise Rich Container Engine Technology developed by the Alibaba group. This technology presents the characteristics of strong isolation, high portability, and low resource consumption for a container. With the help of PouchContainer, corporations can rapidly deploy their business into containers and improve the utilization of physical resources in their data centers under hyperscale at the same time. | ||
|
|
||
| PouchContainer originates from the thoughts of Alibaba's engineers to the problems they had in their business scenarios. These engineers have dedicated enormous time and efforts in delivering internet applications, which could be proved by the characteristics of the PouchContainer listed above. Thanks to the mass scale of Alibaba, this technology embraced its first opportunity to be fully tested on its ability to support business at Nov 11th after it comes to the world. After declared as an open source project, this new technology is positioned to serve for the public and to help enterprises quickly realize the containerization of their business. |
|
|
||
| Server programming has evolved for decades, and many business system development models are based on the Linux operating system on bare metal or the Linux environment in a virtualized environment. Over time, many business application development paradigms interact with system service processes very frequently. For example, an application written in the Java programming language is likely to configure log management via log4j, or via log4j.properties configuration redirects application logs to syslogd in the running environment. If there is no syslogd running in the application runtime environment, it is very likely to affect the startup and operation of the business; also, business applications need to be managed by crond Periodic tasks. If there is no crond system daemon in the application runtime environment, it is impossible for the business application to configure periodic tasks through crontab. For example, the sshd system service system inside the container can quickly help the operation and maintenance engineers to make rapid progress, locate and solve problems, and so on. | ||
|
|
||
| PouchContainer's rich container model, having taken industry's large number of applications and system service delivery applications into consideration, results in the design of init process inside the rich container armed with the ability to manage multiple system service processes. |
|
|
||
| Eventually, the task process running inside the rich container can ensure that the application runtime is stable and normal. However, for the operation and maintenance team, the content should be maintained is often much morer than that with single process running. In general, the operational responsibilities also need to cover the environmental preparation work before the run-time, and the after-work after the end of running. For applications, this is the prestart hook and poststop hook we usually refer to. | ||
|
|
||
| PouchContainer's rich container mode allows users to easily specify the application's start and stop execution hooks: prestart hook and poststop hook. The operation and maintenance team specifies the prestart hook, which can help the application to perform some initialization operations in the container that meet the operation and maintenance requirements before running, such as: initializing the network routing table, obtaining the application execution permission, and downloading the certificate required for the runtime. The same team specifies the poststop hook, which can help the application to perform unified after-work management after the end of the operation or abnormal exit. For example, the intermediate data is cleaned up for the pure environment at the next startup; if it is abnormally exited, the error can be reported immediately which is able to meet operational requirements. |
There was a problem hiding this comment.
从句不能修饰整个句子， 不能用which 指代整句 “the error can be reported immediately”
zhuorantan
reviewed
Jul 24, 2018
|
|
||
|  | ||
|
|
||
| When it first comes to container technology, Alibaba had an amazing amount of backlogs inside at that time. How to quickly containerize these backlogs is the key problem of this technology when it was first promoted inside the company. Nowadays, the open source container technology is becoming more and more popular. Many companies may still be worrying about how to deal with the same problem. In the cloud native field, many of the advanced concepts promoted by the CNCF Foundation are based on business containerization. If enterprises fall behind this trend, they will be overwhelmed by the follow-up problems brought by container management, let alone enjoying the benefits of open source projects like Service Mesh. |
There was a problem hiding this comment.
According to Oxford dictionary, backlog means "An accumulation of uncompleted work or matters needing to be dealt with". It is not accurate to describe the existing businesses Alibaba has. A better translation could be "legacy businesses"
|
Thanks for your contribution. :) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Comments and thoughts:
From what I see, Alibaba is really dedicating itself to make this world a better place, to solve the current problem including the zombie process, they made a bold move where they create different mode for the init processes. The greatest part is that since this project is open source right now, people from all over the world could contribute to this project and benefit from this. As a large company, what they desire is that they could use their experience to help those small business to make this transition from the bare metal or vms to containers.
I think we could learn from what engineers have been doing for centuries. Since there is always trade offs in an engineering problem, like we trade space for time, trade safety for speed. In this case, could we reduce the granularity, to divide the user cases into smaller cases. Providing start up options for the users to give them a choice based on their requirements?