Wednesday, 2016-09-14

*** sdake_ has quit IRC00:17
*** sdake has joined #openstack-meeting-cp00:17
*** gouthamr has quit IRC01:17
*** sdake_ has joined #openstack-meeting-cp01:45
*** sdake_ has quit IRC01:45
*** sdake_ has joined #openstack-meeting-cp01:45
*** sdake has quit IRC01:47
*** stevemar_ is now known as stevemar02:49
*** uxdanielle has quit IRC03:35
*** prateek has joined #openstack-meeting-cp06:38
*** Rockyg has joined #openstack-meeting-cp06:49
*** Horax has joined #openstack-meeting-cp06:52
*** Horax has left #openstack-meeting-cp07:08
*** homerp_ has quit IRC07:42
*** homerp has joined #openstack-meeting-cp07:42
*** prateek has quit IRC09:03
*** coolsvap_ is now known as coolsvap09:09
*** prateek has joined #openstack-meeting-cp09:21
*** sdake_ has quit IRC09:28
*** kbyrne has quit IRC10:02
*** kbyrne has joined #openstack-meeting-cp10:06
*** prateek has quit IRC10:22
*** prateek has joined #openstack-meeting-cp10:33
*** sdague has joined #openstack-meeting-cp11:08
*** gouthamr has joined #openstack-meeting-cp12:09
*** uxdanielle has joined #openstack-meeting-cp12:12
*** xyang1 has joined #openstack-meeting-cp12:37
*** markvoelker has joined #openstack-meeting-cp13:43
*** tongli has joined #openstack-meeting-cp13:43
*** daibz has joined #openstack-meeting-cp13:55
*** catherine_d|1 has joined #openstack-meeting-cp13:57
*** sdake has joined #openstack-meeting-cp13:58
*** MarkBaker has joined #openstack-meeting-cp13:58
topol#startmeeting interop_challenge14:00
openstackMeeting started Wed Sep 14 14:00:20 2016 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
markvoelkero/14:00
topolHi everyone, who is here for the interop challenge meeting today?14:00
skazio/14:00
Rockygo/14:00
catherine_d|1o/14:01
topolThe agenda for today can be found at:14:01
topol#link https://etherpad.openstack.org/p/interop-challenge-meeting-2016-09-1414:01
topolWe can use this same etherpad to take notes14:01
topol#topic review action items from previous meeting14:01
*** openstack changes topic to "review action items from previous meeting (Meeting topic: interop_challenge)"14:01
*** eeiden has joined #openstack-meeting-cp14:01
topol#link http://eavesdrop.openstack.org/meetings/interop_challenge/2016/interop_challenge.2016-09-07-14.00.html14:02
topoltongli topol check on ATT NFV workload scripts.14:02
topol    tongli and topol to check with MarkBaker on write up/point to some docs instructing people how to get going (juju + NFV)14:02
topolI don't believe we got anything on this. MarkBaker you around?14:02
luzCo/14:03
topolI think we are running out of time for this to make it for Barcelona14:03
luzCsorry to be late, what is the topic?14:03
*** lizdurst_ has joined #openstack-meeting-cp14:04
topolespecially based on foundation feedback which I will get to later14:04
eeidenHey all -- sorry was out of the office for about a week and a half. I'm 90% sure we have a workload ready to go, just need to get in contact with the owner.14:04
*** kbyrne has quit IRC14:04
topoleeiden, okay let see what shows up.14:04
topolluzC we are reviewing action items from last meeting14:05
*** jkomg has joined #openstack-meeting-cp14:05
luzCcool, thanks14:05
topolNext action was fredli, will take the action to find out about the DT cloud.14:05
topolany update on DT cloud?14:05
*** JASON__ has joined #openstack-meeting-cp14:05
JASON__Hi, all14:05
*** pilgrimstack has joined #openstack-meeting-cp14:06
topolRockyg, any idea about DT cloud?14:06
*** kbyrne has joined #openstack-meeting-cp14:06
*** sajeesh has joined #openstack-meeting-cp14:06
pilgrimstackHi from OVH14:06
JASON__We will get the answer from DT cloud by end of this week14:07
RockygJASON__,    topol just asked about dt cloud.  any update?14:07
topolJASON__, cool14:07
Rockygthanks14:07
JASON__we have forwarded the message to them in last week14:07
topolpilgrimstack what does OVH stand for just curiously?14:07
*** rarcea has joined #openstack-meeting-cp14:07
*** rohit404 has joined #openstack-meeting-cp14:07
topol#action JASON__, Rockyg  to check on DT cloud14:08
tongli@topol, both Huawei public cloud and DT cloud, I think.14:08
*** Tetsuo_ has joined #openstack-meeting-cp14:08
JASON__BTW , We are prepare the testing on HW cloud since last meeting with tongli14:08
pilgrimstacktopol: what do you mean? what do you want to know?14:08
JASON__Got it14:08
Rockygtongli, yes, right14:08
topol#action JASON__, Rockyg  to check on Huaweii cloud as well14:09
JASON__I will pass the message to all of your guys asap14:09
topolpilgrimstack, its an acronym correct?  Like IBM is Intenrational Business Machines14:09
JASON__Sure, topol14:09
JASON__I will report the progress14:09
* topol I didnt know what OVH stood for as an acronym. And since your cloud is working with the workloads wanted to know :-)14:10
JASON__we have team to support the testing , but i need tongli help as well .14:10
topolJASON__ you may have tongli :-)14:10
JASON__thanks , topol .14:11
pilgrimstackhaha, good question, their is many different stories :p the main one is "On Vous Heberge" in french which means "We Host You"14:11
topolpilgrimstack, That works. Thanks14:11
tongli@pilgrimstack, thanks for pointing me to a different region. BTW, both region worked.14:12
topolnext item Rockyg to post request for clouds to openstack-ops ML14:12
topolRockyg were you able to do that?14:12
*** Daviey_ is now known as Daviey14:12
Rockygoh.  dang.  that was me, too?  dang. today14:12
topolok perfect.  #action Rockyg to post to openstack-ops ML14:13
JASON__@tongli, rocky, do you know the progress of DefCore guideline14:13
topolnext item catherine_d|1 to provide new wiki section for volunteer a cloud acct/who to contact14:13
topolthis was done14:13
catherine_d|1yup14:13
topolThanks!14:14
topolnext item pilgrimstack1 to run workload and also get tongli acess14:14
Rockyglink, please?14:14
topolI believe this is done.  tongli is able to succesfully run on OVH14:14
tongli@topol, yes. OVH worked well in terms of interop.14:15
tongliso did OSIC cloud. with no issues.14:15
topolcatherine_d|1 where did you add this?14:15
topolyes, towards the end we will cover where workloads are successfully running. we have a list14:16
JASON__@all , when the deadline of testing ?14:16
catherine_d|1one sec ..14:16
topolJASON__ we agreed two weeks before Barcelona.  But But sooner is always much better14:17
luzCtongli on OSIC cloud you are changing terraform workload to use Ansible instead right?14:17
JASON__thanks.14:17
topolespecially since the foundation is reviewing stuff14:17
topolokay todays agenda items14:17
tongli@luzC, yes, terraform won't work against many clouds since the multiple endpoints issue,14:18
topolyes, the terraform issue is on todays agenda14:18
tonglithat can not be resolved by changing scripts.14:18
topolwe'll get there folks. I promise14:18
topol#topic Update from meeting/demo with OpenStack Foundation Jonathan Bryce14:18
*** openstack changes topic to "Update from meeting/demo with OpenStack Foundation Jonathan Bryce (Meeting topic: interop_challenge)"14:18
topolDemo went well.  Jonathan most like the LAMPStack workload because it was a true enterprise app with security rules, etc.  This is the app he wants folks to see running across multiple cloud targets14:19
topolHe had an upcoming production call where they will discuss how to show off.14:19
*** rarcea has quit IRC14:19
topolSo everyone should focus on that workload as the priority since that is the one that fits best into the foundations messaging on this topic during the Barcelona keynote day 214:20
*** hj-hpe has joined #openstack-meeting-cp14:20
JASON__got it14:21
catherine_d|1Rockyg: https://wiki.openstack.org/wiki/Interop_Challenge  under the " Test Candidate Process" with tongli: 's contact info14:21
hj-hpeSorry, I got late to the party this morning14:21
topolso this workload uses advanced features like security groups that not all clouds support.  Jonathan's preference was that we stick with this workload because it is a true enterprise workload14:21
Rockygthanks14:21
*** gema has joined #openstack-meeting-cp14:22
topoland Jonathan was okay if a few clouds could not run this workload.  That just leaves room for improvement14:22
topolI would suspect as part of the Keynote they will have several of us up on stage representing the different participating vendors. We’ll keep you posted.14:23
topolI also expect we will be asked for quotes from the different vendors on the importance of interop/value of the the work.14:23
*** rarcea has joined #openstack-meeting-cp14:23
topol#action please figure out who is the right executive in your company that is supposed to handle quotes for the press.  We will need to have PR folks contact them and will need to move quickly on that.  Check with your OpenStack Board member rep.14:23
topolThey typically do it or know who should14:23
topolseveral folks were in attendance with the meeting with Jonathan. Anything else folks would like to mention?14:24
topolMarkVoelker, Rockyg? ^14:24
topolmarkvoelker14:25
RockygOther than the demo went well, nope.14:25
* markvoelker has nothing further14:25
topolcool14:25
topolnext topic:14:25
topol#topic  Interop-challenge code repository, should we establish a more responsive project?14:25
*** openstack changes topic to "Interop-challenge code repository, should we establish a more responsive project? (Meeting topic: interop_challenge)"14:25
topolSo Im getting lots of complaints that where we are trying to host the workloads reviews/merges are taking too long14:26
topolsomeone suggested #link https://github.com/openstack/defcore14:26
Rockygmet with the app ecosystem wg.  They are interested, but timeline might be too long.14:27
markvoelkerCurrently that repo has three cores: myself, hogepodge, and eglute.  I'm not opposed to creating a contrib directory or something if it's helpful.14:27
tongli@markvoelker, that repo is quite big, that is only my concern.14:28
topoltongli as part of the demo do you have to clone the repo or that step is already done?14:29
tongli@markvoelker, not against using it though.14:29
topolwhere does it being a large repo impact us?14:29
luzCI think because of the nature of the workloads is better to keep them on osops-tools-contrib14:30
luzCbut not sure how to accelerate the review process14:30
topolluzC can we get faster reviews?14:30
luzCprobably posting on the ops channel when pending reviews are in the queue14:30
luzClooking for the ptl (if any)... not sure how that particular group works14:31
topolluzC, K please see if we can get reviews speeded up.14:31
topolwe have other repos where we could make everyone cores. tongli has OpenStaclk kiloeyes14:32
topoltongli has big patches that need reviewed I believe14:32
tonglihttps://review.openstack.org/#/q/project:openstack/kiloeyes14:33
topol#action luzC to see if we can get reviews speeded up14:33
tonglithat repo was created for a different purpose, I own it but it is a openstack big tent project.14:33
topoltongli did your big patches get reviewed yet?14:33
tongliif we want to remake that repo, I am ok.14:34
tongli@topol, no.14:34
markvoelker#link https://review.openstack.org/#/c/366784/ < tongli's big patch14:34
markvoelkertongli is this still WIP or has it settled now?  I noticed several new patchsets coming in over the past couple of days after I initially reviewed it14:35
tonglimark reviewed the earlier version, but since then I have made a lot of changes, mainly to add ansible docker swarm tests14:35
* markvoelker notes for future reference that it would probably be easier to attract core reviews if the changes were broken out into separate reviews...this patch does 3 different things.14:36
tongli@markvoelker, now the patch is final, not WIP.14:36
markvoelkerthanks14:36
markvoelkerI'll review it again14:36
luzCme too14:36
markvoelker(and run it again)14:36
tongli@markvoelker, not plan to change anything unless something really bad found.14:36
topolgiven the foundation is most excited about this workload and its hopefully final, this problem may not be as big an issue14:37
topoldoes that seem correct to everyone?14:37
topollet's see if we can make the current repo work14:38
topolunless folks have a better suggestion?14:38
topolluzC, markvoelker, tongli thoughts?14:38
markvoelkerFine by me14:39
luzC+114:39
topolK14:39
tongli@topol, ok, I will keep sending the request for review emails to the defcore channel14:39
topolnext topic14:39
topol#topic Tenant network assumption in the workloads14:39
*** openstack changes topic to "Tenant network assumption in the workloads (Meeting topic: interop_challenge)"14:39
tongliprobably going to piss off few, but brad will take them to lunch in barcelona.14:39
topollunch, beers, both14:40
topolsome vendors do not expose or support tenant network, lampstack workload has been modified to accommodate that setup. A tenant network is no longer needed14:40
topolso tongli, question on this14:40
topolwhen tenant network is no longer required  you no longer use the security groups stuff correct?14:41
tonglisecurity group is still needed.14:41
tongliwhen tenant network is not exposed, the script just does not use one.14:41
rohit404^ topol: nice to have the flexibility for non-tenant networks (provider networks i assume)14:42
tonglisecurity groups created against like all hosts not on specific subnet.14:42
tongliit is more of flat network vs overlay network.14:43
tonglithe script now handle both.14:43
tongliif you do not have a tenant network, leave that parameter blank.14:43
topolok good.  so even with the non-tenant network we don't lose our enterprise features with port egress and ingress?14:43
tonglibut security group is required.14:43
tongliif your cloud does not allow security group, the script fails.14:43
tongli@topol, right. we do not lose anything.14:44
tongliwill use whatever the cloud default to.14:44
topoltongli, ok good. so hopefully these changes allow more clouds to run the workload.14:44
tonglibut security group is still required.14:44
topolok cool.14:44
tonglirright.14:44
tongliright.14:44
topolthanks for doing this tongli14:45
JASON__i suggest we need to check with cloud service guys14:45
topolnext topic and its a biggie14:45
topol#topic Terraform falls over when multiple endpoints for a service (such as compute server) exist from a cloud,14:45
*** openstack changes topic to "Terraform falls over when multiple endpoints for a service (such as compute server) exist from a cloud, (Meeting topic: interop_challenge)"14:45
topolso Tong ran into this in the OSIC cloud.14:46
topolappears to be a well know bug in TerraForm.14:46
tongliterraform has code specifically detect if a OS service has multiple endpoints, if there is, the code simply throw an error and quit14:46
tonglithis is a problem I can not overcome by changing the work load scripts.14:46
topoland the only way Tong got around this was to create an Ansible playbooks for the docker swarm workload14:46
topoltongli did I get everything correct on this?14:47
tongliso I rewrote the work load scripts using ansible which also allows one to run work load a lot easier14:47
markvoelkerFor clarity: you mean like a cloud for which there are multiple regions?  Or a cloud which supports both KEystone v2 and v3?  Or...?14:47
tongli@markvoelker, not multiple regions.14:47
* topol that question is for tong:-)14:47
topoltwo nova endpoint versions?14:48
tongli@markvoelker, say your cloud in a region supports couple v2 and v2.1 endpoints,14:48
tongliterrafrom will fail in this case.14:48
tonglisay your cloud supports both compute 2.0 and 2.1 endpoints, terrafrom will fail.14:49
topolso anyone know any terraform experts?14:49
tongliI suspect this will be quite common. OSIC does that, that is where I found the issue.14:49
markvoelkerIs it checking the catalog, or just using what's in "GET / http://myapiserver:8774/" ?14:49
tongli@markvoelker, I think terraform OS cloud module checks against keystone to get various service endpoints.14:50
tongliyou may notice in the work load tests, we only give keystone endpoint.14:50
tonglithere is no any other endpoints given. cloud modules work under the cover for different service endpoints.14:50
tongliwhich is actually a good thing for interop.14:51
tonglithis in a way testing how keystone works.14:51
*** rohit404 has quit IRC14:51
topolso we can check with the bluebox team since they have experience with TerraForm.  unless anyone knows of a better terraform guru14:51
markvoelkerOk, guess that explains why a lot of folks haven't run into this then.  Most private cloud catalogs I see only contain one nova endpoint even if it supports v2 and v2.1.14:51
tonglias long as there is one end point per service , it is fine.14:52
topolmarkvoelker ++ but in OSIC  its gameover :-)14:52
tonglidoes not matter 2.0 or 2.114:52
tonglibut I can not be 100% sure. I also noticed that terraform states some version supports on openstack.14:52
tongliI am a bit worried about continuing using it.14:53
tonglivs ansible , it just uses shade.14:53
topolso tongli and I can check with our gurus. But tongli provided ansible because we are nervous about this14:53
markvoelkerSo topol, what's the ask here?  You want us to re-run using the ansible version of the workload?14:53
tongliterraform was created using go lang, so the OS module will have to be recreated a lot of what shade does.14:53
topolhmmm.  good question markvoelker14:54
topolwhat do you recommend?14:54
* markvoelker notes that tong's patch referenced above contains the new code14:54
tongli@markvoelker, I would say yes, if your cloud is already working with terraform and lampstack,14:54
tonglirunning ansible script takes even less time for docker swarm.14:54
tongliit will also show when the script started and how long it took to finish.14:55
topolthat would be helpful if folks could try the new ansible script. if terraform already works my view is you still get the checkbox14:55
topolbut under our lessons learned we need to flag this14:55
tonglithe instruction is here for docker swarm. https://review.openstack.org/#/c/366784/7/ansible/dockerswarm/README.md14:55
markvoelkerIMHO it seems like there's some knowledge uncovered here that people would want to know about.14:55
topolmarkvoelker DEFINITELY14:56
topolmarkvoelker you are reading my mind14:56
tongli@markvoelker, +114:56
markvoelkerI would kinda hate to see us tell people not to use the terraform version at all anymore if only a handful have run it so far and it's uncovered something interesting.14:56
markvoelkerPersonally I don't mind running both versions...they're quick.14:56
topolmarkvoelker cool14:56
tongliright.14:57
topolI agree. Let's ask folks to try and run both.14:57
luzCagree14:57
tongliif just use ansible one, you only need to setup ansible env.14:57
topol#action all  try and run both terraform and ansible of docker swarm14:57
tonglinot both ansible and terraform.14:57
topolokay last item14:57
topol#topic Tong needs to test on other folks public clouds ASAP. Here are the cloud Tong has tested against14:58
*** openstack changes topic to "Tong needs to test on other folks public clouds ASAP. Here are the cloud Tong has tested against (Meeting topic: interop_challenge)"14:58
topolOSIC - lampstack and docker swarm both successful14:58
topol    OVH - lampstack and docker swarm both successful14:58
topol    IBM Bluebox - lampstack and docker swarm both successful14:58
topol    RAX Public Cloud-As far as we can tell RAX public cloud does not support security groups  LAMPStack will not run14:58
topol    Mirantis ?14:58
topol    Huawei ?14:58
topolany updates to this14:58
topolRAX public is an issue.14:58
JASON__DT?14:58
JASON__maybe14:58
rarceaso, for SUSE we are testing inhouse and will report the results soon14:58
topolJASON__  yes please :-)14:59
tongliRAX cloud does not support security group, both test won't run, not only lampstack.14:59
topolrarcea. cool let us know14:59
topoleglute need your guidance on RAX public14:59
topol#action tong and brad to ask eglute about running on RAX public and security group support14:59
topolso folks based on foundation input please try and run LAMPStack workload first since they will want to demo that15:00
topol#action all please prioritize testing of LAMPStack15:00
tongliI think Mr. Bryce is pretty happy with use of ansible.15:00
tonglihe made some comments on ansible, do not remember exact words.15:01
topolI think we covered everything and we are out of time. pelase folks keep running workloads. Bug us if you need help!!!15:01
topolThanks everyone!15:01
JASON__thanks15:01
topol#endmeeting15:01
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:01
openstackMeeting ended Wed Sep 14 15:01:57 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/interop_challenge/2016/interop_challenge.2016-09-14-14.00.html15:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/interop_challenge/2016/interop_challenge.2016-09-14-14.00.txt15:02
openstackLog:            http://eavesdrop.openstack.org/meetings/interop_challenge/2016/interop_challenge.2016-09-14-14.00.log.html15:02
*** JASON__ has quit IRC15:02
*** daibz has quit IRC15:03
*** lizdurst_ has quit IRC15:05
*** david-lyle_ has joined #openstack-meeting-cp15:06
*** david-lyle_ has quit IRC15:06
*** hemnafk is now known as hemna15:10
*** hogepodge has joined #openstack-meeting-cp15:34
*** catherine_d|1 has left #openstack-meeting-cp15:52
*** prateek has quit IRC15:55
*** Tetsuo_ has quit IRC16:07
*** reed_ has joined #openstack-meeting-cp16:32
*** reed_ has quit IRC16:54
*** MarkBaker has quit IRC17:01
*** Kiall_ is now known as Kiall17:03
*** MarkBaker has joined #openstack-meeting-cp17:09
*** sajeesh has quit IRC18:44
*** prateek has joined #openstack-meeting-cp19:24
*** prateek has quit IRC19:24
*** sdake_ has joined #openstack-meeting-cp19:29
*** sdake has quit IRC19:33
*** gouthamr has quit IRC20:07
*** tongli has quit IRC20:38
*** gouthamr has joined #openstack-meeting-cp20:43
*** hemna is now known as hemnafk20:44
*** coolsvap has quit IRC20:52
*** rarcea has quit IRC21:37
*** hj-hpe has quit IRC22:33
*** uxdanielle has quit IRC22:37
*** sdake_ has quit IRC22:40
*** sdague has quit IRC23:02
*** xyang1 has quit IRC23:10

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