Wednesday, 2017-03-22

*** kongwei_ has joined #openstack-meeting-500:53
*** kongwei_ has quit IRC00:57
*** Guest31128 has joined #openstack-meeting-501:06
*** davidshi has joined #openstack-meeting-501:21
*** Daisy has joined #openstack-meeting-501:26
*** Guest31128 is now known as kongwei01:29
*** LiXiang has joined #openstack-meeting-501:29
*** kongwei_ has joined #openstack-meeting-501:30
Daisywe will start China chapter InterOp meeting soon01:30
Daisy#startmeeting interop_challenge01:31
openstackMeeting started Wed Mar 22 01:31:03 2017 UTC and is due to finish in 60 minutes.  The chair is Daisy. Information about MeetBot at http://wiki.debian.org/MeetBot.01:31
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.01:31
*** openstack changes topic to " (Meeting topic: interop_challenge)"01:31
openstackThe meeting name has been set to 'interop_challenge'01:31
Daisy早上好01:31
kongwei早上好01:31
Daisy谁在会议室里参加中国地区的互操作项目会议。01:31
Daisy早上好, kongwei01:31
Daisy不知道还有没有其他人来参加,稍微等一两分钟。01:32
davidshi01:32
Daisy早 davidshi01:32
kongwei史天和李响应该都在的01:32
*** kongwei_ has quit IRC01:33
kongweidavidshi,第一次见面,你好。我是zte的孔炜01:33
*** tongli has joined #openstack-meeting-501:33
kongwei李彤,您好01:33
davidshihi,我是中联润通的史天,之前在HPE做OpenStack01:33
Daisy好的,现在到会的有zte孔炜和李响, IBM Daisy和tongli, 中联润通史天01:34
tonglio/01:34
Daisy今天马飞因为连不上IRC,由我来代他主持。01:34
Daisy#topic Review last meeting action items01:34
*** openstack changes topic to "Review last meeting action items (Meeting topic: interop_challenge)"01:34
Daisy#link http://eavesdrop.openstack.org/meetings/interop_challenge/2017/interop_challenge.2017-03-08-01.30.html01:35
DaisyAction items01:35
Daisy1.     easystack to finish LAMP test by next week01:35
Daisy2.     all to start k8s test in this week01:35
Daisy3.     all to finish k8s test by next two weeks01:35
DaisyEasystack的代表在的话,请说句话。01:35
Daisy其他家的代表,请将将k8s的测试进展。01:35
Daisy@kongwei @davidli01:35
Daisy@davidshi01:36
kongweidaisy,我有份ems去拿,出去一下。ZTE完成了ubuntu 16上的k8s测试01:36
Daisywonderful!01:36
kongwei我暂时用手机上irc01:36
*** liuyuqi has joined #openstack-meeting-501:36
Daisykongwei, 听说你们改了一些代码,等你回来方便讲一下吗?01:36
*** Wei_Liu has joined #openstack-meeting-501:36
kongwei好的。01:36
*** kongwei_ has joined #openstack-meeting-501:36
Wei_LiuMorning01:36
Daisy早上好Wei_Liu01:37
Daisy我们正谈到各家的测试进展。01:37
DaisyWei_Liu, 你们开始测试k8s了吗?01:37
*** zuozongming has joined #openstack-meeting-501:38
Wei_LiuEasystack 完成了LAMP,正在测k8s的ubuntu01:38
Daisygood work, Wei_Liu !01:38
Daisy谢谢,非常棒的进展。01:38
Daisyzuozongming,早上好。01:38
*** mafei has joined #openstack-meeting-501:38
zuozongming早上好,早上堵车不好意思来晚了01:39
Daisyzuozongming,请讲讲云英的测试进展,开始测试k8s了吗?01:39
Daisymafei来了01:39
mafei我通过手机进来了01:39
*** liuyuqi has quit IRC01:39
zuozongming正在测试k8s01:39
*** liuyuqi has joined #openstack-meeting-501:39
Daisy太好了,我们正在谈测试进展。ZTE完成了 K8s,不过修改了一些代码,一会我们谈一下;Easystack完成了LAMP;云英和EasyStack都在进行K8s的测试。01:40
*** mafei has quit IRC01:40
Daisy等kongwei回来听听他讲讲k8s测试时碰到的问题,以及他的解决方法。01:41
Wei_Liucool01:41
Daisytongli: 可以给我们谈谈现在k8s 测试脚本的开发进展吗?01:41
tonglidaisy, it is now finished.01:41
Daisy选择了哪个app ?01:42
tongliI have also made changes so that you can use local repo.01:42
tonglicockroachdb cluster.01:42
Daisygreat progress.01:42
tongliyou do not have to access container repos to finish the workload.01:42
Daisy波士顿峰会演示会使用CentOS吗?01:42
Daisy几个节点?01:43
tongliI made some changes, so that you can setup a local http server to hold things needed.01:43
tongliit will run very fast,01:43
tongliI think doing at least 5 nodes.01:43
kongwei太好了。01:43
tonglimeaning 5 VMs.01:43
tonglisorry, I mean 6 VMs.01:44
tongli5 cockroachdb nodes.01:44
Wei_Liutongli: vm01:44
Daisykongwei你现在方便了吗?讲讲你在测试k8s的时候碰到的问题和解决办法。会场上的Easystack和云英都正在进行中。01:44
Wei_Liuvm 的配置有要求吗01:44
kongwei我已经回到办公室了01:44
tongliVM must be coreos openstack image (that is what boston summit requires)01:45
tonglibut the workload can also use Ubuntu 16.xx image.01:45
tonglino other requirements.01:45
Daisyok01:45
Daisy谢谢李彤的更新。这些信息对于想要在波士顿峰会演示的厂家非常有帮助。01:46
Daisykongwei请你讲讲吧。01:46
tongliif I use total of 6 VM, it will finish in about 6 minutes.01:46
kongwei好的,我使用的是一周前的版本。可能李彤已经修改过了。我先列一下我遇到的问题和处理方式吧01:46
tongliit is a lot fast than lampstack workload.01:46
tongliI am planning to make changes to lampstack so that it will also run fast. My goal is making it finish within 8 minutes.01:47
tonglia lot faster01:47
Daisytongli: 您的这些计划打算什么时候完成?我们的4月峰会演示,将使用最新版的LAMP01:48
Daisykongwei: 你继续讲吧。可以多线程发言。01:48
tongliI hope I can get it done within next few days.01:48
Daisy一周之内吗?tongli01:49
kongweiLabel the master node, 这个步骤中,我修改了node的参数01:49
kongwei原先是/opt/bin/kubectl --server={{ private_ip }}:8080 label --overwrite=true nodes.k8sonos master dashboardId=master01:49
kongwei我修改成了:/opt/bin/kubectl --server={{ private_ip }}:8080 label --overwrite=true nodes master dashboardId=master01:49
*** markvoelker has quit IRC01:49
tonglikongwei, take a look at the latest patch, it has been changed to use overwrite01:50
tonglibut in any case, since I am now using fqdn, that is not needed anyway.01:50
kongwei李彤,是的,我看见最新版本也是这么修改过的01:50
tonglibut the latest patch has been added that.01:50
kongwei第二个是我们系统的配置问题01:51
kongweiCreate volumes for the node 部分。01:51
tongliit did not work on the earlier patch set due to the dhcp_domain configuration problem.01:51
kongweiavailability_zone: "{{ app_env.availability_zone }}"01:51
tonglidhcp_domain="" should have been set in the nova.conf file.01:51
tonglibut some cloud does not do that.01:52
tongliresults to wrong hostname.01:52
kongwei我们没配置cinder的availability_zone01:52
kongwei所以我删除了这个01:52
tonglithat was the cause. not sure how your os cloud set that up.01:52
tongliI think you can leave it blank.01:53
*** kongwei_ has quit IRC01:53
kongwei是的01:53
*** kongwei_ has joined #openstack-meeting-501:53
kongwei最后一个遇到的问题01:53
kongweivm启动后,sudo执行会报错。我后来是手动登录到vm。把hostname添加到/etc/hosts里的01:54
kongwei否则会出现执行超时01:54
Daisykongwei: 用的什么虚拟机镜像?01:55
kongweiubuntu 1601:55
tonglihmmm. the k8s workload should do that for you already01:55
kongwei从社区下载的原始镜像01:55
tonglialso lampstack workload does the same thing.01:56
kongwei那我今天更新到最新的k8s脚本再运行一下吧01:56
Daisykongwei: 你们测试LAMP 的时候没有问题,对吧?01:56
Daisy没有hostname的问题,对吧?01:56
kongwei是的,lampstack没遇到01:56
Daisy好的。01:56
kongwei可能是我的k8s脚本不是最新的吧01:56
kongweidaisy,我的发言结束了。01:57
DaisyZTE碰到的三个问题,第一个最新版的代码已经修改了;第二个ZTE系统的特殊配制导致;第三个hostname问题,很奇怪01:57
zuozongming我们在lampstack测试时里遇到了hostname 的问题 当时在脚本里添加了hostname 咱们需要统一镜像吗?感觉是镜像的原因01:58
liuyuqi各位,请教个问题吧,k8s测试的时候启动docker报错,Unit containerd.service not found,大家有遇到过吗01:58
Daisy因为ZTE报名了波士顿峰会的演示,所以关于第二个问题,我的建议是kongwei和tongli看一下是不是可以修改一下脚本,将availability_zone变为可以配置的选项,解决这个问题。01:58
tongliliuyuqi, that problem has been fixed today01:58
tongliI made a mistake. it should be ok now.01:59
liuyuqi那我也更新一下最新代码试试,非常感谢01:59
tongli@liuyuqi, that only happens with ubuntu target. I have fixed it today.01:59
Daisykongwei, tongli: 需不需要把availability_zone变为可以配置的选项?01:59
tongliuse the latest patch set 37 (I believe).01:59
tongliavailability_zone is configurable.02:00
Daisyok. 最终目标是不改代码,而只是改配置,可以在不同的环境中把测试用例跑起来。02:00
kongwei好的02:01
*** mafei has joined #openstack-meeting-502:01
Daisy#action kongwei test with latest k8s code and report progress in the next meeting02:01
Daisy#action davidshi and Wei_Liu continue the k8s test and report progress in the next meeting02:01
Daisy谢谢大家,讨论的很细致02:02
Daisy下一个话题02:02
Daisy#topic About the new LAMP workload02:02
*** openstack changes topic to "About the new LAMP workload (Meeting topic: interop_challenge)"02:02
tongli@kongwei, @daisy, that is exactly right. if each party keeps changing the code to pass the workload test, that means we have failed.02:02
Daisy在4月份的北京开源峰会上,已经决定我们将演示最新版的LAMP场景。02:02
Daisy还有不到4个星期的时间准备了,马飞会筹备几次面对面的预演,来备战峰会上的演示。02:03
tongliI would like to ask everyone who has finished lampstack test, how long did it take you to finish the run?02:03
Daisy好的。02:03
tongliwe have to make sure the run finishes within 8 minutes.02:04
tongliI will arrive on 4/16 evening. Hope I can participate at least one rehearsal.02:04
Daisy#action all to test with the latest LAMP code, calculate the test running time, report the time to tongli by WeChat as soon as possible.02:04
Daisy这项任务关系到咱们4月北京峰会演示的效果,请大家一定要放到高优先级,尽快完成。02:05
Daisytongli: 如果你还想修改LAMP的效率提升速度,也建议你早点完成修改,这样维持一个稳定的最终版。02:06
Daisy刚才zuozongming提到要不要统一虚拟机镜像的问题,tongli你有建议吗?02:06
tongliI know.02:06
tongliyeah, I think we should use ubuntu 16.0402:06
Wei_Liufor LAMP?02:07
Daisyzuozongming,kongwei,Wei_Liu: 我们的目标是不要修改代码,只修改配置文件,完成LAMP的测试。如果测试中有任何问题,请及时在微信群里沟通。02:07
kongwei好的02:07
Wei_Liuok02:07
Daisy#decision: we will use ubuntu 16.04 downloading from official website in the InterOp show in Beijing02:08
kongweilampstack我使用的是社区的ubuntu 14版本测试。我继续测试ubuntu 16吧02:08
kongwei下次会议上反馈测试进展02:08
Daisy大家尽量去测试。先按照这个要求去做,有问题在群里及时沟通。02:08
Daisy目的就是4月的峰会演示,一起加油~02:08
Daisy下一个话题02:09
Daisy#topic Discuss  the interop challenge scheme of the global cloud computing summit in April02:09
*** openstack changes topic to "Discuss  the interop challenge scheme of the global cloud computing summit in April (Meeting topic: interop_challenge)"02:09
Daisy马飞草拟了一个峰会演示的agenda,请大家提提意见。02:09
tonglihow many companies will be on stage now?02:09
Daisy主持人:马飞02:09
Daisy互操作能力展示分为两个环节/部分02:09
Daisy第一部分:openstack基金会非常重视互操作(15分钟)02:09
DaisyMike介绍OpenStack基金会情况(5分钟)02:09
Daisy郭长波介绍基金会董事成员包括个人董事(5分钟)02:09
Daisy李彤介绍interop工作组以及现在工作进展(5分钟)02:09
Daisy 02:09
Daisy第二部分:国内企业互操作能力展示及颁奖(15分钟)02:09
Daisy马飞介绍LAMP工作做了哪些事情(3分钟)02:10
Daisy然后随机采访台上演示人员,目前的工作进展(10分钟)02:10
Daisy最后给所有参与企业颁发一个奖章(5分钟)02:10
Daisy8, including IBM and Huawei02:10
Daisy我们一共有30分钟的上台时间。02:10
tongliok, 10 will be nice.02:10
Daisy包括Mike的演讲,郭长波董事的演讲,tongli的演讲,以及我们的展示环节和颁奖环节。02:11
tonglithe first part is on the first day and the second part is on the second day?02:11
Daisy在一起,第二天上午的第一个节目。02:11
Daisy好像是9:30-10:0002:11
tonglioh, ok.02:11
*** mafei has quit IRC02:12
tongliso, I am not doing the second part, right? Mafei will be doing it?02:12
Daisy我感觉这个时间安排应该有可以重复利用的时间段。02:12
Daisy看起来是你的演讲在第一部分的5分钟里。02:13
Daisy需要马飞确认一下你是不是在第二部分里面讲话。02:13
Daisy可以去群里讨论。02:13
tongliI was surprised by that. I thought I will be conducting the demo.02:13
*** davidshi has quit IRC02:13
*** davidshi has joined #openstack-meeting-502:14
Daisymafei不在,咱们待会去微信群里和他讨论一下吧。02:14
Daisyzuozongming,kongwei,Wei_Liu: 关于4月峰会的展示的安排,你们有什么问题吗?02:14
Daisy没有问题我们结束这个环节的讨论。02:15
Daisy#topic Open discussion02:15
*** openstack changes topic to "Open discussion (Meeting topic: interop_challenge)"02:15
Daisyzuozongming,kongwei,Wei_Liu,tongli: 有什么问题想继续讨论吗?02:16
Wei_Liu没有问题,02:16
Daisy谢谢。02:16
tongliI think we need to confirm the rehearsal time.02:16
Daisygood suggestion02:16
tongliespecially if I will be conducting it.02:16
Daisy#action Mafei to decide the rehearsal date and time02:17
LiXiang4月初是否还要到北京做一下预先演练?02:17
tonglithe demo is on day 2, so last rehearsal should be Monday.02:17
Daisy我记得马飞想安排几次面对面的预演。02:17
*** mafei has joined #openstack-meeting-502:18
LiXiang因为我们在南京,因此希望如果需要面对面演练的话,最好集中在一两天内,我们可以请孔炜去北京出差。02:18
Daisymafei来了。能说话吗?02:18
tongliI think have couple more rehearsals is a good idea.02:18
Daisy好的。02:18
Wei_Liu2次吧,第二次4月17号,让mafei定第一次的时间?02:18
DaisyLiXiang: 好的,我转达给马飞。02:18
Daisymafei来了,能说话吗?02:18
LiXiang第一次排练是什么时间?02:18
Daisy大家的提议都看到了,等马飞决定。02:19
mafei第一次会提前通知大家,在10号那周的前几天02:19
mafei10或者11号02:19
LiXiangok02:19
tongliI will make some changes to lampstack workload.02:20
Wei_Liutongli: 大概什么时候能完成LAMP的修改?02:20
Daisy所以是两次,第一次是10号或者11号,第二次是会议前一天,对吧?02:20
mafei第二次在会前17、18号02:20
tonglithe main change is to make the vm provision parallel.02:20
mafei对的02:20
Daisy好的。收到,mafei02:20
tongliit is to reduce the workload run time.02:20
tongliI am hoping I can finish that by EOD this Friday. but I need all of you to review it.02:20
tongliotherwise, it can not be merged.02:21
Daisy#action all to review tongli's patch to LAMP02:21
tongliI do not want to push my own patch set, not nice , so I need everyone to review the patch.02:22
Daisytongli: 你提交之后,在群里跟大家说一声,我们去review02:22
*** mafei has quit IRC02:22
tonglionce I have it submitted, I will let everybody know.02:22
Daisy好的,多谢tongli02:22
Wei_Liutongli: 能不能让lampstack也用local repo?02:22
tonglihi, btw, I can bring some stuff to beijing from US. if anyone wants something.02:22
tongliI mean something small.02:23
tongliand something won't get me into trouble.02:23
tongliWei_Liu, lampstack can use local repo already02:23
Daisy大家还有想在会上讨论的吗?没有的话,我就结束IRC会议,大家可以转战微信群,继续关心的话题。02:25
Wei_Liuno02:25
Daisy好的,那我就结束IRC会议了。谢谢各位的参与和支持。02:26
tonglibye02:26
Wei_Liubye02:26
Daisy#endmeeting02:26
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"02:26
openstackMeeting ended Wed Mar 22 02:26:25 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)02:26
openstackMinutes:        http://eavesdrop.openstack.org/meetings/interop_challenge/2017/interop_challenge.2017-03-22-01.31.html02:26
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/interop_challenge/2017/interop_challenge.2017-03-22-01.31.txt02:26
openstackLog:            http://eavesdrop.openstack.org/meetings/interop_challenge/2017/interop_challenge.2017-03-22-01.31.log.html02:26
*** tongli has quit IRC02:26
*** zuozongming has quit IRC02:27
kongweibye02:27
*** kongwei has quit IRC02:27
*** LiXiang has quit IRC02:27
*** kongwei_ has quit IRC02:32
*** Wei_Liu has left #openstack-meeting-502:32
*** Daisy has quit IRC02:49
*** markvoelker has joined #openstack-meeting-502:50
*** markvoelker has quit IRC02:54
*** ricolin has quit IRC03:21
*** liuyuqi has quit IRC03:28
*** liuyuqi has joined #openstack-meeting-503:29
*** ricolin has joined #openstack-meeting-503:47
*** markvoelker has joined #openstack-meeting-503:51
*** markvoelker has quit IRC03:55
*** ricolin has quit IRC04:24
*** davidshi has quit IRC04:37
*** liuyuqi has quit IRC04:40
*** markvoelker has joined #openstack-meeting-504:52
*** markvoelker has quit IRC04:56
*** davidshi has joined #openstack-meeting-505:12
*** markvoelker has joined #openstack-meeting-505:52
*** markvoelker has quit IRC05:57
*** tdasilva has quit IRC06:14
*** tdasilva has joined #openstack-meeting-506:28
*** ricolin has joined #openstack-meeting-506:31
*** ricolin has quit IRC06:32
*** ricolin has joined #openstack-meeting-506:32
*** ricolin has joined #openstack-meeting-506:33
*** ricolin_ has joined #openstack-meeting-506:33
*** ricolin_ has quit IRC06:34
*** ricolin_ has joined #openstack-meeting-506:35
*** markvoelker has joined #openstack-meeting-506:53
*** markvoelker has quit IRC06:58
*** ricolin_ has quit IRC07:21
*** ricolin has quit IRC07:21
*** ricolin has joined #openstack-meeting-507:23
*** tiantian has quit IRC07:47
*** matrohon has joined #openstack-meeting-507:53
*** markvoelker has joined #openstack-meeting-507:54
*** markvoelker has quit IRC07:58
*** matrohon has quit IRC08:30
*** matrohon has joined #openstack-meeting-508:33
*** ralonsoh has joined #openstack-meeting-508:45
*** davidshi has quit IRC11:08
*** markvoelker has joined #openstack-meeting-512:51
*** markvoelker_ has joined #openstack-meeting-512:54
*** markvoelker has quit IRC12:54
*** mafei has joined #openstack-meeting-513:47
*** mafei has quit IRC13:49
*** mafei has joined #openstack-meeting-513:54
*** mafei has quit IRC13:56
*** Thor_ has joined #openstack-meeting-513:56
*** tongli has joined #openstack-meeting-513:59
*** mafei has joined #openstack-meeting-513:59
*** zhipeng has joined #openstack-meeting-514:00
tongliPing dmellado tongli gema zhipengh markvoelker daniela_ebert skazi luzC gcb hodgepodge yaohelan eeiden kgarlofftongl14:00
*** mnaser has joined #openstack-meeting-514:00
dmelladoo/ hi tongli ;)14:00
mnasero/14:00
beisnero/14:00
markvoelker_o/14:00
tonglihello, everyone. good day.14:00
dmelladoI hope this meeting won't be in chinese xD14:00
tonglihaha.14:00
dmelladoI'm seeing some characters from the former one14:00
Thor_hello14:00
mafeio/14:00
*** markvoelker_ is now known as markvoelker14:01
zhipengo/14:01
tongliYes. indeed. the China chapter meeting is mixed in English and Chinese.14:01
tongli#startmeeting interop_challenge14:01
openstackMeeting started Wed Mar 22 14:01:23 2017 UTC and is due to finish in 60 minutes.  The chair is tongli. Information about MeetBot at http://wiki.debian.org/MeetBot.14:01
dmelladotongli: it gives me headaches just thinking about that xD14:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:01
*** openstack changes topic to " (Meeting topic: interop_challenge)"14:01
openstackThe meeting name has been set to 'interop_challenge'14:01
tonglican you guys do an o/ again so that the meeting minutes get your name recorded?14:02
markvoelkero/14:02
dmelladoo/14:02
beisnero/14:02
zhipengo/14:02
mnasero/14:02
skazi_o/14:02
tongliThanks.14:02
mafeio/14:02
*** HelenYao_ has joined #openstack-meeting-514:02
tonglitopic Review last meeting action items14:03
Thor_o/14:03
tongli#topic Review last meeting action items14:03
*** openstack changes topic to "Review last meeting action items (Meeting topic: interop_challenge)"14:03
tonglihttp://eavesdrop.openstack.org/meetings/interop_challenge/2017/interop_challenge.2017-03-15-14.01.html14:03
tonglithere are only two actions other than review patch sets from last week.14:04
tongliBTW, Brad is in Vegas, he most likely will miss today's meeting.14:04
vkmco/14:04
dmelladowelcome vkmc ;)14:04
tongliaction #1 was Mark look into the copy right, license thing.14:04
vkmcthx!14:04
HelenYao_o/14:05
tongli@markvoelker, any updates?14:05
markvoelkerI haven't quite finnished the patch, but it's mostly just elbow grease.  Should have that ready soon (today I'm pretty booked, so likely later this week)14:05
tongli@markvoelker, great. thanks. so you are planning to add headers to workload files or creating a new file?14:06
markvoelkerMy current iteration ammends existing files per the guidelines we discussed last week14:06
tongliso your patch will be on top of my patch?14:07
dmelladoyep, IIRC that's what we agreed to and was on the guidelines14:07
markvoelkeryep, just an iteration14:07
dmelladoit should be fairly simple, in any case14:07
tongliok. great. Thanks @markvoelker.14:07
markvoelkerI thought the easiest way to do it would be to make it a separate patch that's dependant on yours14:07
dmelladojust adding a ton of #Apache, I assume ;)14:07
markvoelkerThat way we can keep them separate in gerrit14:07
markvoelkerdmellado: basically, yes. =)14:07
tongli@markvoelker, agreed.14:08
tongliso please, please review this patch set. https://review.openstack.org/#/c/433874/14:08
tongliok, the second action was for daniel look at the os-client-config.14:08
dmelladotongli: I was overcommited this week, but it's on my TODO ;)14:09
tongliI think the discussion was during the NFV workload configuration14:09
dmelladoalso if there aren't any more items I wanted to start a discussion on wether we should try to put even if a reduced version14:09
*** mafei has quit IRC14:09
dmelladoof the workload14:09
tongliok. please work with @HeleYao on the NFV workload regarding the configuration.14:09
dmelladoso we can add it to the openstack CI, to have some kind of 'minimum-workload' around14:09
dmelladowill do ;)14:10
tongli@dmellado, thanks.14:10
tongliI believe that is all the actions from last week, but guys, please review the workload patches.14:10
tongliwe really need to get them merged.14:10
markvoelker++14:11
tongli#topic patches that need reviews.14:11
*** openstack changes topic to "patches that need reviews. (Meeting topic: interop_challenge)"14:11
tonglihttps://review.openstack.org/#/q/status:open+project:openstack/interop-workloads,n,z14:11
tongliwe only have two.14:11
tongliplease review and we need to at least have the k8s workload merged.14:12
tongli#topic k8s patch set issues.14:12
*** openstack changes topic to "k8s patch set issues. (Meeting topic: interop_challenge)"14:12
tongliEarlier I had some issues when I run the workload using ubuntu image,14:12
dmelladotongli: the k8s one?14:13
dmelladooh, nevermind, saw the topic14:13
tonglilater I found I was misconfigured docker on ubuntu14:13
tonglithat has been now fixed.14:13
*** mafei has joined #openstack-meeting-514:13
tongliI had another issue earlier as well, after I deploy cockroachdb cluster, I found that if I use even number of nodes for cockroachdb,14:14
tonglithe cluster won't be very stable, sometimes I see pod craches.14:14
*** kgarloff has joined #openstack-meeting-514:14
tonglibut when I use odd number of nodes for cockroachdb cluster, then it has no issues.14:14
tongliI think I will need more tests on this.14:14
kgarloffcluster quorum stuff?14:15
markvoelkerYEah, pretty typical for distributed systems.14:15
dmelladotongli: did that happen all the times?14:15
tonglibe aware that cockroachdb docker image is Alpha.14:15
dmelladoI mean, all time, even, crashed14:15
*** mafei has quit IRC14:15
dmelladoodd, worked all the time?14:15
tongli@dmellado, not all the time even with even number of cockroachdb nodes.14:15
zhipengi remember once read their blog about the scalability issue14:15
dmelladohm14:15
tongliyes, odd number of nodes worked fine.14:15
tonglivery stable.14:16
tongliso it will be very nice if everybody run the workload and see the behaviors.14:16
tongliplease do read the README.rst file.14:16
*** krtaylor has joined #openstack-meeting-514:16
tongliif stack_size is set to 5, cockroachdb cluster will be 4 nodes.14:16
dmellado+1, will try to do some tests14:16
kgarlofftongli: so we need to set to 6?14:17
markvoelkerEven numbers of nodes in a distributed DB are almost always a bad idea. =)14:17
tonglione node is used as master node, cockroachdb cluster won't use that node. so we end up with stack_size -1 cockroachdb nodes.14:17
tongli@markvoelker, that is what I suspected, I think cockroachdb master node election may have some issues.14:17
tonglibut in theory it should work.14:17
tonglibut anyway, at patch set #37, I have everything working.14:18
tongliand I am planning to give a demo next week to Mark.14:18
tongliif the time is confirmed, I invite everybody to participate.14:18
tonglithis will be a remote meeting with Mark to show what has been developed,14:19
dmelladotongli: pls do send an invite by then ;)14:19
tongliso he may have some suggestions.14:19
* markvoelker notes for posterity that tongli is talking about the other Mark (aka Sparky Collier)14:19
tongli@dmellado, yes I will send out invite.14:19
dmelladomarkvoelker: thanks for the clarification xD14:19
tongli@markvoelker, yes, sorry, Mark Collier from the foundation.14:19
tongli@markvoelker, I will show it to Brad Friday since he has been traveling so much lately.14:20
luzCo/14:20
tongliat the moment, the k8s workload is done.14:20
tongliit works on both ubuntu and coreos images.14:21
mnaseris there any docs so that we can try it on our existing clouds14:21
mnaserjust to have an idea14:21
dmelladomnaser: it should mostly work as it is14:21
tongli@mnaser, yes, please read the README.rst file.14:21
dmelladojust download tongli 's patch14:21
mnasermay i ask for the link to the repos14:21
tonglihttps://review.openstack.org/#/c/433874/37/workloads/ansible/shade/k8s/README.md14:22
dmelladohttps://github.com/openstack/interop-workloads14:22
dmelladomnaser: ^^14:22
mnasermerci tongli and dmellado14:22
dmellado+ pls tongli 's patch14:22
tonglithat is the readme. the patch link is above. I post here again. https://review.openstack.org/#/c/433874/14:22
dmelladoyou're welcome mnaser14:22
tonglithe patch set is now at #37, I am a bit tired keeping adding to it. please guys get it merged.14:23
tongliif there are bugs (I am pretty sure it does), we can fix it.14:23
dmellado+1, tongli I'll give it a spin locally14:24
dmelladoand if it's ok I'd say we can merge it and have it as a starting point at least14:24
tongliI certainly do not want to be the champion in terms of number of patch set.14:24
dmelladoheh14:24
tonglialso, guys I would like everybody know that If I have stack_size set to 6, the workload finishes within 6 minutes.14:25
luzC+1 tongli14:25
mnaserive done a lot of ansible work so14:25
mnaseri can throw in patches which could speed/clean things up14:25
tongliI have also made changes that does docker load container images.14:25
mnaseri agree with merging stuff so that we can tweak it as we go with smaller patches, it makes review easier14:26
tongliso that you do not have to wait for the docker images to be extracted from container image repo especially the cockroachdb image is quite big,14:26
mnaserno one wants to go through a big merge :) (sorry you had to go through that tongli )14:26
dmelladomnaser: feel free to propose any change you might want to ;)14:26
mnaseri would like to do so but ideally once that big patch merges :)14:26
dmelladoworst case you can just do as markvoelker did and make your change dependant on tongli's14:27
tongli#action, tong schedules a demo meeting with Mark Collier next week and send out invite to everybody.14:27
vkmc+1 to smaller patches14:27
tongliBTW, I have also requested to have a OSCI account open, so that I can run the workload against more clouds.14:28
tonglithanks to @luzC for making it happen.14:28
luzCyou mean osic cloud tongli14:28
tongli@luzC, yes, osic cloud14:29
luzCahh yes... we have a project for the challenge...14:29
luzC:)14:29
tongliI can log in to it, but can not create router, which needs to be resolved.14:29
dmelladohaving that on OSIC would be cool ;)14:30
tonglioh, huge updates from Interop Challenge China Chapter.14:30
dmelladobut tongli luzC actually (and maybe we can discuss that in person at boston for future work)14:30
dmelladowe'd *need* some kind of CI14:30
dmelladoI don't think that it's good at a long term to have that14:30
dmellado'it runs on my cloud' review approach :\14:30
tonglithere was a meeting last night and decided to use improved LAMPStack work for the keynote demo in BJ in April Global OpenSource Summit.14:31
luzCdmellado I agree14:31
dmelladootherwise I'll go to Boston with the 'it works on devstack t-shirt'14:31
tongli@dmellado, haha.14:31
vkmchahaha yes, that would be amazing14:31
dmelladoso we would need to have maybe a subset14:31
dmelladothat would fit openstack CI requirements14:31
tongli@dmellado, can you help with that?14:32
dmelladoI can help, but won't be able to handle that myself14:32
dmelladoI'll try to coordinate that, though14:32
dmelladoI tried squeezing everything on a 8GB dsvm14:32
dmelladoand it was a disaster14:32
tongli@dmellado, please, let us know if someone else can help.14:32
mnaserdid you try disabling the unnecessary services14:33
dmelladoso how about getting first the workload merged and then afterwards14:33
dmelladolet's strip it out14:33
* mnaser can help with some stuff14:33
dmelladomnaser: yeah, totally14:33
dmelladobut we can sync on that if you have the time ;)14:33
mnaseryeah, feel free to pm (do we have an interop channel where everyone spends time at)14:33
tongli#action dmellado and mnaser work together to get CI working.14:33
dmelladomnaser: we actually do, @openstack-interop14:34
tonglithere is #openstack-interop channel.14:34
dmellado#14:34
mnaserokay, cool, thanks14:34
dmelladoso far only the doc gate is enabled14:34
dmelladoI do plan to enable at least some linters once the code's around14:34
tongli@dmellado, I would love to have more stuff tested at the gate.14:34
mnaserwe can do some linting but i think the more intresting part is having it tested against other clouds14:35
mnaserex: id love to gate it against our cloud? (or document how to do that)14:35
dmelladohmm maybe a third party CI14:35
mnaserfollowing the "external CI" pattern used in other projects like Cinder or Neutron for example14:35
dmelladomnaser: exactly14:35
mnaseri'll do a bit of reading about that14:36
dmelladoI'll need to check if we can actually do that while disabling that job for the upstream one14:36
dmelladoas it just won't fit14:36
tongli@mnaser, so at present what are the options for the third party CI?14:36
mnaserso every $provider can listen to changes at gerrit for the interop repo14:36
mnaserand then it would check out the change, run it against their cloud, and report results back14:36
mnasertongli https://review.openstack.org/#/c/338139/14:37
dmelladothat could be cool, of course at first I just won't count the 3rd party CI voting14:37
mnasersee how there is external CIs of providers (IBM, etc)14:37
* dmellado has some concerns about some external CIs, tbh14:37
*** zhipeng has quit IRC14:37
mnaserof course14:37
tongliok. thanks for the info.14:37
mnaserit's a step in the right direction at least14:37
mnaserif 6 clouds fail even if they're all non voting14:38
tongli@mnaser, agreed.14:38
mnaseri think we can agree we broke something :-P14:38
tonglihaha.14:38
tongli#topic Boston SUmmit On Stage Keynote Committed Parties.14:38
*** openstack changes topic to "Boston SUmmit On Stage Keynote Committed Parties. (Meeting topic: interop_challenge)"14:38
tonglicurrently we have 11 parties, 5 spots left.14:39
mnaseri am not sure how we can say we'd like to do it14:39
tongliif your company is not on the list, please make sure there is someone from your company commits to it.14:39
beisnerhi all - question: is there a reason Ocata isn't targeted in that list?14:39
mnaserwhere can we find "the list" :-p14:39
kgarlofftongli: Working on it!14:39
*** zhipeng has joined #openstack-meeting-514:39
kgarloffWe want to be there -- just need to make sure we can run the workload14:40
tongli@heisner, no, I just do not think we require Ocata or any particular version of OpenStack.14:40
luzCmnaser https://wiki.openstack.org/wiki/Interop_Challenge#Boston_Summit_On_Stage_Keynote_K8S_Demo_Commited_Parties14:40
kgarloffOr maybe I should enter there right now?14:40
dmelladomnaser: https://wiki.openstack.org/wiki/Interop_Challenge14:40
tongliprobably not many public/private production cloud uses Ocata yet.14:40
markvoelkerbeisner the idea is to test the workload on real-world products that people can get today.  No particular version is required, the list there is just what versions people have productized right now.14:41
mnaserluzC / dmellado : thanks, added14:41
beisnermarkvoelker, ok tyvm.14:41
tongliok, only 4 spots left.14:42
tongliplease review the patch sets, please please please.14:42
krtaylorOpenPower is working to be there too14:42
tongli@krtaylor, great. would love to see how the workload runs on the cloud.14:42
krtaylormaking sure we can run the workload atm14:42
mnasercan i ask what is stopping us from merging tongli work14:43
tongli@HelenYao, do you have any updates on the NFV workload?14:43
krtaylortongli, thanks, I'll ping you in channel later with a few questions14:43
tongli@maser, good question, need +1 and +2s haha.14:43
mnaserby 37 patch sets i think most of the things are ironed out (and its been over a month).. maybe good to get to the bottom of it14:43
HelenYao_tongli: i am working on the test improvement14:44
HelenYao_the deployment should be working14:44
mnaserwe can do improvements in further patches14:44
HelenYao_the test cases are required to be polished14:44
markvoelkermnaser: just review time.  Lots of folks traveling/out lately.  I expect it'll land shortly (I know I'm planning to finish up this week)14:44
mnaserokay coool14:44
tongli@HelenYao_, that is great. I have not had time to try it yet. thanks for working on it though.14:44
zhipengHelonYao_ we test the deployment on the M version ?14:45
HelenYao_it supports both M and previous version14:45
dmelladotongli: I'll +2+A your k8s patch14:45
dmelladolet's work from that -into smaller patches, please-14:46
luzCI already +2 it14:46
HelenYao_the deployment is tested on newton and mitaka14:46
tongli#@luzC, thanks.14:46
dmelladoluzC: saw it, that's why I think that +2+A it14:47
dmelladoand let's split the reviews from now on14:47
dmellado#action smaller patches, please xD14:47
zhipengfolks could we discuss the nfv workload ? Please help review it14:48
dmelladozhipeng: I'll review it again too14:48
tongli@zhipeng, agreed, please review that patch set as well,14:48
zhipengHelenYao_ has been working crazy to meet the deadline Brad mentioned last time14:48
dmelladooverall, IIRC (and pls let me go again thru it before)14:48
dmelladothat it'd be great to have the tech details that HelenYao_ kindly explained14:49
dmelladore: juju charms usage and so on14:49
dmelladobut I need to go again over it, will do that later on today14:49
zhipengi think it is better to run the workload first to see if it works, get a visional sense :)14:50
zhipengthen dig into the tech details14:50
HelenYao_yes. get a rough view about the process will help you better grasp the tech details14:51
HelenYao_ping me anytime if you have problem14:51
tongli@HelenYao_, yes. that is right, thanks a lot for your help on the workload.14:52
dmelladoI'll get to that, thaks HelenYao_ and zhipeng ;)14:52
HelenYao_any bugs and feedback are appreciated :)14:53
zhipenganother issue is that, let say if we were able to catch the deadline and also demo the nfv workload on stage14:53
zhipengwe might need actual pod on the stage14:53
zhipengHelenYao_ plz correct me if i'm wrong, if we test the App behind VPN, there will be sound issue14:54
zhipengso it is better to present the demo using actual hardware14:54
zhipenglike the OPNFV Doctor demo at Barcelona14:54
HelenYao_yes, the VPN might block the multimedia transmission (voice/video)14:54
HelenYao_in my lab, the VPN does not allow the multimedia14:55
tongli@HelenYao_, we got 5 minutes left. Can we pick up this topic next week if we run out time?14:55
*** admcleod has joined #openstack-meeting-514:56
dmellado+1, I also need to leave14:56
tongli@HelenYao_, so we need to run this in a cloud which does not block voice and video?14:56
dmelladothanks everyone!14:56
tongli@dmellado, thanks.14:57
HelenYao_tongli: i am fine with discussing it next week14:57
tongliok. let me put that on agenda for next week.14:57
HelenYao_tongli: the VPN is supposed to allow the multimedia14:57
HelenYao_sounds good, thx14:58
tongli#action place NFV workload requirement discussion on next week agenda.14:58
*** cwolferh has joined #openstack-meeting-514:58
tongliok, I think we pretty much run out of the time, any last minute item?14:59
tongliall right. I think we are good for today.14:59
beisnerthanks, all14:59
tongliThanks everyone! have a great day!!14:59
tongli#endmeeting15:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:00
openstackMeeting ended Wed Mar 22 15:00:05 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/interop_challenge/2017/interop_challenge.2017-03-22-14.01.html15:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/interop_challenge/2017/interop_challenge.2017-03-22-14.01.txt15:00
openstackLog:            http://eavesdrop.openstack.org/meetings/interop_challenge/2017/interop_challenge.2017-03-22-14.01.log.html15:00
zhipengthx15:00
*** mnaser has left #openstack-meeting-515:00
ricolin#startmeeting heat15:00
openstackMeeting started Wed Mar 22 15:00:32 2017 UTC and is due to finish in 60 minutes.  The chair is ricolin. Information about MeetBot at http://wiki.debian.org/MeetBot.15:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:00
*** openstack changes topic to " (Meeting topic: heat)"15:00
openstackThe meeting name has been set to 'heat'15:00
ricolin#topic roll call15:00
*** openstack changes topic to "roll call (Meeting topic: heat)"15:00
*** therve has joined #openstack-meeting-515:01
cwolferho/15:01
ricolinhi:)15:01
*** Thor_ has quit IRC15:01
*** tongli has quit IRC15:01
ricolinno many here this week15:02
zanebhey hey15:02
*** nilles has joined #openstack-meeting-515:03
ricolinThis will be a short one:)15:03
ricolin#topic adding items to agenda15:03
*** openstack changes topic to "adding items to agenda (Meeting topic: heat)"15:03
ricolin#link https://wiki.openstack.org/wiki/Meetings/HeatAgenda#Agenda_.282017-03-22_1500_UTC.2915:03
ricolinzaneb How can we send some one to apply for stable branch core reviewer?15:05
*** HelenYao_ has quit IRC15:05
zanebricolin: ML post with [stable][heat] in the subject15:05
ricolinwonder that right remain on us or the core-stable-mint?15:06
kgarloff5~/leave15:06
*** kgarloff has left #openstack-meeting-515:06
ricolin#topic Future of ''converge'' ability during stack update15:06
*** openstack changes topic to "Future of ''converge'' ability during stack update (Meeting topic: heat)"15:06
ricolin#link https://review.openstack.org/#/q/topic:bp/get-reality-for-resources+status:open15:07
ricolinprazumovsky is this about asking review for the rest four patches?:)15:07
ricolinIt seems we have only four patches left for bp/get-reality15:08
ricolinI assume this topic is about hope more people will review it:)15:09
*** prazumovsky has joined #openstack-meeting-515:09
prazumovskyHi15:09
prazumovskySorru for late15:09
ricolinhi15:09
ricolinNP15:09
prazumovskyThis is my topic15:09
ricolinyour topic now:)15:09
ricolinit this about asking reviewer for the rest four?15:09
prazumovskyI just want to know the future of this feature15:09
prazumovskyAnd yes, this is ask to review:)15:10
prazumovskyDo we still want to add option --converge to stack update?15:10
prazumovskyOr something same15:11
ricolinsure we do, I'm actually writing that now15:11
ricolinbut I assume that's not the `feature15:12
ricolinWe do have some discussion in PTG, about how we get to next step of convergence15:13
ricolin#link https://etherpad.openstack.org/p/pike-heat-ptg-convergence215:13
prazumovskyThanks for sharing15:13
prazumovskyNow I know what to do:)15:13
ricolinNeed New Resource Plugin interface15:13
ricolinmight be the next thing?15:14
ricolinAlso We need some nicer notification service15:14
ricolinprazumovsky interested?!15:14
ricolin:)15:15
prazumovskyInterested in new resource plugin, yes15:15
prazumovskyWill create some spec to discuss proc and cons of it15:16
ricolinzaneb is the one comes out with that BTW15:16
zanebI have no recollection of agreeing to that ;)15:16
prazumovskyOh, ok15:17
prazumovsky:)15:17
zanebprazumovsky: it's all yours :)15:17
prazumovskyWill add you all on review to discuss it in the future;)15:18
prazumovskyWell, now I understand the future of convergence phase 2, we can move next15:19
ricolincool15:19
ricolinprazumovsky still there is always room for more discussion around that15:20
ricolin#topic Forum preparation15:20
*** openstack changes topic to "Forum preparation (Meeting topic: heat)"15:20
prazumovskyricolin okey15:20
ricolinshall we propose `Large Heat stacks` to Forum?15:21
ricolin#link https://etherpad.openstack.org/p/BOS-Heat-brainstorming15:21
zaneb+1 obvs15:21
ricolinzaneb and you like to host that or wish someone else?15:22
zanebI will moderate if I am there15:22
zaneb(which is still not confirmed)15:23
ricolinzaneb NP15:23
ricolinWe also will have a on-bording session15:23
ricolin#link http://lists.openstack.org/pipermail/openstack-dev/2017-March/114063.html15:23
ricolinabout some deep learning for new guys15:24
ricolinaround 45min-90mins15:24
ricolinI will prepare that one, but would also like if more guys to join:)15:25
ricolin#topic Open discussion15:25
*** openstack changes topic to "Open discussion (Meeting topic: heat)"15:25
ricolinanything else would like to discuss?15:26
ricolinI think we can call if off for today and move back to heat:)15:27
prazumovskySame thought:)15:27
ricolinthanks all15:27
prazumovskyThanks, bye15:28
ricolinremember to review more patches15:28
ricolinwe need reviewer15:28
ricolin#endmeeting15:28
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:28
openstackMeeting ended Wed Mar 22 15:28:17 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:28
openstackMinutes:        http://eavesdrop.openstack.org/meetings/heat/2017/heat.2017-03-22-15.00.html15:28
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/heat/2017/heat.2017-03-22-15.00.txt15:28
openstackLog:            http://eavesdrop.openstack.org/meetings/heat/2017/heat.2017-03-22-15.00.log.html15:28
*** prazumovsky has quit IRC15:28
*** nilles has left #openstack-meeting-515:29
*** therve has left #openstack-meeting-515:29
*** kbaikov has joined #openstack-meeting-515:58
*** matrohon has quit IRC16:39
*** matrohon has joined #openstack-meeting-516:44
*** zhipeng has quit IRC16:56
*** matrohon has quit IRC17:11
*** ricolin has quit IRC17:22
*** ralonsoh has quit IRC18:04
*** joanna is now known as joana_lunch19:26
*** krtaylor has quit IRC19:36
*** bzhao_ has joined #openstack-meeting-520:49
*** joana_lunch is now known as joanna20:51
*** matrohon has joined #openstack-meeting-521:02
*** krtaylor has joined #openstack-meeting-521:06
*** joanna has quit IRC21:38
*** matrohon has quit IRC22:15
*** krtaylor has quit IRC22:16
*** bzhao_ has quit IRC22:58
*** joanna has joined #openstack-meeting-523:15

Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!