Wednesday, 2017-02-01

*** Rockyg has quit IRC05:52
*** ralonsoh has joined #openstack-meeting-508:14
*** ralonsoh_ has joined #openstack-meeting-513:07
*** ralonsoh has quit IRC13:09
*** ralonsoh_ is now known as ralonsoh13:11
*** skazi_ has joined #openstack-meeting-513:46
*** makowals_ has joined #openstack-meeting-513:46
*** zhipengh has joined #openstack-meeting-513:47
*** makowals has quit IRC13:49
*** tongli has joined #openstack-meeting-513:55
topol#startmeeting interop_challenge14:00
openstackMeeting started Wed Feb  1 14:00:27 2017 UTC and is due to finish in 60 minutes.  The chair is topol. Information about MeetBot at http://wiki.debian.org/MeetBot.14:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:00
*** openstack changes topic to " (Meeting topic: interop_challenge)"14:00
openstackThe meeting name has been set to 'interop_challenge'14:00
tonglio/14:00
topolHi everyone, who is here for the interop challenge meeting today?14:00
topolThe agenda for today can be found at:14:00
topol# https://etherpad.openstack.org/p/interop-challenge-meeting-2017-02-0114:00
topolWe can use this same etherpad to take notes14:00
markvoelker_o/14:00
topolsmall crowd today... anyone else here?14:02
eeideno/14:02
topolK, lets gets started. hopefully other folks join.14:02
topolAgenda:14:02
topol    #topic Review last meeting action items14:02
topol     #link http://eavesdrop.openstack.org/meetings/interop_challenge/2017/interop_challenge.2017-01-25-14.03.html14:02
*** gema has joined #openstack-meeting-514:03
topoltongli to update agenda with corrected terminology14:03
topolI think you already dis this, correct?14:03
dmelladohey topol o/14:03
dmelladoI was about to miss the meeting14:03
topolhi dmellado, glad you made it14:04
tongli@topol, yes, I did.14:04
dmelladoas it isn't even stated on the IRC14:04
gemao/14:04
topoldmellado what does that mean?14:04
dmelladoon last meeting tongli IIRC stated that there woudln't be due the to the chinese new year14:04
zhipengho/14:04
dmelladoI mean, it wasn't on the meeting page, IIRC14:04
dmelladoit stated that it was going to be next week14:04
dmelladolet me check, just in case14:04
*** daniela_ebert has joined #openstack-meeting-514:05
tongli@dmellado, that was for the china chapter meeting.14:05
dmelladohttps://wiki.openstack.org/wiki/Interop_Challenge#Meeting_Information14:05
tongliwe still have our own. their meeting most likely will be in Chinese.14:05
topoloh... wow, I thought I went rogue there for a sec. :-)14:05
dmelladooh, it's there now14:05
dmelladocool!14:05
skazi_o/14:05
dmelladocan't we integrate that china chapter meeting with the usual one?14:06
dmelladoI'd love to hear what do they have to say ;)14:06
topolbut that reminds me I can send a ping to everyone before meetings start on IRC.   I look at the logs and make a list of our common attendees14:06
tongli@dmellado, you are welcome to join in. the problem was language and time14:06
topoldmellado, we plan to use tongli and his bilingual abilities to keep us uodated.  I should add that as a permanent agenda item.14:07
dmelladotongli: I see, well, if it's just about time we can have a split in US/EMEA/ASIA14:07
tongli@topol, yes, please.14:07
dmelladobut if you're proxy-ing tongli , then I'm fine for now ;)14:07
topol#action topol to create a ping reminder list for our meeting attendees14:07
topol#action topol add agenda item for update from China chapter meeting14:08
tongli@dmellado, also language issue. most of these guys insisted to use Chinese when I talked to them while I was there two weeks ago to kick off the chapter.14:08
dmelladotongli: hmm, interesting stuff14:08
topolbut there code goes in our repository :-)14:08
topolerr their code14:08
dmelladoI can kinda understand the language barrier14:08
dmelladobut then I might request a spanish meeting too xD14:09
tongli@topol, that is  right. also the meeting minutes everything.14:09
topoltongli to add a recommended actions before you show up at PTG section to the agenda etherpd14:09
tonglijust different time and language for the meeting.14:09
topoltongli did you add this?14:09
dmelladoanyway, I won't block the meeting with this ;)14:09
gemadmellado: you mean more than you already did? :P14:09
dmelladogema: heh xD14:09
topoltongli I dont see. this. I think you still need to add it14:10
dmelladogema: don't go on, or I'll sing you up for the spanish chapter14:10
gemadmellado: I don't speak spanish, lo siento senyor14:10
tongli@topol, what did I add?14:10
topoldmellado Yo hablo espanol.14:10
dmelladotopol: gema oh, perfecto entonces xD14:11
tonglihaha.14:11
topoltongli you were supposed to add a section of what new folks should ahead of the meeting to be able to show up and run the workloads I think14:11
topolshould do ahead of the meeting14:11
tongli@topol, do you mean the meeting information on the wikipage about China chapter?14:12
topolno, Im talking about the PTG meeting14:12
topol#link https://etherpad.openstack.org/p/interop-challenge-meeting-2017-01-1114:12
topolwerent you going to add something to that or did I misunderstand?14:12
topolanyway, we can figure that out offline14:13
tonglik.14:13
topoltopol to add agenda item to discuss using coreos for k8s workload14:13
topolthat was done14:13
topoltopol to confirm exact PTG schedule time allocation with cdiep14:13
topolthis is done as well.  I updated #link  https://etherpad.openstack.org/p/interop-challenge-meeting-2017-01-1114:14
topolWe get the RefStack room 1:30-5:00 on Tuesday :-)14:14
topolnext item:14:15
topolall, please review patches #link https://review.openstack.org/#/q/status:open+project:openstack/interop-workloads,n,z14:15
dmelladoon the patches, tongli14:15
dmelladocould you please test some ansible versions and upted my patch on the tox envs14:15
dmelladoI really do think that having proper tox and maybe gates14:15
dmelladowould be a must if we want to verify versions14:15
dmelladoxD14:15
topollooks like #link https://review.openstack.org/#/c/409180/ is the only one that needs reviewed. Nice!14:16
tongli@dmellado, ok, I will try that.14:16
topolgreat thanks dmellado and tongli14:16
tongli@topol, yes, I reviewed zhipeng's summary patch. it just went in, I think.14:16
dmelladothanks tongli !14:16
topoltodays items14:16
tonglithis one , we kind need confirmation on the versions of ansible and shade.14:16
tongliI will try few things. and add comments.14:17
tonglias an action.14:17
topol#action, tongli to try some thing on the patch14:17
topol#topic PTG Meeting Agenda and Logistics:14:18
topol     Meeting Feb 21, Tuesday afternoon 1:30 - 5:00 RefStack room:14:18
topol    Agenda and participant List:  https://etherpad.openstack.org/p/interop-challenge-meeting-2017-01-1114:18
*** openstack changes topic to "PTG Meeting Agenda and Logistics: (Meeting topic: interop_challenge)"14:18
topol14:18
tongli#action, tong will figure out versions of ansible and shade to be supported by lampstack workload14:18
topolokay thats been covered well enough. Look forward to seeing everyone!14:18
topol    #topic China Chapter update14:18
topoltongli any updates?14:18
topolor none due to Chinese New Year?14:18
tonglino, they are on New Year vacation for two weeks.14:19
tonglithey won't be back until after 2/1514:19
* topol easy agenda today :-014:19
topol#topic updates from eeiden on nfv.14:19
*** openstack changes topic to "updates from eeiden on nfv. (Meeting topic: interop_challenge)"14:19
topoleeiden any updates on the NFV app?14:19
topoleeiden, still around?14:21
zhipenghone thing I might add on this topic, we could coordinate this with OPNFV testing folks14:21
zhipenghthey have done plenty related  work14:21
topolzhipengh,  can you provide more details. This sounds interesting14:21
gemazhipengh: who are the "opnfv" testing folks?14:22
eeidenyes sorry!14:22
dmelladogema: that could be plenty14:22
dmelladoOPNFV, just ODL, both?14:23
zhipenghso for example in OPNFV we first define scenarios, sth like "VM-2-VM traffic measurement for clearwater vIMS "14:23
dmelladoI kinda think that going OPNFV goes a li'l bit out of the scope of OpenStack14:23
zhipenghwith scenarios there will be test scripts developed14:23
zhipenghand testing projects will help feature projects to test out those scripts with workloads14:24
zhipenghgema meaning developers from Ericsson, Cisco, Huawei, great people14:24
eeidenNo updates yet. OPNFV Danube release code freeze just completed so we should be good very soon -- will check on it today14:24
topoli guess I would have to see what the code for the scenario looked like to see if it was in or out of scope14:25
zhipenghdmellado OPNFV, which includes ODL integration with OpenStack14:25
dmelladozhipengh: I know, but just pointing at it14:25
zhipenghtopol we could pick those scenarios that involved OpenStack14:25
gematopol: we also need to understand what APIs are we targetting here14:25
gematopol: if they are outside of the scope of openstack then the use case is not what we need14:25
dmelladozhipengh: that's exactly why I do say that's going over the boundaries14:25
dmelladothere are a couple of OPNFV installers, such as apex14:26
markvoelker_FWIW, the Interop WG will be having some discussions with OPNFV folks in the near future anyway regarding a possible "OpenStack Powered NFV" program (this is not committed yet, just an idea we're working up).14:26
dmelladobut not every vendor would have OPNFV14:26
dmelladoif we all agree on adding such scenario, fine14:26
dmelladobut that've to be first agreed14:26
topolgema. I agree. I guess I'm waiting to see some NFV workloads to review.  Between China Chapter, eeiden do we have anyting close to pushing a patch to review?14:26
dmelladothat'd be a good start14:26
markvoelker_If vertical programs like this do come into existence, it seems quite reasonable to coordinate an interop challenge for them too.14:27
topolmarkvoelker_ +++14:27
zhipenghdmellado we could just don't use non-OpenStack related test cases14:27
topolits sounds like an interesting discussion.  But until a patch shows up.... :-)14:28
dmelladozhipengh: I was mainly wondering about for example14:28
markvoelker_We will likely at least have some hallway track discussion on this (if not something more formal) at the PTG for folks who are interested.  I'll keep you all advised as we figure out scheduling. =)14:28
topolmarkvoelker_ I am okay with it being on our agenda. Anyone is free to add to the agenda14:29
zhipenghdmellado :)14:29
dmelladozhipengh: my main 'concern' is for example14:29
dmelladothe different behaviour between plain neutron14:29
dmelladoand neutron+odl14:29
dmelladoI'd see that as something as what markvoelker_ said, something along the lines on an extensions from the interop14:30
dmelladobut let's wait to see some actual patch ;)14:30
zhipenghagree14:30
topoldmellado. makes sense!14:30
topoleeiden, any updates on your NFV workload?14:31
eeidenNo, so sorry. Will keep you all posted as soon as I have something.14:32
tongli@dmellado, exactly, code talks.14:32
tongliI like to see some patches from anyone,14:32
topoltongli+++14:32
topolK next topic14:32
topol#topic open discussion14:32
*** openstack changes topic to "open discussion (Meeting topic: interop_challenge)"14:32
tongli@topol, I added one item14:33
topolanything else for today? any updates on k8s workload?14:33
dmelladotopol: I was wondering if ther's any plan for the Boston summit, I guess we'll get to talk about that at the PTG14:33
tongli@topol, I have been working on it. but as you may have expected, the networking part is quite difficult.14:33
gematopol: are we going to be doing something in Boston related to interop ? present something? I need to decide whether I need to be there14:33
dmelladobut would the idea be to repeat the keynote?14:33
dmelladowe might need a bigger stage, though xD14:34
tongliI would like to ask the folks, for the workload, what kind of networking configuration we like to have for the k8s workload.14:34
topol#topic Any preference for networking choice for kubernetes workload?14:34
*** openstack changes topic to "Any preference for networking choice for kubernetes workload? (Meeting topic: interop_challenge)"14:34
topoldmellado, good question14:34
topollets cove after tongli topic14:35
topolgo ahead tongli14:35
tonglinetworking choice for k8s workload, what folks think? there are quite a lot options.14:35
tongliflat networking or overlay over overlay.14:35
daniela_ebertwhich options do you have in mind tongli?14:36
tongliI am thinking flat which seems to me to be more practical like how google does it.14:36
dmelladohow to you plan to run the k8s workload?14:37
dmelladok8s over OpenStack?14:37
dmelladoif so, it could even make sense to give kuryr a try14:37
daniela_ebertflat sounds less error-proune14:37
tongliflannal, is the overlay, since we are doing this on OpenStack, it will be overlay over overlay,14:37
zhipenghdmellado +114:37
tongliprobably will not be a good choice for production.14:38
topoltongli what would be a good hoice for production?14:38
markvoelker_From an interop perspective I think flat makes sense.  Not a lot of productized kuryr yet.14:38
tongli@dmellado, the workload will basically like this.14:38
markvoelker_O-in-o with flannel would probably be fine too, but there are some downsides to that approach.14:38
topolmarkvoelker+++14:38
tongli1. provision few nodes (4 at first, configurable of course)14:39
tongli2. install k8s mater and 3 worker nodes14:39
tongli3. setup networking14:39
tongli4. start some container apps.14:39
tongli5. test they are all working14:39
tongli6 (option), remove a node, make sure everything still work14:40
topoltongli I vagely recall a walk stage of a k8s app as well :-014:40
dmelladotongli: ack, thanks for the clarification14:40
tongli7(option), add a node,14:40
tongli@dmellado, I think that is what I am thinking of doing now, basically k8s over openstack.14:41
tongliI do not know openstack over k8s will be something we should look into. but I am open.14:41
topolboth use cases are interesting but my preference is k8s over openstack... ask me why14:42
tongli@topol, why brad?14:42
topolthanks tongli :-). I owe you.14:43
dmelladoheh xD14:43
topolThere are many folks in the container world who view OpenStack as not providing value to k8s.   They say its too complicated, etc.14:43
gematopol: to be fair to them, I am still struggling to understand how this workout works14:44
topolI think we help OpenStack a lot if we show that k8s runs great on an OpenStack infrastructure14:44
gemaworkload, sorry14:44
topolgema at a high level I think of it as k8s using OpenStack as its cloud infrastructure14:45
tongli@gema, the problem is really the networking, what else can I say.14:45
gematopol: as the provider of what?14:45
gemacontainers?14:45
gemaVMs?14:45
zhipenghk8s is growing way more complicated ...14:45
gemaVMs with containers?14:45
topolCause the alternative is k8s doesnt use OpenStack, rolls its own volume storage and virtual networking and claims OpenStack provides no value14:45
tonglik8s also started doing the networking plugins.14:45
zhipenghtongli storage is alsi a headache14:46
zhipenghalso14:46
dmelladotopol: +1 on k8s over OpenStack14:46
topolzhipengh you are correct. But I see two possible futures14:46
topol1.  K8s runs great on OpenStack and the projects are complementary14:46
tongliany way, I just want to get a feel on how people thinking about networking choice for our workload.14:47
topol2.   k8s becomes frustrated with trying to make OpenStack work and reinvents all our wheels14:47
topolwhich future do we want?14:47
tonglimost likely that the workload will need OpenStack tenant network.14:47
topoltongli, that is up to us to show the way forward?  Does that make sense?14:48
* gema wonders how topol and tongli's private meetings look like, each one of them following their own train of thought x)14:48
zhipenghtongli volumes are a mess atm14:48
tongli@topol, understand.14:48
gemazhipengh: what does that mean?14:48
zhipenghtopol i doubt they could do 2 tbh14:48
topolgema how so?  the meetings usually end up with me taking tongli to lunch and he forgets is wallet (not last time though, he paid)14:48
gemahaha14:49
tongli@topol, haha.14:49
zhipenghgema k8s has a volume plugin mechanism, but the in-tree and out-of-tree are still up to debate14:49
tonglibecause I was so focused on my work.14:49
topolon a serious note, if this group doesnt show k8s running great on OpenStack,  who else would?14:49
zhipenghanyways OpenStack could do a lot as a cloudprovider for k8s14:49
zhipenghtopol agree14:49
topolI have been to kubecon,  OpenStack does not get high praise fromt hat community..14:50
tongliok, guys, I did not want to start a meeting to talk about which is better, just want to know the preference of networking for our k8s workload.14:50
tongliI will go with the flat for now and see how it goes.14:50
topolso that's why I think we help OpenStack if we do k8s over OpenStack as the focus14:50
gematongli: sorry I was only able to follow topol's meeting line14:50
topolsorry tongli go ahead14:51
dmelladotongli: on that,  I guess we can go for flat first, and then let's see if we can get to flannel if everything works ok14:51
topolany concerns with going flat first?14:51
gemanope, sounds easier14:52
tongli@dmellado, that is what I am thinking as well, since this is a bit sensitive to our various network implementation from many different cloud.14:52
tongliI know some of the folks do not have tenant network.14:52
topol#agreed k8s workload will use flat networking  first14:53
topolok 7 mins left14:53
tongliI forgot which cloud, but at least there were two clouds do not support tenant network.14:53
gematongli: is this how we use it: https://kubernetes.io/docs/getting-started-guides/openstack-heat/ ?14:53
tongli@gema, can not use heat14:53
gemais the heat api the right one for this?14:53
tonglimost clouds do not have it on.14:54
gemaoh, so we are ahead of ourselves, ok14:54
dmelladogema: depending on what we want to do14:54
topol#topic plans for Boston14:54
*** openstack changes topic to "plans for Boston (Meeting topic: interop_challenge)"14:54
dmelladoI guess we can switch heat for ansible as an orchestrator14:54
gemadmellado: ok, I will listen to you guys, you have tried it14:54
gemago ahead topol14:55
topolSo I havent thought about trying to getback on the keynote stage for Boston.  It was a lot of pressure and my fear was we'd go back into make things work and lock them down14:55
topolas opposed to having less pressure to make progress on interop with the workloads14:56
topolmark voelker, tongli, and I are submitting a session to do an update on phase two14:56
gemaplus it wouldn't be as impressive anymore since we've done it once?14:56
gemaok14:57
topolgema.  yes not as much to gain because that day in Barcelona was magical14:57
tongli@gema, unless something very different and as exciting as what we did last time.14:57
*** rarcea has joined #openstack-meeting-514:57
dmelladomaybe some kind of workshop14:57
dmelladoi mean, a session showing how do we run the workloads on the clouds14:57
topolBut I think a workshop session would be awesome to submit14:57
zhipenghForum ?14:57
topoldmellado +++14:57
dmelladowhere any dev from any cloud might join14:57
topolzhipengh, I think Anni Lai from Huawei is trying to put together a panel too14:58
dmelladoI'll try to put something as a session before the deadline14:58
tongli@topol, I like workshop a lot.14:58
dmelladowhen was it, Feb 6th?14:58
topoldmellado  please put a session together.  Include some other folks if you dont mind14:59
topoldmellado, yes Feb 6th is the deadline14:59
dmelladosure, is there anyone around who sould like to co-present?14:59
dmelladogema: hogepodge luzC ?14:59
dmelladoanyone ?14:59
topoldmellado want me to voluntold tongli?15:00
markvoelker_I can probably help with that15:00
gemaI would love to, but I am not sure I am going to be there x D15:00
daniela_ebertI could help with that dmellado15:00
topoldaniela_bert, very nice15:00
tongliI can help with workshop sessions.15:00
dmelladocool, then IIRC there's a max of 3 presenters15:00
dmelladolet me check15:00
luzCyes, o/15:01
topolwould be nice to get as many folks visibility as we can15:01
dmelladotongli: markvoelker_ tongli15:01
dmelladoif you guys are doing the another session15:01
dmelladoI'll put daniela_ebert and luzC along15:01
dmelladowould that work for you guys?15:02
dmelladowe can all together work on the workshop in any case15:02
topoldmellado that makes sense to me15:02
topoleveryone okay with that?15:02
tongliwe ran out the time.15:02
dmelladoyep15:03
daniela_ebertfine with me :-)15:03
dmelladodaniela_ebert: luzC I'll put a brief description and add you as co-presenters so you can edit it15:03
dmelladotomorrow morning my time ;)15:03
topolk ping folks on irc if any concerns15:03
topol#endmeeting15:03
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:03
openstackMeeting ended Wed Feb  1 15:03:33 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:03
openstackMinutes:        http://eavesdrop.openstack.org/meetings/interop_challenge/2017/interop_challenge.2017-02-01-14.00.html15:03
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/interop_challenge/2017/interop_challenge.2017-02-01-14.00.txt15:03
openstackLog:            http://eavesdrop.openstack.org/meetings/interop_challenge/2017/interop_challenge.2017-02-01-14.00.log.html15:03
*** gema has left #openstack-meeting-515:03
*** zhipengh has left #openstack-meeting-515:04
*** tongli has quit IRC15:09
*** sigmavirus has quit IRC15:14
*** makowals_ has quit IRC15:18
*** makowals has joined #openstack-meeting-515:19
*** sigmavirus has joined #openstack-meeting-515:23
*** tongli has joined #openstack-meeting-516:38
*** Rockyg has joined #openstack-meeting-516:41
*** daniela_ebert has quit IRC16:57
*** tongli has quit IRC17:00
hogepodgedmellado: you can add me to anything. I'm pretty much afk for this week, but can talk more Monday.17:10
*** ralonsoh has quit IRC18:04
*** ricolin has joined #openstack-meeting-518:04
*** ricolin has quit IRC18:11
*** makowals has quit IRC18:13
*** makowals has joined #openstack-meeting-518:16
*** rarcea has quit IRC18:55

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