191 lines
4.1 KiB
Markdown
191 lines
4.1 KiB
Markdown
|
<!--
|
|||
|
|
---
|
|||
|
|
title: " Weekly Kubernetes Community Hangout Notes - July 31 2015 "
|
|||
|
|
date: 2015-08-04
|
|||
|
|
slug: weekly-kubernetes-community-hangout
|
|||
|
|
url: /blog/2015/08/Weekly-Kubernetes-Community-Hangout
|
|||
|
|
---
|
|||
|
|
-->
|
|||
|
|
|
|||
|
|
---
|
|||
|
|
title: " Kubernetes社区每周环聊笔记-2015年7月31日 "
|
|||
|
|
date: 2015-08-04
|
|||
|
|
slug: weekly-kubernetes-community-hangout
|
|||
|
|
url: /blog/2015/08/Weekly-Kubernetes-Community-Hangout
|
|||
|
|
---
|
|||
|
|
|
|||
|
|
<!--
|
|||
|
|
Every week the Kubernetes contributing community meet virtually over Google Hangouts. We want anyone who's interested to know what's discussed in this forum.
|
|||
|
|
|
|||
|
|
Here are the notes from today's meeting:
|
|||
|
|
-->
|
|||
|
|
|
|||
|
|
每周，Kubernetes 贡献社区都会通过Google 环聊虚拟开会。我们希望任何有兴趣的人都知道本论坛讨论的内容。
|
|||
|
|
|
|||
|
|
这是今天会议的笔记：
|
|||
|
|
|
|||
|
|
<!--
|
|||
|
|
* Private Registry Demo - Muhammed
|
|||
|
|
|
|||
|
|
* Run docker-registry as an RC/Pod/Service
|
|||
|
|
|
|||
|
|
* Run a proxy on every node
|
|||
|
|
|
|||
|
|
* Access as localhost:5000
|
|||
|
|
|
|||
|
|
* Discussion:
|
|||
|
|
|
|||
|
|
* Should we back it by GCS or S3 when possible?
|
|||
|
|
|
|||
|
|
* Run real registry backed by $object_store on each node
|
|||
|
|
|
|||
|
|
* DNS instead of localhost?
|
|||
|
|
|
|||
|
|
* disassemble image strings?
|
|||
|
|
|
|||
|
|
* more like DNS policy?
|
|||
|
|
-->
|
|||
|
|
* 私人注册表演示 - Muhammed
|
|||
|
|
|
|||
|
|
* 将 docker-registry 作为 RC/Pod/Service 运行
|
|||
|
|
|
|||
|
|
* 在每个节点上运行代理
|
|||
|
|
|
|||
|
|
* 以 localhost:5000 访问
|
|||
|
|
|
|||
|
|
* 讨论：
|
|||
|
|
|
|||
|
|
* 我们应该在可能的情况下通过 GCS 或 S3 支持它吗？
|
|||
|
|
|
|||
|
|
* 在每个节点上运行由 $object_store 支持的真实注册表
|
|||
|
|
|
|||
|
|
* DNS 代替 localhost？
|
|||
|
|
|
|||
|
|
* 分解图像字符串？
|
|||
|
|
|
|||
|
|
* 更像 DNS 策略吗？
|
|||
|
|
<!--
|
|||
|
|
* Running Large Clusters - Joe
|
|||
|
|
|
|||
|
|
* Samsung keen to see large scale O(1000)
|
|||
|
|
|
|||
|
|
* Starting on AWS
|
|||
|
|
|
|||
|
|
* RH also interested - test plan needed
|
|||
|
|
|
|||
|
|
* Plan for next week: discuss working-groups
|
|||
|
|
|
|||
|
|
* If you are interested in joining conversation on cluster scalability send mail to [joe@0xBEDA.com][4]
|
|||
|
|
-->
|
|||
|
|
|
|||
|
|
* 运行大型集群 - Joe
|
|||
|
|
|
|||
|
|
* 三星渴望看到大规模 O(1000)
|
|||
|
|
|
|||
|
|
* 从AWS开始
|
|||
|
|
|
|||
|
|
* RH也有兴趣 - 需要测试计划
|
|||
|
|
|
|||
|
|
* 计划下周：讨论工作组
|
|||
|
|
|
|||
|
|
* 如果您有兴趣加入有关集群可扩展性的对话，请发送邮件至[joe@0xBEDA.com][4]
|
|||
|
|
|
|||
|
|
<!--
|
|||
|
|
* Resource API Proposal - Clayton
|
|||
|
|
|
|||
|
|
* New stuff wants more info on resources
|
|||
|
|
|
|||
|
|
* Proposal for resources API - ask apiserver for info on pods
|
|||
|
|
|
|||
|
|
* Send feedback to: #11951
|
|||
|
|
|
|||
|
|
* Discussion on snapshot vs time-series vs aggregates
|
|||
|
|
-->
|
|||
|
|
|
|||
|
|
* 资源 API 提案 - Clayton
|
|||
|
|
|
|||
|
|
* 新东西需要更多资源信息
|
|||
|
|
|
|||
|
|
* 关于资源 API 的提案 - 向 apiserver 询问有关pod的信息
|
|||
|
|
|
|||
|
|
* 发送反馈至：＃11951
|
|||
|
|
|
|||
|
|
* 关于快照，时间序列和聚合的讨论
|
|||
|
|
|
|||
|
|
<!--
|
|||
|
|
* Containerized kubelet - Clayton
|
|||
|
|
|
|||
|
|
* Open pull
|
|||
|
|
|
|||
|
|
* Docker mount propagation - RH carries patches
|
|||
|
|
|
|||
|
|
* Big issues around whole bootstrap of the system
|
|||
|
|
|
|||
|
|
* dual: boot-docker/system-docker
|
|||
|
|
|
|||
|
|
* Kube-in-docker is really nice, but maybe not critical
|
|||
|
|
|
|||
|
|
* Do the small stuff to make progress
|
|||
|
|
|
|||
|
|
* Keep pressure on docker
|
|||
|
|
-->
|
|||
|
|
* 容器化 kubelet - Clayton
|
|||
|
|
|
|||
|
|
* 打开 pull
|
|||
|
|
|
|||
|
|
* Docker挂载传播 - RH 带有补丁
|
|||
|
|
|
|||
|
|
* 有关整个系统引导程序的大问题
|
|||
|
|
|
|||
|
|
* 双：引导docker /系统docker
|
|||
|
|
|
|||
|
|
* Kube-in-docker非常好，但可能并不关键
|
|||
|
|
|
|||
|
|
* 做些小事以取得进步
|
|||
|
|
|
|||
|
|
* 对 docker 施加压力
|
|||
|
|
<!--
|
|||
|
|
* Web UI (preilly)
|
|||
|
|
|
|||
|
|
* Where does web UI stand?
|
|||
|
|
|
|||
|
|
* OK to split it back out
|
|||
|
|
|
|||
|
|
* Use it as a container image
|
|||
|
|
|
|||
|
|
* Build image as part of kube release process
|
|||
|
|
|
|||
|
|
* Vendor it back in? Maybe, maybe not.
|
|||
|
|
|
|||
|
|
* Will DNS be split out?
|
|||
|
|
|
|||
|
|
* Probably more tightly integrated, instead
|
|||
|
|
|
|||
|
|
* Other potential spin-outs:
|
|||
|
|
|
|||
|
|
* apiserver
|
|||
|
|
|
|||
|
|
* clients
|
|||
|
|
-->
|
|||
|
|
* Web UI（普通用户）
|
|||
|
|
|
|||
|
|
* Web UI 放在哪里？
|
|||
|
|
|
|||
|
|
* 确定将其拆分出去
|
|||
|
|
|
|||
|
|
* 将其用作容器图像
|
|||
|
|
|
|||
|
|
* 作为 kube 发布过程的一部分构建映像
|
|||
|
|
|
|||
|
|
* vendor回来了吗？也许吧，也许不是。
|
|||
|
|
|
|||
|
|
* DNS将被拆分吗？
|
|||
|
|
|
|||
|
|
* 可能更紧密地集成在一起，而不是
|
|||
|
|
|
|||
|
|
* 其他潜在的衍生产品：
|
|||
|
|
|
|||
|
|
* apiserver
|
|||
|
|
|
|||
|
|
* clients
|