Update 2016-02-00-State-Of-Container-World-January-2016.md
This commit is contained in:
Sophy417
GitHub
parent
02eb3ff623
commit
fd0234299b
|
|
@ -1,5 +1,5 @@
|
|||
---
|
||||
title: " 容器世界情况，2016年1月 "
|
||||
title: " 容器世界现状，2016年1月 "
|
||||
date: 2016-02-01
|
||||
slug: state-of-container-world-january-2016
|
||||
url: /blog/2016/02/State-Of-Container-World-January-2016
|
||||
|
|
@ -15,7 +15,7 @@ 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 月的数据（感谢您的参与！）。
|
||||
|
||||
<!--
|
||||
|
|
@ -23,13 +23,13 @@ A note about these numbers: First, you may notice that the numbers don’t add u
|
|||
-->
|
||||
关于这些数字的注释：
|
||||
首先，您可能会注意到，这些数字加起来并不是 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))。
|
||||
其次，虽然我们尝试覆盖广泛的云社区，但调查最初是通过 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.
|
||||
-->
|
||||
|
|
@ -42,8 +42,8 @@ First off, lots of you are using containers! 71% are currently using containers,
|
|||
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%的容器用户表示你们计划很快进入生产阶段。
|
||||
超过 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.
|
||||
|
|
@ -76,7 +76,7 @@ Finally, we asked people for free-text answers about the challenges of working w
|
|||
- “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，到基础网络等。”
|
||||
- “孤立的开发环境/工作流程可能是零散的，调试容器时可以轻松访问日志等工具，但有时却不太直观，需要大量知识来掌握整个基础架构堆栈和部署/ 更新 kubernetes，到底层网络等。”
|
||||
- “迁移开发者的工作流程。 那些不熟悉容器、卷等的人只是想工作。”
|
||||
|
||||
<!--
|
||||
|
|
@ -89,7 +89,7 @@ Finally, we asked people for free-text answers about the challenges of working w
|
|||
- “Secrets”
|
||||
-->
|
||||
- “网络安全”
|
||||
- “秘密”
|
||||
- “Secrets”
|
||||
|
||||
<!--
|
||||
###### Immaturity
|
||||
|
|
@ -117,9 +117,9 @@ Finally, we asked people for free-text answers about the challenges of working w
|
|||
- “Clustering is still too hard”
|
||||
- “Setting up Mesos and Kubernetes too damn complicated!!”
|
||||
-->
|
||||
- “网络支持， 为 kubernetes 在裸机上为每个 Pod 提供 Ip”
|
||||
- “网络支持， 为 kubernetes 在裸机上为每个 Pod 提供 IP”
|
||||
- “集群化还是太难了”
|
||||
- “设置 Mesos 和 Kubernetes 太他妈复杂了！！”
|
||||
- “设置 Mesos 和 Kubernetes 太复杂了！！”
|
||||
|
||||
<!--
|
||||
###### Data
|
||||
|
|
@ -140,7 +140,7 @@ Finally, we asked people for free-text answers about the challenges of working w
|
|||
<!--
|
||||
_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 文件）。_
|
||||
_下载完整的调查结果 [链接](https://docs.google.com/spreadsheets/d/18wZe7wEDvRuT78CEifs13maXoSGem_hJvbOSmsuJtkA/pub?gid=530616014&single=true&output=csv) (CSV 文件）。_
|
||||
|
||||
<!--
|
||||
_Up-- Brendan Burns, Software Engineer, Google
|
||||
|
|
|
|||
Loading…
Reference in New Issue