Merge pull request #25698 from Sophy417/patch-42
Create 2016-02-00-State-Of-Container-World-January-2016.mdpull/25719/head
Kubernetes Prow Robot
GitHub
commit
c0b0d77248
|
|
@ -0,0 +1,148 @@
|
|||
---
|
||||
title: " 容器世界现状，2016年1月 "
|
||||
date: 2016-02-01
|
||||
slug: state-of-container-world-january-2016
|
||||
url: /blog/2016/02/State-Of-Container-World-January-2016
|
||||
---
|
||||
<!--
|
||||
---
|
||||
title: " State of the Container World, January 2016 "
|
||||
date: 2016-02-01
|
||||
slug: state-of-container-world-january-2016
|
||||
url: /blog/2016/02/State-Of-Container-World-January-2016
|
||||
---
|
||||
-->
|
||||
<!--
|
||||
At the start of the new year, we sent out a survey to gauge the state of the container world. We’re ready to send the [February edition](https://docs.google.com/forms/d/13yxxBqb5igUhwrrnDExLzZPjREiCnSs-AH-y4SSZ-5c/viewform), but before we do, let’s take a look at the January data from the 119 responses (thank you for participating!).
|
||||
-->
|
||||
新年伊始，我们进行了一项调查，以评估容器世界的现状。
|
||||
我们已经准备好发送[ 2 月版](https://docs.google.com/forms/d/13yxxBqb5igUhwrrnDExLzZPjREiCnSs-AH-y4SSZ-5c/viewform)但在此之前，让我们从 119 条回复中看一下 1 月的数据（感谢您的参与！）。
|
||||
|
||||
<!--
|
||||
A note about these numbers: First, you may notice that the numbers don’t add up to 100%, the choices were not exclusive in most cases and so percentages given are the percentage of all respondents who selected a particular choice. Second, while we attempted to reach a broad cross-section of the cloud community, the survey was initially sent out via Twitter to followers of [@brendandburns](https://twitter.com/brendandburns), [@kelseyhightower](https://twitter.com/kelseyhightower), [@sarahnovotny](https://twitter.com/sarahnovotny), [@juliaferraioli](https://twitter.com/juliaferraioli), [@thagomizer\_rb](https://twitter.com/thagomizer_rb), so the audience is likely not a perfect cross-section. We’re working to broaden our sample size (have I mentioned our February survey? [Come take it now](https://docs.google.com/forms/d/13yxxBqb5igUhwrrnDExLzZPjREiCnSs-AH-y4SSZ-5c/viewform)).
|
||||
-->
|
||||
关于这些数字的注释：
|
||||
首先，您可能会注意到，这些数字加起来并不是 100％，在大多数情况下，选择不是唯一的，因此给出的百分比是选择特定选择的所有受访者的百分比。
|
||||
其次，虽然我们尝试覆盖广泛的云社区，但调查最初是通过 Twitter 发送给[@brendandburns](https://twitter.com/brendandburns)，[@kelseyhightower](https://twitter.com/kelseyhightower)，[@sarahnovotny](https://twitter.com/sarahnovotny)，[@juliaferraioli](https://twitter.com/juliaferraioli)，[@thagomizer\_rb](https://twitter.com/thagomizer_rb)，因此受众覆盖可能并不完美。
|
||||
我们正在努力扩大样本数量（我是否提到过2月份的调查？[点击立即参加](https://docs.google.com/forms/d/13yxxBqb5igUhwrrnDExLzZPjREiCnSs-AH-y4SSZ-5c/viewform))。
|
||||
|
||||
<!--
|
||||
#### Now, without further ado, the data:
|
||||
-->
|
||||
#### 言归正传，来谈谈数据：
|
||||
<!--
|
||||
First off, lots of you are using containers! 71% are currently using containers, while 24% of you are considering using them soon. Obviously this indicates a somewhat biased sample set. Numbers for container usage in the broader community vary, but are definitely lower than 71%. Consequently, take all of the rest of these numbers with a grain of salt.
|
||||
-->
|
||||
首先，很多人正在使用容器！目前有 71％ 的人正在使用容器，而其中有 24％ 的人正在考虑尽快使用它们。
|
||||
显然，这表明样本集有些偏颇。
|
||||
在更广泛的社区中，容器使用的数量有所不同，但绝对低于 71％。
|
||||
因此，对这些数字的其余部分要持怀疑态度。
|
||||
|
||||
<!--
|
||||
So what are folks using containers for? More than 80% of respondents are using containers for development, while only 50% are using containers for production. But you plan to move to production soon, as 78% of container users said that you were planning on moving to production sometime soon.
|
||||
-->
|
||||
那么人们在使用容器做什么呢？
|
||||
超过 80％ 的受访者使用容器进行开发，但只有 50％ 的人在生产环境下使用容器。
|
||||
但是他们有计划很快投入到生产环境之中，78% 的容器用户表示了意愿。
|
||||
|
||||
<!--
|
||||
Where do you deploy containers? Your laptop was the clear winner here, with 53% of folks deploying to laptops. Next up was 44% of people running on their own VMs (Vagrant? OpenStack? we’ll try dive into this in the February survey), followed by 33% of folks running on physical infrastructure, and 31% on public cloud VMs.
|
||||
-->
|
||||
你们在哪里部署容器？
|
||||
你的笔记本电脑显然是赢家，53% 的人使用笔记本电脑。
|
||||
接下来是 44％ 的人在自己的 VM 上运行（Vagrant？OpenStack？我们将在2月的调查中尝试深入研究），然后是 33％ 的人在物理基础架构上运行，而 31％ 的人在公共云 VM 上运行。
|
||||
|
||||
<!--
|
||||
And how are you deploying containers? 54% of you are using Kubernetes, awesome to see, though likely somewhat biased by the sample set (see the notes above), possibly more surprising, 45% of you are using shell scripts. Is it because of the extensive (and awesome) Bash scripting going on in the Kubernetes repository? Go on, you can tell me the truth… Rounding out the numbers, 25% are using CAPS (Chef/Ansible/Puppet/Salt) systems, and roughly 13% are using Docker Swarm, Mesos or other systems.
|
||||
-->
|
||||
如何部署容器？
|
||||
你们当中有 54% 的人使用 Kubernetes，虽然看起来有点受样本集的偏见（请参阅上面的注释），但真是令人惊讶，但有 45％ 的人在使用 shell 脚本。
|
||||
是因为 Kubernetes 存储库中正在运行大量（且很好）的 Bash 脚本吗？
|
||||
继续下去，我们可以看到真相……
|
||||
数据显示，25% 使用 CAPS (Chef/Ansible/Puppet/Salt)系统，约 13% 使用 Docker Swarm、Mesos 或其他系统。
|
||||
|
||||
<!--
|
||||
Finally, we asked people for free-text answers about the challenges of working with containers. Some of the most interesting answers are grouped and reproduced here:
|
||||
-->
|
||||
最后，我们让人们自由回答使用容器的挑战。
|
||||
这儿有一些进行了分组和复制的最有趣的答案：
|
||||
|
||||
<!--
|
||||
###### Development Complexity
|
||||
-->
|
||||
###### 开发复杂性
|
||||
|
||||
<!--
|
||||
- “Silo'd development environments / workflows can be fragmented, ease of access to tools like logs is available when debugging containers but not intuitive at times, massive amounts of knowledge is required to grasp the whole infrastructure stack and best practices from say deploying / updating kubernetes, to underlying networking etc.”
|
||||
- “Migrating developer workflow. People uninitiated with containers, volumes, etc just want to work.”
|
||||
-->
|
||||
- “孤立的开发环境/工作流程可能是零散的，调试容器时可以轻松访问日志等工具，但有时却不太直观，需要大量知识来掌握整个基础架构堆栈和部署/ 更新 kubernetes，到底层网络等。”
|
||||
- “迁移开发者的工作流程。 那些不熟悉容器、卷等的人只是想工作。”
|
||||
|
||||
<!--
|
||||
###### Security
|
||||
-->
|
||||
###### 安全
|
||||
|
||||
<!--
|
||||
- “Network Security”
|
||||
- “Secrets”
|
||||
-->
|
||||
- “网络安全”
|
||||
- “Secrets”
|
||||
|
||||
<!--
|
||||
###### Immaturity
|
||||
-->
|
||||
###### 不成熟
|
||||
|
||||
<!--
|
||||
- “Lack of a comprehensive non-proprietary standard (i.e. non-Docker) like e.g runC / OCI”
|
||||
- “Still early stage with few tools and many missing features.”
|
||||
- “Poor CI support, a lot of tooling still in very early days.”
|
||||
- "We've never done it that way before."
|
||||
-->
|
||||
- “缺乏全面的非专有标准（例如，非 Docker），例如 runC / OCI”
|
||||
- “仍处于早期阶段，只有很少的工具和许多缺少的功能。”
|
||||
- “糟糕的 CI 支持，很多工具仍然处于非常早期的阶段。”
|
||||
- "我们以前从未那样做过。"
|
||||
|
||||
<!--
|
||||
###### Complexity
|
||||
-->
|
||||
###### 复杂性
|
||||
|
||||
<!--
|
||||
- “Networking support, providing ip per pod on bare metal for kubernetes”
|
||||
- “Clustering is still too hard”
|
||||
- “Setting up Mesos and Kubernetes too damn complicated!!”
|
||||
-->
|
||||
- “网络支持， 为 kubernetes 在裸机上为每个 Pod 提供 IP”
|
||||
- “集群化还是太难了”
|
||||
- “设置 Mesos 和 Kubernetes 太复杂了！！”
|
||||
|
||||
<!--
|
||||
###### Data
|
||||
-->
|
||||
###### 数据
|
||||
|
||||
<!--
|
||||
- “Lack of flexibility of volumes (which is the same problem with VMs, physical hardware, etc)”
|
||||
- “Persistency”
|
||||
- “Storage”
|
||||
- “Persistent Data”
|
||||
-->
|
||||
- “卷缺乏灵活性（与 VM，物理硬件等相同的问题）”
|
||||
- “坚持不懈”
|
||||
- “存储”
|
||||
- “永久数据”
|
||||
|
||||
<!--
|
||||
_Download the full survey results [here](https://docs.google.com/spreadsheets/d/18wZe7wEDvRuT78CEifs13maXoSGem_hJvbOSmsuJtkA/pub?gid=530616014&single=true&output=csv) (CSV file)._
|
||||
-->
|
||||
_下载完整的调查结果 [链接](https://docs.google.com/spreadsheets/d/18wZe7wEDvRuT78CEifs13maXoSGem_hJvbOSmsuJtkA/pub?gid=530616014&single=true&output=csv) (CSV 文件）。_
|
||||
|
||||
<!--
|
||||
_Up-- Brendan Burns, Software Engineer, Google
|
||||
-->
|
||||
_Up-- Brendan Burns，Google 软件工程师
|
||||
Loading…
Reference in New Issue