Wednesday, 2017-01-18

*** Daisy has joined #openstack-meeting-501:31
*** Daisy has quit IRC01:35
*** Daisy has joined #openstack-meeting-502:04
*** Daisy has quit IRC02:06
*** jrist has quit IRC02:18
*** jrist has joined #openstack-meeting-502:32
*** luzC has quit IRC03:23
*** luzC has joined #openstack-meeting-504:22
*** jrist has quit IRC07:11
*** jrist has joined #openstack-meeting-507:11
*** jrist has quit IRC07:14
*** jrist has joined #openstack-meeting-507:16
*** ralonsoh has joined #openstack-meeting-508:18
*** matrohon has joined #openstack-meeting-508:22
*** markvoelker has joined #openstack-meeting-508:26
*** matrohon has quit IRC11:20
*** kbaikov has joined #openstack-meeting-512:31
*** tongli has joined #openstack-meeting-513:01
*** matrohon has joined #openstack-meeting-513:03
*** matrohon_ has joined #openstack-meeting-513:14
*** matrohon has quit IRC13:17
*** zhipengh has joined #openstack-meeting-513:44
*** Rocky_g has joined #openstack-meeting-514:00
topolstartmeeting interop_challenge14: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-01-1814:00
topolWe can use this same etherpad to take notes14:00
dmelladoo/14:00
dmelladohi topol14:00
markvoelkero/14:00
tonglio/14:00
hogepodgeo/14:00
Rocky_go/14:00
topol#topic Review last meeting action items14:01
topol     #link http://eavesdrop.openstack.org/meetings/interop_challenge/2017/interop_challenge.2017-01-11-14.01.html14:01
skazio/14:01
topoltongli to check on eeiden about NVF workload14:02
zhipengho/14:02
topoltongli were you able to get a hold of eeiden?14:02
tongli@topol, brad, that was not done but I have a few more people who will be willing to work on NFV. a writeup about the workload will be done very quickly.14:03
topoltongli, that works :-)14:03
tongliI will have some details in the agenda.14:03
topolK, I put you on the agenda. you will see where14:03
topolzhipeng to add overview section to lessons learned doc14:04
*** gema has joined #openstack-meeting-514:04
tongliwhen we go through the agenda, I can talk about them.14:04
topolthis was done14:04
topolzhipeng pushed a fitst patch for folks to review14:04
zhipenghand updated with a second one :)14:04
tongli@topol. I feel the patch is a bit overlap with the conclusion section of the doc.14:04
topol#link https://review.openstack.org/#/c/421275/14:05
topola little overlap is okay.  I'll re-review the whole doc14:05
tonglialso it stated that ansible + shade is the recommended approach, do we want to say that?14:05
tongliI am not really sure about it. but we are clearly doing it.14:06
topolwell nsible + shade is what we had the most success with across all the cloud environments14:06
tongliok.14:06
topolThat I think is a fair statement14:06
tonglisure.14:06
topolso in aany case folks please review this patch14:06
markvoelkerI think it's fair to say we found it to be a good choice, but I'd be careful to word it such that we don't look like we're saying we did an exhaustive evaluation of many options14:07
topoltongli to create an etherpad for PTG topics real fast so we can put the link in this meeting <-- This was completed and on our agenda to review14:07
dmellado+1, I'd say that it's an approach that worked fine for us so far14:07
topolmarkvoelker +++ I agree, please make a comment on the pacth with that suggestion14:07
topoldmellado feel free to comment on the patch as well14:08
tongli@markvoelker, @dmellado, you guys said what I could not say it well.14:08
zhipenghmarkvoelker agree14:08
topol#topic Patches that need review  #link https://review.openstack.org/#/q/status:open+project:openstack/interop-workloads,n,z14:09
tongliI did not want to make that strong a statement. basically that is the reason I did not +1.14:09
topolwe have three patches for folks to review14:09
*** daniela_ebert has joined #openstack-meeting-514:09
topolso if you have some time please review. Great to see folks making updates!14:09
topol#topic Update from tongli on interlock on interop with OpenStack China companies14:10
topoltongli, update us please. whats happening in Beijing14:10
*** garloff has joined #openstack-meeting-514:10
tonglithere were total 10 parties/companies attended their interop challenge wg kick off meeting.14:11
tongliI have listed these companies/parties in the etherpad.14:11
tonglisome I do not have their English names.14:11
tongliplease take a look at the etherpad.14:12
tongliI gave an introduction session talked about our effort and what we have done and what we have planed to do.14:12
tongliguys from ZTE, Huawei, China Mobile will start working on NFV workload.14:13
topollist of companies ooks strong14:13
topoltongli very nice to see folks start on NFV workload!14:13
tonglion the second day of the meeting, I went over the LAMPStack workload, and talked about the structure of the new repo.14:13
tonglihow the new workload should look like and how to deal with different targets etc.14:14
tonglithese companies have started running LAMPStack on their cloud, few have run the workload successfully but most of them have various issues.14:14
topoltongli can any of the folks attend our irc interop meeting? is the time too late for them?14:15
zhipenghfor the second round, should we provide use case descriptions for each workload to be tested ?14:15
tonglitwo companies will also have resources to help with Kubernetes workload14:15
tonglisome of them will attend this IRC meeting,14:15
topoltongli excellent14:16
garloffIt would seem reasonable for them to pass LAMP first before moving to more advanced workloads, no?14:16
tonglithey want to use our time Tuesday night 10:00pm at this channel to do their own meeting since the meeting will be conducted in Chinese.14:16
topolgarloff, if they have enough resources theymight be able to both in parallel14:16
garloffok14:16
tongli@garloff, yes, they are doing exactly that.14:16
topolthey are all doing lampstack first?14:17
tonglithey also want to develop some workloads from their own use cases. but that will come later.14:17
garloffMy worry otherwise would be is that we test interop at container level where possibly the lower layers (OpenStack) are not interoperable at all ...14:17
tonglibut all agreed to put their workload in the same repo.14:17
tongliso we will have to review more workloads.14:17
topoltongli, so putting the workloads in the same repo is key.  Ideally we end up with a broad set of workloads for demonstrating interop14:18
topoltongli, reviewing more workloads is a good thing!14:18
tongli@topol, I am hoping that they can officially use this channel at our time Tuesday night 10:00pm.14:18
tongliand their conversations will be also recorded just like ours.14:19
topoltongli, dont they just have to reserve the slot?14:19
tonglieverything (meetings, workloads) will be all at the same place.14:19
tongliyes, I do not know how to reserve that.14:19
topoltongli shamail knows how to do this14:20
topolI believe14:20
tongliok, let me ask him to help.14:20
topoltongli thanks14:20
tonglior he can point me to the right place.14:20
tongliyes, please add an action for me.14:20
* garloff will not try to read a conversation recorded in chinese though14:20
topol#action tongli to work with shamail to reserve evening timeslot on meeting5 for china interop14:21
tongli@garloff, some of the conversation probbably will be in English.14:21
kbaikovo/14:21
topolgarloff I will struggle with that as well14:21
tonglithey were a bit afraid using English will take them 3 times longer to do the same thing in Chinese.14:21
topoltongli, this is excellent progress. Any more updates on the china company interop initiative?14:21
tonglithey are excited and ready to contribute, i am very happy about that.14:22
topoltongli thats fine, perhaps a meetign sumamr or action items can be added in english?14:22
tonglithey will have a summit in April and Interop show off is part of it.14:22
tongliI think they have allocated 10 minutes for a demo.14:23
topoltongli you will attend their meeting correct? So you can keep us updated?14:23
tonglimost likely they will use LAMPStack, maybe a new one.14:23
tongliI will try to at least attend first few ones.14:23
topoltongli ok14:23
tonglibut they will be on Chinese New Year next week for about two weeks.14:24
topoltongli or at least read their meeting minutes?14:24
tongliso their first will be in Feb.14:24
tongli@topol, I will attend.14:24
tongliand report back next day in our meeting.14:24
topolhow many folks do we have who speak chinese? You cdiep, zhipeng?  perhaps you can split the translation duties?14:25
tonglisure. that will be nice.14:25
tonglior use google translate?14:25
topolI know catherine (cdiep) speaks chinese14:25
gemagoogle translate won't work for chinese, I don't think14:26
gemaplus what do you guys want to translate?14:26
tongli@gema, it does.14:26
gemasurely just the main points?14:26
topolgema+++ Just need a sumamry or main points or issues14:26
tonglihaha, yeah, I can help, no worries.14:26
gematongli: great news :D14:26
topolok, great progress, tongli is that all on the china meetings?14:26
dmelladoplease, chinese it's not my greatest skill14:27
dmelladoxD14:27
* topol me either14:27
Rocky_gNo, it works kind of ok.the ordering of clauses can get weird, but lots of folks keep it simple on irc, so that helps14:27
tongli@topol, that is all.14:27
topol#topic Check on possible day/time for our half day session at PTG14:27
topolmarkvoelker, any clarity on when we might squeeze the half day session in?14:28
tongli@topol. I have put the china trip update on the etherpad before this meeting. you can also check it out if you like14:28
markvoelkerI have an email out to catherine to start banging on the schedule--hopefully we'll get that settled in the next few days.14:28
topolalso I was hoping I could fly in monday morning (one less day away from the family).  So if its not first thing monday morning I wont cry14:29
topolmarkvoelker, that sounds good14:29
topolmarkvoelker, our flight from rdu is only like an hour. YAY!14:30
markvoelker=)14:30
Rocky_gTopol, just don't snow ;-)14:30
* topol guessing that markvoelker could use coming in monday morning too14:30
dmelladoI'd try my best to squeeze there in too, I'll be attending some another sessions too14:31
topolRocky_g snow is an evil word around here14:31
* markvoelker is in face flying in on Monday morning14:31
dmellado(also let's see how the jet lag treats me after my 10 hour flight xD)14:31
markvoelker*fact14:31
Rocky_gOops. I meant snore. Sorry to swear.14:31
topolmarkvoelker what time?14:31
tongliI have not booked the flight yet.14:32
markvoelkertopol: I land at 7:30am in ATL.  Should be at the PTG shortly thereafter.14:32
topolI have not booked flight yet either but will soon14:32
Rocky_gOuch14:32
topolRocky_g I agree, that seems a little early14:33
topol#topic Review current PTG Agenda  #link https://etherpad.openstack.org/p/interop-challenge-meeting-2017-01-1114:33
gemamarkvoelker: you are too efficient14:33
topolany updates?14:33
topolgema, efficient would be he leaves at a time where he can take the kids to school monday morning then head to the airport. Im channeling Mark's wife :-)14:34
gema:)14:34
tonglihaha.14:34
topolgema, at least thats my plan14:34
topolso folks take a look at the ptg agenda. any updates? Additions?14:35
gematopol: do we need to spend time of the morning organizing a dinner?14:36
tongliBoston activities?14:36
gematopol: cannot we do that in advance?14:36
tongliwhat we should do as a group for Boston summit?14:36
topolgema, as far as Im concerned either way. a dinner should not take long to organize14:36
tongli@topol, should not take more than 2 minutes. I do put there so that we know we will have a dinner, no?14:37
Rocky_g++14:37
gemaack14:37
topollets see how many people we are. did folks add their name on the etherpad so we know who will be there14:37
gemaNFV is behind organising a dinner14:37
eeidenA quick NFV note since it's on the agenda -- OPNFV had a 2 week delay due to lab issues, so we're still trying to verify that we got the workload fixed. I'll keep you all posted as it progresses, but we're working to get it up and in the repo asap.14:37
gemathat's how I read it xD14:37
tongli@gema, that list is not the priority list. :-)14:38
topoleeiden did you see we have some companies in china interested in adding an nfv workload as well14:38
Rocky_gUh, Gigli, when was the last time you tried to get even ten engineers to are on food choices?14:38
gematongli: great, thanks for clarifying14:38
eeidenooh no I did not!14:38
Rocky_gGigli should be tongli. Dang phone auto correct14:38
topoleeiden connect with tongli for details14:38
eeidenThanks!14:39
topollots of restaurant in ATL. we'll find somehting great Im sure14:39
tongli@eeiden, look at my updates on the etherpad can also help.14:39
topol#action all, please review and update PTG agenda with topics #link https://etherpad.openstack.org/p/interop-challenge-meeting-2017-01-1114:40
topol #topic Open discussion14:40
topolany other topics for today?14:40
tongliBrad, I added an item for discussion.14:41
tongliI have started working on Kubernetes workload.14:41
topoltongli go ahead14:41
tongligot one question though,14:41
zhipengh@tongli could you first provide a spec describing the use case for k8s workload ?14:41
tonglicompile kubernetes normally will take about 1 hour.14:41
tongliso that is not really good.14:42
topoltongli, my compile takes about 18 minutes.  Are you generating a release as well?14:42
tongliso I have decided to use the prebuilt kubernetes14:42
topoltongli, prebuilt seems okay to me14:42
tongliyou can download from here.14:42
topoltongli, you running in a VM?14:43
tonglihmmm. mine took way longer, I am not sure even 18 minutes is good enough.14:43
tongliyes. running in a VM.14:43
tongliit has to.14:43
topoltongli how much memory, cpus and diskspace did you allocate? we should compare envs14:43
topolin any case prebuilt I think is fine14:44
topolIm guessing most folks would appreciate the stability of not compiling Kube everytime14:45
topolIs everyone ok with prebuilt Kube?14:45
hogepodgeMagnum can have a kube cluster up in minutes14:45
tongliif we do compile , will it buy us anything ?14:45
tonglithe VM I have has 8 GB of memory, 10 GB diskspace.14:45
tongliused 4 GB, actually the compiler run out memory and died.14:45
tongliok, if no one object, I will use the prebuilt kubernetes.14:45
tongliuse prebuilt image?14:45
topoltongli Ha Ha Ha. I did that too. Also didnt provide enough diskspace. An even more painful mistake14:46
tongli@hogepodge, if not use prebuilt image, I would really like to know how they did it.14:46
topol8GB memory and 80GB disk space is my rule14:46
topoltongli, as ton ngo14:46
topolhe is magnum core14:46
hogepodgeThey use prebuilt images.14:46
tongli@topol, I have already talked to him.14:47
topolhogepodge +++14:47
tonglihe said it normally will take about 30 minutes to 1 hour to build it14:47
topoltongli sounds about right14:47
tonglihe suggested to use the binary and gave me the url14:47
topoltongli, I think using the binary makes a lot of sense14:47
tongli@hogepodge, I would love to know how Magnum does it within minutes.14:48
topoltongli, my guess is they have it on an image and provision the image14:48
topolcooking show, cake is already baked :-)14:48
tongliif yes, I do not know if we want to go that route.14:49
hogepodgeThey use an image like coreos. They just have to boot then wire everything together14:49
tonglido we want to do that?14:49
tongliour dockerwarm workload uses coreos image already.14:49
topolmy preference would be to do it how real operators would actually do it14:49
tongli@topol, that is my preference as well.14:50
topolmy guess that is something probably more on the faster side14:50
tongli@zhipeng, the spec in one sentence will be create a kubernetes cluster on OpenStack cloud.14:50
topoltongli, what did ton ngo recommend14:51
topolI would start with that14:51
zhipengh@tongli and to do what ?14:51
tongliuse binary.14:51
tonglinot to use image14:51
zhipenghI think we should have scenarios other than just purely testing stuff14:51
tongliif use the coreos image, then there isn't a whole lot need to be done.14:51
topolzhipengh. thats fine14:51
topolcan you think of stuff to add. we can view getting kube cluster up as the crawl stage14:52
tongli@zhipeng, propose what you like to do, and do it.14:52
tonglipatch will be really nice.14:52
Rocky_g++14:52
topolSo Im okay with crawl, walk, run approach with kube14:53
topolget something going and then build a bigger scenario with it14:53
tongli@topol. I was thinking once we have basic stuff working, then we can add/remove worker nodes, and ensure cluster still working.14:53
tongliapps are still running.14:53
topolso tongli go the binary route and then lets build on top of it14:54
tongliright.14:54
topolscenario suggestions and code are welcome14:54
tonglicreate a basic working workload, then add more things to it.14:54
topolsounds like a good approach to me14:54
topolI have some friends in kubernetes land that do Kube apps. So if we need suggestions there we can follow up14:55
tongliok.14:56
topoleveryone ok with the approach we are taking with Kube?14:56
Rocky_gYeah. But we do eventually need the app on top14:56
topolRocky_g agreed14:57
Rocky_gKewl14:57
Rocky_gI'm dropping off. In China and have an early morning. Bye!14:58
topolKubernetes has a whole SIG dedicated to Apps.  The WG lead is very nice.  I just have to goto slack to contact her14:58
topolOK.14:58
topol#action tongli to use binary to do kube, will add an app/scenario on top. looking for suggestions14:58
tongli@Rocky_g, I am in china as well.14:58
*** Rocky_g has quit IRC14:58
topol1 min left. anthing else?14:58
tongliwe are good I think.14:59
topolK, great meeting everyone! Thanks for partiicpating14:59
topol#endmeeting14:59
*** daniela_ebert has quit IRC15:00
*** tongli has quit IRC15:00
topol#startmeeting interop_challenge15:01
openstackMeeting started Wed Jan 18 15:01:50 2017 UTC and is due to finish in 60 minutes.  The chair is topol. Information about MeetBot at http://wiki.debian.org/MeetBot.15:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:01
*** openstack changes topic to " (Meeting topic: interop_challenge)"15:01
openstackThe meeting name has been set to 'interop_challenge'15:01
topoltopol: startmeeting interop_challenge15:01
topol09:00 topol: Hi everyone, who is here for the interop challenge meeting today?15:01
topol09:00 topol: The agenda for today can be found at:15:01
topol09:00 topol: # https://etherpad.openstack.org/p/interop-challenge-meeting-2017-01-1815:01
topol09:00 topol: We can use this same etherpad to take notes15:02
topol09:00 dmellado: o/15:02
topol09:00 dmellado: hi topol15:02
topol09:00 markvoelker: o/15:02
topol09:00 tongli: o/15:02
topol09:00 hogepodge: o/15:02
topol09:00 Rocky_g: o/15:02
topol09:01 topol: #topic Review last meeting action items15:02
topol09:01 topol:     #link http://eavesdrop.openstack.org/meetings/interop_challenge/2017/interop_challenge.2017-01-11-14.01.html15:02
topol09:01 skazi: o/15:02
topol09:02 topol: tongli to check on eeiden about NVF workload15:02
topol09:02 zhipengh: o/15:02
topol09:02 topol: tongli were you able to get a hold of eeiden?15:02
topol09:03 tongli: @topol, brad, that was not done but I have a few more people who will be willing to work on NFV. a writeup about the workload will be done very quickly.15:02
topol09:03 topol: tongli, that works :-)15:02
topol09:03 tongli: I will have some details in the agenda.15:02
topol09:03 topol: K, I put you on the agenda. you will see where15:02
topol09:04 topol: zhipeng to add overview section to lessons learned doc15:02
topol09:04 gema has joined (~Gema@host31-48-176-122.range31-48.btcentralplus.com)15:02
topol09:04 tongli: when we go through the agenda, I can talk about them.15:02
topol09:04 topol: this was done15:02
topol09:04 topol: zhipeng pushed a fitst patch for folks to review15:02
topol09:04 zhipengh: and updated with a second one :)15:02
topol09:04 tongli: @topol. I feel the patch is a bit overlap with the conclusion section of the doc.15:02
topol09:05 topol: #link https://review.openstack.org/#/c/421275/15:02
topol09:05 topol: a little overlap is okay.  I'll re-review the whole doc15:02
topol09:05 tongli: also it stated that ansible + shade is the recommended approach, do we want to say that?15:02
topol09:06 tongli: I am not really sure about it. but we are clearly doing it.15:02
topol09:06 topol: well nsible + shade is what we had the most success with across all the cloud environments15:02
topol09:06 tongli: ok.15:02
topol09:06 topol: That I think is a fair statement15:03
topol09:06 topol: so in aany case folks please review this patch15:03
topol09:06 tongli: sure.15:03
topol09:07 markvoelker: I think it's fair to say we found it to be a good choice, but I'd be careful to word it such that we don't look like we're saying we did an exhaustive evaluation of many options15:03
topol09:07 topol: tongli to create an etherpad for PTG topics real fast so we can put the link in this meeting <-- This was completed and on our agenda to review15:03
topol09:07 dmellado: +1, I'd say that it's an approach that worked fine for us so far15:03
topol09:07 topol: markvoelker +++ I agree, please make a comment on the pacth with that suggestion15:03
topol09:08 topol: dmellado feel free to comment on the patch as well15:03
topol09:08 tongli: @markvoelker, @dmellado, you guys said what I could not say it well.15:03
topol09:08 zhipengh: markvoelker agree15:03
topol09:09 topol: #topic Patches that need review  #link https://review.openstack.org/#/q/status:open+project:openstack/interop-workloads,n,z15:03
topol09:09 tongli: I did not want to make that strong a statement. basically that is the reason I did not +1.15:03
topol09:09 topol: we have three patches for folks to review15:03
topol09:09 daniela_ebert has joined (c2191e09@gateway/web/freenode/ip.194.25.30.9)15:03
topol09:09 topol: so if you have some time please review. Great to see folks making updates!15:03
topol09:10 topol: #topic Update from tongli on interlock on interop with OpenStack China companies15:03
topol09:10 topol: tongli, update us please. whats happening in Beijing15:03
topol09:10 garloff has joined (~kgarloff@160.44.193.111)15:03
topol09:11 tongli: there were total 10 parties/companies attended their interop challenge wg kick off meeting.15:03
topol09:11 tongli: I have listed these companies/parties in the etherpad.15:03
topol09:11 tongli: some I do not have their English names.15:03
topol09:12 tongli: please take a look at the etherpad.15:03
topol09:12 tongli: I gave an introduction session talked about our effort and what we have done and what we have planed to do.15:03
topol09:13 tongli: guys from ZTE, Huawei, China Mobile will start working on NFV workload.15:03
topol09:13 topol: list of companies ooks strong15:03
topol09:13 topol: tongli very nice to see folks start on NFV workload!15:03
topol09:13 tongli: on the second day of the meeting, I went over the LAMPStack workload, and talked about the structure of the new repo.15:03
topol09:14 tongli: how the new workload should look like and how to deal with different targets etc.15:03
topol09:14 tongli: these companies have started running LAMPStack on their cloud, few have run the workload successfully but most of them have various issues.15:03
topol09:15 topol: tongli can any of the folks attend our irc interop meeting? is the time too late for them?15:03
topol09:15 zhipengh: for the second round, should we provide use case descriptions for each workload to be tested ?15:04
topol09:15 tongli: two companies will also have resources to help with Kubernetes workload15:04
topol09:15 tongli: some of them will attend this IRC meeting,15:04
topol09:16 topol: tongli excellent15:04
topol09:16 garloff: It would seem reasonable for them to pass LAMP first before moving to more advanced workloads, no?15:04
topol09:16 tongli: they want to use our time Tuesday night 10:00pm at this channel to do their own meeting since the meeting will be conducted in Chinese.15:04
topol09:16 topol: garloff, if they have enough resources theymight be able to both in parallel15:04
topol09:16 garloff: ok15:04
topol09:16 tongli: @garloff, yes, they are doing exactly that.15:04
topol09:17 topol: they are all doing lampstack first?15:04
topol09:17 tongli: they also want to develop some workloads from their own use cases. but that will come later.15:04
topol09:17 garloff: My worry otherwise would be is that we test interop at container level where possibly the lower layers (OpenStack) are not interoperable at all ...15:04
topol09:17 tongli: but all agreed to put their workload in the same repo.15:04
topol09:17 tongli: so we will have to review more workloads.15:04
topol09:18 topol: tongli, so putting the workloads in the same repo is key.  Ideally we end up with a broad set of workloads for demonstrating interop15:04
topol09:18 topol: tongli, reviewing more workloads is a good thing!15:04
topol09:18 tongli: @topol, I am hoping that they can officially use this channel at our time Tuesday night 10:00pm.15:04
eeidenWould we be interested in having both workloads if we can get ours up soon?15:04
topol09:19 tongli: and their conversations will be also recorded just like ours.15:04
topol09:19 topol: tongli, dont they just have to reserve the slot?15:04
topol09:19 tongli: everything (meetings, workloads) will be all at the same place.15:04
topol09:19 tongli: yes, I do not know how to reserve that.15:04
topol09:20 topol: tongli shamail knows how to do this15:04
topol09:20 topol: I believe15:04
topol09:20 tongli: ok, let me ask him to help.15:04
topol09:20 topol: tongli thanks15:04
topol09:20 tongli: or he can point me to the right place.15:04
topol09:20 tongli: yes, please add an action for me.15:04
topol09:20 garloff will not try to read a conversation recorded in chinese though15:04
topol09:21 topol: #action tongli to work with shamail to reserve evening timeslot on meeting5 for china interop15:04
topol09:21 tongli: @garloff, some of the conversation probbably will be in English.15:04
topol09:21 kbaikov: o/15:05
topol09:21 topol: garloff I will struggle with that as well15:05
topol09:21 tongli: they were a bit afraid using English will take them 3 times longer to do the same thing in Chinese.15:05
topol09:21 topol: tongli, this is excellent progress. Any more updates on the china company interop initiative?15:05
topol09:22 tongli: they are excited and ready to contribute, i am very happy about that.15:05
topol09:22 topol: tongli thats fine, perhaps a meetign sumamr or action items can be added in english?15:05
topol09:22 tongli: they will have a summit in April and Interop show off is part of it.15:05
topol09:23 tongli: I think they have allocated 10 minutes for a demo.15:05
topol09:23 topol: tongli you will attend their meeting correct? So you can keep us updated?15:05
topol09:23 tongli: most likely they will use LAMPStack, maybe a new one.15:05
topol09:23 tongli: I will try to at least attend first few ones.15:05
topol09:23 topol: tongli ok15:05
topol09:24 tongli: but they will be on Chinese New Year next week for about two weeks.15:05
topol09:24 topol: tongli or at least read their meeting minutes?15:05
topol09:24 tongli: so their first will be in Feb.15:05
topol09:24 tongli: @topol, I will attend.15:05
topol09:24 tongli: and report back next day in our meeting.15:05
topol09:25 topol: how many folks do we have who speak chinese? You cdiep, zhipeng?  perhaps you can split the translation duties?15:05
topol09:25 tongli: sure. that will be nice.15:05
topol09:25 tongli: or use google translate?15:05
*** kbaikov has left #openstack-meeting-515:05
luzCo/15:05
topol09:25 topol: I know catherine (cdiep) speaks chinese15:05
topol09:26 gema: google translate won't work for chinese, I don't think15:05
topol09:26 gema: plus what do you guys want to translate?15:05
topol09:26 tongli: @gema, it does.15:05
topol09:26 gema: surely just the main points?15:05
topol09:26 topol: gema+++ Just need a sumamry or main points or issues15:05
topol09:26 tongli: haha, yeah, I can help, no worries.15:05
topol09:26 gema: tongli: great news :D15:05
topol09:26 topol: ok, great progress, tongli is that all on the china meetings?15:05
topol09:27 dmellado: please, chinese it's not my greatest skill15:05
topol09:27 dmellado: xD15:06
topol09:27 topol me either15:06
topol09:27 Rocky_g: No, it works kind of ok.the ordering of clauses can get weird, but lots of folks keep it simple on irc, so that helps15:06
topol09:27 tongli: @topol, that is all.15:06
topol09:27 topol: #topic Check on possible day/time for our half day session at PTG15:06
topol09:28 topol: markvoelker, any clarity on when we might squeeze the half day session in?15:06
topol09:28 tongli: @topol. I have put the china trip update on the etherpad before this meeting. you can also check it out if you like15:06
topol09:28 markvoelker: I have an email out to catherine to start banging on the schedule--hopefully we'll get that settled in the next few days.15:06
topol09:29 topol: also I was hoping I could fly in monday morning (one less day away from the family).  So if its not first thing monday morning I wont cry15:06
topol09:29 topol: markvoelker, that sounds good15:06
topol09:30 topol: markvoelker, our flight from rdu is only like an hour. YAY!15:06
topol09:30 markvoelker: =)15:06
topol09:30 Rocky_g: Topol, just don't snow ;-)15:06
topol09:30 topol guessing that markvoelker could use coming in monday morning too15:06
topol09:31 dmellado: I'd try my best to squeeze there in too, I'll be attending some another sessions too15:06
topol09:31 topol: Rocky_g snow is an evil word around here15:06
topol09:31 markvoelker is in face flying in on Monday morning15:06
topol09:31 dmellado: (also let's see how the jet lag treats me after my 10 hour flight xD)15:06
topol09:31 markvoelker: *fact15:06
topol09:31 Rocky_g: Oops. I meant snore. Sorry to swear.15:06
topol09:31 topol: markvoelker what time?15:06
topol09:32 tongli: I have not booked the flight yet.15:06
topol09:32 markvoelker: topol: I land at 7:30am in ATL.  Should be at the PTG shortly thereafter.15:06
topol09:32 topol: I have not booked flight yet either but will soon15:06
topol09:32 Rocky_g: Ouch15:06
topol09:33 topol: Rocky_g I agree, that seems a little early15:06
topol09:33 topol: #topic Review current PTG Agenda  #link https://etherpad.openstack.org/p/interop-challenge-meeting-2017-01-1115:06
topol09:33 gema: markvoelker: you are too efficient15:06
topol09:33 topol: any updates?15:06
topol09:34 topol: gema, efficient would be he leaves at a time where he can take the kids to school monday morning then head to the airport. Im channeling Mark's wife :-)15:06
topol09:34 gema: :)15:07
topol09:34 tongli: haha.15:07
topol09:34 topol: gema, at least thats my plan15:07
topol09:35 topol: so folks take a look at the ptg agenda. any updates? Additions?15:07
topol09:36 gema: topol: do we need to spend time of the morning organizing a dinner?15:07
topol09:36 tongli: Boston activities?15:07
topol09:36 gema: topol: cannot we do that in advance?15:07
topol09:36 tongli: what we should do as a group for Boston summit?15:07
topol09:36 topol: gema, as far as Im concerned either way. a dinner should not take long to organize15:07
topol09:37 tongli: @topol, should not take more than 2 minutes. I do put there so that we know we will have a dinner, no?15:07
topol09:37 Rocky_g: ++15:07
topol09:37 gema: ack15:07
topol09:37 topol: lets see how many people we are. did folks add their name on the etherpad so we know who will be there15:07
topol09:37 gema: NFV is behind organising a dinner15:07
topol09:37 eeiden: A quick NFV note since it's on the agenda -- OPNFV had a 2 week delay due to lab issues, so we're still trying to verify that we got the workload fixed. I'll keep you all posted as it progresses, but we're working to get it up and in the repo asap.15:07
topol09:37 gema: that's how I read it xD15:07
topol09:38 tongli: @gema, that list is not the priority list. :-)15:07
topol09:38 topol: eeiden did you see we have some companies in china interested in adding an nfv workload as well15:07
topol09:38 Rocky_g: Uh, Gigli, when was the last time you tried to get even ten engineers to are on food choices?15:07
topol09:38 gema: tongli: great, thanks for clarifying15:07
topol09:38 eeiden: ooh no I did not!15:07
topol09:38 Rocky_g: Gigli should be tongli. Dang phone auto correct15:07
topol09:38 topol: eeiden connect with tongli for details15:07
topol09:39 eeiden: Thanks!15:07
topol09:39 topol: lots of restaurant in ATL. we'll find somehting great Im sure15:07
topol09:39 tongli: @eeiden, look at my updates on the etherpad can also help.15:07
topol09:40 topol: #action all, please review and update PTG agenda with topics #link https://etherpad.openstack.org/p/interop-challenge-meeting-2017-01-1115:07
topol09:40 topol: #topic Open discussion15:07
topol09:40 topol: any other topics for today?15:07
topol09:41 tongli: Brad, I added an item for discussion.15:07
topol09:41 tongli: I have started working on Kubernetes workload.15:08
topol09:41 topol: tongli go ahead15:08
topol09:41 tongli: got one question though,15:08
topol09:41 zhipengh: @tongli could you first provide a spec describing the use case for k8s workload ?15:08
topol09:41 tongli: compile kubernetes normally will take about 1 hour.15:08
topol09:42 tongli: so that is not really good.15:08
topol09:42 topol: tongli, my compile takes about 18 minutes.  Are you generating a release as well?15:08
topol09:42 tongli: so I have decided to use the prebuilt kubernetes15:08
topol09:42 topol: tongli, prebuilt seems okay to me15:08
topol09:42 tongli: you can download from here.15:08
topol09:43 topol: tongli, you running in a VM?15:08
topol09:43 tongli: hmmm. mine took way longer, I am not sure even 18 minutes is good enough.15:08
topol09:43 tongli: yes. running in a VM.15:08
topol09:43 tongli: it has to.15:08
topol09:43 topol: tongli how much memory, cpus and diskspace did you allocate? we should compare envs15:08
topol09:44 topol: in any case prebuilt I think is fine15:08
topol09:45 topol: Im guessing most folks would appreciate the stability of not compiling Kube everytime15:08
topol09:45 topol: Is everyone ok with prebuilt Kube?15:08
topol09:45 hogepodge: Magnum can have a kube cluster up in minutes15:08
topol09:45 tongli: if we do compile , will it buy us anything ?15:08
topol09:45 tongli: the VM I have has 8 GB of memory, 10 GB diskspace.15:08
topol09:45 tongli: used 4 GB, actually the compiler run out memory and died.15:08
topol09:45 tongli: ok, if no one object, I will use the prebuilt kubernetes.15:08
topol09:45 tongli: use prebuilt image?15:08
topol09:46 topol: tongli Ha Ha Ha. I did that too. Also didnt provide enough diskspace. An even more painful mistake15:08
topol09:46 tongli: @hogepodge, if not use prebuilt image, I would really like to know how they did it.15:08
topol09:46 topol: 8GB memory and 80GB disk space is my rule15:08
topol09:46 topol: tongli, as ton ngo15:08
topol09:46 topol: he is magnum core15:08
topol09:46 hogepodge: They use prebuilt images.15:08
topol09:47 tongli: @topol, I have already talked to him.15:09
topol09:47 topol: hogepodge +++15:09
topol09:47 tongli: he said it normally will take about 30 minutes to 1 hour to build it15:09
topol09:47 topol: tongli sounds about right15:09
topol09:47 tongli: he suggested to use the binary and gave me the url15:09
topol09:47 topol: tongli, I think using the binary makes a lot of sense15:09
topol09:48 tongli: @hogepodge, I would love to know how Magnum does it within minutes.15:09
topol09:48 topol: tongli, my guess is they have it on an image and provision the image15:09
topol09:48 topol: cooking show, cake is already baked :-)15:09
topol09:49 tongli: if yes, I do not know if we want to go that route.15:09
topol09:49 hogepodge: They use an image like coreos. They just have to boot then wire everything together15:09
topol09:49 tongli: do we want to do that?15:09
topol09:49 tongli: our dockerwarm workload uses coreos image already.15:09
topol09:49 topol: my preference would be to do it how real operators would actually do it15:09
topol09:50 tongli: @topol, that is my preference as well.15:09
topol09:50 topol: my guess that is something probably more on the faster side15:09
topol09:50 tongli: @zhipeng, the spec in one sentence will be create a kubernetes cluster on OpenStack cloud.15:09
topol09:51 topol: tongli, what did ton ngo recommend15:09
topol09:51 topol: I would start with that15:09
topol09:51 zhipengh: @tongli and to do what ?15:09
topol09:51 tongli: use binary.15:09
topol09:51 tongli: not to use image15:09
topol09:51 zhipengh: I think we should have scenarios other than just purely testing stuff15:09
topol09:51 tongli: if use the coreos image, then there isn't a whole lot need to be done.15:09
topol09:51 topol: zhipengh. thats fine15:09
topol09:52 topol: can you think of stuff to add. we can view getting kube cluster up as the crawl stage15:09
topol09:52 tongli: @zhipeng, propose what you like to do, and do it.15:09
topol09:52 tongli: patch will be really nice.15:09
topol09:52 Rocky_g: ++15:09
topol09:53 topol: So Im okay with crawl, walk, run approach with kube15:09
topol09:53 topol: get something going and then build a bigger scenario with it15:10
topol09:53 tongli: @topol. I was thinking once we have basic stuff working, then we can add/remove worker nodes, and ensure cluster still working.15:10
topol09:53 tongli: apps are still running.15:10
topol09:54 topol: so tongli go the binary route and then lets build on top of it15:10
topol09:54 tongli: right.15:10
topol09:54 topol: scenario suggestions and code are welcome15:10
topol09:54 tongli: create a basic working workload, then add more things to it.15:10
topol09:54 topol: sounds like a good approach to me15:10
topol09:55 topol: I have some friends in kubernetes land that do Kube apps. So if we need suggestions there we can follow up15:10
topol09:56 tongli: ok.15:10
topol09:56 topol: everyone ok with the approach we are taking with Kube?15:10
topol09:56 Rocky_g: Yeah. But we do eventually need the app on top15:10
topol09:57 topol: Rocky_g agreed15:10
topol09:57 Rocky_g: Kewl15:10
topol09:58 Rocky_g: I'm dropping off. In China and have an early morning. Bye!15:10
topol09:58 topol: Kubernetes has a whole SIG dedicated to Apps.  The WG lead is very nice.  I just have to goto slack to contact her15:10
topol09:58 topol: OK.15:10
topol09:58 topol: #action tongli to use binary to do kube, will add an app/scenario on top. looking for suggestions15:10
topol09:58 tongli: @Rocky_g, I am in china as well.15:10
topol09:58 Rocky_g has left IRC (Quit: Bye)15:10
topol09:58 topol: 1 min left. anthing else?15:10
topol09:59 tongli: we are good I think.15:10
topol09:59 topol: K, great meeting everyone! Thanks for partiicpating15:10
topol09:59 topol: #endmeeting15:10
topol10:00 daniela_ebert has left IRC (Quit: Page closed)15:10
topol#end meeting15:10
topol#endmeeting15:10
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:10
openstackMeeting ended Wed Jan 18 15:10:54 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:10
openstackMinutes:        http://eavesdrop.openstack.org/meetings/interop_challenge/2017/interop_challenge.2017-01-18-15.01.html15:10
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/interop_challenge/2017/interop_challenge.2017-01-18-15.01.txt15:10
topoleeiden, sure15:11
openstackLog:            http://eavesdrop.openstack.org/meetings/interop_challenge/2017/interop_challenge.2017-01-18-15.01.log.html15:11
*** openstack has joined #openstack-meeting-515:20
*** ChanServ sets mode: +o openstack15:20
*** jlvillal_ is now known as jlvillal15:20
*** jlvillal is now known as Guest8897715:20
*** fungi has joined #openstack-meeting-515:21
*** ttx has joined #openstack-meeting-515:21
*** Daviey has joined #openstack-meeting-515:22
*** MarkAtwood has joined #openstack-meeting-515:27
*** hogepodge has joined #openstack-meeting-515:31
*** eeiden has joined #openstack-meeting-515:53
*** markvoelker has quit IRC16:11
*** Guest88977 is now known as jlvillal16:25
*** zhipengh has quit IRC16:29
*** gema has left #openstack-meeting-516:47
*** matrohon_ has quit IRC17:23
*** markvoelker has joined #openstack-meeting-517:38
*** markvoelker_ has joined #openstack-meeting-517:44
*** markvoelker has quit IRC17:46
*** markvoelker has joined #openstack-meeting-517:58
*** markvoelker_ has quit IRC18:01
*** ralonsoh has quit IRC18:05
*** matrohon has joined #openstack-meeting-519:49
*** markvoelker_ has joined #openstack-meeting-520:03
*** markvoelker has quit IRC20:05
*** matrohon has quit IRC20:19
*** markvoelker_ has quit IRC20:32
*** fungi has quit IRC23:24
*** garloff has quit IRC23:24
*** fungi has joined #openstack-meeting-523:24
*** garloff has joined #openstack-meeting-523:24

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