| *** Liwei has joined #openstack-meeting-5 | 00:53 | |
| *** Liwei has quit IRC | 00:59 | |
| *** tiger has joined #openstack-meeting-5 | 00:59 | |
| *** Liwei has joined #openstack-meeting-5 | 00:59 | |
| Liwei | hello？ | 00:59 |
|---|---|---|
| *** tiger is now known as Guest81208 | 00:59 | |
| *** Liwei has quit IRC | 01:00 | |
| Guest81208 | hi | 01:00 |
| *** LiXiang has joined #openstack-meeting-5 | 01:01 | |
| *** mafei has joined #openstack-meeting-5 | 01:02 | |
| *** Guest81208 has quit IRC | 01:03 | |
| LiXiang | Hello~ Is it China Interop meeting? | 01:04 |
| mafei | yes | 01:07 |
| *** Liwei has joined #openstack-meeting-5 | 01:07 | |
| LiXiang | 9:30? | 01:07 |
| mafei | yes | 01:07 |
| *** Liwei has quit IRC | 01:09 | |
| *** joycc has joined #openstack-meeting-5 | 01:10 | |
| *** WangChangJin has joined #openstack-meeting-5 | 01:11 | |
| *** Liwei has joined #openstack-meeting-5 | 01:12 | |
| *** Liwei has quit IRC | 01:14 | |
| *** t2cloud has joined #openstack-meeting-5 | 01:14 | |
| *** joycc has quit IRC | 01:15 | |
| *** WangChangJin has quit IRC | 01:15 | |
| *** fiberhome-joycc has joined #openstack-meeting-5 | 01:16 | |
| *** WangChangJin has joined #openstack-meeting-5 | 01:16 | |
| *** LiXiang is now known as Lixiang-ZTE | 01:16 | |
| *** wenwen has joined #openstack-meeting-5 | 01:20 | |
| *** zuozongming has joined #openstack-meeting-5 | 01:20 | |
| *** wenwen has quit IRC | 01:23 | |
| *** wenwen has joined #openstack-meeting-5 | 01:24 | |
| *** kongwei has joined #openstack-meeting-5 | 01:26 | |
| *** Liwei has joined #openstack-meeting-5 | 01:26 | |
| *** backup has joined #openstack-meeting-5 | 01:27 | |
| *** wenwen has quit IRC | 01:27 | |
| *** Liwei has quit IRC | 01:27 | |
| *** xietaotao has joined #openstack-meeting-5 | 01:27 | |
| kongwei | hi 谢涛涛 | 01:27 |
| kongwei | ：） | 01:27 |
| xietaotao | hi, :) | 01:27 |
| mafei | 看来已经有好多人进来了 | 01:28 |
| *** backup has quit IRC | 01:29 | |
| *** tianquan has joined #openstack-meeting-5 | 01:29 | |
| *** Liwei has joined #openstack-meeting-5 | 01:29 | |
| *** tongli has joined #openstack-meeting-5 | 01:29 | |
| mafei | #startmeeting interop_challenge | 01:30 |
| openstack | 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 |
| openstack | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 01:30 |
| *** openstack changes topic to " (Meeting topic: interop_challenge)" | 01:30 | |
| openstack | The meeting name has been set to 'interop_challenge' | 01:30 |
| mafei | Ok，我们开始会议，今天都谁在互操作的会上？打个招呼吧 | 01:30 |
| mafei | 我们今天会议的议题如下： | 01:30 |
| mafei | #link https://etherpad.openstack.org/p/interop-challenge-china-meeting-2017-02-08 | 01:30 |
| *** Liwei has quit IRC | 01:30 | |
| mafei | 第一个议题： | 01:31 |
| mafei | #topic Happy Chinese new year | 01:31 |
| *** openstack changes topic to "Happy Chinese new year (Meeting topic: interop_challenge)" | 01:31 | |
| *** zuozongming has quit IRC | 01:31 | |
| *** Liwei has joined #openstack-meeting-5 | 01:31 | |
| mafei | 新的一年，祝大家新年快乐，鸡年大吉 | 01:31 |
| tongli | o/ | 01:31 |
| Lixiang-ZTE | o/ | 01:31 |
| kongwei | o/ | 01:31 |
| xietaotao | 大家新年快乐：） | 01:31 |
| mafei | 下一个议题： | 01:32 |
| WangChangJin | 新年快乐 | 01:32 |
| mafei | #topic What about the deployment of the LAMP workload | 01:32 |
| *** openstack changes topic to "What about the deployment of the LAMP workload (Meeting topic: interop_challenge)" | 01:32 | |
| tongli | @mafei, @Lixiang-ZTE, @xietaotao, happy Chinese New Year folks. very happy to see everyone here. | 01:32 |
| *** Liwei has quit IRC | 01:32 | |
| t2cloud | 大家新年快乐！ | 01:32 |
| Lixiang-ZTE | 新年快乐~ | 01:32 |
| mafei | 1月份的训练营上希望大家在年前完成LAMP的部署，不知道各家是否完成部署？或者计划何时完成？ | 01:32 |
| mafei | 麻烦回复xx公司已完成，或者xx公司计划何时完成 | 01:33 |
| *** Liwei has joined #openstack-meeting-5 | 01:33 | |
| *** daisyguo has joined #openstack-meeting-5 | 01:34 | |
| daisyguo | good morning | 01:34 |
| t2cloud | 云途腾己完成 | 01:34 |
| mafei | ok | 01:34 |
| mafei | good | 01:34 |
| tianquan | 因年底冲刺项目有拖延，北京云英计划本周日（2月12日）前完成 | 01:34 |
| xietaotao | 浪潮已完成。 | 01:34 |
| *** daisyguo has quit IRC | 01:34 | |
| mafei | 好的，加油 | 01:35 |
| *** daisyguo has joined #openstack-meeting-5 | 01:35 | |
| mafei | 因为今天我们将开始下一个workload，所以还请大家往前赶 | 01:35 |
| daisyguo | 早上好 | 01:35 |
| *** Liwei has quit IRC | 01:36 | |
| mafei | 早上好daisy | 01:36 |
| *** Liwei has joined #openstack-meeting-5 | 01:36 | |
| mafei | 中兴结果呢？ | 01:36 |
| mafei | @kongwei | 01:36 |
| tongli | 我记得有家公司会提交一个patch to fix the problem with the root access. | 01:36 |
| tongli | I have not see the patch, can we get that patch submitted? | 01:37 |
| mafei | 好像是云途腾吧 | 01:37 |
| tongli | when install wordpress tool, if use root, it fails without an option. | 01:37 |
| kongwei | zte 已经完成lamp测试 | 01:37 |
| tongli | it should be a very simple patch. can someone please submit the patch? | 01:37 |
| mafei | @kongwei，ok | 01:37 |
| *** changhongli has joined #openstack-meeting-5 | 01:37 | |
| t2cloud | 关于root access，刚测试完，马上会提交 | 01:38 |
| mafei | 烽火呢？ | 01:38 |
| mafei | 情况如何？ | 01:38 |
| *** wenwen has joined #openstack-meeting-5 | 01:38 | |
| mafei | ok，@t2cloud | 01:38 |
| tongli | @t2cloud, great. great. add my name to the reviewer, so that I can review it quickly. | 01:38 |
| *** zuozongming has joined #openstack-meeting-5 | 01:38 | |
| *** WangChangJin has quit IRC | 01:38 | |
| mafei | 好的，大家都加油 | 01:39 |
| fiberhome-joycc | 烽火这边测试人员年前在客户现场忙其他项目，现在正在测试，计划本周内完成 | 01:39 |
| mafei | 下一个议题： | 01:39 |
| *** WangChangJin has joined #openstack-meeting-5 | 01:39 | |
| t2cloud | @tongli ok | 01:39 |
| *** wenwen has quit IRC | 01:39 | |
| mafei | ok，@fiberhome-joycc | 01:40 |
| mafei | #topic Decide when to finish the deployment of the dockerswarm workload | 01:40 |
| *** openstack changes topic to "Decide when to finish the deployment of the dockerswarm workload (Meeting topic: interop_challenge)" | 01:40 | |
| mafei | 下一步我们计划部署dockerswarm，大家认为需要多长时间？两周是否可以？ | 01:40 |
| tongli | since we will be working on kubernetes, is it absolutely necessary to run the dockerswarm workload? @mafei. | 01:41 |
| *** marven has joined #openstack-meeting-5 | 01:41 | |
| tongli | I mean kubernetes workload, I am writing it right now. | 01:41 |
| *** wenwen has joined #openstack-meeting-5 | 01:41 | |
| *** daisyguo has quit IRC | 01:42 | |
| *** Liwei has quit IRC | 01:42 | |
| *** daisyguo has joined #openstack-meeting-5 | 01:42 | |
| *** wenwen has quit IRC | 01:42 | |
| tongli | are we having people dropping off? | 01:42 |
| mafei | 我觉得可以同步进行 | 01:43 |
| tongli | @mafei, sure, that is fine. | 01:43 |
| mafei | i am here | 01:43 |
| mafei | 其他人意见呢 | 01:43 |
| tongli | I saw that Liwei and wenwen both left. | 01:43 |
| *** marven has quit IRC | 01:43 | |
| *** daisyguo has quit IRC | 01:44 | |
| mafei | maybe the network is bad @tongli | 01:44 |
| *** Daisy has joined #openstack-meeting-5 | 01:44 | |
| *** daisyguo has joined #openstack-meeting-5 | 01:44 | |
| *** daisyguo has quit IRC | 01:44 | |
| tongli | ok. | 01:45 |
| Daisy | I'm here | 01:45 |
| Daisy | tongli: Docker swarm的难度有多大？ | 01:45 |
| *** Liwei has joined #openstack-meeting-5 | 01:45 | |
| tongli | @Daisy, easier than lampstack. | 01:45 |
| Daisy | ok | 01:45 |
| tongli | it is relatively smaller. | 01:45 |
| tongli | @mafei, probably run it to get a feeling about. | 01:46 |
| kongwei | docker测试是否也需要连接互联网？ | 01:46 |
| *** Liwei has quit IRC | 01:46 | |
| xietaotao | dockerswarm 依赖coreos，国内拉取coreos会不会很痛苦哦？ | 01:46 |
| tongli | 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 |
| Daisy | tongli: 我想mafei可能是想多测一个workload，k8s和nfv还在开发过程中。 | 01:46 |
| kongwei | 测试的结果怎么提交到社区啊？ | 01:47 |
| mafei | @Daisy, that`s right | 01:47 |
| Daisy | tongli: 如果k8s开发完毕，可以给大家测试了，那么直接测k8s也可以。 | 01:47 |
| tongli | @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:47 |
| *** Liwei has joined #openstack-meeting-5 | 01:47 | |
| *** makai has joined #openstack-meeting-5 | 01:48 | |
| xietaotao | @tongli, OK | 01:48 |
| tongli | @Daisy,@mafei, it is ok to run dockerswarm now, try it and see. | 01:48 |
| mafei | 因为k8s和NVF还在开发阶段，所以我们还是先去跑一下dockerswarm | 01:48 |
| *** wenwen has joined #openstack-meeting-5 | 01:48 | |
| Daisy | mafei: dockerswarm这个大家都没有做过，不知道2周能不能完成。 | 01:49 |
| *** Liwei has quit IRC | 01:49 | |
| mafei | 一是可以找一下感觉，二来也可以为4月份的展示做一个储备 | 01:49 |
| mafei | 如果没有问题，我们就安排2周左右的时间来进行部署 | 01:49 |
| mafei | ok？ | 01:49 |
| tongli | @mafei, good idea. | 01:49 |
| xietaotao | @mafei, 好的 | 01:49 |
| tongli | @Daisy, 2 weeks should be enough. | 01:50 |
| Daisy | 好的，同意。 | 01:50 |
| mafei | ok | 01:50 |
| t2cloud | 好的 | 01:50 |
| *** wenwen has quit IRC | 01:50 | |
| mafei | 下一个议题： | 01:50 |
| fiberhome-joycc | OK | 01:50 |
| mafei | #topic Decide who to develop the k8s and NFV workload | 01:50 |
| *** openstack changes topic to "Decide who to develop the k8s and NFV workload (Meeting topic: interop_challenge)" | 01:50 | |
| Daisy | 我记得春节之前的会上讨论过这个。 | 01:51 |
| mafei | k8s和NFV两个workload正在开发中 | 01:51 |
| mafei | 还有谁要参与其中 | 01:51 |
| Daisy | tongli: 能讲讲k8s的进展吗？ | 01:51 |
| kongwei | zte在做nfv的工作了 | 01:52 |
| mafei | good | 01:52 |
| mafei | @kongwei | 01:52 |
| *** Liwei has joined #openstack-meeting-5 | 01:52 | |
| kongwei | ：） | 01:52 |
| mafei | 其他公司呢 | 01:52 |
| Lixiang-ZTE | ZTE非常愿意做NFV相关的workload | 01:52 |
| tongli | @Lixiang-ZTE, great. thanks a lot. | 01:53 |
| tongli | can you describe the flow? | 01:53 |
| mafei | cloudin云英 | 01:53 |
| mafei | 浪潮 | 01:53 |
| *** Liwei has quit IRC | 01:53 | |
| mafei | 中国移动苏研 | 01:53 |
| tongli | such as this for lampstack. | 01:53 |
| tongli | 1. Provision VMs, 2. create security group, rules, 3, install related software, 4 , setup database etc. | 01:53 |
| *** hongliang has joined #openstack-meeting-5 | 01:54 | |
| tongli | now for NFV, what is the use case or scenarios, can you describe it? | 01:54 |
| Lixiang-ZTE | @tongli 具体内容现在@kongwei 和 @WangChangJin在做工作 | 01:54 |
| *** Liwei has joined #openstack-meeting-5 | 01:54 | |
| Daisy | Liwei: 我们正在讨论nfv，你那边有什么新的进展吗？ | 01:55 |
| tongli | @Lixiang-ZTE, ok, if you can ask them to just create that flow, that will be nice. | 01:55 |
| Lixiang-ZTE | @ | 01:55 |
| *** Liwei has quit IRC | 01:55 | |
| WangChangJin | NFV的场景，我有两个提议 | 01:55 |
| WangChangJin | 1.VNF基于ZTE的网元来进行构造 | 01:56 |
| *** Liwei has joined #openstack-meeting-5 | 01:56 | |
| Lixiang-ZTE | @tongli 另外有个问题还请帮忙。我们按照openstak interop challenge页面的要求发邮件请求加入，但是没收到回应。你看能否麻烦你这边知会社区一下接纳我们的申请？ | 01:56 |
| Lixiang-ZTE | 谢谢 | 01:56 |
| WangChangJin | 大家认为如何？ | 01:57 |
| tongli | oh, @Lixiang-ZTE, you mean that you tried to subscribe to the mailing list and there was no response? | 01:57 |
| kongwei | yes | 01:57 |
| Daisy | WangChangJin: 我只看到一个提议。1.VNF基于ZTE的网元来进行构造 另外一个是什么？ | 01:57 |
| Lixiang-ZTE | 孔炜请求的，但是没收到回应 | 01:57 |
| tongli | @Lixiang-ZTE, ok. will check into that. | 01:57 |
| Lixiang-ZTE | thank you very much! | 01:58 |
| kongwei | 我已经收到订阅邮件了。但是有个申请被拒绝 | 01:58 |
| tongli | which part was rejected? | 01:58 |
| *** Liwei has quit IRC | 01:58 | |
| *** liuhaijie has joined #openstack-meeting-5 | 01:59 | |
| mafei | NFV现在应该华为、移动、中兴都可以参与 | 01:59 |
| mafei | 国内的SDN/NFV联盟的互操作工作组也有这方面的意向，还在沟通中，但是觉得NFV是一个比较大的框架，最好先做哪个层次的脚本，需要评估可行性。 | 01:59 |
| mafei | 看看李彤的想法吧 | 01:59 |
| mafei | from liwei | 01:59 |
| *** Liwei has joined #openstack-meeting-5 | 02:00 | |
| tongli | @mafei, I think we start with small and easy one, can have many revisions. | 02:00 |
| tongli | but the small and easy one should represent typical use case. | 02:00 |
| kongwei | 我发了一封邮件“zte want to join the interop challenge” 想把我们测试的内容提交到社区。这个邮件被rejected了@tongli | 02:00 |
| WangChangJin | NFV最简单的场景也比LAMP复杂的多，这个大家要有心理准备，呵呵 | 02:01 |
| tongli | 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 |
| tongli | @kongwei, if your subscription is in the process queue, the email will be rejected. | 02:01 |
| hongliang | 大家好，我是EasyStack的，很高兴和大家一起交流 | 02:01 |
| Lixiang-ZTE | WangChangJin is this kind of expert :-) | 02:01 |
| Daisy | hongliang: 欢迎 | 02:02 |
| *** Liwei has quit IRC | 02:02 | |
| mafei | @tongli i agree | 02:02 |
| kongwei | @tongli 那么是不是需要重新发邮件申请啊？ | 02:02 |
| tongli | @kongwei, give it couple of days, you should receive an email on if the subscription is accepted or not. | 02:02 |
| tongli | then send the email again. | 02:02 |
| WangChangJin | LAMP部署完成后，可以让大家有个直观的感受最终的结果 | 02:02 |
| mafei | 欢迎@hongliang | 02:02 |
| tongli | @hongliang, welcome. | 02:02 |
| kongwei | 好的。十分感谢@tongli | 02:02 |
| *** Liwei has joined #openstack-meeting-5 | 02:02 | |
| WangChangJin | NFV部署后，如果做不到端到端，直观用户感受很难体验 | 02:03 |
| Daisy | 那就通过社区的邮件列表继续nfv的细节的讨论？ | 02:03 |
| liuhaijie | I've been working in Ericsson for 7+ years, and 3 years PC/NFV experience. I may share my effort if needed. | 02:03 |
| tongli | @kongwei, 不用客气。we are all brothers and sisters. I feel very much at home. | 02:03 |
| *** Liwei has quit IRC | 02:04 | |
| mafei | nice @liuhaijie | 02:04 |
| tongli | @liuhaijie, that will be awesome. | 02:04 |
| Daisy | 我来记录action item吧。 | 02:04 |
| tongli | @liuhaijie, if you can provide some work flow (use case), then we can have some discussions in this work group. | 02:04 |
| mafei | ok，@Daisy | 02:05 |
| tongli | I think we should just write #action | 02:05 |
| *** Liwei has joined #openstack-meeting-5 | 02:05 | |
| Lixiang-ZTE | 我觉得最好能实现一个打通电话的场景。这个利于演示。 | 02:05 |
| tongli | #action T2Cloud submit the patch to fix root access issue on lampstack | 02:05 |
| mafei | ok | 02:05 |
| Lixiang-ZTE | 去年summit上OPNFV那个拿大剪刀剪光纤的效果很好，哈哈。 | 02:05 |
| tongli | #action Liuhaijie to provide some details on NFV use cases or at least thoughts since his expereiences in the past. | 02:06 |
| Lixiang-ZTE | interop如果有也有实际的电话业务演示感觉会更令人感兴趣 | 02:06 |
| liuhaijie | @tongli there is a white paper from ITU, regarding to NFV use case. I can share it later. | 02:06 |
| tongli | I think when we do something like that, it automatically list these things in a file we can later refer to. | 02:06 |
| Daisy | #action all to start dockerswarm testing and update progress in the next meeting | 02:06 |
| *** Liwei has quit IRC | 02:06 | |
| mafei | any other action？ | 02:07 |
| tongli | @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 |
| tongli | #action each company should run dockerswarm and complete within two weeks. | 02:07 |
| mafei | ok | 02:08 |
| liuhaijie | 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 |
| tongli | btw, Boston summit will have another big interop show, do not know what yet. | 02:08 |
| mafei | #action | 02:08 |
| tongli | that is the latest news I got. | 02:08 |
| tongli | any good ideas will be appreciated very much. | 02:09 |
| liuhaijie | @tongli understood, i'll figure out some 'typical' cases. | 02:09 |
| *** changhongli has quit IRC | 02:09 | |
| *** wenwen has joined #openstack-meeting-5 | 02:09 | |
| Daisy | #action CloudIn and FiberHome to finish LAMP test by this week | 02:09 |
| tongli | that will be the message also for ZTE brothers and sisters. | 02:09 |
| Daisy | tongli: glad to see there will be another interop show in Boston. Our Chinese companies can join the show. | 02:10 |
| Lixiang-ZTE | only brothers now , hahah | 02:10 |
| tongli | @Daisy, absolutely, I would love to see all these telecom companies to be represented on the stage. | 02:10 |
| tongli | that will be absolutely awesome. | 02:11 |
| tongli | of course, other players as well. | 02:11 |
| tongli | the more, the merrier | 02:11 |
| Daisy | shall we move to next topic ? | 02:11 |
| *** wenwen has quit IRC | 02:11 | |
| mafei | ok | 02:11 |
| mafei | 下一个议题： | 02:12 |
| mafei | #topic Discuss how to write the white paper about openstack interop | 02:12 |
| *** openstack changes topic to "Discuss how to write the white paper about openstack interop (Meeting topic: interop_challenge)" | 02:12 | |
| *** Liwei has joined #openstack-meeting-5 | 02:12 | |
| mafei | 互操作的白皮书 | 02:12 |
| Daisy | 白皮书，先从目录开始吧？ | 02:12 |
| mafei | 我梳理了一个框架 | 02:12 |
| mafei | 大家可以提提意见 | 02:12 |
| Daisy | mafei: awesome | 02:12 |
| mafei | 一、openstack互操作简介 | 02:13 |
| mafei | 二、开展openstack互操作目的 | 02:13 |
| mafei | 三、开源社区互操作情况 | 02:13 |
| mafei | 四、互操作应用场景 | 02:13 |
| mafei | 五、互操作遇到的问题 | 02:13 |
| mafei | 1.1 什么是openstack互操作 | 02:14 |
| mafei | 1.2 openstack互操作的内容 | 02:14 |
| mafei | 4.1 LAMP | 02:14 |
| mafei | 4.2 dockerswarm | 02:14 |
| mafei | 4.3 k8s | 02:14 |
| mafei | 4.4 NFV | 02:14 |
| mafei | 4.5 其他 | 02:14 |
| *** Liwei has quit IRC | 02:15 | |
| mafei | 看看有何意见 | 02:15 |
| tongli | good start @Daisy, thanks. | 02:15 |
| tongli | we probably can add that these work loads will be very much targeting the Openstack certification processes. | 02:16 |
| mafei | 另外，大家如果对那部分感兴趣，也可以参与一下 | 02:16 |
| *** changhongli has joined #openstack-meeting-5 | 02:16 | |
| tongli | these word should be part of the purposes of the interop challenge effort. | 02:16 |
| Daisy | mafei: 看起来不错。 | 02:16 |
| mafei | 其他人有无意见 | 02:18 |
| tongli | @mafei, thanks for putting it together, looks nice. maybe add some part like lesson's learnt | 02:18 |
| Daisy | tongli: good suggestion | 02:19 |
| tongli | these section normally are valuable to service providers. | 02:19 |
| Daisy | "五、互操作遇到的问题"改为“五、互操作遇到的问题及建议”？ | 02:19 |
| mafei | sorry, what about lesson's learnt | 02:19 |
| tongli | @mafei, plus, we already have a document in the current project, you can simply copy and paste (maybe translate). | 02:19 |
| mafei | ok,daisy | 02:19 |
| tongli | this is good because we are all part of the interop challenge, so there is no stealing material problem. | 02:20 |
| mafei | good, tongli | 02:20 |
| mafei | ok | 02:20 |
| Daisy | mafei: 就是一些互操作性的经验和最佳实践的分享 | 02:20 |
| *** changhongli has quit IRC | 02:20 | |
| mafei | ok | 02:20 |
| Daisy | mafei: litong说社区里面有一些英文文档了。可以参考 | 02:20 |
| mafei | 恩 明白 | 02:21 |
| *** zuozongming has quit IRC | 02:21 | |
| mafei | 我们还有十分钟 | 02:21 |
| Daisy | 没有意见就下一个话题了？ | 02:21 |
| mafei | 最后一个议题 | 02:21 |
| Lixiang-ZTE | 我觉得是否可以不需要4.5其他?如果我们有openstack社区中没有的场景，就按场景分类单列。 | 02:21 |
| mafei | ok | 02:21 |
| mafei | good | 02:22 |
| Lixiang-ZTE | 防止其他这节成为大杂烩 | 02:22 |
| mafei | 好主意 | 02:22 |
| mafei | #topic Discuss how to show the interop challenge on the global cloud computing summit in April | 02:22 |
| *** openstack changes topic to "Discuss how to show the interop challenge on the global cloud computing summit in April (Meeting topic: interop_challenge)" | 02:22 | |
| Daisy | 好，同意。 | 02:22 |
| mafei | 讨论下4月份峰会的演示 | 02:22 |
| Daisy | 希望能够邀请到重量级的嘉宾来主持这个部分。 | 02:22 |
| mafei | 我们也计划邀请openstack基金会的高层过来主持，但这取决于我们可以展示的东西和效果 | 02:22 |
| Daisy | mafei: 也取决于这个会议的规模 | 02:23 |
| tongli | @mafei, yes, agree | 02:23 |
| mafei | 集思广益 | 02:23 |
| *** fiberhome-joycc has quit IRC | 02:23 | |
| mafei | tongli，你有何建议 | 02:23 |
| Lixiang-ZTE | 谁厉害把jonathan抓来 :-D | 02:24 |
| mafei | 首先得看我们也展示的东西 | 02:24 |
| mafei | 先自身强 | 02:24 |
| Daisy | LAMP不适合再演示一遍了。如果K8s或者NFV能够完成，我感觉新的usecase比较好。 | 02:24 |
| mafei | k8s或NVF时间上是否来得及 | 02:25 |
| Lixiang-ZTE | 具体4月什么时候？ | 02:25 |
| Daisy | 4月19日20日 | 02:25 |
| mafei | 4月19-20日 | 02:25 |
| Lixiang-ZTE | NFV感觉会太紧张 | 02:25 |
| tongli | k8s is an cadidate, but I think number of people attending is the most important factor. | 02:25 |
| Daisy | Boston峰会在这个之后一个月，不知道峰会上打算演示什么。 | 02:25 |
| tongli | @Daisy, do not know yet. | 02:26 |
| mafei | 4月份的峰会规模在3000-4000好像 | 02:26 |
| Daisy | mafei: wow, amazing number | 02:26 |
| *** fiberhome-joycc has joined #openstack-meeting-5 | 02:26 | |
| Lixiang-ZTE | @mafei 这么大啊？ | 02:26 |
| Lixiang-ZTE | 没想到 | 02:26 |
| Daisy | k8s大约什么时间能够给大家测试？ | 02:27 |
| Daisy | tongli: k8s大约什么时间能够开始给大家测试？ | 02:27 |
| mafei | 我们的演示安排在主会场上 | 02:27 |
| mafei | 应该是第二天上午 | 02:27 |
| mafei | 也就是20日上午 | 02:27 |
| *** fiberhome-joycc has quit IRC | 02:28 | |
| tongli | @Daisy, do not know yet, I have few issues to resolve first. | 02:28 |
| tongli | I am hoping I can resolve these issues in next couple of weeks. | 02:28 |
| Daisy | tongli: ok | 02:28 |
| Daisy | 我想大家至少需要提前一个半月开始测试吧？ | 02:28 |
| *** fiberhome-joycc has joined #openstack-meeting-5 | 02:29 | |
| mafei | 时间快要到了，我们是否可以继续讨论 | 02:29 |
| Daisy | mafei: 没人占会议室就可以继续讨论。 | 02:29 |
| mafei | 或者，我们下周三在讨论峰会演示的话题 | 02:30 |
| Daisy | 这个会议是一周一次吗？ | 02:30 |
| mafei | 好像是一周一次的 | 02:30 |
| Daisy | 哦。 | 02:30 |
| Daisy | ok | 02:30 |
| tongli | it was reserved once a week, but I think we decided to have it every other week. | 02:31 |
| fiberhome-joycc | ok | 02:31 |
| tongli | we are free to use it every week though. | 02:31 |
| tongli | #action decide who to update the wiki page | 02:31 |
| mafei | 峰会的演示确实需要好好讨论下，大家也可以在这周内思考下如何演示会更好 | 02:32 |
| *** zuozongming has joined #openstack-meeting-5 | 02:32 | |
| tongli | I think Daisy has been doing that, I prefer an non-ibmer does that for us. | 02:32 |
| Daisy | tongli: 有什么需要更新的啊？我可以去做。:) | 02:32 |
| tongli | the meeting information & the etherpad link need to be updated each week. | 02:33 |
| tongli | like time, etc | 02:33 |
| Daisy | 我去做吧。一回生两回熟。 | 02:33 |
| mafei | 原计划我们想二周一次会 | 02:33 |
| mafei | 但是峰会的事还没有讨论好，所以我们是否下周继续讨论 | 02:34 |
| Daisy | mafei: 会后你可以试一下看能不能更新wiki，如果能的话，以后你可以直接去更新。 | 02:34 |
| mafei | 如何更新？ | 02:34 |
| Daisy | 会后跟你说。 | 02:34 |
| mafei | 好的 | 02:35 |
| mafei | 那好吧，今天的会议就到这儿吧 | 02:35 |
| mafei | 感谢大家的参与 | 02:35 |
| tongli | @Daisy,@mafei, need to end the meeting I think. | 02:35 |
| mafei | i | 02:35 |
| Daisy | 谢谢@mafei, @tongli, all | 02:35 |
| mafei | i know | 02:35 |
| tongli | @mafei, great. | 02:35 |
| mafei | tongli, good night | 02:35 |
| tongli | Thanks a lot. | 02:35 |
| mafei | #endmeeting | 02:36 |
| *** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings" | 02:36 | |
| openstack | Meeting ended Wed Feb 8 02:36:03 2017 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 02:36 |
| openstack | Minutes: http://eavesdrop.openstack.org/meetings/interop_challenge/2017/interop_challenge.2017-02-08-01.30.html | 02:36 |
| openstack | Minutes (text): http://eavesdrop.openstack.org/meetings/interop_challenge/2017/interop_challenge.2017-02-08-01.30.txt | 02:36 |
| openstack | Log: http://eavesdrop.openstack.org/meetings/interop_challenge/2017/interop_challenge.2017-02-08-01.30.log.html | 02:36 |
| tongli | this is very nice, | 02:36 |
| tongli | click on any of the link above to see what it does. | 02:37 |
| tongli | http://eavesdrop.openstack.org/meetings/interop_challenge/2017/interop_challenge.2017-02-08-01.30.html | 02:37 |
| tongli | that link already shows all the action items | 02:37 |
| *** tongli has quit IRC | 02:38 | |
| Lixiang-ZTE | bye | 02:38 |
| *** Lixiang-ZTE has quit IRC | 02:38 | |
| *** mafei has quit IRC | 02:39 | |
| *** fiberhome-joycc has quit IRC | 02:39 | |
| *** xietaotao has quit IRC | 02:39 | |
| *** hongliang has quit IRC | 02:42 | |
| *** liuhaijie has quit IRC | 02:49 | |
| *** makai has quit IRC | 02:51 | |
| *** Daisy has quit IRC | 02:58 | |
| *** WangChangJin has quit IRC | 03:04 | |
| *** Rockyg has quit IRC | 03:12 | |
| *** makai has joined #openstack-meeting-5 | 03:12 | |
| *** makai has quit IRC | 03:15 | |
| *** makai has joined #openstack-meeting-5 | 03:15 | |
| *** wenwen has joined #openstack-meeting-5 | 03:24 | |
| *** wenwen has quit IRC | 03:28 | |
| *** kongwei has quit IRC | 03:30 | |
| *** makai has quit IRC | 03:35 | |
| *** ricolin has joined #openstack-meeting-5 | 03:55 | |
| *** tianquan has quit IRC | 04:31 | |
| *** makai has joined #openstack-meeting-5 | 05:29 | |
| *** tianquan has joined #openstack-meeting-5 | 05:36 | |
| *** makai has quit IRC | 07:43 | |
| *** matrohon has joined #openstack-meeting-5 | 07:48 | |
| *** t2cloud has quit IRC | 08:21 | |
| *** t2cloud has joined #openstack-meeting-5 | 08:21 | |
| *** ralonsoh has joined #openstack-meeting-5 | 08:56 | |
| *** tianquan has quit IRC | 09:01 | |
| *** tianquan has joined #openstack-meeting-5 | 09:01 | |
| *** ralonsoh_ has joined #openstack-meeting-5 | 09:05 | |
| *** ralonsoh has quit IRC | 09:05 | |
| *** tianquan has quit IRC | 09:11 | |
| *** tianquan has joined #openstack-meeting-5 | 09:13 | |
| *** tianquan has quit IRC | 09:22 | |
| *** tianquan has joined #openstack-meeting-5 | 09:23 | |
| *** tianquan has quit IRC | 09:23 | |
| *** ricolin has quit IRC | 09:24 | |
| *** ricolin has joined #openstack-meeting-5 | 09:38 | |
| *** luzC- has joined #openstack-meeting-5 | 09:42 | |
| *** topol_ has joined #openstack-meeting-5 | 09:44 | |
| *** topol has quit IRC | 09:45 | |
| *** luzC has quit IRC | 09:45 | |
| *** luzC- is now known as luzC | 09:45 | |
| *** ralonsoh__ has joined #openstack-meeting-5 | 10:02 | |
| *** ralonsoh_ has quit IRC | 10:04 | |
| *** ralonsoh__ is now known as ralonsoh | 10:06 | |
| *** tianquan has joined #openstack-meeting-5 | 10:09 | |
| *** t2cloud has quit IRC | 10:18 | |
| *** zuozongming has quit IRC | 11:09 | |
| *** ricolin has quit IRC | 11:54 | |
| *** tianquan has quit IRC | 12:46 | |
| *** tianquan has joined #openstack-meeting-5 | 13:30 | |
| *** zhipengh_ has joined #openstack-meeting-5 | 13:31 | |
| *** tianquan has quit IRC | 13:35 | |
| *** ricolin has joined #openstack-meeting-5 | 13:36 | |
| *** zhipengh_ has quit IRC | 13:42 | |
| *** matrohon has quit IRC | 13:44 | |
| *** zhipengh_ has joined #openstack-meeting-5 | 13:45 | |
| *** matrohon has joined #openstack-meeting-5 | 13:50 | |
| *** zhipengh_ has quit IRC | 13:54 | |
| *** HelenYao has joined #openstack-meeting-5 | 13:54 | |
| *** zhipengh_ has joined #openstack-meeting-5 | 13:59 | |
| *** tongli has joined #openstack-meeting-5 | 13:59 | |
| topol_ | Ping dmellado tongli gema zhipengh markvoelker daniela_ebert skazi luzC | 14:00 |
| markvoelker | o/ | 14:00 |
| tongli | o/ | 14:01 |
| dmellado | o/ | 14:01 |
| topol_ | #startmeeting interop_challenge | 14:01 |
| openstack | Meeting started Wed Feb 8 14:01:02 2017 UTC and is due to finish in 60 minutes. The chair is topol_. Information about MeetBot at http://wiki.debian.org/MeetBot. | 14:01 |
| zhipengh_ | o/ | 14:01 |
| openstack | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 14:01 |
| *** openstack changes topic to " (Meeting topic: interop_challenge)" | 14:01 | |
| openstack | The meeting name has been set to 'interop_challenge' | 14:01 |
| HelenYao | o/ | 14:01 |
| topol_ | Hi everyone, who is here for the interop challenge meeting today? | 14:01 |
| topol_ | The agenda for today can be found at: | 14:01 |
| topol_ | # https://etherpad.openstack.org/p/interop-challenge-meeting-2017-02-08 | 14:01 |
| topol_ | We can use this same etherpad to take notes | 14:01 |
| skazi | o/ | 14:01 |
| topol_ | Agenda: | 14:01 |
| topol_ | #topic Review last meeting action items | 14:02 |
| topol_ | #link http://eavesdrop.openstack.org/meetings/interop_challenge/2017/interop_challenge.2017-02-01-14.00.html | 14:02 |
| topol_ | topol to create a ping reminder list for our meeting attendees | 14:02 |
| topol_ | this is done, let me know if I need to add someone to the list | 14:02 |
| topol_ | topol add agenda item for update from China chapter meeting | 14:02 |
| topol_ | this is done as well | 14:02 |
| topol_ | next last meeting action item: | 14:03 |
| topol_ | tongli to try some thing on the patch | 14:03 |
| topol_ | , tong will figure out versions of ansible and shade to be supported by lampstack workload | 14:03 |
| topol_ | tongli any progress on these? | 14:03 |
| tongli | @topol, I have not had time to try different version of ansible /shade on this, heads down on k8s. | 14:03 |
| tongli | @topol, sorry. | 14:04 |
| topol_ | K, no worries, we will keep it on the list :-) | 14:04 |
| tongli | trying to get k8s in a shape that I can submit a patch. | 14:04 |
| dmellado | yep, please, I'll try to take some time to test that out too | 14:04 |
| topol_ | tongli sounds good. | 14:04 |
| dmellado | worst case let's sync on the PTG | 14:04 |
| tongli | @dmellado, thanks. | 14:05 |
| topol_ | Okay, todays agenda which is action packed: | 14:05 |
| *** daniela_ebert has joined #openstack-meeting-5 | 14:05 | |
| topol_ | #topic Patches that need review https://review.openstack.org/#/q/status:open+project:openstack/interop-workloads,n,z | 14:05 |
| *** openstack changes topic to "Patches that need review https://review.openstack.org/#/q/status:open+project:openstack/interop-workloads,n,z (Meeting topic: interop_challenge)" | 14:05 | |
| luzC | o/ | 14:05 |
| tongli | one is the tox thing, and the other is the root access for wordpress deployment in lampstack. | 14:06 |
| topol_ | 2 two patches out there, all please review. anything specific we need to discuss about the patches? | 14:06 |
| tongli | the problem was that if you use root to deploy wordpress, it will fail. | 14:06 |
| topol_ | #action all please review patches #link https://review.openstack.org/#/q/status:open+project:openstack/interop-workloads,n,z | 14:07 |
| tongli | there needs to be an option, china chapter (T2Cloud) submitted that patch. | 14:07 |
| *** gema has joined #openstack-meeting-5 | 14:07 | |
| topol_ | so with #link we are waiting for dmellado to push a new patch? | 14:07 |
| topol_ | er #link https://review.openstack.org/#/c/409180/ | 14:08 |
| dmellado | I'll push a patch as soon as I sync with tongli on the ansible versions | 14:08 |
| topol_ | dmellado, excellent THANKS | 14:08 |
| dmellado | as it is, it would work, but we might want to be more open on that | 14:08 |
| topol_ | #action dmellado to push a new patch for #link https://review.openstack.org/#/c/409180/ | 14:08 |
| topol_ | zhengming will you push a new patch for #link https://review.openstack.org/#/c/430631/ | 14:10 |
| topol_ | ? | 14:10 |
| topol_ | tongli is that a china team patch? | 14:10 |
| tongli | @topol, zhengming's patch is good. that flag is necessary. | 14:10 |
| tongli | @topol, yes, it is. after we run the workload while I was in China, we found this problem, and discussed the patch. | 14:11 |
| topol_ | tongli it has a -1 from markvoelker | 14:11 |
| tongli | yes, since Mark did not know the reason why it is needed, I have answered his question | 14:11 |
| tongli | this is a necessary fix. | 14:11 |
| markvoelker | We should get that kind of information into the commit message though. The commit message really gives no indication about why we're doing this. | 14:12 |
| zhipengh_ | but still need a patch right ? | 14:12 |
| zhipengh_ | agree with mark here | 14:12 |
| tongli | @markvoelker, sure. | 14:12 |
| topol_ | markvoelker +++ was just about to say that | 14:12 |
| *** chandankumar has joined #openstack-meeting-5 | 14:12 | |
| tongli | add a bit of info in the commit msg. Let me add some comment there. | 14:12 |
| chandankumar | \o/ | 14:13 |
| topol_ | #action tongli to follow up to make sure commit message gets updated in https://review.openstack.org/#/c/430631/ | 14:13 |
| dmellado | o/ chandankumar | 14:13 |
| topol_ | K, think we are getting close to the fun stuff :-) | 14:13 |
| topol_ | #topic review last weeks networking choice | 14:14 |
| *** openstack changes topic to "review last weeks networking choice (Meeting topic: interop_challenge)" | 14:14 | |
| topol_ | just FYI, We have decided to use flat GCE like networking choice for our k8s workload | 14:14 |
| topol_ | #topic Huawei (Helen) NFV workload proposal. | 14:14 |
| *** openstack changes topic to "Huawei (Helen) NFV workload proposal. (Meeting topic: interop_challenge)" | 14:14 | |
| HelenYao | Hi everyone | 14:15 |
| topol_ | Hi HelenYao, Welcome! | 14:15 |
| dmellado | hey HelenYao welcome! | 14:15 |
| HelenYao | thx :) | 14:15 |
| zhipengh_ | So I think everyone should already got the slide Helen prepared which I sent to the interop mailinglist | 14:15 |
| topol_ | HelenYao tell us about your NFV Workload proposal | 14:15 |
| HelenYao | sure | 14:15 |
| tongli | @HelenYao, thanks for taking time joining this wg, I saw that you have added the flow to the etherpad, please take us through the steps. | 14:15 |
| HelenYao | Sample Workflow: Run vIMS on OpenStack with OPEN-O | 14:15 |
| HelenYao | 1. Deploy 1 VM and install OPEN-O | 14:15 |
| HelenYao | 2. Deploy 2 VM and install Juju (OpenStack should be able to support Juju) | 14:15 |
| HelenYao | 3. Call the OPEN-O Rest API to upload the NSD and VNFD package(definition files for the network service and VNF) | 14:15 |
| HelenYao | 4. Call the OPEN-O Rest API to deploy the Clearwater vIMS (1 VM) | 14:15 |
| HelenYao | 5. Call the vIMS Rest API to configure Ellis (a specific call number is set for each OpenStack vendor) | 14:16 |
| HelenYao | 6. Show the audience by dialing the specific call number | 14:16 |
| HelenYao | basically, for the nfv, we can demo the call function | 14:16 |
| HelenYao | which is deployed by vIMS - a VNF service | 14:16 |
| dmellado | I would be keen on not using Juju | 14:16 |
| dmellado | can't we use another orchestrator? | 14:16 |
| HelenYao | dmellado: could u explain the reason? | 14:17 |
| zhipengh_ | dmellado any reason why not juju ? | 14:17 |
| HelenYao | open-o is the orchestrator | 14:17 |
| dmellado | because basically, Juju is totally tied to Ubuntu | 14:17 |
| HelenYao | juju is just used to deploy vIMS | 14:17 |
| dmellado | and if we're going to show interop | 14:17 |
| tongli | @demllado, I think similar steps can be done using ansible, but let's not hang on the tools. | 14:17 |
| dmellado | I'd rather use something that would be supported and available for *all* distributions | 14:17 |
| tongli | we just need to figure out what need to be done here. | 14:17 |
| HelenYao | dmellado: yeah, u r making a good point | 14:18 |
| zhipengh_ | agree tongli | 14:18 |
| tongli | we need to figure out what needs to be done here, tools can be chosen later. | 14:18 |
| topol_ | dmellado, so I had the same discussion with markbaker yesterday. He is willing to put some resources to show that juju will run everywhere. I agree that needs to be proven | 14:18 |
| topol_ | But they are willing to try | 14:18 |
| dmellado | we can ellaborate more on that | 14:19 |
| topol_ | The safest thing for us is to try and support some options here | 14:19 |
| dmellado | I'd like to have a look if possible | 14:19 |
| tongli | @zhengming, step 3 and step 4, what are the details there? | 14:19 |
| dmellado | but I don't think that, as of now | 14:19 |
| HelenYao | we can define the main flow first and find tools to fit in | 14:19 |
| dmellado | another distributions wuold spend resources on juju, tbh | 14:19 |
| tongli | when you say call OPEN-O Rest API to upload NSD and VNFD package, what do they mean specifically? | 14:20 |
| HelenYao | for step 3, to deploy a vnf, a topology is needed to define the network service, that is done by NSD and VNFD | 14:20 |
| topol_ | so the safe thing to do is do have ansible which we know works everywhere but let folks also try to see if juju will run everywhere | 14:20 |
| HelenYao | it is basically tosca yaml | 14:20 |
| topol_ | HelenYao, step 3 uses tosca yaml? | 14:21 |
| zhipengh_ | yes | 14:21 |
| HelenYao | the open-o is the orchestrator to deploy the service and juju is to managne all deployed vnfs | 14:21 |
| HelenYao | topol_: yes | 14:21 |
| * topol_ gold star for HelenYao! I started that project years ago :-) | 14:21 | |
| dmellado | heh, I need to check on open-o | 14:21 |
| dmellado | is it under openstack/ github's? | 14:22 |
| zhipengh_ | #link https://wiki.opnfv.org/display/PROJ/Opera+Project | 14:22 |
| HelenYao | topol_: wow, u started tosca, brilliant | 14:22 |
| zhipengh_ | open-o is an individual community | 14:22 |
| luzC | me too | 14:22 |
| topol_ | HelenYao, actually the heat translator project, not TOSCA | 14:22 |
| luzC | I need to check it out too | 14:22 |
| zhipengh_ | topol_ i worked with sahdev vert closely on that | 14:22 |
| topol_ | gold star for zhipengh_ as well | 14:23 |
| topol_ | :-) | 14:23 |
| topol_ | very nice | 14:23 |
| zhipengh_ | dmellado luzc please follow the link I provided | 14:23 |
| zhipengh_ | opera is opnfv integration project for open-o | 14:23 |
| zhipengh_ | it got all the information you need | 14:24 |
| zhipengh_ | topol_ thx :) | 14:24 |
| topol_ | HelenYao, zhipengh any more details you can provide? | 14:24 |
| HelenYao | clearwater mentioned here is also an open source project for vIMS | 14:25 |
| HelenYao | we can count on it to make a call | 14:25 |
| topol_ | HelenYao so what is the specific network service that is started by all this orchestration? | 14:26 |
| HelenYao | to make a call to a vIMS deployed by a openstack is good candidate for nfv demo | 14:26 |
| zhipengh_ | topol_ IMS | 14:27 |
| HelenYao | the orchetrator will deploy the all topology of vIMS | 14:27 |
| dmellado | thsnks zhipengh_ , I'll take a look | 14:27 |
| tongli | what is vIMS? | 14:27 |
| topol_ | HelenYao, zhipengh please excuse my limited NFV background. what does IMS do? | 14:27 |
| HelenYao | http://www.projectclearwater.org/technical/clearwater-architecture/ | 14:27 |
| zhipengh_ | virtual IP Multimedia Subsystem | 14:27 |
| topol_ | well thats sounds pretty impressive | 14:28 |
| zhipengh_ | tongli it is a classic core network service | 14:28 |
| dmellado | heh, then I guessed it right | 14:28 |
| dmellado | was just wondering about the v | 14:28 |
| topol_ | Im impressed | 14:28 |
| zhipengh_ | topol_ you could dial calls via SIP based client, where IMS will handle the SIP protocal in the core network | 14:29 |
| HelenYao | v stands for virtualized version | 14:29 |
| zhipengh_ | so basically it is a VoIP function | 14:29 |
| zhipengh_ | something like that | 14:29 |
| * topol_ I get all dazzled by worklaods that have multimedia in their name | 14:29 | |
| zhipengh_ | IMS was a hot topic ten years ago | 14:29 |
| topol_ | zhipengh_, HelenYao, here are my thoughts. | 14:30 |
| dmellado | topol_: I always recall about those old pentium's MMX whenever I listen that word | 14:30 |
| topol_ | This looks like an exciting workload and we really wanted an NFV workload. I would love to see this submitted as a patch to the repository. | 14:31 |
| dmellado | +1 zhipengh_ HelenYao would you mind drafting this as a patch? | 14:31 |
| dmellado | I was wondering if we should have blueprints | 14:31 |
| dmellado | I'd really love to discuss those implementation details over something concrete and not on the irc | 14:31 |
| zhipengh_ | topol_ for patch you mean just for the scripts or the actual vIMS and juju source code ? | 14:31 |
| HelenYao | what is expected in the patch? all the scripts to run whole workable flow | 14:32 |
| topol_ | Now for reasons that will become clear later in the agenda, we need to make sure everyone can run this. Hint Interop Challenge phase 2 Boston Summit, as requested by the foundation | 14:32 |
| zhipengh_ | dmellado we could schedule ZOOm calls :P | 14:32 |
| dmellado | topol_: tongli would it be reasonable to expect a blueprint? | 14:32 |
| dmellado | zhipengh_: ZOOm? | 14:32 |
| zhipengh_ | ZOOM, the anti-gotomeeting-webex | 14:32 |
| dmellado | heh xD | 14:32 |
| topol_ | dmellado, we will need a blueprint/ some for of description. that will help everyone. I fine with it being submitted with the patch | 14:32 |
| tongli | @dmellado, a blueprint will be nice. so that we can comment and agree on by our wg members. | 14:33 |
| dmellado | then can we add an action on zhipengh_ and HelenYao to submit a blueprint? | 14:33 |
| HelenYao | what is a blueprint? sorry, I am new here :-) | 14:33 |
| tongli | consider other companies are also willing to contribute. that is one of the things china chapter has talked about last night. | 14:33 |
| topol_ | Are folks wanting a blueprint to provide more description or because they want a more formal approval process? | 14:34 |
| tongli | @HelenYao, I can help with that. we can talk offline on that. | 14:34 |
| topol_ | I do have one issue with this | 14:34 |
| HelenYao | tongli: neat | 14:34 |
| dmellado | topol_: from my side, maybe more description and comments there | 14:34 |
| zhipengh_ | tongli do we need to register the bp on the launchpad ? | 14:34 |
| tongli | @topol, I would like the blueprint just to clarify things and more description. | 14:34 |
| dmellado | I'd like to have a deeper look at it after checking some stuff ;) | 14:34 |
| topol_ | demellado that is what I am thinking. | 14:34 |
| *** rarcea has joined #openstack-meeting-5 | 14:35 | |
| tongli | @demellado, @topol_, I think we are going the same direction on the blueprint | 14:35 |
| topol_ | My one issue is the juju needs to be optional and can replaced with ansible if for some reason juju will not run everywhere. | 14:35 |
| dmellado | +1 | 14:35 |
| tongli | moving forward, we probably should have two workload implementations. | 14:35 |
| zhipengh_ | topol_ we could look at alternatives, but ansible might not be the answer as well | 14:36 |
| dmellado | but would it make sense to spend time on juju | 14:36 |
| tongli | if one is done, doing the other should be fairly easy | 14:36 |
| dmellado | if in the end it won't be interoperable | 14:36 |
| dmellado | ? | 14:36 |
| HelenYao | I think openstack heat could be a replacement for juju | 14:36 |
| rarcea | dmellado: +1 | 14:36 |
| tongli | well, regardless which tool we use, the end results have to be the same. | 14:36 |
| topol_ | So here is where my dream is where I want to be. We show we have workloads that run on all clouds and we show we have more that one autoamtion tool (thnk ansible,juju) that work on all clouds | 14:36 |
| tongli | otherwise, we just defeated ourselves. | 14:36 |
| topol_ | this desire originally mentioned by markvoelker way back when | 14:37 |
| dmellado | I'd rather use heat/ansible | 14:37 |
| rarcea | dmellado: +1 for heat | 14:37 |
| dmellado | markvoelker: around? any reason for the juju thing? | 14:37 |
| zhipengh_ | heat + heat-translator could be the alternative | 14:37 |
| topol_ | dmellado markvoelker wanted multiple tools not juju specifically | 14:37 |
| markvoelker | I don't recall asking for Juju specifically. I do recall saying we want to not be tied to any particular config management tool | 14:37 |
| topol_ | markvoelker yes, I tried to captrue that acccurately | 14:38 |
| dmellado | topol_: I understand that, but my concern is that if we don't narrow the scope in the end we won't ever end it ;) | 14:38 |
| markvoelker | Basically: if we find problems with a particular tool in terms of it's ability to provision workloads on OpenStack clouds, shedding light on those is actually a good thing so they can be addressed | 14:38 |
| HelenYao | even chef, docker compose can be an option. We have all kinds of tools | 14:38 |
| markvoelker | My concern there is primarily on the OpenSTack side rather than than guest though. | 14:39 |
| topol_ | dmellado, so I need to be risk averse here. ideally we have a path that has a high level of confidence works everywhere | 14:39 |
| dmellado | topol_: markvoelker I see your point | 14:39 |
| dmellado | but then, I'd start with some tool that would work on every distro | 14:39 |
| markvoelker | E.g. if ToolX can't provision VM's on 6/10 OpenStack clouds b/c it uses an archaic API version or something, that's a problem | 14:39 |
| dmellado | and and a fallback | 14:39 |
| tongli | man , can we not talk about tools today, my head really hurts. | 14:39 |
| HelenYao | one thing to mention, juju is a verified VNFM. it takes time to evaluate other tools as VNFM | 14:39 |
| dmellado | i.e. heat/ansible | 14:40 |
| topol_ | at the same time I need to let markbaker kick tires on juju to see if it will really run on lots of clouds like he claims | 14:40 |
| dmellado | but if they submit the blueprint we can modify it | 14:40 |
| dmellado | so I won't block the conversation here ;) | 14:40 |
| markvoelker | If the workloads requires you to boot a Fedora VM, I'm less concerned about it because most clouds will be able to boot VM's (regardless of whther it's Fedora or something else) | 14:40 |
| dmellado | would this work for you too rarcea markvoelker ? | 14:40 |
| topol_ | do the issues im trying to worry about/balance make sense? | 14:41 |
| dmellado | topol_: yep, they would for me, just that I'd try to go for tools that would be available in most clouds | 14:41 |
| markvoelker | topol_: Yes. Again, I'm most concerned with the bits that touch OpenStack and less concerned with the contents of the workload itself. | 14:41 |
| zhipengh_ | tongli where should we submit the BP ? have a new spec folder under the interop-workload repo ? | 14:42 |
| *** chandankumar has left #openstack-meeting-5 | 14:43 | |
| topol_ | markvoelker, are you saying the juju is not scary cause int inside the workload? | 14:43 |
| topol_ | err its inside the workload? | 14:43 |
| tongli | out project has a page for submit blueprint. | 14:43 |
| tongli | let me find the link. | 14:43 |
| tongli | https://blueprints.launchpad.net/interop-workloads | 14:44 |
| markvoelker | topol_: If it's being used to spin up infrastructure within OpenSTack and can do that across many OPenStack clouds, I'm fine with that. If this particular workload requires that the guests be one OS or another, I'm even ok with that. | 14:44 |
| tongli | that is our launchapd site, where we can file bugs, blueprints. | 14:44 |
| zhipengh_ | got it thx tongli | 14:44 |
| topol_ | in any case I think we need to get it submitted and folks can see if it runs in their clouds or not. | 14:45 |
| tongli | @topol_, sure, we should have a blueprint for this considering that people have quite different views of NFV. | 14:45 |
| tongli | consolidate it a bit is a good thing. | 14:46 |
| topol_ | if juju has issues markbaker promised to provide a rover to help other clouds. But I also like backup options.. | 14:46 |
| dmellado | +1 on the blueprint | 14:46 |
| *** elynn_ has joined #openstack-meeting-5 | 14:46 | |
| topol_ | so everyone okay with we move forward with the blueprint? | 14:46 |
| topol_ | can the patch be submitted concurrently with the blueprint? Any concerns doing both? | 14:47 |
| dmellado | topol_: well, I'd implement the patch after agreeing on the blueprint | 14:48 |
| dmellado | both of them can be sumitted at a time | 14:48 |
| tongli | @topol_, blueprint first please | 14:48 |
| dmellado | but the patch should be modified along the requirements on the blueprint | 14:48 |
| dmellado | IMHO | 14:48 |
| topol_ | k, lets see a blueprint first | 14:48 |
| tongli | consider the patch may take some time to complete | 14:48 |
| gema | tongli: I get an error when I open that link | 14:49 |
| gema | LAunchpad doesn't seem to know how interop challenge workloads tracks feature planning | 14:49 |
| topol_ | tongli+++ I wasnt sure if the patch was close. Blueprints are used to save the patch committer pain and misery of submitting something that then has the wrong design/architetcure | 14:49 |
| tongli | the blueprint page? | 14:49 |
| gema | yep, you will have to go into the settings and tell it you want to use blueprints | 14:49 |
| tongli | @topol_, exactly, we should have the blueprint first. | 14:49 |
| topol_ | #action HelenYao, zhipengh_,tongli to work together to get a blueprint submitted | 14:50 |
| tongli | I am sure other companies wanting to contribute to NFV might have some say to it. so let's have an agreement on the content first. | 14:50 |
| topol_ | tongli+++ | 14:50 |
| dmellado | I can't say more ++ on it ;) | 14:50 |
| topol_ | k so how will we do our blueprints, we going to have a specs-folder and review blueprint in there like they are code? | 14:51 |
| tongli | https://blueprints.launchpad.net/interop-workloads @gema, you can not open it? | 14:51 |
| zhipengh_ | topol_ what i asked earlier | 14:51 |
| dmellado | I'd go for that, I guess it'd be easier than spawning a new repo | 14:52 |
| tongli | @topol_, we do blueprint on the launchpad page. | 14:52 |
| zhipengh_ | tongli that is for registering | 14:52 |
| topol_ | tongli yes but thats old school | 14:52 |
| zhipengh_ | tongli the actual BP rst file needs to go somewhere | 14:52 |
| topol_ | register there but reveiw comment in some form of repository | 14:52 |
| zhipengh_ | yep | 14:52 |
| topol_ | for example, #link https://review.openstack.org/#/q/status:open+project:openstack/keystone-specs,n,z | 14:53 |
| tongli | hmmm, ok, I thought we create it there like create bugs. | 14:53 |
| tongli | hmmm. ok, | 14:53 |
| topol_ | tongli, you register it there but then look at the contents of https://review.openstack.org/#/q/status:open+project:openstack/keystone-specs,n,z | 14:53 |
| topol_ | to keep life simple, should we just have a specs folder? | 14:54 |
| *** tianquan has joined #openstack-meeting-5 | 14:54 | |
| topol_ | and not a spearate repo? | 14:54 |
| dmellado | topol_: yep | 14:54 |
| tongli | so, we create a new folder in the project for blueprint | 14:54 |
| dmellado | +1 on the folder | 14:54 |
| dmellado | maybe within docs | 14:54 |
| dmellado | and I can tweak a patch for tox to generate the docs | 14:54 |
| topol_ | dmellado, can you set up the specs folder for us? | 14:54 |
| dmellado | yep, I'll put a patch for that, no worries | 14:55 |
| tongli | can we just create /bp at the root of the project folder? | 14:55 |
| dmellado | I'll do that after the meeting | 14:55 |
| topol_ | dmellado very nice, I love the autogenerate of docs | 14:55 |
| topol_ | K, folks I only have 5 mins I need to move on | 14:55 |
| topol_ | let me jump ahead | 14:55 |
| topol_ | #topic PTG Meeting Agenda and Logistics: Meeting Feb 21, Tuesday afternoon 1:30 - 5:00 RefStack room: | 14:56 |
| topol_ | Agenda and participant List: https://etherpad.openstack.org/p/interop-challenge-meeting-2017-01-11 | 14:56 |
| topol_ | PTG Meeting will now include meeting with Mark Collier to discuss showcasing Interop Challenge Phase 2 in Boston | 14:56 |
| *** openstack changes topic to "PTG Meeting Agenda and Logistics: Meeting Feb 21, Tuesday afternoon 1:30 - 5:00 RefStack room: (Meeting topic: interop_challenge)" | 14:56 | |
| topol_ | so good news but bad for my blodd pressure | 14:56 |
| topol_ | Mark Collier will meet with us at PTG, the foundation wants to do something with InteropChallenge in Boston | 14:56 |
| dmellado | heh, live demo again? | 14:57 |
| topol_ | so yay more visibility. I thought we could stay under the radar but the bug stage is calling us again | 14:57 |
| *** tiantian has joined #openstack-meeting-5 | 14:57 | |
| topol_ | dmellado, looking like something like that. we can discuss at the PTG with Mark | 14:57 |
| topol_ | but understand now I have to go back to making sure we deliver. | 14:58 |
| *** nilles has joined #openstack-meeting-5 | 14:58 | |
| dmellado | let's discuss it there too | 14:58 |
| topol_ | so I worry about things like juju vs ansible etc | 14:58 |
| dmellado | but if that's the case we ought to try small milestones | 14:58 |
| *** tianquan has quit IRC | 14:58 | |
| topol_ | dmellado agreed | 14:58 |
| dmellado | and try to focus on small enhancements | 14:58 |
| topol_ | need some MVPs | 14:58 |
| *** ramishra has joined #openstack-meeting-5 | 14:59 | |
| topol_ | so lets see how we are with workload progress at the PTG | 14:59 |
| dmellado | sounds fine for me ;) | 14:59 |
| topol_ | Im out of time, tongli if we have an update on chapter it needs to wait till next week | 14:59 |
| gema | o/ | 15:00 |
| topol_ | #action tongli to update on china chapter | 15:00 |
| gema | bye | 15:00 |
| tongli | that is fine. | 15:00 |
| zhipengh_ | one thing yall need to keep in mind is that NFV workload will run on NFV private clouds, that means for verified VNFM like Juju, chances are majority of the NFV private clouds should already support that | 15:00 |
| topol_ | #endmeeting | 15:00 |
| *** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings" | 15:00 | |
| openstack | Meeting ended Wed Feb 8 15:00:25 2017 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 15:00 |
| openstack | Minutes: http://eavesdrop.openstack.org/meetings/interop_challenge/2017/interop_challenge.2017-02-08-14.01.html | 15:00 |
| openstack | Minutes (text): http://eavesdrop.openstack.org/meetings/interop_challenge/2017/interop_challenge.2017-02-08-14.01.txt | 15:00 |
| openstack | Log: http://eavesdrop.openstack.org/meetings/interop_challenge/2017/interop_challenge.2017-02-08-14.01.log.html | 15:00 |
| *** therve_ has joined #openstack-meeting-5 | 15:00 | |
| ricolin | #startmeeting heat | 15:01 |
| openstack | Meeting started Wed Feb 8 15:01:08 2017 UTC and is due to finish in 60 minutes. The chair is ricolin. Information about MeetBot at http://wiki.debian.org/MeetBot. | 15:01 |
| openstack | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 15:01 |
| *** openstack changes topic to " (Meeting topic: heat)" | 15:01 | |
| openstack | The meeting name has been set to 'heat' | 15:01 |
| ricolin | #topic roll call | 15:01 |
| *** openstack changes topic to "roll call (Meeting topic: heat)" | 15:01 | |
| ramishra | hi | 15:01 |
| therve_ | Hey | 15:01 |
| tiantian | hi | 15:01 |
| *** cwolferh has joined #openstack-meeting-5 | 15:02 | |
| cwolferh | o/ | 15:02 |
| elynn_ | hi | 15:02 |
| nilles | hi | 15:02 |
| *** zhipengh_ has quit IRC | 15:02 | |
| *** zaneb has joined #openstack-meeting-5 | 15:03 | |
| zaneb | hola | 15:03 |
| ricolin | #topic adding items to agenda | 15:03 |
| ricolin | #link https://wiki.openstack.org/wiki/Meetings/HeatAgenda#Agenda_.282017-02-08_1500_UTC.29 | 15:03 |
| *** openstack changes topic to "adding items to agenda (Meeting topic: heat)" | 15:03 | |
| ricolin | BTW our meeting now change to Wednesday 1500 on openstack-meeting-5 weekly :) | 15:05 |
| zaneb | ricolin: so it's always in this channel now? | 15:05 |
| ricolin | yes | 15:05 |
| * zaneb leaves #openstack-meeting-4 | 15:05 | |
| ricolin | lol | 15:05 |
| ricolin | #topic Docs liaison | 15:06 |
| *** openstack changes topic to "Docs liaison (Meeting topic: heat)" | 15:06 | |
| ramishra | so we retruned slots for busy meeting rooms:) | 15:06 |
| ricolin | We need a Docs liaison | 15:07 |
| *** daniela_ebert has quit IRC | 15:07 | |
| ricolin | Randle signed off that duty | 15:07 |
| ricolin | #link https://wiki.openstack.org/wiki/CrossProjectLiaisons#Documentation | 15:08 |
| ricolin | Any one would like to take over? | 15:08 |
| ricolin | I suppose it will not be too much works to do | 15:08 |
| zaneb | I have my hands full failing at being the stable-branch liason ;) | 15:09 |
| therve_ | I'm good too :) | 15:09 |
| ricolin | zaneb: Keep it full!! | 15:09 |
| ramishra | Don't know what's the expectation from the docs team. Seems no one is volunteering... | 15:11 |
| ramishra | ricolin: ok, I'll try do it | 15:12 |
| zaneb | do we actually have any docs that are maintained outside of our local repo any more? | 15:12 |
| ricolin | ramishra: sold! | 15:12 |
| ricolin | zaneb: I think not | 15:12 |
| ricolin | ramishra: Thanks! | 15:13 |
| ricolin | ok | 15:13 |
| ricolin | move on | 15:13 |
| ricolin | #topic PTG Schedule discuss | 15:13 |
| *** openstack changes topic to "PTG Schedule discuss (Meeting topic: heat)" | 15:13 | |
| ricolin | #link https://etherpad.openstack.org/p/heat-pike-ptg-sessions | 15:13 |
| ramishra | ricolin: Is there a specific etherpad for cross-project topics? | 15:13 |
| ricolin | ramishra: appears we have to orginize the cross project ourself | 15:14 |
| ramishra | Have not seen one. Wanted to add the keystone federation releated topic | 15:14 |
| ricolin | I do put some idea below | 15:14 |
| ricolin | thinking maybe one with Mistral, zaqar, TripleO? | 15:15 |
| ricolin | for Mistral + heat case? | 15:15 |
| ramishra | We need the keystone guys | 15:15 |
| ricolin | ramishra: Okey, let's put that in, and I will help to get keystone team to discuss that session:) | 15:16 |
| *** tongli has quit IRC | 15:16 | |
| ramishra | ricolin: ok | 15:16 |
| ricolin | And how about Mistral + heat case? | 15:17 |
| ricolin | anyone would like it? | 15:18 |
| zaneb | sure, but I'm not clear on exactly what the topic would be | 15:20 |
| ricolin | I actually get that idea from a TripleO session | 15:20 |
| ricolin | therve_: you're the one to work on it right? | 15:20 |
| zaneb | a discussion about the "How to run mistral workflows via templates" thread might be helpful | 15:21 |
| ricolin | Also I would like to put a session for cross project feedback from other teams who use heat? | 15:21 |
| therve_ | ricolin, The workflow execution one? | 15:21 |
| ricolin | therve_: yes | 15:21 |
| therve_ | I'm helping yeah. There is a tripleo session, maybe we can join it | 15:21 |
| ricolin | zaneb: agree:) | 15:21 |
| *** fengxia41103 has joined #openstack-meeting-5 | 15:22 | |
| ricolin | therve_: yeah, it might be a session for TripleO+ heat+mistral+zaqar right:)? | 15:22 |
| therve_ | No zaqar no | 15:22 |
| ricolin | therve_: fine! | 15:23 |
| ricolin | And how about a feedback session from other teams who use heat? | 15:23 |
| ricolin | Magnum, sahara, TripleO, etc. | 15:23 |
| zaneb | ricolin: +1. we made some performance improvements in Ocata for big stacks and it would be good to hear about how much it did/didn't help | 15:24 |
| zaneb | + we have more plans to Pike to tell them about | 15:24 |
| ricolin | zaneb: great idea:) | 15:25 |
| *** gema has left #openstack-meeting-5 | 15:25 | |
| ricolin | I assume we will do all topic from the etherpad | 15:26 |
| ricolin | but not sure how we do Property Translation with out peter | 15:26 |
| zaneb | is it confirmed that Peter is not coming, or is it just that nobody has filled in the attendee list? | 15:27 |
| ricolin | right! Can guys please put you name in attendee list :) | 15:28 |
| ricolin | #link https://etherpad.openstack.org/p/heat-pike-ptg-sessions | 15:28 |
| ricolin | it will help us to make sure who will be there | 15:28 |
| ricolin | Will anyone going to host 'Property Translation' session in PTG? | 15:30 |
| fengxia41103 | Hi.. this is my first time here.. just want to sit in and learn about this project :) | 15:30 |
| ricolin | fengxia41103: happy to have you here:) | 15:31 |
| fengxia41103 | thank you ricolin :) | 15:31 |
| *** tongli has joined #openstack-meeting-5 | 15:31 | |
| ramishra | ricolin: Peter is right person to host that session unless he is not joining us at PTG | 15:32 |
| ricolin | ramishra: yeah, but seems Peter will not be there:( | 15:33 |
| ramishra | ricolin: he has number of patches up for review for that, may be he can join virtually or something like that. | 15:34 |
| ricolin | Okey, we sure can have that session | 15:34 |
| ricolin | and one more thing for PTG, Time schedule | 15:35 |
| ricolin | I'd put a daft time schedule in the end of Etherpad | 15:36 |
| ricolin | Any idea on that? | 15:36 |
| ricolin | And of curse There will be beer sessions:) | 15:37 |
| fengxia41103 | hooray... | 15:38 |
| ricolin | Okey, than will send the schedule out once we confirm with other teams on cross project | 15:40 |
| ricolin | Feel free to give any suggestion | 15:40 |
| ricolin | #topic Open discussion | 15:41 |
| *** openstack changes topic to "Open discussion (Meeting topic: heat)" | 15:41 | |
| ricolin | Any other topic?:) | 15:41 |
| ramishra | btw, if you've not noticed, we have moved all dsvm jobs to use apache by default and added a voting non-apache job | 15:43 |
| ricolin | ramishra: it seems works fine on gate | 15:45 |
| ramishra | ricolin: yes | 15:46 |
| ricolin | Okey, any other discuss? | 15:47 |
| ramishra | should we skip test_create_stack_with_multi_signal_waitcondition? it seems to be failing more often than not. | 15:47 |
| ramishra | most of the job failures are becuase of it. | 15:47 |
| ramishra | we don't seem to have a solution for it yet | 15:48 |
| ricolin | ramishra: IIRC we adjust the timeout for it | 15:48 |
| ricolin | ramishra: seems not help much? | 15:48 |
| ramishra | It's the ConcurrentTransaction error when setting metadata | 15:49 |
| ramishra | therve_, zaneb ? | 15:49 |
| zaneb | we need to fix that one so badly | 15:49 |
| ricolin | maybe skip for now? | 15:50 |
| ramishra | we can keep it, but 9/10 failures are becuase of it and it seems to be somewhat only happening for non-convergence | 15:51 |
| zaneb | https://review.openstack.org/#/c/321783/ should help, but it just makes it worse in convergence | 15:53 |
| ramishra | We know that issue and unless we fix it soon, we should think about disabling it | 15:53 |
| ricolin | Is there anyone volunteer to track on this issue? | 15:55 |
| ricolin | I will track on it, and if we can't fix it soon (not even in PTG) maybe we should disable it first | 15:57 |
| ricolin | Okey, anything else?:) | 15:58 |
| ricolin | Than thanks you all to attend, hope you all have a good day! | 15:59 |
| ricolin | #endmeeting | 15:59 |
| *** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings" | 15:59 | |
| openstack | Meeting ended Wed Feb 8 15:59:33 2017 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 15:59 |
| openstack | Minutes: http://eavesdrop.openstack.org/meetings/heat/2017/heat.2017-02-08-15.01.html | 15:59 |
| openstack | Minutes (text): http://eavesdrop.openstack.org/meetings/heat/2017/heat.2017-02-08-15.01.txt | 15:59 |
| openstack | Log: http://eavesdrop.openstack.org/meetings/heat/2017/heat.2017-02-08-15.01.log.html | 15:59 |
| fengxia41103 | thank you ricolin | 15:59 |
| *** fengxia41103 has quit IRC | 16:00 | |
| *** nilles has left #openstack-meeting-5 | 16:00 | |
| *** therve_ has left #openstack-meeting-5 | 16:03 | |
| *** Rockyg has joined #openstack-meeting-5 | 16:04 | |
| *** matrohon has quit IRC | 16:15 | |
| *** ricolin has quit IRC | 16:50 | |
| *** topol_ is now known as topol | 17:33 | |
| *** rarcea has quit IRC | 17:52 | |
| *** tianquan has joined #openstack-meeting-5 | 17:56 | |
| *** tianquan has quit IRC | 18:00 | |
| *** ralonsoh has quit IRC | 18:02 | |
| *** MarkAtwood has quit IRC | 18:35 | |
| *** hogepodge has quit IRC | 18:45 | |
| *** uli-k has quit IRC | 18:45 | |
| *** elynn_ has quit IRC | 19:04 | |
| *** rarcea has joined #openstack-meeting-5 | 19:22 | |
| *** MarkAtwood has joined #openstack-meeting-5 | 19:36 | |
| *** uli-k has joined #openstack-meeting-5 | 19:43 | |
| *** tianquan has joined #openstack-meeting-5 | 20:07 | |
| *** tianquan has quit IRC | 20:13 | |
| *** hogepodge has joined #openstack-meeting-5 | 20:19 | |
| *** matrohon has joined #openstack-meeting-5 | 20:28 | |
| *** tianquan has joined #openstack-meeting-5 | 21:19 | |
| *** matrohon has quit IRC | 21:22 | |
| *** tianquan has quit IRC | 21:44 | |
| *** tianquan has joined #openstack-meeting-5 | 21:50 | |
| *** tianquan has quit IRC | 21:54 | |
| *** tianquan has joined #openstack-meeting-5 | 23:51 | |
| *** rarcea has quit IRC | 23:55 | |
| *** tianquan has quit IRC | 23:57 | |
Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!