Wednesday, 2016-08-17

*** hockeynut has joined #openstack-defcore00:22
*** kei has joined #openstack-defcore00:40
*** kei_ has quit IRC00:42
*** hockeynut has quit IRC01:02
*** hockeynut has joined #openstack-defcore01:02
*** woodster_ has quit IRC01:09
*** kei_ has joined #openstack-defcore03:20
*** kei has quit IRC03:21
*** rarcea has quit IRC03:23
*** rarcea has joined #openstack-defcore03:36
*** hockeynut has quit IRC04:03
*** gema has quit IRC05:06
*** gema has joined #openstack-defcore05:08
*** kei_ has quit IRC06:39
*** markvoelker has quit IRC07:00
*** markvoelker has joined #openstack-defcore08:00
*** markvoelker has quit IRC08:05
*** kbaikov has joined #openstack-defcore08:28
*** markvoelker has joined #openstack-defcore09:01
*** markvoelker has quit IRC09:06
*** kbaikov has quit IRC09:32
*** openstack has joined #openstack-defcore10:18
*** kbaikov has joined #openstack-defcore11:00
*** markvoelker has joined #openstack-defcore12:09
*** pilgrimstack has joined #openstack-defcore12:19
*** pilgrimstack has quit IRC12:40
*** pilgrimstack has joined #openstack-defcore12:46
openstackgerritMark T. Voelker proposed openstack/defcore: Create first Interop Issues Report  https://review.openstack.org/35452813:07
*** pilgrimstack has quit IRC13:30
openstackgerritMark T. Voelker proposed openstack/defcore: Create 2016.08 Guideline from next.json  https://review.openstack.org/35133913:32
*** woodster_ has joined #openstack-defcore13:34
*** pilgrimstack has joined #openstack-defcore13:36
*** edmondsw has joined #openstack-defcore13:37
*** tongli has joined #openstack-defcore13:39
*** ametts has joined #openstack-defcore13:40
*** AlanClark has joined #openstack-defcore13:58
*** rohit404 has joined #openstack-defcore13:59
*** jokoester has joined #openstack-defcore13:59
*** catherine_d|1 has joined #openstack-defcore13:59
topol#startmeeting interop_challenge14:00
openstackMeeting started Wed Aug 17 14:00:02 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
openstackThe meeting name has been set to 'interop_challenge'14:00
catherine_d|1o/14:00
markvoelkero/14:00
gemao/14:00
topolHi everyone, who is here for the interop challenge meeting today?14:00
rohit404o/14:00
tonglio/14:00
topolThe agenda for today can be found at:14:00
topol#link https://wiki.openstack.org/wiki/Interop_Challenge#Meeting_Information14:01
topolIn case we need to take notes, the etherpad for this meeting can be found here14:01
topol#link https://etherpad.openstack.org/p/interop-challenge-meeting-2016-08-1714:01
topol#topic review action items from previous meeting14:01
topol#link14:02
topolhttp://eavesdrop.openstack.org/meetings/interop_challenge/2016/interop_challenge.2016-08-10-14.00.html14:02
*** leong has joined #openstack-defcore14:02
*** woodburn has joined #openstack-defcore14:02
*** kei has joined #openstack-defcore14:02
leongo/14:03
*** tkfjt has joined #openstack-defcore14:03
topolHave folks added which version of OpenStack they plan to interop?14:03
keio/14:03
topoltongli, shamail, where folks supposed to put this?14:03
gemawhere do we add that?14:03
*** dbutsu has joined #openstack-defcore14:03
*** tetsuo has joined #openstack-defcore14:03
tongli@topol, I would say put in the etherpad, then put in the summary after.14:04
topoltongli, that works.  for now folks can add it to the bottom of the etherpad for todays meeting14:05
* markvoelker notes that in the 8/3 meeting some folks reported plans to use Mitaka and Kilo (see line 35 of https://etherpad.openstack.org/p/interop-challenge-meeting-2016-08-03#35 )14:05
*** dcnatt_ has joined #openstack-defcore14:05
topoltongli can you gather all this up and then put somewhere?  Separate etherpad for it perhaps???14:05
tongli@topol, let's just use this etherpad. too many links probably not good.14:06
topolAlso it looks like in last weeks meeting everyone agreed to start with LAMPStack14:07
tongli@topol, I put it at the end of today's etherpad.14:07
*** catherine_d|1 has quit IRC14:07
tongli@topol, we voted using ansible.14:07
topoltongli, thats fine just gather up from last weeks etherpad so its all inone place14:07
tonglithe lampstack ansible has been merged.14:07
topoltongli Yay!  That was my next item to review.14:07
tonglican other folks put your preferred test OS release in the etherpad, please!14:08
*** catherine_d|1 has joined #openstack-defcore14:08
*** Rockyg has joined #openstack-defcore14:08
*** lizdurst has joined #openstack-defcore14:08
topol#action other folks put your preferred test OS release in the etherpad, please!14:08
*** mfisher_ora has joined #openstack-defcore14:08
tongli@markvoelker, can you put your releases on the etherpad.14:09
topolThanks for the quick reviews and merge of LAMPStack14:09
markvoelkertongli: already did14:09
tongli@markvoelker, thanks.14:09
topolDid everyone look at the results template?  Any concerns with that?14:09
topol#link http://paste.openstack.org/show/553587/14:10
tongli@topol, we had discussion, and generally agree with the content.14:10
topolK cool.14:10
topol#agree Folks like the results template14:10
tongliI think that the question is how often we run the test against each cloud14:11
leongMaybe add an affiliate/company?14:11
topolleong good idea14:11
gemayep and we'll need to agree on what running successfully means14:11
gemaother than that I am also good14:11
tongliseems to me Mark wants to produce just one report per test per cloud, is that right? @markvoelker14:11
topol#action shamail to add affiliate/company to the results template14:12
markvoelkertongli: Well, Barcelona is about 69 days away.  I think a good start would be for vendors to show a result for their products that are on the market now and that consumers can actually get today14:12
topol@markvoelker, that sounds good to me14:12
markvoelkerThere's not likely to be tremendous churn in those products in the next 69 days, so I'm not sure multiple runs really tells us much.14:12
topol@markvoelker +++14:13
tongli@markvoelker, ok, fine.14:13
markvoelkerE.g. even if VendorX releases some maintenance patches for their Liberty distro, it seems relatively unlikely to break the workload.14:13
Rockyggood point, markvoelker14:13
topol#agree Folks should produce one report per cloud14:13
tongliI would like to ask if it is all possible that vendors create a test account for me, and I can run against each cloud.14:13
gematongli: are you volunteering to run the workloads instead of us running them independently? :D14:14
catherine_d|1The first test category is RefStack test ... At the minimum, all participants should collect RefStack test data now14:14
topolyes, so tongli is available to anyone that needs help and he is eager to run tests14:14
tongli@gema, yes. I am14:14
gematongli: you got it :D14:14
gematongli: thanks!14:14
topol@gema we are here to serve :-)14:15
gematopol:  :D14:15
tongliif that is ok, please send me the credentials to my email , I put the email in the etherpad.14:15
gematongli: as soon as the cloud is up will do :D14:15
topol#action if folks want tongli to help run tests on their cloud, get him an account14:15
catherine_d|1gema: does it make sense for someone else to run the tests?  Some clouds maybe private..14:15
gemacatherine_d|1: our cloud is going to be public and a developer cloud, so I am happy for him to try14:16
topolcatherine_d,  either way, as long as test get run14:16
gemacatherine_d|1: I will also try and it will be interesting to compare14:16
topolgema thats awesome14:16
topolokay, new topic14:16
*** brunssen has joined #openstack-defcore14:16
Rockygquestion -- creds and tongli doing tests will only work on public clouds... what about distros without a public cloud?14:16
gemaRockyg: those may stand up a test cloud for this testing anyway14:17
gemathey can run it14:17
brunsseno/14:17
topolRockyg I guess whoever has acces to the private cloud will have to run14:17
markvoelkerRockyg: I'm reading it as "if you want tongli to run tests for you and it's feasible to get him access to your cloud/lab/whatever, he's available. Otherwise, you can do it."14:17
gemayep14:17
topolas usual markvoelker is spot on14:17
topol#topic Test candidates review (refer to the current test candidates on the etherpad)14:18
catherine_d|1generally tongli: won't have access to the cloud for debug ... it may make sense that he run the last test run once all are verified working14:18
RockygGreat.  I think w should write rules a little more formally as part of the "challenge rules"14:18
dcnatt_Catching up. Has the team discussed a vnf test candidate yet?14:18
topolSo right now we have the docker terraform and LampStack with Ansible.  Do we need any more?14:19
markvoelkerdcnatt_: No, but test candidates is the current topic. =)14:19
topolThe foundation folks also would like an NFV app if possible14:19
topolI believe AT&T is looking for one of these14:20
dcnatt_Interested in throwing out nfv test candidate and containerized workloads for consideration14:20
topoldcnatt_  Yes, you haveone of these??14:20
dcnatt_I have inflight POCs for both14:20
dcnatt_Can repurpose14:20
*** hockeynut has joined #openstack-defcore14:20
dcnatt_If team sees value14:20
topoldcnatt_ when can code be pushed to the repository?14:20
dcnatt_lmc.. I wanted to propose here first then verify14:21
*** vkmc has joined #openstack-defcore14:21
topoldcnatt Definitely value.  I heard from the foundation folks they would like that included14:21
dcnatt_I'll pursue asap. What about containerized multi-cloud interop14:21
tongli@dncatt_, if you need any help with ansible, I like to lend a hand.14:22
topoldcnatt_  There is certainly interest in NFV.  There maybe interest in containerized multi-cloud interop. My guess is folks will want to see the workload code14:22
dcnatt_@tongli - thanks, always appreciated14:23
markvoelkerHm.  We have a Swarm workload.  I was monkeying with a k8s workload (deployed atop OS with Ansible) the other day in the lab.  Might be able to tidy that up if we need it.14:23
markvoelkerDo we though?14:23
topolSo best thing is to get the workload pushed up to the repository as soon as possible.14:23
dcnatt_We have semantic pipeline auth/auth at the CNI to support workloads across OS and AWS etc.14:24
topolMy hope is we get a few of these workloads runnning for everyone.  Then if time permits we can add others. Does that make sense?14:24
tongli@markvoelker, do you mean the docker swarm test already in the contrib project, or you have a different one?14:24
markvoelkertongli: the one already there14:24
topolDid we decide what should be the second workload to try and run?14:25
dcnatt_We are showing app decomp to component workloads, dynamic networking at the container level plumbed to virtual network across providers and managed by policy14:25
markvoelkertopol: Sure, time is of the essence (which is sort of why I was hesitating...we'd originally said we wanted workloads decided by Aug 8 =p)14:25
tongli@markvoelker, ok. thanks for clarifying it.14:25
topolmarkvoelker.  if we get them soon I think we are okay. We all just need near term deadlines to get the adrenaline going14:26
topolmarkvoelker I'm also okay with some workloads being run ats14:26
markvoelkertopol: Ok.  So if time permits I'll see if I can get a k8s workload posted.  If not, no worries, we can always do more workloads post-Barcelona.14:27
markvoelkerSound good?14:27
topolmarkvoelker sounds good14:27
tongliso work load tests as follows: 1. Ansible lampstack 2. Terraform docker swarm 3. ATT NFV?14:27
* markvoelker sets himself a reminder 14:27
dcnatt_Agree14:27
topoltongli YES!14:27
topoltongli you type faster than me14:28
gemawill the NFV workload run on a normal neutron enabled cloud?14:28
tongliso #3 is a try as much as possible?14:28
dcnatt_It will "Run"...14:28
topol#agree so work load tests as follows: 1. Ansible lampstack 2. Terraform docker swarm 3. ATT NFV14:28
topoldcnatt_ please push the code up as soon as you can. tongli can help with wrapping ansible around it14:28
dcnatt_Will do14:29
tongliawesome.14:29
topolone other question, did folks have issues with the Terraform?  If necessary tongli could rewrite as Ansible14:30
tongliI will  send results to the owner of the cloud who sends me account info.14:30
* topol topol ducks14:30
markvoelkertopol: no.  The more the merrier.14:30
topol#action let tongli, topol know if any issues with Terraform14:30
gematopol: no, we wanted to try different deployment methods for the different workloads14:31
gemato increase the coverage14:31
topolmarkvoelker okay tongli will be happy to hear that14:31
rohit404topol i gave the terraform docker swarm a spin last nite, saw some ssh key issues, i'll follow up14:31
Rockygtopol, good thing tongli has his hand full14:31
markvoelker(e.g. if Terraform or some other orch tool is making assumptions about what everyone's OpenStack clouds can do and that makes stuff break, that will be useful data)14:31
topolmarkvoelker ++ excellentpoint14:31
topol#topic Test environment from different vendors. or should we just test stuff against our own environment?14:32
topoli think we covered this.14:32
topolEveryone runs themselves but if you can give tongli access he is willing to help14:32
markvoelkertopol: ++14:32
gematopol: ++14:33
Rockyg==14:33
Rockyg++14:33
dcnatt_++14:33
topol#agree Everyone runs tests themselves but if you can give tongli access he is willing to help14:33
topolnew topic14:33
tonglionly 5 company indicated OS releases on etherpad, should there be more?14:33
catherine_d|1topol: ++14:34
topoltongli lets you and I follow up on who may be missing14:34
Rockygsorry guys.  It's really early and I'v bee doing early for the week.  Burnout14:34
Rockygsounds like we need to....14:35
dhellmanntongli : which etherpad?14:35
gemahttps://etherpad.openstack.org/p/interop-challenge-meeting-2016-08-1714:35
topol#action tongli and topol to follow up on who has declared  their release14:35
tongli@gema, you beat me on that.14:35
gematongli: :D14:35
topol#topic result repository14:36
topolSend as emails? Or a better suggestion?14:37
topola new folder in the ops repository that holds the workloads?14:37
tongliif we only produce one report per test per cloud, then email maybe just fine.14:37
dhellmannemail to the defcore mailing list?14:37
markvoelkerOr something like SurveyMonkey to make it a bit more structured, perhaps?14:38
Rockygdhellmann, sounds good...14:38
topoldhellmann, so folks won't view that as spam?14:38
dhellmanntopol : I was asking if that's what you meant by "email"14:39
topolas long as everyone is okay wiht the mailing list14:39
* markvoelker puts on DefCore co-chair hat14:39
markvoelkerI won't consider it spam. =)14:39
* markvoelker doffs hat14:39
Rockygmarkvoelker, ++14:39
* topol topol kisses the ring of markvoelker14:39
tongli@markvoelker, then defcore-committee mailing list.14:39
markvoelkerOk, so how about I post the information that we expect people to send in via email in some location that's more permanent that paste.openstack.org? =)14:40
markvoelkerDo we have a wiki page for the interop challenge?  If not maybe I'll just go create one.14:41
markvoelkertopol: ^^14:41
tongli@markvoelker, shamail already created one.14:41
topol#agree folks can email their results to the defcore mailing list14:42
catherine_d|1markvoelker: we do have wiki page for interop-challenge https://wiki.openstack.org/wiki/Interop_Challenge#Meeting_Information14:42
markvoelkerOk, I'll put it there14:42
topolgot diconeected for a sec14:43
topolso folks are to mail the list and markvoelker to record on the wiki page?14:43
markvoelkertopol: yep14:43
markvoelker#action markvoelker update wiki page with how to submit test results14:44
topol#action markvoelker to record results on the wiki page,  folks you email results to the defcore meeting list14:44
topolexcellent14:44
topol#topic next weeks meeting, topo and shamail at OpenStack East next week14:45
* markvoelker is too14:45
topolSo for next week should we cancel?14:45
topolOr we could leave the hour as an open office hour if folks need help from tongli14:45
dcnatt_is at containercon/cloud native day in Toronto14:45
markvoelkerI'd be fine with that.14:45
topolK, so next weeks meeting is canceled but tongli available on IRC for help14:46
topol#topic open discussion14:47
tongliI added a little section at the end of the etherpad for summary. please update if miss something.14:48
topolI think we got a lot covered in this meeting. Very productive14:48
topolAny open issues or do folks want time back14:49
dcnatt_Good here14:49
gemaall good14:49
tongli@dncatt_, eager to see NFV stuff in , let me know if you need a hand. Thanks.14:49
topolAwesome. Great meeting everyone.  And I look forward to seeing folks at OpenStack East!14:50
dcnatt_will do, thanks for support offer14:50
tonglithanks.14:50
gemathank you all!14:50
rohit404thanks folks !14:50
*** lizdurst has quit IRC14:50
Rockygyhaks?14:52
Rockygthanks...14:52
topol#endmeeting14:52
openstackMeeting ended Wed Aug 17 14:52:49 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:52
openstackMinutes:        http://eavesdrop.openstack.org/meetings/interop_challenge/2016/interop_challenge.2016-08-17-14.00.html14:52
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/interop_challenge/2016/interop_challenge.2016-08-17-14.00.txt14:52
openstackLog:            http://eavesdrop.openstack.org/meetings/interop_challenge/2016/interop_challenge.2016-08-17-14.00.log.html14:52
*** brunssen has quit IRC14:54
*** dbutsu has quit IRC14:57
*** tkfjt has quit IRC14:57
*** leong has quit IRC15:00
*** pilgrimstack has quit IRC15:01
*** jokoester has quit IRC15:03
*** openstackgerrit has quit IRC15:03
*** openstackgerrit has joined #openstack-defcore15:04
gemamarkvoelker: I am a bit wary15:07
gemaI took a few mins to read the instructions15:07
gemahttps://github.com/openstack/osops-tools-contrib/tree/master/ansible/lampstack15:07
gemaif we use shade, aren't we avoiding poking the API directly?15:07
*** dcnatt_ has quit IRC15:07
markvoelkerWell, shade still calls the API.  If we're using a workload that is built on shade and it runs successfully across lots of products, that may just tell us that using Shade is a good idea if you're designing workloads for multiple clouds.15:08
gemamarkvoelker: yeah, that is fair enough15:08
*** tetsuo has quit IRC15:13
*** dcnatt has joined #openstack-defcore15:13
tongli@gema, @markvoelker, just want to make sure that it is not the project LAMPstack wants to use shade, it is the Ansible OS cloud module uses shade.15:15
tongliif you want to use ansible to deal with OS cloud, shade is required. there is no other options. but I do think it is a good thing15:16
tonglisame tool, same client, against various cloud, that is exactly what interop should be doing.15:17
markvoelkertongli: yep, I think we're on the same page.15:17
tongli@markvoelker, it is good to be on the same page that you are on. :-)15:18
markvoelkertongli: haha15:18
gematongli: yep, mark convinced me it is a good thing15:45
gemawe are good15:45
gematongli: every time you add an @ to my nickname my irssi refuses to notify me you are talking to me :D15:45
gemajust saying, not ignoring you on purpose :D15:45
tongligema, hmmm, so the IRC client is not working for you?15:46
gematongli: now it is15:46
tongliI should not add that to your name then.15:47
gemait's the @ at the beginning :)15:47
gematongli: thanks!15:47
tongligema, right, right.15:47
gema:D15:47
tongliwill do as you suggested.15:47
gemathanks!15:47
tonglithx15:47
openstackgerritChris Hoge proposed openstack/defcore: Introduce target_programs definition  https://review.openstack.org/31062115:51
*** catherine_d|1 has left #openstack-defcore16:01
*** dmellado is now known as dmellado|off16:05
*** pilgrimstack has joined #openstack-defcore16:08
*** rohit404 has quit IRC16:11
openstackgerritMerged openstack/defcore: Create 2016.08 Guideline from next.json  https://review.openstack.org/35133916:14
openstackgerritMerged openstack/defcore: Remove tests that require second set of credentials from next.  https://review.openstack.org/33860916:25
*** pilgrimstack has quit IRC16:43
gemaeglute: I just sent an email did you receive it in the defcore mailing?17:01
gemaI am not sure if my emails are getting through since I changed my subscription to my work account17:02
egluteyes!17:02
gemaack, thanks!17:02
gemacalling it a day now then :D17:02
eglutethank you for sending it out!17:02
gemayw :)17:02
eglutehave a good evening :)17:02
*** Rockyg has quit IRC17:32
*** dcnatt has quit IRC17:39
*** hockeynut has quit IRC17:48
openstackgerritChris Hoge proposed openstack/defcore: Update schema to 1.6 to disallow additional properties  https://review.openstack.org/35664117:56
*** hockeynut has joined #openstack-defcore17:59
openstackgerritChris Hoge proposed openstack/defcore: Update schema to 1.6 to disallow additional properties  https://review.openstack.org/35664118:05
openstackgerritMark T. Voelker proposed openstack/defcore: Fix status of 2016A process doc  https://review.openstack.org/35664818:06
hogepodgemarkvoelker: eglute: catherineD: I didn't want to debug the dependent patch issue, so I just abandoned and resubmitted18:12
markvoelkerk18:12
eglutethank you hogepodge!18:12
catherineDhogepodge: eglute: markvoelker: please do not merge the 1.6 schema patch until we update the RefStack website ... I will let you know18:14
markvoelkercatherineD: duly noted18:14
hogepodgecatherineD: I'm still sending up patches to make it work. ;-)18:14
hogepodgecomcast to openstack is particularly bad today.18:15
hogepodgeThree minutes to return from git review18:15
eglutei put -1 on workflow catherineD18:15
openstackgerritChris Hoge proposed openstack/defcore: Update schema to 1.6 to disallow additional properties  https://review.openstack.org/35664118:15
catherineDeglute: thank you!18:20
openstackgerritMark T. Voelker proposed openstack/defcore: Change doc references to DefCore  https://review.openstack.org/32708618:27
openstackgerritMark T. Voelker proposed openstack/defcore: Change doc references to DefCore  https://review.openstack.org/32708618:31
*** ametts has quit IRC18:45
*** woodster_ has quit IRC18:49
markvoelkerhmmm, something does seem to be up with CI today.  Can't remember the last time I saw Jenkins leave a -1 with POST_FAILURE and no logs on a patch18:50
*** ametts has joined #openstack-defcore18:56
hogepodgemarkvoelker: I fixed my problem by turning off ipv6 on my home network stack. comcast + ipv6 = :-(19:07
markvoelkerFunny...I noticed that infra pulled OSIC out of the CI today due to issues and they think the problem may be rooted in IPv6 too19:08
*** tongli has quit IRC19:15
*** edmondsw has quit IRC19:28
catherineDmarkvoelker: hogepodge: eglute: We made a new tag (1.1.4) on RefStack but have not seen it on https://pypi.python.org/pypi/refstack yet ... will update when there is new status..19:40
markvoelkerroger that19:41
hogepodgecatherineD: np, there's no rush19:42
hogepodgecatherineD: thanks19:43
-openstackstatus- NOTICE: The volume for logs.openstack.org filled up rather suddenly, causing a number of jobs to fail with a POST_FAILURE result and no logs; we're manually expiring some logs now to buy breathing room, but any changes which hit that in the past few minutes will need to be rechecked and/or approved again19:44
markvoelkerAh, so it wasn't IPv6 after all!19:45
*** edmondsw has joined #openstack-defcore20:58
*** mfisher_ora has quit IRC21:01
*** AlanClark has quit IRC21:56
*** ametts has quit IRC22:04
*** hockeynut has quit IRC22:22
*** eeiden has quit IRC22:25
*** pilgrimstack has joined #openstack-defcore22:29
*** pilgrimstack has quit IRC22:33
*** eeiden has joined #openstack-defcore22:49
*** pilgrimstack has joined #openstack-defcore23:30
*** pilgrimstack has quit IRC23:35
*** hjanssen-hpe has quit IRC23:58
*** hpe-hj has quit IRC23:58

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