mirror of
https://github.com/LCTT/TranslateProject.git
synced 2025-01-25 23:11:02 +08:00
translated
This commit is contained in:
rieonke
parent
bd52ac07df
commit
0f19f709d1
@ -1,91 +0,0 @@
|
||||
> translating by rieon
|
||||
|
||||
DEMYSTIFYING THE OPEN CONTAINER INITIATIVE (OCI) SPECIFICATIONS
|
||||
============================================================
|
||||
|
||||
|
||||
The Open Container Initiative (OCI) announced the completion of the first versions of the container runtime and image specifications this week. The OCI is an effort under the auspices of the Linux Foundation to develop specifications and standards to support container solutions. A lot of effort has gone into the [building of these specifications][12] over the past two years. With that in mind, let’s take a look at some of the myths that have arisen over the past two years.
|
||||
|
||||
|
||||
|
||||
Myth: The OCI is a replacement for Docker
|
||||
|
||||
Standards are important, but they are far from a complete production platform. Take for example, the World Wide Web. It has evolved over the last 25 years and was built on core dependable standards like TCP/IP, HTTP and HTML. Using TCP/IP as an example, when enterprises coalesced around TCP/IP as a common protocol, it fueled the growth of routers and in particular – Cisco. However, Cisco became a leader in its market by focusing on differentiated features on its routing platform. We believe the parallel exists with the OCI specifications and Docker.
|
||||
|
||||
[Docker is a complete production platform][13] for developing, distributing, securing and orchestrating container-based solutions. The OCI specification is used by Docker, but it represents only about five percent of our code and a small part of the Docker platform concerned with the runtime behavior of a container and the layout of a container image.
|
||||
|
||||
Myth: Products and projects already are certified to the OCI specifications
|
||||
|
||||
The runtime and image specifications have just released as 1.0 this week. However, the OCI certification program is still in development so companies cannot claim compliance, conformance or compatibility until certification is formally rolled out later this year.
|
||||
|
||||
The OCI [certification working group][14] is currently defining the standard so that products and open source projects can demonstrate conformance to the specifications. Standards and specifications are important for engineers implementing solutions, but formal certification is the only way to reassure customers that the technology they are working with is truly conformant to the standard.
|
||||
|
||||
Myth: Docker doesn’t support the OCI specifications work
|
||||
|
||||
Docker has a long history with contributing to the OCI. We developed and donated a majority of the OCI code and have been instrumental in defining the OCI runtime and image specifications as maintainers of the project. When the Docker runtime and image format quickly became the de facto standards after being released as open source in 2013, we thought it would be beneficial to donate the code to a neutral governance body to avoid fragmentation and encourage innovation. The goal was to provide a dependable and standardized specification so Docker contributed runc, a simple container runtime, as the basis of the runtime specification work, and later contributed the Docker V2 image specification as the basis for the OCI image specification work.
|
||||
|
||||
Docker developers like Michael Crosby and Stephen Day have been key contributors from the beginning of this work, ensuring Docker’s experience hosting and running billions of container images carries through to the OCI. When the certification working group completes its work, Docker will bring its products through the OCI certification process to demonstrate OCI conformance.
|
||||
|
||||
Myth: The OCI specifications are about Linux containers
|
||||
|
||||
There is a misperception that the OCI is only applicable to Linux container technologies because it is under the aegis of the Linux Foundation. The reality is that although Docker technology started in the Linux world, Docker has been collaborating with Microsoft to bring our container technology, platform and tooling to the world of Windows Server. Additionally, the underlying technology that Docker has donated to the OCI is broadly applicable to multi-architecture environments including Linux, Windows and Solaris and covers x86, ARM and IBM zSeries.
|
||||
|
||||
Myth: Docker was just one of many contributors to the OCI
|
||||
|
||||
The OCI as an organization has a lot of supporting members representing the breadth of the container industry. That said, it has been a small but dedicated group of individual technologists that have contributed the time and technology to the efforts that have produced the initial specifications. Docker was a founding member of the OCI, contributing the initial code base that would form the basis of the runtime specification and later the reference implementation itself. Likewise, Docker contributed the Docker V2 Image specification to act as the basis of the OCI image specification.
|
||||
|
||||
Myth: CRI-O is an OCI project
|
||||
|
||||
CRI-O is an open source project in the Kubernetes incubator in the Cloud Native Computing Foundation (CNCF) – it is not an OCI project. It is based on an earlier version of the Docker architecture, whereas containerd is a direct CNCF project that is a larger container runtime that includes the runc reference implementation. containerd is responsible for image transfer and storage, container execution and supervision, and low-level functions to support storage and network attachments. Docker donated containerd to the CNCF with the support of the five largest cloud providers: Alibaba Cloud, AWS, Google Cloud Platform, IBM Softlayer and Microsoft Azure with a charter of being a core container runtime for multiple container platforms and orchestration systems.
|
||||
|
||||
Myth: The OCI specifications are now complete
|
||||
|
||||
While the release of the runtime and image format specifications is an important milestone, there’s still work to be done. The initial scope of the OCI was to define a narrow specification on which developers could depend for the runtime behavior of a container, preventing fragmentation in the industry, and still allowing innovation in the evolving container domain. This was later expanded to include a container image specification.
|
||||
|
||||
As the working groups complete the first stable specifications for runtime behavior and image format, new work is under consideration. Ideas for future work include distribution and signing. The next most important work for the OCI, however, is delivering on a certification process backed by a test suite now that the first specifications are stable.
|
||||
|
||||
**Learn more about OCI and Open Source at Docker:**
|
||||
|
||||
* Read the blog post about the [OCI Release of v1.0 Runtime and Image Format Specifications][1]
|
||||
|
||||
* Visit the [Open Container Initiative website][2]
|
||||
|
||||
* Visit the [Moby Project website][3]
|
||||
|
||||
* Attend [DockerCon Europe 2017][4]
|
||||
|
||||
* Attend the [Moby Summit LA][5] alongside OSS NA
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
作者简介：
|
||||
|
||||
Stephen is Director, Open Source Programs at Docker. He has been a Director and Distinguished Technologist at Hewlett-Packard Enterprise. He blogs about open source software and business at “Once More Unto The Breach” (http://stephesblog.blogs.com) and opensource.com.
|
||||
|
||||
|
||||
|
||||
-----------------
|
||||
|
||||
via: https://blog.docker.com/2017/07/demystifying-open-container-initiative-oci-specifications/
|
||||
|
||||
作者：[Stephen ][a]
|
||||
译者：[译者ID](https://github.com/译者ID)
|
||||
校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
|
||||
|
||||
[a]:
|
||||
[1]:https://blog.docker.com/2017/07/oci-release-of-v1-0-runtime-and-image-format-specifications
|
||||
[2]:https://www.opencontainers.org/join
|
||||
[3]:http://mobyproject.org/
|
||||
[4]:https://europe-2017.dockercon.com/
|
||||
[5]:https://www.eventbrite.com/e/moby-summit-los-angeles-tickets-35930560273
|
||||
[6]:https://blog.docker.com/author/stephen-walli/
|
||||
[7]:https://blog.docker.com/tag/containerd/
|
||||
[8]:https://blog.docker.com/tag/cri-o/
|
||||
[9]:https://blog.docker.com/tag/linux-containers/
|
||||
[10]:https://blog.docker.com/tag/linux-foundation/
|
||||
[11]:https://blog.docker.com/tag/oci/
|
||||
[12]:https://blog.docker.com/2017/07/oci-release-of-v1-0-runtime-and-image-format-specifications
|
||||
[13]:https://www.docker.com/
|
||||
[14]:https://github.com/opencontainers/certification
|
||||
@ -0,0 +1,88 @@
|
||||
解密开放容器计划（OCI）规范
|
||||
============================================================
|
||||
|
||||
|
||||
开放容器计划（OCI）宣布本周完成容器运行时和镜像的第一版规范。OCI 在是 Linux 基金会支持下的容器解决方案标准化的成果。两年来，为了[建立这些规范][12]已经付出了大量的努力。 考虑到这一点，让我们来看看过去两年来出现的一些误区。
|
||||
|
||||
|
||||
|
||||
误区：OCI 是 Docker 的替代品
|
||||
|
||||
诚然标准非常重要，但它们远非一个完整的生产平台。 以万维网为例，它25年来一路演进，建立在诸如 TCP/IP ，HTTP 和 HTML 等核心可靠的标准之上。再以 TCP/IP 为例，当企业将 TCP/IP 合并为一种通用协议时，它推动了路由器行业，尤其是思科的发展。 然而，思科通过专注于在其路由平台上提供差异化的功能，而成为市场的领导者。我们认为 OCI 规范和 Docker 也是类似这样并行存在的。
|
||||
|
||||
[Docker 是一个完整的生产平台][13]，提供了基于容器的开发、分发、安全、编排的一体化解决方案。Docker 使用了 OCI 规范，但它大约只占总代码的 5％，而且 Docker 平台只有一小部分涉及容器的运行时行为和容器镜像的布局。
|
||||
|
||||
误区：产品和项目已经通过了 OCI 规范认证
|
||||
|
||||
运行时和镜像规范本周刚发布1.0的版本。 而且 OCI 认证计划仍在开发阶段，所以企业在认证正式推出之前（今年晚些时候），没法要求容器产品的合规性，一致性或兼容性。
|
||||
|
||||
OCI [认证工作组][14] 目前正在制定标准，使容器产品和开源项目能够符合规范的要求。标准和规范对于实施解决方案的工程师很重要，但正式认证是向客户保证其正在使用的技术真正符合标准的唯一方式。
|
||||
|
||||
误区：Docker不支持 OCI 规范的工作
|
||||
|
||||
Docker 很早就开始为 OCI 做出贡献。 我们向 OCI 贡献了大部分的代码，作为 OCI 项目的维护者，为OCI运行时和镜像规范定义提供了积极的帮助。当 Docker 运行时和镜像格式在 2013 年开源发布之后，迅速成为事实上的标准，我们认为将代码捐赠给中立的管理机构，对于避免容器行业的碎片化和鼓励行业创新将是有益的。我们的目标是提供一个可靠和标准化的规范，因此 Docker 提供了一个简单的容器运行时 runc 作为运行时规范工作的基础，后来提供了 Docker V2 镜像规范作为 OCI 镜像规范工作的基础。
|
||||
|
||||
Docker 的开发人员如 Michael Crosby 和 Stephen Day 从一开始就是这项工作的关键贡献者，确保能将 Docker 的托管和运行数十亿个容器镜像的经验带给 OCI。 等认证工作组完成（制定认证规范的）工作后，Docker将通过OCI认证过程将其产品展示出来，以证明OCI的一致性。
|
||||
|
||||
误区：OCI 仅用于 Linux 容器技术
|
||||
|
||||
因为 OCI 是由 Linux 基金会 （Linux Foundation） 由负责制定的，所以很容易让人误解为，OCI 仅适用于 Linux 容器技术。 而实际上并非如此，尽管 Docker 技术始于 Linux 世界，但 Docker 也一直在与微软合作，将我们的容器技术，平台和工具带入 Windows Server 的世界。 此外，Docker 向 OCI 捐赠的基础技术广泛适用于包括 Linux ，Windows 和 Solaris 在内的多种操作系统环境，涵盖了 x86，ARM 和 IBM zSeries 等多种架构环境。
|
||||
|
||||
误区：Docker只是OCI的众多贡献者之一
|
||||
|
||||
OCI 作为一个组织有很多支持成员，代表了容器行业的广度。 也就是说，它是一个小而专业的个人技术专家组，为制作初始规范的工作贡献了大量的时间和技术。 Docker 是 OCI 的创始成员，贡献了初始代码库，构成了运行时规范的基础，后来引入了参考实现。 同样地，Docker 也将 Docker V2 镜像规范贡献给 OCI 作为镜像规范的基础。
|
||||
|
||||
误区：CRI-O 是 OCI 项目
|
||||
|
||||
CRI-O 是云计算基金会（CNCF）Kubernetes 孵化器的开源项目 -- 它不是 OCI 项目。 它基于早期版本的 Docker 体系结构，而 containerd 是一个直接的 CNCF 项目，它是一个包括 runc 参考实现的更大的容器运行时。 containerd 负责镜像传输和存储，容器运行和监控，以及支持存储和网络附件的底层功能。 Docker 在五个最大的云提供商（阿里云，AWS，Google Cloud Platform （GCP），IBM Softlayer 和 Microsoft Azure）的支持下，将 containerd 捐赠给了云计算基金会（CNCF），作为多个容器平台和编排系统的核心容器运行时。
|
||||
|
||||
规格：OCI 规范现在已经完成了
|
||||
|
||||
虽然首版运行时和镜像格式规范的发布是一个重要的里程碑，但还有许多工作有待完成。 OCI 的一开始着眼于定义一个狭窄的规范：开发人员可以依赖于容器的运行时行为，防止容器行业碎片化，并且仍然允许在不断变化的容器域中进行创新。之后才将含容器镜像规范囊括其中。
|
||||
|
||||
随着工作组完成运行时行为和镜像格式的第一个稳定规范，新的工作考量也已经同步展开。未来的新特性包括分发和签名。 然而，OCI 的下一个最重要的工作是提供一个由测试套件支持的认证过程，因为第一个规范已经稳定了。
|
||||
|
||||
** 在 Docker 了解更多关于 OCI 和开源的信息：**
|
||||
|
||||
* 阅读关于[OCI v1.0 版本的运行时和镜像格式规范]的博文[1]
|
||||
|
||||
* 访问 [OCI 的网站][2]
|
||||
|
||||
* 访问 [Moby 项目网站][3]
|
||||
|
||||
* 参加 [DockerCon Europe 2017][4]
|
||||
|
||||
* 参加 [Moby Summit LA][5]
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
作者简介：
|
||||
|
||||
Stephen 是 Docker 开源项目总监。 他曾在 Hewlett-Packard Enterprise （惠普企业）担任董事和杰出技术专家。 他的关于开源软件和商业的博客“再次违约”（http://stephesblog.blogs.com）和网站 opensource.com。
|
||||
|
||||
|
||||
-----------------
|
||||
|
||||
via: https://blog.docker.com/2017/07/demystifying-open-container-initiative-oci-specifications/
|
||||
|
||||
作者：[Stephen ][a]
|
||||
译者：[rieonke](https://github.com/rieonke)
|
||||
校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
|
||||
|
||||
[a]:
|
||||
[1]:https://blog.docker.com/2017/07/oci-release-of-v1-0-runtime-and-image-format-specifications
|
||||
[2]:https://www.opencontainers.org/join
|
||||
[3]:http://mobyproject.org/
|
||||
[4]:https://europe-2017.dockercon.com/
|
||||
[5]:https://www.eventbrite.com/e/moby-summit-los-angeles-tickets-35930560273
|
||||
[6]:https://blog.docker.com/author/stephen-walli/
|
||||
[7]:https://blog.docker.com/tag/containerd/
|
||||
[8]:https://blog.docker.com/tag/cri-o/
|
||||
[9]:https://blog.docker.com/tag/linux-containers/
|
||||
[10]:https://blog.docker.com/tag/linux-foundation/
|
||||
[11]:https://blog.docker.com/tag/oci/
|
||||
[12]:https://blog.docker.com/2017/07/oci-release-of-v1-0-runtime-and-image-format-specifications
|
||||
[13]:https://www.docker.com/
|
||||
[14]:https://github.com/opencontainers/certification
|
||||
Loading…
Reference in New Issue
Block a user