14:30:01 #startmeeting lithium release review 14:30:01 Meeting started Wed Jun 24 14:30:01 2015 UTC. The chair is phrobb. Information about MeetBot at http://ci.openstack.org/meetbot.html. 14:30:01 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:30:01 The meeting name has been set to 'lithium_release_review' 14:30:10 #topic roll call 14:30:20 VPN Service URL - Release Notes - https://wiki.opendaylight.org/view/Vpnservice:Lithium_Release_Notes 14:30:22 #info Project Leaders and TSC members please #info in 14:30:23 morning 14:30:29 Prem_ for VPNService 14:30:45 #info Prem_ for VPNService 14:30:53 thanks Prem_ . We'll start your review in just a couple minutes 14:30:57 #info LuisGomez 14:30:59 #info gzhao 14:31:10 #chair LuisGomez gzhao 14:31:10 Current chairs: LuisGomez gzhao phrobb 14:31:54 Let's go ahead and get started.... 14:32:01 #topic VPN Service 14:32:20 Prem_ could you also link in your release notes page? 14:32:32 Ah, sorry. See you did 14:32:36 Release Review - https://wiki.opendaylight.org/view/Vpnservice:Lithium_Release_Review 14:32:49 Release Notes - https://wiki.opendaylight.org/view/Vpnservice:Lithium_Release_Notes 14:32:59 #info Prem_ is representing VPN Service 14:33:46 We have verified the latest RC and updated the release sheet as GO 14:34:03 Documentation (User Guide) was competed, reviewed and checked in 14:34:10 Prem_, there is 1 test case failing in csit test: https://jenkins.opendaylight.org/releng/view/CSIT-1node/job/vpnservice-csit-1node-cds-vpnservice-only-stable-lithium/ 14:34:16 is it expected? 14:35:31 I checked this morning about this failure 14:36:12 Prem_ Are there really no applicable security considerations?... ie are you leveraging any security features from other parts of ODL?... or could you but you chose not to in this release, etc? 14:36:33 #info LuisGomez asks if the test failure in csit is expected 14:36:55 We are not leveraging any security features in this release 14:37:14 Prem_ for the open bugs that are listed, are there any work-arounds available?.. if so, could we document them in the releae notes? 14:37:30 Yes Phil, we will document the work arounds 14:38:03 #action Prem_ to document known work-arounds for listed bugs in release notes 14:38:06 #info phrobb asks if security feature really n/a, Prem_ says they are not leveraging any security features. 14:38:14 thanks gzhao 14:39:02 did we get and document an answer re the CSIT test that is failing? 14:39:03 On the failed test case, verification of fib entry is failing and manually it works 14:39:16 Brady said he would be in around 8:00 14:39:26 so it is test issue 14:39:27 We are checking on the mismatch reason and we will address the same 14:39:34 So next project will be SNMP4sdn 14:39:43 OK gzhao thanks 14:39:51 it is a test script issue. 14:40:03 As Vishal said, it is a script issue 14:40:04 thanks Prem_ 14:40:12 #info Prem_ says manually the test works 14:40:38 #info Prem_ notes they are still investigating csit failure 14:40:51 Thanks Prem No more questions from me. Anyone else? 14:40:58 no 14:41:16 #topic SNMP4SDN 14:41:17 Thanks Phil, George and Luis! 14:41:23 thanks Prem 14:41:38 Christine can you link in your release review page and release notes? 14:41:55 I'll help... 14:42:04 #link https://wiki.opendaylight.org/view/SNMP4SDN:Lithium_Release_Review 14:42:56 ChristineH: 14:43:00 Christine, are you here?.... I thought I saw you join a bit ago 14:43:11 Prem_: np 14:43:40 ChristineH ?? 14:43:46 vina_ermagan: ayt 14:44:12 hi! 14:44:19 there we go 14:44:22 sorry, just left for a while 14:44:29 ChristineH could you link in your release notes page 14:44:34 #topic SNMP4SDN 14:44:41 https://wiki.opendaylight.org/view/SNMP4SDN:Lithium_Release_Note 14:44:55 gzhao: I'll be ready in another 10 minutes 14:45:18 ebrjohn: ok 14:45:54 #info ChristineH is reprenting SNMP4SDN 14:46:20 The main different of snmp4sdn from Helium to Lithium is that API ported from ad-sal to md-sal 14:46:32 #info ChristineH are there any migration concerns for users moving from Helium to Lithium regarding SNMP4SDN? 14:47:43 ChristineH: do we have release review? 14:47:49 phrobb: for developer, the API is changed. for user, I think it's more convenient for them to use snmp4sdn via REST API 14:48:02 snmp4sdn's release review: https://wiki.opendaylight.org/view/SNMP4SDN:Lithium_Release_Review 14:48:15 REST API did not change this release? 14:48:24 #info ChristineH notes that for developer, the API is changed. for user, I think it's more convenient for them to use snmp4sdn via REST AP 14:48:58 REST API is the first time release in Lithium. In Helium release not supported. 14:49:10 ChristineH: thanks, I cannot access Google spreadsheet. 14:49:22 OK, got it 14:49:36 gzhao: I vote Lithium build as GO 14:49:52 ChristineH: thanks 14:50:04 thanks 14:50:27 No more questions from me. Anyone else 14:50:28 vina_ermagan: a.y.t 14:50:46 #info Vina Ermagan for LISP Flow Mapping 14:50:55 gzhao: yes 14:51:02 #topic LISP 14:51:05 https://wiki.opendaylight.org/view/OpenDaylight_Lisp_Flow_Mapping:Lithium_Release_Review 14:51:17 https://wiki.opendaylight.org/view/OpenDaylight_Lisp_Flow_Mapping:Lithium_Release_Notes 14:51:58 Major changes include migration to md-sal 14:53:55 as a consequence , our previous northbound API is removed to avoid pulling in ad-sal libraries. The bundle is still built but not included in the feature 14:53:56 vina_ermagan: I only saw a snapshot of the voting page, did Lisp project vote? 14:54:06 #info vina_ermagan Can you describe the migration issues for users moving from Helium to Lithium? 14:54:31 No, I do not think that LISP has voted yet 14:54:52 phrobb: the only migration issue is transition to RPCs from original northbound apis 14:55:02 phrobb: I'll make that clear 14:55:07 #link https://docs.google.com/spreadsheets/d/1KPpO9LH539Vlcoa4RvLa6PPCdLifi5JD-ihRhlybqeo/edit#gid=478292312 Link to voting page 14:55:39 gzhao: Have not updated the voting sheet 14:55:53 #info LISP Flow Mapping is Go on Li 14:56:03 gzhao: I'll update the sheet now 14:56:15 vina_ermagan: thanks 14:56:37 gzhao: Done 14:57:20 phrobb: I cannot access Google spreadsheet, I can only see which projects voted yesterday. 14:57:40 Any question for Lisp 14:57:41 #info vina_ermagan Notes that the only migration issue is transition to RPCs from original northbound apis and the release notes call out where the new interfaces are documents 14:57:54 not from me 14:58:30 Is ebrjohn available yet? 14:58:57 ebrjohn: are you ready? 14:59:00 gzhao: phrobb: is LISP Flow Mapping review complete? 14:59:14 vina_ermagan: yes, thanks 14:59:17 vina_ermagan yes. Congrats and thank you! 14:59:18 thanks 14:59:30 Great! Thanks all. 14:59:46 Who will represent Alto? 15:00:07 I will 15:00:09 <__Kai__> Shu and me. 15:00:33 start? 15:00:37 Cool. Let's move to ALTO then 15:00:43 #topic ALTO 15:00:46 Release Review - https://wiki.opendaylight.org/view/ALTO:Lithium:Release_Review 15:00:53 Release Notes - https://wiki.opendaylight.org/view/ALTO:Lithium:Release_Notes 15:01:00 <__Kai__> #link https://wiki.opendaylight.org/view/ALTO:Lithium:Release_Review 15:01:03 * phrobb reads... 15:01:19 <__Kai__> #link https://wiki.opendaylight.org/view/ALTO:Lithium:Release_Notes 15:03:38 dongshu and __Kai__ No Security considerations? Could you use AAA and chose not to this release or did it not make sense to use it ever?... as an example 15:03:53 Ok 15:03:53 #topic ALTO 15:03:57 #info dongshu and __Kai__ are representing ALTO 15:04:02 (note: monitoring chat while in another meeting, please ping me if needed for NIC before 9am PST) 15:04:19 will do dbainbri 15:04:20 Im here now 15:04:35 sorry I was late 15:04:38 <__Kai__> #link https://wiki.opendaylight.org/view/ALTO:LithiumReleaseNotes <-- Release Notes 15:04:39 hi ebrjohn we'll put you up next after ALTO 15:04:42 #undo 15:04:42 Removing item from minutes: 15:04:42 #undo 15:04:42 Removing item from minutes: 15:04:44 ok, great 15:05:32 We could use AAA to protect sensitive info or customized info, but choose to not, for simplicity. 15:05:37 * gzhao will not use chairman right to due long latency 15:05:56 #info ebrjohn for Service Function Chaining 15:06:28 dongshu I believe that's the type of considerations we want to document/understand. Could you note that in the release review page? 15:06:51 Sure. I will update the release page later 15:07:06 #info phrobb asks No Security considerations? Could you use AAA and chose not to this release or did it not make sense to use it ever?... as an example 15:07:14 I will edit it right now 15:07:34 #info dongshu notes We could use AAA to protect sensitive info or customized info, but choose to not, for simplicity. 15:07:44 #action dongshu to security concern to release review 15:07:59 #action dongshu to update release review wiki re security consideration 15:08:18 Done 15:08:26 More questions for ALTO? 15:08:41 yes 15:09:27 dongshu for the bugs you list on the review, is there a reason that they are not all listed on the release notes with any work arounds you are aware of? 15:09:37 <__Kai__> They have been fixed. 15:10:07 Ah :-D... that's an awesome answer. So they should be removed from the bug list on the review? 15:11:12 <__Kai__> By this and the related patches: #link https://git.opendaylight.org/gerrit/22769/ 15:11:16 I thought we have to list all bugs in the review. Removed now. 15:11:45 No, it's for outstanding bugs 15:12:04 I'm finished with questions. Thanks dongshu and __Kai__ 15:12:13 <__Kai__> p.s. Bug 3147 is more like a yangtool bug rather than ours. 15:12:13 Any one else have questions for ALTO? 15:12:31 #action dongshu __Kai__ to remove non-outstanding bugs from release review 15:12:53 No for me 15:12:57 #topic SFC 15:13:12 ebrjohn can you link in the reivew page and release notes? 15:13:21 <__Kai__> Are we done here guys? 15:13:22 yes 15:13:38 You are don __Kai__ . and dongshu . Thanks! 15:13:39 #link https://wiki.opendaylight.org/view/Service_Function_Chaining:Lithium_Release_Review#Standards_.28summary_of_standard_compliance.29 15:13:46 #info ebrjohn for SFC 15:13:51 Thanks for your review! 15:13:51 #undo 15:14:01 __Kai__: yes and thanks 15:14:13 #link https://wiki.opendaylight.org/view/Service_Function_Chaining:Lithium_Release_Review 15:14:30 #link https://wiki.opendaylight.org/view/Service_Function_Chaining:Lithium_Release_Notes 15:14:36 Those are the links 15:14:44 thanks ebrjohn 15:15:10 * ebrjohn wondering if I undid gzhao's #info ??? 15:15:21 I meant to undo the #link 15:16:30 nope you got his #info :-) 15:16:35 want to put it back? 15:16:52 #info ebrjohn for SFC 15:16:53 ebrjohn: no, you need chair privilege to undo 15:16:56 * ebrjohn sorry 15:17:51 I actually have no questions for SFC 15:17:54 ebrjohn are any of the 28 bugs identified blockers 15:18:08 no, we dont have any blocking bugs 15:18:21 vishnoianil: will you represent odlparent? 15:18:44 3825 was a blocker, but its been fixed 15:18:50 cool 15:19:03 so no migration problems for sfc I see 15:19:23 ebrjohn Nicely done on your description and coverage of known issues in your release notes 15:19:28 nope, the only thing I can think of would be changed YANG models 15:19:32 #info ebrjohn says 3825 was a blocker, but its been fixed 15:19:36 phrobb: thanks!! 15:19:36 I have no frurther questions for SFC 15:19:40 csit test is pushed but is not runnint in CI, please work on that after the release 15:19:49 no more questions 15:19:58 LuisGomez: ok, will o 15:20:04 LuisGomez: ok, will do 15:20:40 thanks 15:20:50 Thanks ebrjohn . 15:20:57 Thanks all of you 15:21:07 Is SFC oficial now?? :) 15:21:15 vishnoianil: a.y.t 15:21:24 ebrjohn: yes 15:21:25 do we have someone represeting odlparent on the channel? 15:21:35 great! 15:21:42 yes 15:21:46 I am here 15:21:50 cool 15:21:55 #topic odlparent 15:22:03 https://wiki.opendaylight.org/view/ODL_Root_Parent:Lithium_Release_Review 15:22:10 #info Vaishali representing odlparent 15:22:27 Vaishali please also link in the release notes page 15:22:32 #info Vaishali for odlparent 15:22:44 #undo 15:22:44 Removing item from minutes: 15:23:09 I didnt create release notes link, as no issues, checked with George on that. If required I can create one stating no issues? Let me know if thats ok? 15:23:15 Vaishali do you have (the need for ) release notes 15:23:33 yep, that makes sense to me... this is going to be a quick review :-) 15:24:07 Vaishali: did odlparent vote for lithium? 15:24:32 yes 15:24:42 mlemay: a.y.t? 15:24:51 Vaishali, I would not expect it, but are there any user or developer facing issues that may be encountered as they migrate from Helium to Lithium? 15:25:07 no there should not be 15:25:11 cool 15:25:26 gzhao: yes 15:25:30 #info phrobb asks are there any user or developer facing issues that may be encountered as they migrate from Helium to Lithium? 15:25:48 #info Vaishali Notes that thre shoiuld not be any migration issues 15:25:59 mlemay: cool you are next. 15:26:09 thanks all 15:26:15 I have no more questions for odlparent. Does anyone else? 15:26:21 nop 15:26:25 No for me 15:26:33 Thanks Vaishali! Nice job 15:26:37 thanks all 15:26:42 #topic reservation 15:27:01 mlemay could you please link in your releaese review and release notes 15:27:14 #info mlemay for reservation project 15:27:16 yes 15:27:42 https://wiki.opendaylight.org/view/Reservation:Lithium_Release_Review 15:27:58 https://wiki.opendaylight.org/view/Reservation:Lithium_Release_Notes 15:28:03 mlemay: is lithium voting done for reservation? 15:28:07 yes 15:28:21 (I think I did it this am) 15:28:40 reservation only managed to ship TL1 Southbound and 2 models 15:29:25 mlemay does reservation require Java 8? 15:29:31 mlemay: thanks 15:29:32 no 15:29:48 did I required that anywhere? 15:30:06 it is however what has been used in dev / test 15:30:13 I assumed it from your target env of OpenJDK JRE 8 15:30:30 ok will fix rel notes 15:30:40 also reservation has a serious lack of doc 15:30:43 cool 15:30:53 I'm addressing it now 15:31:01 (wiki) 15:31:38 #info phrobb asks if Java 8 is required, mlemay responds no it is not and he will make that more clear in the release notes 15:31:59 #action mlemay to clarify Java 7/8 requirements in release notes 15:32:29 "Can we flag things as "experimental" this release"? I would flag Reservation as such .. it works but at your own risks 15:33:48 I don't think there is a problem with you putting such a statement in your relese notes 15:34:32 Call it a technology preview or some such 15:35:06 yes 15:35:06 #info phrobb says there is no problem putting such a statement in your relese notes 15:35:07 ok 15:35:12 will do that 15:35:22 right away 15:35:40 #undo 15:35:40 Removing item from minutes: 15:35:43 gzhao.. I don't think you captured the question so the #info response won't make much sense 15:35:54 :-) 15:35:54 gzhao, i think my name got confused with someone else 15:36:49 gzhao, i am not PTL/comitter to odlparent :-) 15:37:36 gzhao: phrobb FYI, I'm here and ready whenever you all are 15:38:13 thanks Keith 15:38:33 #info phrobb says there is no problem putting such a statement in your relese notes such as flag things as "experimental" this release"? 15:38:42 vishnoianil - Thanks for the clarification. It all worked out in the end :-) 15:38:55 vishnoianil: sorry 15:39:25 phrobb.. cool, that's what matters the most :-) 15:39:42 mlemay there are no outstanding bugs for reservation? 15:40:06 not yet as no one is really using it.. it does what it does... 15:40:11 (not much) 15:40:25 but I suspect that as people use TL1 Southbound we'll get some there 15:40:40 Not much testing done at all then. Including by the reservation team 15:40:42 (we'll likely find some) 15:40:48 correct 15:41:18 it basically connects to device and can push TL1 verbs 15:41:26 as for the models well they are models 15:41:29 Yea, would strongly suggest putting some kind of warning in the release notes that this is Experimental/beta/tech-preview etc 15:41:36 yes 15:41:44 #info mlemay notes no outstanding bugs found since there are not much testing on reservation 15:42:31 #info phrobb strongly suggests putting some kind of warning in the release notes that this is Experimental/beta/tech-preview etc 15:43:57 would the current sentence in red do the trick? 15:44:07 The Reservation Project is an Experimental / Tech Preview Project, use at your own risks 15:45:10 Yea, just make sure you are clear that the warning is for this release with a promise of making it more usable/stable in Beryllium and beyond.... lest you scare your potential user s away 15:45:31 I've got no other questions for reservation. Does anyone else? 15:45:39 No 15:45:59 thanks mlemay 15:46:19 #topic gbp 15:46:22 hello 15:46:29 @phrobb: ok sound good , point of joining was to get more community around it... 15:46:35 for next cycle 15:46:36 alagalah: hello 15:46:40 alagalah could you please link in the release review and release notes page 15:46:43 #info Release Review: https://wiki.opendaylight.org/view/Group_Based_Policy_(GBP)/Releases/Lithium/Release_Review 15:46:57 * phrobb needs to step away for ~5 minutes 15:46:58 #info Release Notes: https://wiki.opendaylight.org/view/Group_Based_Policy_(GBP)/Releases/Lithium/Release_Notes 15:48:49 Hi All, is this the ODL Lithium release review meeting? 15:49:15 gbp writing looks good to me 15:49:34 so no issues expected in tha migration, right? 15:49:37 YuLing_: yes 15:49:42 great, thanks 15:50:16 LuisGomez: I highlighted one I think may cause problems 15:50:28 alagalah: GBP only have of and 15:50:43 in the ofoverlay 15:50:44 LuisGomez: But in terms of OpenStack GBP API integration, that change was already made, so no 15:50:52 gzhao: I don't understand 15:51:05 LuisGomez: I guess I am not following the question, sorry 15:51:34 alagalah: GBP only has OF and SFC render for Lithium? 15:51:39 no question, just looking the migration issue is in the ofoverlay :) 15:51:41 gzhao: Not quite 15:51:57 gzhao: Let me bold out the user facing features 15:52:56 * phrobb is back and reading... 15:53:07 alagalah: I see, those are major feature 15:53:25 gzhao: updated 15:53:27 gzhao: Refresh 15:53:32 alagalah: did GBP vote for lithium? 15:53:35 LuisGomez: Yes, that would be in the OfOverlay renderer 15:53:42 gzhao: I don't understand the question 15:54:24 gzhao: If you are referring to the TSC meeting last week re: go/no-go my vote at the time was "go" and it currently still is 15:54:43 gzhao: Do we need to be #info'ing this stuff ? 15:54:58 08:51 gzhao: alagalah: GBP only has OF and SFC render for Lithium? 15:55:01 alagalah: thanks 15:55:10 gzhao: ^^^ SFC is a part of the renderer action... 15:55:36 gzhao: With one renderer, yes it is fair to say SFC integration is in OfOverlay, but technically more correct to say it is part of the renderer, not the core model and policy resolution process. 15:56:05 alagalah, the tcp/udp classifier change is only in the rederer implementation or does it also change the user API? 15:56:25 LuisGomez: It would the parameters input to the API. 15:56:33 LuisGomez: And it is only in the renderer implementation 15:56:41 ok, got it 15:56:53 #info alagalah notes technically more correct to say it is part of the renderer, not the core model and policy resolution process. 15:57:02 #undo 15:57:02 Removing item from minutes: 15:57:33 11:56 下午 #info alagalah notes technically more correct to say SFC is part of the renderer, not the core model and policy resolution process. 15:58:25 alagalah could you vote go/nogo on the voting page? 15:58:31 phrobb: link ? 15:58:41 phrobb: Is it in same spreadsheet as blocking bugs ? 15:58:43 #link https://docs.google.com/spreadsheets/d/1KPpO9LH539Vlcoa4RvLa6PPCdLifi5JD-ihRhlybqeo/edit#gid=478292312 15:58:49 #info alagalah notes technically more correct to say SFC is part of the renderer, not the core model and policy resolution process. 15:59:00 done 15:59:06 cool, thanks 15:59:48 I don't have any other questions for gbp... do others? 15:59:56 not me 16:00:07 thanks alagalah 16:00:08 alagalah: I cannot access Google spreadsheet, but GBP is a major project didn't vote, thus I change background color 16:00:11 phrobb: LuisGomez gzhao Have you checked out our bright shiney wiki ? 16:00:12 gzhao did you get everything documented in #infos that you wanted? 16:00:20 gzhao: I just voted 16:00:38 alagalah: thanks 16:00:48 Hi, I'm ready to present Persistence. 16:00:53 phrobb: I have no questions 16:01:03 gzhao: phrobb Am I free to go, officers ? 16:01:05 :) 16:01:07 gzhao I removed the color highlight from the go/nogo sheet 16:01:20 alagalah move along... nothing to see here :-) 16:01:24 phrobb: Thank you sir :) 16:01:31 alagalah: thanks,yes 16:01:39 alagalah, i saw a mail the other day and just browsed a little 16:01:40 Thanks alagalah 16:01:56 it looks good :) 16:02:00 LuisGomez: :D 16:02:06 * alagalah blushes 16:02:15 next up is persistence is Shreyas here? 16:02:21 yes 16:02:22 LuisGomez: Couldn't be worse than what we had... have a good day folks 16:02:22 Ah, just read back 16:02:28 https://wiki.opendaylight.org/view/Persistence:Lithium:Release_Review 16:02:29 #topic Persistence 16:02:33 LuisGomez: +1 on that email 16:02:43 https://wiki.opendaylight.org/view/Persistence:Lithium:Release_Review 16:02:48 https://wiki.opendaylight.org/view/Persistence:Lithium_Release_Notes 16:03:13 Shreyas: you made it 16:03:21 just about :) 16:04:12 no bugs or limitations this release? 16:04:31 Shreyas: can you link the unit test coverage in release review 16:04:55 LuisGomez: This is the first release for Persistence; as other modules will start using it now, we might have bugs coming in 16:05:13 #info LuisGomez asks there is no bugs and limitations? 16:05:14 gzhao: sure. I'll do that 16:05:56 #info Shreyas notest that This is the first release for Persistence; as other modules will start using it now, we might have bugs coming in 16:06:12 what is code coverage %? 16:06:27 #action Shreyas to link the unit test coverage in release review 16:06:27 unit test i mean 16:06:31 Shreyas: target environment is blank? 16:06:42 LuisGomez: There is one limitation to be updated; Persistence works only for in-memory databases currently. will be extended to all other databases in Beryllium 16:07:26 ok, please update RN accordingly 16:07:58 #action Shreyas to add "known Limitations" section to release notes calling out Persistence works only for in-memory databases 16:08:05 #info persistence only for in memory database currently. 16:08:14 so this is kind of experimental/beta code this release? 16:08:20 #undo 16:08:20 Removing item from minutes: 16:08:34 LuisGomez: yes. I'll update that on Release Notes as well 16:08:53 #info LuisGomez asks so this is kind of experimental/beta code this release? 16:09:42 #action Shreyas to update relesase notes to call out that this release of Persistence is experimental/beta code 16:10:19 did I capture that correctly LuisGomez and Shreyas ? 16:10:37 phrobb: yes :) 16:10:42 sure 16:10:51 phrobb: I think so 16:11:01 Cool. Any other questions for Persistence? 16:11:11