14:00:02 #startmeeting interop_challenge 14:00:02 Meeting 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:03 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:00:06 The meeting name has been set to 'interop_challenge' 14:00:14 o/ 14:00:14 o/ 14:00:16 o/ 14:00:16 Hi everyone, who is here for the interop challenge meeting today? 14:00:17 o/ 14:00:19 o/ 14:00:51 The agenda for today can be found at: 14:01:05 #link https://wiki.openstack.org/wiki/Interop_Challenge#Meeting_Information 14:01:20 In case we need to take notes, the etherpad for this meeting can be found here 14:01:33 #link https://etherpad.openstack.org/p/interop-challenge-meeting-2016-08-17 14:01:47 #topic review action items from previous meeting 14:02:01 #link 14:02:01 http://eavesdrop.openstack.org/meetings/interop_challenge/2016/interop_challenge.2016-08-10-14.00.html 14:03:01 o/ 14:03:14 Have folks added which version of OpenStack they plan to interop? 14:03:14 o/ 14:03:41 tongli, shamail, where folks supposed to put this? 14:03:43 where do we add that? 14:04:23 @topol, I would say put in the etherpad, then put in the summary after. 14:05:01 tongli, that works. for now folks can add it to the bottom of the etherpad for todays meeting 14:05:07 * 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:59 tongli can you gather all this up and then put somewhere? Separate etherpad for it perhaps??? 14:06:41 @topol, let's just use this etherpad. too many links probably not good. 14:07:04 Also it looks like in last weeks meeting everyone agreed to start with LAMPStack 14:07:04 @topol, I put it at the end of today's etherpad. 14:07:19 @topol, we voted using ansible. 14:07:25 tongli, thats fine just gather up from last weeks etherpad so its all inone place 14:07:32 the lampstack ansible has been merged. 14:07:59 tongli Yay! That was my next item to review. 14:08:14 can other folks put your preferred test OS release in the etherpad, please! 14:08:37 #action other folks put your preferred test OS release in the etherpad, please! 14:09:08 @markvoelker, can you put your releases on the etherpad. 14:09:14 Thanks for the quick reviews and merge of LAMPStack 14:09:20 tongli: already did 14:09:39 @markvoelker, thanks. 14:09:53 Did everyone look at the results template? Any concerns with that? 14:10:12 #link http://paste.openstack.org/show/553587/ 14:10:19 @topol, we had discussion, and generally agree with the content. 14:10:57 K cool. 14:10:58 #agree Folks like the results template 14:11:06 I think that the question is how often we run the test against each cloud 14:11:14 Maybe add an affiliate/company? 14:11:37 leong good idea 14:11:39 yep and we'll need to agree on what running successfully means 14:11:45 other than that I am also good 14:11:48 seems to me Mark wants to produce just one report per test per cloud, is that right? @markvoelker 14:12:13 #action shamail to add affiliate/company to the results template 14:12:26 tongli: 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 today 14:12:44 @markvoelker, that sounds good to me 14:12:48 There'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:13:01 @markvoelker +++ 14:13:10 @markvoelker, ok, fine. 14:13:31 E.g. even if VendorX releases some maintenance patches for their Liberty distro, it seems relatively unlikely to break the workload. 14:13:46 good point, markvoelker 14:13:54 #agree Folks should produce one report per cloud 14:13:56 I 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:14:29 tongli: are you volunteering to run the workloads instead of us running them independently? :D 14:14:30 The first test category is RefStack test ... At the minimum, all participants should collect RefStack test data now 14:14:31 yes, so tongli is available to anyone that needs help and he is eager to run tests 14:14:38 @gema, yes. I am 14:14:42 tongli: you got it :D 14:14:50 tongli: thanks! 14:15:01 @gema we are here to serve :-) 14:15:09 topol: :D 14:15:14 if that is ok, please send me the credentials to my email , I put the email in the etherpad. 14:15:27 tongli: as soon as the cloud is up will do :D 14:15:36 #action if folks want tongli to help run tests on their cloud, get him an account 14:15:47 gema: does it make sense for someone else to run the tests? Some clouds maybe private.. 14:16:06 catherine_d|1: our cloud is going to be public and a developer cloud, so I am happy for him to try 14:16:07 catherine_d, either way, as long as test get run 14:16:17 catherine_d|1: I will also try and it will be interesting to compare 14:16:18 gema thats awesome 14:16:32 okay, new topic 14:16:48 question -- creds and tongli doing tests will only work on public clouds... what about distros without a public cloud? 14:17:09 Rockyg: those may stand up a test cloud for this testing anyway 14:17:11 they can run it 14:17:26 o/ 14:17:29 Rockyg I guess whoever has acces to the private cloud will have to run 14:17:34 Rockyg: 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:47 yep 14:17:51 as usual markvoelker is spot on 14:18:05 #topic Test candidates review (refer to the current test candidates on the etherpad) 14:18:43 generally 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 working 14:18:50 Great. I think w should write rules a little more formally as part of the "challenge rules" 14:18:52 Catching up. Has the team discussed a vnf test candidate yet? 14:19:08 So right now we have the docker terraform and LampStack with Ansible. Do we need any more? 14:19:17 dcnatt_: No, but test candidates is the current topic. =) 14:19:33 The foundation folks also would like an NFV app if possible 14:20:06 I believe AT&T is looking for one of these 14:20:07 Interested in throwing out nfv test candidate and containerized workloads for consideration 14:20:27 dcnatt_ Yes, you haveone of these?? 14:20:41 I have inflight POCs for both 14:20:46 Can repurpose 14:20:55 If team sees value 14:20:55 dcnatt_ when can code be pushed to the repository? 14:21:18 lmc.. I wanted to propose here first then verify 14:21:25 dcnatt Definitely value. I heard from the foundation folks they would like that included 14:21:51 I'll pursue asap. What about containerized multi-cloud interop 14:22:49 @dncatt_, if you need any help with ansible, I like to lend a hand. 14:22:53 dcnatt_ There is certainly interest in NFV. There maybe interest in containerized multi-cloud interop. My guess is folks will want to see the workload code 14:23:05 @tongli - thanks, always appreciated 14:23:24 Hm. 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:26 Do we though? 14:23:56 So best thing is to get the workload pushed up to the repository as soon as possible. 14:24:13 We have semantic pipeline auth/auth at the CNI to support workloads across OS and AWS etc. 14:24:26 My 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:28 @markvoelker, do you mean the docker swarm test already in the contrib project, or you have a different one? 14:24:38 tongli: the one already there 14:25:15 Did we decide what should be the second workload to try and run? 14:25:24 We are showing app decomp to component workloads, dynamic networking at the container level plumbed to virtual network across providers and managed by policy 14:25:28 topol: 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:30 @markvoelker, ok. thanks for clarifying it. 14:26:09 markvoelker. if we get them soon I think we are okay. We all just need near term deadlines to get the adrenaline going 14:26:41 markvoelker I'm also okay with some workloads being run ats 14:27:02 topol: 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:14 Sound good? 14:27:21 markvoelker sounds good 14:27:36 so work load tests as follows: 1. Ansible lampstack 2. Terraform docker swarm 3. ATT NFV? 14:27:45 * markvoelker sets himself a reminder 14:27:47 Agree 14:27:49 tongli YES! 14:27:59 tongli you type faster than me 14:28:04 will the NFV workload run on a normal neutron enabled cloud? 14:28:07 so #3 is a try as much as possible? 14:28:21 It will "Run"... 14:28:24 #agree so work load tests as follows: 1. Ansible lampstack 2. Terraform docker swarm 3. ATT NFV 14:28:53 dcnatt_ please push the code up as soon as you can. tongli can help with wrapping ansible around it 14:29:02 Will do 14:29:43 awesome. 14:30:02 one other question, did folks have issues with the Terraform? If necessary tongli could rewrite as Ansible 14:30:10 I will send results to the owner of the cloud who sends me account info. 14:30:12 * topol topol ducks 14:30:41 topol: no. The more the merrier. 14:30:43 #action let tongli, topol know if any issues with Terraform 14:31:01 topol: no, we wanted to try different deployment methods for the different workloads 14:31:05 to increase the coverage 14:31:23 markvoelker okay tongli will be happy to hear that 14:31:27 topol i gave the terraform docker swarm a spin last nite, saw some ssh key issues, i'll follow up 14:31:28 topol, good thing tongli has his hand full 14:31:37 (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:56 markvoelker ++ excellentpoint 14:32:27 #topic Test environment from different vendors. or should we just test stuff against our own environment? 14:32:33 i think we covered this. 14:32:52 Everyone runs themselves but if you can give tongli access he is willing to help 14:32:59 topol: ++ 14:33:04 topol: ++ 14:33:33 == 14:33:36 ++ 14:33:41 ++ 14:33:41 #agree Everyone runs tests themselves but if you can give tongli access he is willing to help 14:33:48 new topic 14:33:55 only 5 company indicated OS releases on etherpad, should there be more? 14:34:16 topol: ++ 14:34:32 tongli lets you and I follow up on who may be missing 14:34:37 sorry guys. It's really early and I'v bee doing early for the week. Burnout 14:35:05 sounds like we need to.... 14:35:10 tongli : which etherpad? 14:35:19 https://etherpad.openstack.org/p/interop-challenge-meeting-2016-08-17 14:35:26 #action tongli and topol to follow up on who has declared their release 14:35:29 @gema, you beat me on that. 14:35:37 tongli: :D 14:36:55 #topic result repository 14:37:06 Send as emails? Or a better suggestion? 14:37:25 a new folder in the ops repository that holds the workloads? 14:37:30 if we only produce one report per test per cloud, then email maybe just fine. 14:37:46 email to the defcore mailing list? 14:38:01 Or something like SurveyMonkey to make it a bit more structured, perhaps? 14:38:08 dhellmann, sounds good... 14:38:46 dhellmann, so folks won't view that as spam? 14:39:00 topol : I was asking if that's what you meant by "email" 14:39:01 as long as everyone is okay wiht the mailing list 14:39:08 * markvoelker puts on DefCore co-chair hat 14:39:13 I won't consider it spam. =) 14:39:17 * markvoelker doffs hat 14:39:30 markvoelker, ++ 14:39:35 * topol topol kisses the ring of markvoelker 14:39:50 @markvoelker, then defcore-committee mailing list. 14:40:57 Ok, 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:41:15 Do we have a wiki page for the interop challenge? If not maybe I'll just go create one. 14:41:20 topol: ^^ 14:41:39 @markvoelker, shamail already created one. 14:42:11 #agree folks can email their results to the defcore mailing list 14:42:13 markvoelker: we do have wiki page for interop-challenge https://wiki.openstack.org/wiki/Interop_Challenge#Meeting_Information 14:42:33 Ok, I'll put it there 14:43:08 got diconeected for a sec 14:43:26 so folks are to mail the list and markvoelker to record on the wiki page? 14:43:40 topol: yep 14:44:01 #action markvoelker update wiki page with how to submit test results 14:44:11 #action markvoelker to record results on the wiki page, folks you email results to the defcore meeting list 14:44:29 excellent 14:45:07 #topic next weeks meeting, topo and shamail at OpenStack East next week 14:45:13 * markvoelker is too 14:45:20 So for next week should we cancel? 14:45:46 Or we could leave the hour as an open office hour if folks need help from tongli 14:45:46 is at containercon/cloud native day in Toronto 14:45:52 I'd be fine with that. 14:46:30 K, so next weeks meeting is canceled but tongli available on IRC for help 14:47:19 #topic open discussion 14:48:18 I added a little section at the end of the etherpad for summary. please update if miss something. 14:48:58 I think we got a lot covered in this meeting. Very productive 14:49:12 Any open issues or do folks want time back 14:49:25 Good here 14:49:28 all good 14:49:54 @dncatt_, eager to see NFV stuff in , let me know if you need a hand. Thanks. 14:50:03 Awesome. Great meeting everyone. And I look forward to seeing folks at OpenStack East! 14:50:08 will do, thanks for support offer 14:50:18 thanks. 14:50:19 thank you all! 14:50:26 thanks folks ! 14:52:16 yhaks? 14:52:25 thanks... 14:52:49 #endmeeting