16:02:53 #startmeeting networking_ml2 16:02:54 Meeting started Wed Jun 25 16:02:53 2014 UTC and is due to finish in 60 minutes. The chair is Sukhdev. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:02:55 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 16:02:57 The meeting name has been set to 'networking_ml2' 16:03:10 Sorry guys - overslept :-) 16:03:21 sukhdev: what time zone are you in? 16:03:25 Good morning 16:03:25 hi 16:03:32 PST 16:03:34 hoi 16:03:35 It's 9 a.m. here, 16:03:37 oh 16:03:38 same 16:03:51 I jut woke up too, don't feel bad 16:04:08 #topic: Agenda https://wiki.openstack.org/wiki/Meetings/ML2#Meeting_June_25.2C_2014 16:04:38 I do not have any announcements - does anyone? 16:05:16 meeting next week ? 16:05:17 I am sure you all know about Nova to Neutron parity sprint coming up in couple of weeks 16:05:36 shivharis: yes 16:06:25 #topic: Action items from last week 16:06:33 banix: Hi 16:06:38 hi 16:06:52 banix: I saw the updates to the wiki - looks good 16:06:59 cool 16:07:10 added “type” also a table for code review 16:07:15 I don't recall who, but someone was going to talk to me offline about bug fixing - could be I wasn't on IRC and missed it. Who was it? 16:07:16 Did everybody have a chance to look/update the wiki? 16:07:34 slogan: i was 16:07:36 I saw the wiki, looks good 16:07:58 slogan: i could not map you to a lauchpad id or email 16:08:02 I think we have couple of patches ready for merge - 16:08:15 shivharis: slogan@broadcom.com 16:08:20 i am going to talk about in the bugs section 16:08:51 k 16:09:03 Please review the patches so that we can get them merged 16:09:16 Also, update the wiki to reflect that 16:09:46 Starting next week, I intend to use this wiki to take it to core team and use it to get approvals 16:10:03 So, it will help if it updated and current 16:10:15 on to next topic 16:10:17 Sukhdev: yes, updated the wiki for my BP spec review 16:10:20 Sukhdev, cool - so you're our muscle 16:10:34 rcurran: :-) 16:10:49 #topic: Modular L2 Agent 16:11:11 Sukhdev, thanks for getting us core attention 16:11:21 banix: I looked at the schematic - somehow the picture is crooked 16:11:33 Haven’t heard much from others. Have started sending email to people :) 16:12:00 Sukhdev: sorry don’t know why; i just recalled someone else had the same problem last week and I forgot to address it. sorry. 16:12:25 markmcclain has agreed to review and give feed back. i have asked a couple of others as well. 16:12:26 banix: I saw it…I am bit guilty as well….started to look into this, but, got pulled into critical issue -but, I did review good chunk of it 16:12:48 Sukhdev: did you leave any comments? 16:13:05 banix: not yet - will do soon 16:13:16 Sukhdev: sure thanks 16:13:25 Everybody - please have a look and provide feed back 16:13:33 will do 16:13:36 will try to move into a spec by this time next week; that may generate a wider set of reviewers 16:13:46 shivharis: thanks 16:13:53 banix: good idea 16:14:16 #topic: Bugs 16:14:25 shivharis: Floor is yours 16:14:50 i need email/lanunchpad ids from:slogan, nlhouti, banix, padkrish_ 16:15:02 please send me email at shivharis@gmail.com 16:15:10 banix: will do 16:15:11 shivharis: nlahouti@cisco.com 16:15:13 I had a tough time mapping these 16:15:15 shivharis: will do 16:15:17 shivharis# will do 16:15:23 thanks 16:15:26 ok 16:15:41 shivharis: I got one bug you assigned to me 16:16:01 i need help is delgating a bug, 1204456 please see agenda for link 16:16:07 nlahouti: cool - thanks 16:16:31 this bug new owner will be working with mestery if need be 16:16:38 https://bugs.launchpad.net/neutron/+bug/1204456 16:16:40 Launchpad bug 1204456 in neutron "neutron ml2 plugin test failures" [Medium,Confirmed] 16:16:52 nlahouti: i could map u, thanks summit 16:17:16 slogan: ? 16:17:29 yes? 16:17:48 can you please pick this bug? 16:17:54 let me look at that bug, just a sec... 16:18:29 we'll move on: I need the next bug on agenda to be fixed in J2 16:18:37 #shiv# My e-mail is kprad1@yahoo.com, i have also e-mailed you 16:18:42 https://bugs.launchpad.net/neutron/+bug/1276391 16:18:43 Launchpad bug 1276391 in neutron "ML2 MechanismDriver.bind_port() called inside transaction" [High,In progress] 16:19:04 sukhdev: can u ping bob on this? 16:19:23 shivharis: I chatted with him on this one yesterday 16:19:31 slogan: I may be able to help with bug 1204456 16:19:32 Launchpad bug 1204456 in neutron "neutron ml2 plugin test failures" [Medium,Confirmed] https://launchpad.net/bugs/1204456 16:20:03 Bob is working on it - he is on vacation and mentioned he will work on it while travelling 16:20:22 sukhdev: ok thanks, this is high priority 16:20:35 HenryG: that will be really cool - thanks 16:20:41 HenryG: ok 16:20:42 this bug seems serious bug no action for a while; https://bugs.launchpad.net/neutron/+bug/1224978 16:20:44 Launchpad bug 1224978 in neutron "port binding on multi segment networks could lead to agent misconfiguration" [Medium,Incomplete] 16:20:52 HenryG: Thx 16:21:37 I need help in getting closure on this, may not need real tech work it seems, need followup 16:22:16 Any volunteers to help out? 16:22:18 any takers? or else I will ping individually 16:22:27 shivharis: I can help with that one 16:22:36 asomya: thanks 16:22:43 asomya: Thanks - that will be really nice 16:22:55 This is a good time to get bugs fixed that affect all 16:23:20 and be done by J2, so others affected can proceed 16:23:33 Also by J3 we will have review crunch 16:23:59 Also I will start a wiki like banix, for bug reviews 16:24:05 Yes that is a good goal shivharis 16:24:32 so if you have something needing atttention you can update that 16:24:53 banix: I was suppose to discuss with you on one bug - 16:24:54 please ping me if you need review assistance. 16:24:58 that all from my end 16:25:11 Sukhdev: yeah the bulk ops 16:25:35 Sukhdev: i can work on it and leave the sync stuff to later. would that be reasonable? 16:25:50 banix: correct - we need to that and make a decision as to how to proceed with this 16:26:11 banix: sync stuff and bulk ops may be related? 16:26:15 banix: yes - I wanted to discuss with you to come up with a plan 16:26:25 shivharis: correct 16:26:26 bulk ops may use sync stuff as task 16:26:26 shall we discuss here? 16:26:46 banix: sure - everybody is here 16:27:06 so there are two things wrt the bulk ops bug 16:27:22 one is to remove the postcommit stuff out of transactions 16:27:36 the other is how to deal with failiure in some 16:27:50 is this a correct description? 16:28:10 banix: yes - go on... 16:28:23 sounds fine at high level, problems happen in details 16:28:32 So we can address these as separate items 16:28:34 i.e. failure conditions 16:28:43 banix: sure 16:29:11 banix: agreed remove these from transactions 16:29:22 Sukhdev was planning to the sync operation we can use that when it is there; just thinking loud here 16:29:52 banix: OK 16:29:52 * banix needs to use punctuation 16:30:08 which means you need sync stuff before bulk stuff (in that situation) 16:30:28 shivharis: I guess so 16:30:44 shivharis: well, may be not; considerring that the sync stuff is a much bigger task 16:31:08 we may want to do what we did earlier wrt failures in postcommit ops 16:31:26 banix: can we (possibly) have a way to do post_commit asynchronously 16:31:36 banix: not may not be a big task. 16:31:56 * banix thinking 16:31:58 banix: we can leave aside "tasks" that Mark is implementing for now 16:32:32 yeah wonder if that would be a major piece 16:32:46 shivharis: Bob had action to investigate taks - 16:33:00 banix: again thinking out loud, correct me if i am wrong 16:33:30 banix: you can read the db in the async task and call post_commits 16:34:00 banix: we can ignore the "tasks" for now 16:34:14 shivharis: what you just said is very close to ML2 sync proposal :-) 16:34:25 shivharis: yeah but a change like that may require spec/bp and all that; wont be a bug fix. no? 16:34:40 yeah similarly with the sync 16:34:41 banix: we already have a BP 16:34:52 Sukhdev: spec too? 16:34:59 banix: no 16:35:11 planning to write the spec? 16:35:14 banix: yeah, but then we are stuck 16:35:23 banix: we have google doc 16:35:48 shivharis: Sukhdev so may be we need to plan this first? 16:36:04 how to start working on sync I meant 16:36:10 we bit the bullet and do all that (spec,bp etc) 16:36:15 So, shall I say - how I was thinking about addressing this issue? 16:36:16 bit/bite 16:36:28 Sukhdev: yes :) 16:36:43 banix shivharis: I need volunteer to work on it with me 16:36:45 Sukhdev: you are chair say whatever :-) 16:36:57 So, here it goes - 16:37:17 Sukhdev is muscle, remember? 16:37:21 i can volunteer 16:37:26 :) 16:37:27 I am thinking we perform pre-commits() - which means the operations are committed to DB 16:37:59 then we perform post-commits() 16:38:03 i have a fairly reasonable idea what i want and how to map later to "tasks" 16:38:36 Sukhdev: are you talking about bulk ops or in general? 16:38:50 The DB is considered "True source" - that is if a post-commit fails, it will be retied until the Driver is in sync with DB 16:39:06 banix: this will solve for all cases 16:39:06 oops, i though he was talking about sync 16:39:30 banix can still work on bulk stuff 16:39:45 It will not matter if you bulk all operations or perform serially 16:39:57 yup got it; makes sense 16:40:09 If you look at Arista Driver - I support both Bulk as well individual operations in sync 16:40:15 and it works like a charm 16:40:33 I have a working model of sync in Arista Driver 16:40:44 20 mins left 16:40:55 Bob and I have been chatting about brining it into ML2 plugin 16:41:31 so this will be a major revision of ml2 architecture in some ways; correct? not bad but we need to keep that in mind. 16:41:47 So, if I can get some volunteers, we can setup a web-chat and go over this, plan it, write up specs…implementation is not too hard 16:41:54 banix: right 16:42:03 banix: yes - it will be 16:42:15 banix: hence, requires proper planning 16:42:40 yeah; sure; but we should consider that this wont make it in this cycle 16:43:01 banix: I am affriad so 16:43:06 considering all that is going on in Neutron 16:44:07 is it worth to deal with the bulk bug wrt removing the post commit out of transaction? 16:44:09 If you guys are willing to, we can take it to #openstack-neturon after this meeting and continue discussion and plan 16:44:35 Sukhdev: sure; i will be available for 30 minutes past this call 16:44:36 banix: yes, I agree with you - we need to have a short term solution 16:44:37 lets take it up later, i may not be available for about 1 hr after this meeting 16:44:44 Sukhadev: on bug 1204456 what platform are you on (e.g., OS and version) when you made comment 2? 16:44:46 Launchpad bug 1204456 in neutron "neutron ml2 plugin test failures" [Medium,Confirmed] https://launchpad.net/bugs/1204456 16:44:48 OK - lets move on 16:44:57 #topic Spec Reviews 16:45:24 I went through the specs and reviewed many of them - all, please do the same 16:45:40 I believe two are ready to go - I listed them in the agenda 16:46:06 If you believe any other is ready to go, this is the time to call out 16:46:20 We should use this meeting and this time slot to cover that - 16:46:42 there is extension support for MD as well 16:46:42 consider #link: https://review.openstack.org/#/c/88101/ 16:47:05 I have initiated a dialogue with Kyle to get core approvals on these - hence, everybody won't have to chase the cores 16:47:18 sukhdev# Thanks 16:47:19 rkukura supposed to review it 16:47:47 banix: thanks for pointing out - i missed it for some reason. I will get this pushed as well 16:48:04 Sukhdev: thx 16:48:22 banix: it is very much like ODL, should not have a prob going through 16:48:26 Any other? 16:48:38 https://review.openstack.org/#/c/89208 16:49:06 shivharis: yeah; hope we can refactor/reuse code and possibly for future SDN controlers. 16:49:06 As long as we have 3 +1's from this sub-committee, I will go to work 16:49:22 did mestery put -2 on it, did his comments get addressed? 16:49:39 ^^nlahouti^^ 16:49:50 nlahouti: I have seen and been waiting for you to address the comments 16:49:51 wants rkukura to review 16:49:56 shivharis: yes. as I mentioned rkukura supposed to review it 16:50:27 i skipped looking at it due to -2, can you remove that from the wiki 16:50:33 I captured them in the etherpad:https://etherpad.openstack.org/p/ML2_MD_extensions 16:51:15 nlahouti: OK - rkukura told me yesterday that he has few specs to review - perhaps he was talking about this…he mentioned he will do it while travelling - 16:51:18 shivharis: you mean the -2 ? 16:51:32 yes, you need to update the wiki 16:51:44 nlahouti: so, lets wait --- if he pings me while travelling, I will remind him of this 16:51:53 Sukhdev: yes he was mentioning that is one of his top proirotity 16:52:17 Any other spec? 16:52:23 7 mins left 16:52:24 Sukhdev: thx. Our other BP depends on it 16:52:53 i want to make a progress on this. any idea? https://review.openstack.org/#/c/89463/ 16:52:55 Moving on 16:53:36 yamamoto: did you connect with Mark on it? 16:54:11 #topic: Code Reviews 16:54:36 #link https://review.openstack.org/#/q/status:open+project:openstack/neutron,n,z 16:55:32 When you review a spec, it will be good idea to follow up with a code review as well 16:55:58 #topic: Third Party Test Sytem 16:56:15 I am sure all of us are impacted by this - 16:56:27 I am updating my CI to correct the logs - 16:56:55 Please be sure to follow the guidelines https://wiki.openstack.org/wiki/NeutronThirdPartyTesting 16:57:17 Anita is going to come very hard on us - who do not follow the guidelines 16:57:23 i pinged mark today 16:57:29 I believe the deadline is J2 16:57:41 yamamoto: good 16:57:56 #topic Open Discussion 16:57:59 J2 -> july 24 16:58:04 is it supposed to test stable branches as well? 16:58:13 I have bug https://bugs.launchpad.net/neutron/+bug/1236127, wondering what the coverage goal is 16:58:14 Launchpad bug 1236127 in neutron "ML2 plugin needs additional unit tests" [Medium,In progress] 16:58:34 the wiki page is not clear about branches 16:58:59 i believe stable should be covered, but check with anteaya 16:59:06 chuckC: what do you mean? 16:59:14 yamamoto: i think we need to clarfiy the requirement. It should be raised to neutron meeting. 16:59:32 IMO at least stable/icehouse should be covered 16:59:39 Sukhdev: bug is code coverage bug, do I need to hit 100% coverage to close the bug? 17:00:04 chuckC: please send mestery a mail, he owned this bug before 17:00:17 shivharis: ok, thanks 17:00:40 chuckC: I have seen less than 100% - but, it is not hard and fast rule 17:01:14 Sukhdev: ok, thanks 17:01:20 out of time 17:01:24 we can use partial-bug, but if it is big i would suggest to split the bug into several sub-bugs. 17:01:27 Anything else - we are out of time 17:01:48 #endmeeting