01:30:02 #startmeeting interop_challenge 01:30:03 Meeting started Wed Feb 8 01:30:02 2017 UTC and is due to finish in 60 minutes. The chair is mafei. Information about MeetBot at http://wiki.debian.org/MeetBot. 01:30:04 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 01:30:06 The meeting name has been set to 'interop_challenge' 01:30:21 Ok，我们开始会议，今天都谁在互操作的会上？打个招呼吧 01:30:38 我们今天会议的议题如下： 01:30:45 #link https://etherpad.openstack.org/p/interop-challenge-china-meeting-2017-02-08 01:31:07 第一个议题： 01:31:14 #topic Happy Chinese new year 01:31:23 新的一年，祝大家新年快乐，鸡年大吉 01:31:26 o/ 01:31:35 o/ 01:31:47 o/ 01:31:47 大家新年快乐：） 01:32:05 下一个议题： 01:32:08 新年快乐 01:32:10 #topic What about the deployment of the LAMP workload 01:32:12 @mafei, @Lixiang-ZTE, @xietaotao, happy Chinese New Year folks. very happy to see everyone here. 01:32:19 大家新年快乐！ 01:32:30 新年快乐~ 01:32:50 1月份的训练营上希望大家在年前完成LAMP的部署，不知道各家是否完成部署？或者计划何时完成？ 01:33:27 麻烦回复xx公司已完成，或者xx公司计划何时完成 01:34:25 good morning 01:34:41 云途腾己完成 01:34:44 ok 01:34:47 good 01:34:48 因年底冲刺项目有拖延，北京云英计划本周日（2月12日）前完成 01:34:55 浪潮已完成。 01:35:03 好的，加油 01:35:46 因为今天我们将开始下一个workload，所以还请大家往前赶 01:35:55 早上好 01:36:04 早上好daisy 01:36:33 中兴结果呢？ 01:36:43 @kongwei 01:36:49 我记得有家公司会提交一个patch to fix the problem with the root access. 01:37:02 I have not see the patch, can we get that patch submitted? 01:37:17 好像是云途腾吧 01:37:32 when install wordpress tool, if use root, it fails without an option. 01:37:40 zte 已经完成lamp测试 01:37:49 it should be a very simple patch. can someone please submit the patch? 01:37:51 @kongwei，ok 01:38:17 关于root access，刚测试完，马上会提交 01:38:20 烽火呢？ 01:38:30 情况如何？ 01:38:43 ok，@t2cloud 01:38:46 @t2cloud, great. great. add my name to the reviewer, so that I can review it quickly. 01:39:27 好的，大家都加油 01:39:31 烽火这边测试人员年前在客户现场忙其他项目，现在正在测试，计划本周内完成 01:39:35 下一个议题： 01:39:46 @tongli ok 01:40:00 ok，@fiberhome-joycc 01:40:04 #topic Decide when to finish the deployment of the dockerswarm workload 01:40:22 下一步我们计划部署dockerswarm，大家认为需要多长时间？两周是否可以？ 01:41:05 since we will be working on kubernetes, is it absolutely necessary to run the dockerswarm workload? @mafei. 01:41:21 I mean kubernetes workload, I am writing it right now. 01:42:57 are we having people dropping off? 01:43:07 我觉得可以同步进行 01:43:18 @mafei, sure, that is fine. 01:43:21 i am here 01:43:34 其他人意见呢 01:43:36 I saw that Liwei and wenwen both left. 01:44:09 maybe the network is bad @tongli 01:45:11 ok. 01:45:15 I'm here 01:45:29 tongli: Docker swarm的难度有多大？ 01:45:48 @Daisy, easier than lampstack. 01:45:55 ok 01:45:56 it is relatively smaller. 01:46:12 @mafei, probably run it to get a feeling about. 01:46:24 docker测试是否也需要连接互联网？ 01:46:44 dockerswarm 依赖coreos，国内拉取coreos会不会很痛苦哦？ 01:46:44 sorry guys, input Chinese from my side is slow, hope that using English is ok with everyone, if not, I will try to type in Chinese. 01:46:56 tongli: 我想mafei可能是想多测一个workload，k8s和nfv还在开发过程中。 01:47:18 测试的结果怎么提交到社区啊？ 01:47:24 @Daisy, that`s right 01:47:39 tongli: 如果k8s开发完毕，可以给大家测试了，那么直接测k8s也可以。 01:47:43 @xietaotao, you only need to get coreos image once and place it in your glance, one time, you do not have to do it everytime you run the workload. 01:48:16 @tongli, OK 01:48:27 @Daisy,@mafei, it is ok to run dockerswarm now, try it and see. 01:48:52 因为k8s和NVF还在开发阶段，所以我们还是先去跑一下dockerswarm 01:49:01 mafei: dockerswarm这个大家都没有做过，不知道2周能不能完成。 01:49:12 一是可以找一下感觉，二来也可以为4月份的展示做一个储备 01:49:34 如果没有问题，我们就安排2周左右的时间来进行部署 01:49:38 ok？ 01:49:40 @mafei, good idea. 01:49:54 @mafei, 好的 01:50:02 @Daisy, 2 weeks should be enough. 01:50:17 好的，同意。 01:50:29 ok 01:50:31 好的 01:50:36 下一个议题： 01:50:48 OK 01:50:51 #topic Decide who to develop the k8s and NFV workload 01:51:33 我记得春节之前的会上讨论过这个。 01:51:40 k8s和NFV两个workload正在开发中 01:51:52 还有谁要参与其中 01:51:54 tongli: 能讲讲k8s的进展吗？ 01:52:11 zte在做nfv的工作了 01:52:17 good 01:52:23 @kongwei 01:52:34 ：） 01:52:47 其他公司呢 01:52:51 ZTE非常愿意做NFV相关的workload 01:53:05 @Lixiang-ZTE, great. thanks a lot. 01:53:13 can you describe the flow? 01:53:16 cloudin云英 01:53:16 浪潮 01:53:24 中国移动苏研 01:53:27 such as this for lampstack. 01:53:58 1. Provision VMs, 2. create security group, rules, 3, install related software, 4 , setup database etc. 01:54:24 now for NFV, what is the use case or scenarios, can you describe it? 01:54:33 @tongli 具体内容现在@kongwei 和 @WangChangJin在做工作 01:55:17 Liwei: 我们正在讨论nfv，你那边有什么新的进展吗？ 01:55:20 @Lixiang-ZTE, ok, if you can ask them to just create that flow, that will be nice. 01:55:36 @ 01:55:43 NFV的场景，我有两个提议 01:56:14 1.VNF基于ZTE的网元来进行构造 01:56:29 @tongli 另外有个问题还请帮忙。我们按照openstak interop challenge页面的要求发邮件请求加入，但是没收到回应。你看能否麻烦你这边知会社区一下接纳我们的申请？ 01:56:30 谢谢 01:57:04 大家认为如何？ 01:57:09 oh, @Lixiang-ZTE, you mean that you tried to subscribe to the mailing list and there was no response? 01:57:26 yes 01:57:39 WangChangJin: 我只看到一个提议。1.VNF基于ZTE的网元来进行构造另外一个是什么？ 01:57:42 孔炜请求的，但是没收到回应 01:57:52 @Lixiang-ZTE, ok. will check into that. 01:58:01 thank you very much! 01:58:05 我已经收到订阅邮件了。但是有个申请被拒绝 01:58:33 which part was rejected? 01:59:30 NFV现在应该华为、移动、中兴都可以参与 01:59:36 国内的SDN/NFV联盟的互操作工作组也有这方面的意向，还在沟通中，但是觉得NFV是一个比较大的框架，最好先做哪个层次的脚本，需要评估可行性。 01:59:42 看看李彤的想法吧 01:59:46 from liwei 02:00:11 @mafei, I think we start with small and easy one, can have many revisions. 02:00:27 but the small and easy one should represent typical use case. 02:00:52 我发了一封邮件“zte want to join the interop challenge” 想把我们测试的内容提交到社区。这个邮件被rejected了@tongli 02:01:08 NFV最简单的场景也比LAMP复杂的多，这个大家要有心理准备，呵呵 02:01:17 the problem is that I do not know what is the typical use case as I have no NFV experiences, I think we rely on experts here in this channel 02:01:41 @kongwei, if your subscription is in the process queue, the email will be rejected. 02:01:42 大家好，我是EasyStack的，很高兴和大家一起交流 02:01:54 WangChangJin is this kind of expert :-) 02:02:00 hongliang: 欢迎 02:02:10 @tongli i agree 02:02:25 @tongli 那么是不是需要重新发邮件申请啊？ 02:02:27 @kongwei, give it couple of days, you should receive an email on if the subscription is accepted or not. 02:02:31 then send the email again. 02:02:40 LAMP部署完成后，可以让大家有个直观的感受最终的结果 02:02:45 欢迎@hongliang 02:02:54 @hongliang, welcome. 02:02:56 好的。十分感谢@tongli 02:03:11 NFV部署后，如果做不到端到端，直观用户感受很难体验 02:03:31 那就通过社区的邮件列表继续nfv的细节的讨论？ 02:03:32 I've been working in Ericsson for 7+ years, and 3 years PC/NFV experience. I may share my effort if needed. 02:03:40 @kongwei, 不用客气。we are all brothers and sisters. I feel very much at home. 02:04:05 nice @liuhaijie 02:04:11 @liuhaijie, that will be awesome. 02:04:36 我来记录action item吧。 02:04:44 @liuhaijie, if you can provide some work flow (use case), then we can have some discussions in this work group. 02:05:05 ok，@Daisy 02:05:09 I think we should just write #action 02:05:20 我觉得最好能实现一个打通电话的场景。这个利于演示。 02:05:30 #action T2Cloud submit the patch to fix root access issue on lampstack 02:05:37 ok 02:05:53 去年summit上OPNFV那个拿大剪刀剪光纤的效果很好，哈哈。 02:06:02 #action Liuhaijie to provide some details on NFV use cases or at least thoughts since his expereiences in the past. 02:06:16 interop如果有也有实际的电话业务演示感觉会更令人感兴趣 02:06:29 @tongli there is a white paper from ITU, regarding to NFV use case. I can share it later. 02:06:30 I think when we do something like that, it automatically list these things in a file we can later refer to. 02:06:33 #action all to start dockerswarm testing and update progress in the next meeting 02:07:29 any other action？ 02:07:30 @liuhaijie, yes, that is nice, but if you can take the typical use case out and share with folks, that will be nicer. you know people are very busy. 02:07:50 #action each company should run dockerswarm and complete within two weeks. 02:08:00 ok 02:08:16 For a phone call, we need much more functions in telecom, i.e., packet core, eNode B, etc. It need strong support from telecom companies. 02:08:27 btw, Boston summit will have another big interop show, do not know what yet. 02:08:33 #action 02:08:37 that is the latest news I got. 02:09:07 any good ideas will be appreciated very much. 02:09:09 @tongli understood, i'll figure out some 'typical' cases. 02:09:43 #action CloudIn and FiberHome to finish LAMP test by this week 02:09:43 that will be the message also for ZTE brothers and sisters. 02:10:25 tongli: glad to see there will be another interop show in Boston. Our Chinese companies can join the show. 02:10:26 only brothers now , hahah 02:10:57 @Daisy, absolutely, I would love to see all these telecom companies to be represented on the stage. 02:11:03 that will be absolutely awesome. 02:11:17 of course, other players as well. 02:11:47 the more, the merrier 02:11:47 shall we move to next topic ? 02:11:51 ok 02:12:00 下一个议题： 02:12:07 #topic Discuss how to write the white paper about openstack interop 02:12:24 互操作的白皮书 02:12:26 白皮书，先从目录开始吧？ 02:12:45 我梳理了一个框架 02:12:56 大家可以提提意见 02:12:56 mafei: awesome 02:13:03 一、openstack互操作简介 02:13:31 二、开展openstack互操作目的 02:13:37 三、开源社区互操作情况 02:13:43 四、互操作应用场景 02:13:49 五、互操作遇到的问题 02:14:05 1.1 什么是openstack互操作 02:14:18 1.2 openstack互操作的内容 02:14:38 4.1 LAMP 02:14:44 4.2 dockerswarm 02:14:49 4.3 k8s 02:14:53 4.4 NFV 02:14:59 4.5 其他 02:15:15 看看有何意见 02:15:36 good start @Daisy, thanks. 02:16:05 we probably can add that these work loads will be very much targeting the Openstack certification processes. 02:16:27 另外，大家如果对那部分感兴趣，也可以参与一下 02:16:39 these word should be part of the purposes of the interop challenge effort. 02:16:56 mafei: 看起来不错。 02:18:34 其他人有无意见 02:18:44 @mafei, thanks for putting it together, looks nice. maybe add some part like lesson's learnt 02:19:04 tongli: good suggestion 02:19:05 these section normally are valuable to service providers. 02:19:31 "五、互操作遇到的问题"改为“五、互操作遇到的问题及建议”？ 02:19:34 sorry, what about lesson's learnt 02:19:46 @mafei, plus, we already have a document in the current project, you can simply copy and paste (maybe translate). 02:19:52 ok,daisy 02:20:09 this is good because we are all part of the interop challenge, so there is no stealing material problem. 02:20:13 good, tongli 02:20:27 ok 02:20:37 mafei: 就是一些互操作性的经验和最佳实践的分享 02:20:48 ok 02:20:52 mafei: litong说社区里面有一些英文文档了。可以参考 02:21:05 恩明白 02:21:30 我们还有十分钟 02:21:35 没有意见就下一个话题了？ 02:21:42 最后一个议题 02:21:47 我觉得是否可以不需要4.5其他?如果我们有openstack社区中没有的场景，就按场景分类单列。 02:21:58 ok 02:22:01 good 02:22:02 防止其他这节成为大杂烩 02:22:18 好主意 02:22:19 #topic Discuss how to show the interop challenge on the global cloud computing summit in April 02:22:21 好，同意。 02:22:35 讨论下4月份峰会的演示 02:22:44 希望能够邀请到重量级的嘉宾来主持这个部分。 02:22:53 我们也计划邀请openstack基金会的高层过来主持，但这取决于我们可以展示的东西和效果 02:23:07 mafei: 也取决于这个会议的规模 02:23:10 @mafei, yes, agree 02:23:30 集思广益 02:23:52 tongli，你有何建议 02:24:00 谁厉害把jonathan抓来 :-D 02:24:33 首先得看我们也展示的东西 02:24:43 先自身强 02:24:49 LAMP不适合再演示一遍了。如果K8s或者NFV能够完成，我感觉新的usecase比较好。 02:25:10 k8s或NVF时间上是否来得及 02:25:19 具体4月什么时候？ 02:25:26 4月19日20日 02:25:32 4月19-20日 02:25:40 NFV感觉会太紧张 02:25:42 k8s is an cadidate, but I think number of people attending is the most important factor. 02:25:54 Boston峰会在这个之后一个月，不知道峰会上打算演示什么。 02:26:09 @Daisy, do not know yet. 02:26:14 4月份的峰会规模在3000-4000好像 02:26:32 mafei: wow, amazing number 02:26:52 @mafei 这么大啊？ 02:26:57 没想到 02:27:01 k8s大约什么时间能够给大家测试？ 02:27:14 tongli: k8s大约什么时间能够开始给大家测试？ 02:27:43 我们的演示安排在主会场上 02:27:49 应该是第二天上午 02:27:56 也就是20日上午 02:28:05 @Daisy, do not know yet, I have few issues to resolve first. 02:28:21 I am hoping I can resolve these issues in next couple of weeks. 02:28:27 tongli: ok 02:28:39 我想大家至少需要提前一个半月开始测试吧？ 02:29:26 时间快要到了，我们是否可以继续讨论 02:29:55 mafei: 没人占会议室就可以继续讨论。 02:30:08 或者，我们下周三在讨论峰会演示的话题 02:30:20 这个会议是一周一次吗？ 02:30:37 好像是一周一次的 02:30:41 哦。 02:30:42 ok 02:31:07 it was reserved once a week, but I think we decided to have it every other week. 02:31:10 ok 02:31:14 we are free to use it every week though. 02:31:46 #action decide who to update the wiki page 02:32:05 峰会的演示确实需要好好讨论下，大家也可以在这周内思考下如何演示会更好 02:32:10 I think Daisy has been doing that, I prefer an non-ibmer does that for us. 02:32:32 tongli: 有什么需要更新的啊？我可以去做。:) 02:33:08 the meeting information & the etherpad link need to be updated each week. 02:33:14 like time, etc 02:33:24 我去做吧。一回生两回熟。 02:33:38 原计划我们想二周一次会 02:34:06 但是峰会的事还没有讨论好，所以我们是否下周继续讨论 02:34:26 mafei: 会后你可以试一下看能不能更新wiki，如果能的话，以后你可以直接去更新。 02:34:50 如何更新？ 02:34:59 会后跟你说。 02:35:02 好的 02:35:10 那好吧，今天的会议就到这儿吧 02:35:16 感谢大家的参与 02:35:22 @Daisy,@mafei, need to end the meeting I think. 02:35:29 i 02:35:32 谢谢@mafei, @tongli, all 02:35:36 i know 02:35:43 @mafei, great. 02:35:45 tongli, good night 02:35:46 Thanks a lot. 02:36:03 #endmeeting