14:30:32 #startmeeting boron release review 14:30:32 Meeting started Mon Aug 29 14:30:32 2016 UTC. The chair is anipbu. Information about MeetBot at http://ci.openstack.org/meetbot.html. 14:30:32 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:30:32 The meeting name has been set to 'boron_release_review' 14:30:38 #topic roll call 14:30:46 #info PTL and TSC members please #info in 14:30:51 #info anipbu 14:31:23 #info Ryan Goulding (rgoulding) for AAA 14:31:24 #info skitt 14:31:42 #info Alec Leckey for NetIDE 14:31:49 #info colindixon for docs, and TSC 14:32:09 #info Jensen Zhang for ALTO 14:33:16 #info Kai for ALTO 14:33:38 Do we have anyone from integration here? 14:34:09 #info Vratko polak for integration/distribution and integration/test 14:34:10 anipbu: jamo said he wouldn't be here until 8:05 14:34:16 but he sent out summaries 14:34:30 #info VivekSri for Genius 14:34:37 colindixon: vrpolak says he can represent integration 14:34:46 cool! 14:34:49 Good Morning vrpolak colindixon 14:34:50 want to get started? 14:34:51 Let's get started 14:34:56 #topic AAA 14:35:01 #link https://wiki.opendaylight.org/view/AAA:Boron:Release_Review <--- Release Review 14:35:06 #link https://wiki.opendaylight.org/view/AAA:Boron:Release_Notes <--- Release Notes 14:35:11 #info rgoulding is representing AAA 14:35:16 rgoulding: anything you would like to add? 14:35:25 anipbu: no nothing I can think of 14:35:40 open to questions/concerns from others 14:36:13 rgoulding: 1) Have you tested against RC2 and were there any blockers? 2) Do you have any features that should be considered experimental? 3) What are the user-facing features in your project? 14:36:38 rgoulding: is all the information on the wiki pages migrated to docs in the open patch, or just some of it? 14:36:58 anipbu: 1) yes, looks good 2) they are listed in the release review and notes 3) in the release review as well 14:37:17 rgoulding: please update with AAA RC2 testing https://docs.google.com/spreadsheets/d/1zImtd764e-hOgJAxoJKl85fxHCPu2agLfqsBtf13zQY/edit#gid=199721620 14:37:19 I read through everything and it looks good to me 14:37:26 colindixon: no just the stuff that is useful for users; there is development oriented stuff that is still just wiki 14:38:00 anipbu: done 14:38:57 i'm happy 14:39:22 AAA has two CSIT suites, one is passing, the other one is failing. Perhaps wrong features are being installed. That means some features should be considered experimental, but I am not sure which ones. 14:39:40 vrpolak: that suite (idmlite) has never passed 14:39:52 vrpolak: some features are considered experimental, they are listed in the release review... 14:40:02 #link https://wiki.opendaylight.org/view/AAA:Boron:Release_Review 14:40:33 idmlite is not a feature at all... i don't know who pushed the original code for that test 14:41:18 #info idmlite is not a feature in aaa for boron. tests are failing, but they are invalid anyways. 14:41:59 vrpolak: based on rgoulding response to your questions, do you have any other concerns? 14:42:24 #info all of AAA features are experimental 14:42:34 #info AAA has tested RC2 and found no problems 14:42:56 If there vrpolak has no other concerns, I am ready to move on. 14:43:18 anipbu: wait, all of AAA features are experimental? 14:43:18 odl-aaa-cli and odl-aaa-cert features do not seem to be tested in the one passing job. 14:43:51 I believe odl-aaa-shiro is the only feature tested successfully. 14:43:58 colindixon: it looks that way form the release review template https://wiki.opendaylight.org/view/AAA:Boron:Release_Review 14:43:59 odl-aaa-authn (which is odl-aaa-shiro) I think is tested and is no experiemntal 14:44:03 odl-aaa-shiro wraps odl-aaa-authn 14:44:10 OK 14:44:12 but yes, the old-aaa-cli and old-aaa-cert are experimental 14:44:27 they are tested only through unit tests at this point 14:44:31 rgoulding: is shiro supposed to be experimental? I thought no. 14:44:33 i did not contribute those 14:44:52 colindixon: i don't know the definition of experimental... it is not in my opinion 14:45:09 it has tests, it's considered prodution ready? 14:45:13 if so, it's not experimental 14:45:25 yes... it is installed one every running instance of ODL in the world to my knowledge 14:45:35 i think the test suite is called authn 14:45:37 #action rgoulding to follow up with shiro experimental state 14:45:38 but its really testing shiro 14:45:55 shiro just wraps authn and adds IDP on top 14:46:09 colindixon rgoulding I have added an action item for AAA to follow up on the state of shiro. 14:46:20 i just did... its not experimental. 14:46:23 ill change it 14:46:28 ok 14:46:29 thanks 14:47:05 Okay, do folks have any additional concerns or comments for AAA? 14:47:12 no, I think we're good 14:48:12 #action rgoulding to follow up on code coverage for the system test: "odl-aaa-cli and odl-aaa-cert features do not seem to be tested in the one passing job." 14:48:16 anipbu: No more comments on AAA. 14:48:26 Okay, Let's move on 14:48:31 #info AAA approved for Boron pending action items. Congratulations! 14:48:36 #topic ODLPARENT 14:48:40 #link https://wiki.opendaylight.org/view/ODL_Parent:Boron:Release_Review <--- Release Review 14:48:44 #link https://wiki.opendaylight.org/view/ODL_Parent:Boron:Release_Notes <--- Release Notes 14:48:52 #info skitt is representing ODLPARENT 14:48:57 skitt: anything you would like to add? 14:49:03 anipbu, not that I can think of 14:49:38 skitt: 1) Have you tested against RC2 and were there any blockers? 2) Do you have any features that should be considered experimental? 3) What are the user-facing features in your project? 14:49:54 no blockers on RC2 14:50:04 no experimental features 14:50:10 no user-facing features 14:50:19 Oldparent has a system test waiver, so no comments from integration. 14:50:27 the Karaf 3.0.7 upgrade is done? 14:50:37 colindixon, yes, it's done in Boron 14:50:58 colindixon, RC2 and I think RC1 use 3.0.7 14:51:10 cool! 14:51:27 :-) 14:51:28 #info odlparent has no blockers in RC2 (tested). no experimental features. no user facing features 14:51:47 #info karaf 3.0.7 upgrade is complete 14:52:34 skitt did you state in release notes the 3.0.7 upgrade? 14:52:38 yes 14:52:47 yes 14:52:49 Many upstream upgrades, including Karaf (3.0.7 for Boron) 14:52:51 " Many upstream upgrades, including Karaf (3.0.7 for Boron) " 14:53:11 #info ODLPARENT has system test waiver approved by the integration team https://wiki.opendaylight.org/view/Simultaneous_Release/Boron/Waiver/System_Test 14:53:28 I'm fine with odlparent 14:53:37 so am I 14:53:54 Do folks have any futhur concerns or questions? 14:54:34 I think we're ready to move on. 14:55:00 #info ODLPARENT approved for Boron. Congratulations! 14:55:05 thanks! 14:55:05 #topic NETIDE 14:55:11 #link https://wiki.opendaylight.org/view/NetIDE:Boron_Release_Review <--- Release Review 14:55:14 #link https://wiki.opendaylight.org/view/NetIDE:Boron_Release_Notes <--- Release Notes 14:55:24 #info aleckey is representing NETIDE 14:55:29 aleckey: anything you would like to add? 14:55:39 No, think that is everything 14:55:42 aleckey: 1) Have you tested against RC2 and were there any blockers? 2) Do you have any features that should be considered experimental? 3) What are the user-facing features in your project? 14:56:31 we have the one user facing feature: odl-netide-rest. It is experimental and has been tested for RC2. All good, forgot to update spreadsheet 14:57:13 NetIDE feature repository is included in integration, but its features are commented out, so the do not participate in compatibility testing (-all- jobs). 14:57:41 #info netide has tested RC2 and found no issues 14:58:20 it looks good to me 14:58:21 aleckey: please take a moment to update column B/C of the spreadsheet https://docs.google.com/spreadsheets/d/1zImtd764e-hOgJAxoJKl85fxHCPu2agLfqsBtf13zQY/edit#gid=199721620 14:58:21 One CSIT suite is run, but it does not test NetIDE at all. Yep, experimental. 14:58:34 in the long-run it would be good to push the docuemntation into reStructuredText so it's all in one place 14:58:44 Yes, I'll update spreadsheet 14:58:55 netide looks good to me 14:59:17 #info netide features are experimental 14:59:38 #info NetIDE feature repository is included in integration, but its features are commented out, so the do not participate in compatibility testing (-all- jobs) 14:59:54 Do folks have any futhur concerns or questions? 15:00:25 it looks good to me 15:00:27 cool stuff 15:00:41 #action aleckey to follow up on pushing the docuemntation into reStructuredText so it's all in one place 15:00:46 Okay let's move on 15:01:11 #info NETIDE approved for Boron. Congratulations! 15:01:16 #topic ALTO 15:01:21 #link https://wiki.opendaylight.org/view/ALTO:Boron:Release_Review <--- Release Review 15:01:26 #link https://wiki.opendaylight.org/view/ALTO:Boron:Release_Notes <--- Release Notes 15:01:30 #info jensen_zhang is representing ALTO 15:01:33 jensen_zhang: anything you would like to add? 15:01:51 No. I think that is all. 15:02:20 anipbu, vrpolak, colindixon: I'm here now. 15:02:29 * colindixon reads 15:02:36 jensen_zhang: 1) Have you tested against RC2 and were there any blockers? 2) Do you have any features that should be considered experimental? 3) What are the user-facing features in your project? 15:02:55 #chair jamoluhrsen colindixon vrpolak 15:02:55 Current chairs: anipbu colindixon jamoluhrsen vrpolak 15:03:16 afk 1 min 15:04:03 jensen_zhang: 1) Have you tested against RC2 and were there any blockers? 2) Do you have any features that should be considered experimental? 3) What are the user-facing features in your project? 15:04:05 no blockers on rc2. odl-alto-release is our top feature. it is experimental and user-facing. 15:04:19 #info alto has tested RC2 and found no blockers 15:04:37 #info all of alto features are experimental 15:05:46 looks good to me 15:07:11 Great, thanks. 15:07:19 jensen_zhang: no new code this release, is that correct? 15:07:30 I'm also fine with ALTO 15:07:53 There is a CSIT job. One test case (in Resourcepool suite) passes, the other three tests fail (possibly because only feature named odl-alto-resourcepool is installed). 15:07:55 anipbu: I think we introduce two new funtions in this release. 15:08:41 okay, so those two new functions are wrapped in the existing feature, correct? 15:08:56 anipbu: yes 15:10:34 Do folks have any futhur concerns or questions? 15:10:44 I'm good 15:11:00 Okay, I think we're ready to move on. 15:11:21 jamoluhrsen: good morning, glad to see you join us! 15:11:33 #info ALTO approved for Boron. Congratulations! 15:11:40 Thanks. 15:11:41 #topic BGPCEP 15:11:47 #link https://wiki.opendaylight.org/view/BGP_LS_PCEP:Boron_Release_Review <--- Release Review 15:11:51 #link https://wiki.opendaylight.org/view/BGP_LS_PCEP:Boron_Release_Notes <--- Release Notes 15:11:56 #info milfabia is representing BGPCEP 15:12:00 milfabia: anything you would like to add? 15:13:12 anipbu: are you linking project csit analysis here in irc? 15:13:48 CSIT BGP tests results shows some failures - https://bugs.opendaylight.org/show_bug.cgi?id=6497 - affecting functionality, issue was addressed to yangtools and mdsal 15:14:08 jamoluhrsen: I think vrpolak has been giving the CSIT analysis on IRC 15:14:18 ok 15:14:30 problem it is all working locally but not on ODL machines 15:14:46 milfabia, is this a blocker? 15:14:56 I thought taht timing issues had been plaguing bgpcep 15:15:03 jamoluhrsen: but we haven't had any links available. Please feel free to #info #link as appropriate 15:15:14 milfabia: 1) Have you tested against RC2 and were there any blockers? 2) Do you have any features that should be considered experimental? 3) What are the user-facing features in your project? 15:16:02 milfabia: is there an ETA for when bug 6497 will be resolved? 15:16:13 yes, I would say this one is a blocker - I will prepare a wrokaround in BGP code, if there is not response from yantools 15:16:41 ETA tomorrow 15:16:52 milfabia: seems we are cutting very close the last and final build (RC3 this Thursday). Has yangtools been notified? 15:17:08 email was sent 15:17:14 on friday 15:17:15 milfabia: is 6497 expected to clean up all the csit failures? 15:17:52 #info CRITICAL: bug 6497 appears to be a blocking bug somewhere between bgpcep and yangtools, it's being debugged and a fix is hoped for by tomorrow 15:18:21 milfabia: please update the spreadsheet on BGPCEP testing for RC2: https://docs.google.com/spreadsheets/d/1zImtd764e-hOgJAxoJKl85fxHCPu2agLfqsBtf13zQY/edit#gid=199721620 15:18:24 #action milfabia to follow up with bug 6497 15:18:33 ok, will do 15:19:46 milfabia: could you state in the release notes that the target environment https://wiki.opendaylight.org/view/BGP_LS_PCEP:Boron_Release_Notes 15:20:00 I think it's java 8 requirement, correct? 15:20:15 yes, you are right 15:20:56 I would say BMP and PCEP features have stable tests, but BGP tests failures do not point to corresponding Bugs. So BGP would be experimental from testing point of view. 15:21:04 milfabia: could you list out the features and whether they are user-facing or experimental or have CSIT code with it https://wiki.opendaylight.org/view/BGP_LS_PCEP:Boron_Release_Review#Major_Features 15:21:34 You can see an example of the listing here: https://wiki.opendaylight.org/view/Sample_Release_Review#Features 15:21:47 at some point we should go through and make an official set of requiments so others can ignore the rest, I've been meaning to better tempaltize the release review and release notes 15:21:49 but didn't have time 15:22:09 #action milfabia to update the target environment 15:22:11 ok, I will update 15:22:34 #link https://lists.opendaylight.org/pipermail/bgpcep-dev/2016-August/000729.html email with CSIT analysis. 15:22:44 #action milfabia to update the list of features and if they are user-facing or experimental, etc. 15:23:10 milfabia: it seems most features are experimental, is that correct? 15:23:28 #info 10 CSIT jobs (which is great), but 8 of them have unexpected failures. as vrpolak points out, they might be consistently failing but they should point to an open non-blocking bug if so. 15:24:19 there are 3 user facing feature in bgpcep, none of them are considered stable 15:24:55 milfabia: did you mention in the release notes that BGPCEP has refactored to remove TCPMD5 dependencies? 15:25:51 oh, good point...I forget to mention that 15:26:20 #action milfabia to update the release notes with reference on TCPMD5 migration 15:27:13 #action milfabia to follow up on the CSIT failures. (if they are all experimental features, then okay. but for any non-experimental features, the CSIT must pass, etc) 15:27:28 I don't have any additional questions. 15:27:41 milfabia: Are there top-level features which are only experimental (as opposed to just not stable)? 15:28:44 no, they are not experimental 15:28:51 mlemay_: Do you know if Maxime Millette-Coulombe is online? 15:30:06 no new top-level feature were add in Boron, just updated existing with new functionality 15:30:14 milfabia: for the ones that are not experimental, please review the CSIT comments from the integration team. You have been #action to follow up on those. 15:30:19 vrpolak, by definition most if not all bgpcep features are experimental, right? 15:31:09 jamoluhrsen: It seems from milfabia's commentst that there are some non-experimental features. 15:31:37 milfabia: which features are non experimental that are doing CSIT? 15:32:18 odl-bgpcep-bgp, odl-bgpcep-pcep, odl-bgpcep-bmp 15:32:36 jamoluhrsen: Based on CSIT? odl-bgpcep-bgp is experiemental, but odl-bgpcep-bgp and odl-bgpcep-bgp are not as their suites pass 100%. 15:32:37 the bgp has failures in CSIT 15:32:58 anipbu: should we take this offline? 15:33:12 colindixon: I think BGPCEP is worth following up over email 15:33:23 colindixon, there is already the email they can reply to about this. 15:33:27 #action anipbu to follow up with BGPCEP over email 15:34:08 Do folks have any further concerns or questions? Otherwise Let's follow up with BGPCEP over email and move on. 15:34:08 Sorry, wrong paste. odl-bgpcep-pcep and odl-bgpcep-bmp 15:34:39 #info CAPWAP cannot made their release review. Will reschedule. 15:35:07 Is anybody from controller here? 15:35:27 I never received any confirmation from controller team. 15:36:00 If there are no representatives from controller, we will have to reschedule controller as well. 15:36:50 #info CONTROLLER was unresponsive. Will reschedule. 15:37:04 I can do docs 15:37:51 Next up is DLUX actually 15:38:01 #topic DLUX 15:38:16 #link https://wiki.opendaylight.org/view/OpenDaylight_DLUX:Boron_Release_Review <--- Release Review 15:38:28 #link https://wiki.opendaylight.org/view/OpenDaylight_DLUX:Boron:Release_Notes <--- Release Notes 15:38:39 #info mmcoulombe is representing DLUX 15:38:45 mmcoulombe: anything you would like to add? 15:38:59 one thing, links won't difer a lot from Berrilyum 15:39:06 nothing really change 15:39:10 * colindixon reads 15:39:24 nobody got time to work on DLUX 15:40:05 mmcoulombe: 1) Have you tested against RC2 and were there any blockers? 2) Do you have any features that should be considered experimental? 3) What are the user-facing features in your project? 15:40:13 is this still up-to-date? http://docs.opendaylight.org/en/stable-boron/user-guide/using-the-opendaylight-user-interface-(dlux).html 15:40:25 #info all dlux features should be considered experimental 15:40:40 I'm assuming this is: http://docs.opendaylight.org/en/stable-boron/developer-guide/dlux.html 15:40:53 :colindixon this should be 15:41:06 the first link I think was written a long time ago 15:42:30 :colinduxon true but it's still accurate. Nothing really change since helium release for DLUX 15:42:57 mmcoulombe: Have you tested against RC2 and were there any blockers? 15:43:19 :anipbu not yet 15:44:07 mmcoulombe: please take a moment to download and test RC2. The last and final build is this Thursday. 15:44:20 sure i will 15:44:21 mmcoulombe: is there an ETA for when you can test RC2? 15:44:38 today, worst case tomorrow 15:45:21 #action mmcoulombe to test RC2 today or (worst case) tomorrow and confirm if there are any blocking issues and update the spreadsheet appropriately: https://docs.google.com/spreadsheets/d/1zImtd764e-hOgJAxoJKl85fxHCPu2agLfqsBtf13zQY/edit#gid=199721620 15:45:56 #info dlux docs are still accurate since nothing really change since helium release for DLUX 15:47:00 mmcoulombe: it think for the target environment, it requires java 8. seems like you listed java 7 or 8. 15:47:44 my mistake, i'll update it 15:47:58 #action mmcoulombe to update the release notes target environment 15:48:41 dlux looks good to me 15:48:47 same here 15:49:00 jamoluhrsen: any other comments? 15:49:12 Do folks have any further concerns or questions? Other let's move on. 15:49:16 anipbu, nothing from me. easy one from csit point of view 15:49:26 #info DLUX approved for Boron pending action items. Congratulations! 15:49:35 #topic DOCS 15:49:36 #link https://wiki.opendaylight.org/view/Documentation/Boron/Release_Review <--- Release Review 15:49:42 #link https://wiki.opendaylight.org/view/Documentation/Boron/Release_Notes <--- Release Notes 15:49:48 #info colindixon is representing DOCS 15:49:59 colindixon: anything you would like to add? 15:50:29 not really, migration to reST is ongoing, but moves, we plan to merge these patches w/o project involvment on thursday: https://git.opendaylight.org/gerrit/#/q/(topic:adoc2rst+OR+topic:adoc2rst-user)+status:open 15:50:58 that's something like 12 projects of stuff 15:51:43 #info migration to reST is ongoing pending 12 projects https://git.opendaylight.org/gerrit/#/q/(topic:adoc2rst+OR+topic:adoc2rst-user)+status:open 15:52:20 #info docs does not need to test RC2: N/A 15:52:34 yeah... CSIT is n/a 15:54:40 anything else? 15:55:00 #link http://docs.opendaylight.org/ this is the big thing we delivered 15:55:13 #info we also no support inclusion of docs directly from project repos 15:55:16 For the Non-Code Aspects section, please update with link to the docs docs.opendaylight.org. 15:55:28 * colindixon does that 15:55:47 #action colindixon to update Non Code Aspects with appropriate links. 15:56:22 docs looks good to me 15:56:29 Do folks have any further concerns or questions? 15:57:38 If folks do not have any futhur questions, then let's move on. 15:58:17 #info DOCS approved for Boron. Congratulations! 15:58:33 The eman team has requested to reschedule. 15:58:43 thanks 15:58:59 #info EMAN cannot made their release review. Will reschedule. 15:59:25 #topic GENIUS 15:59:33 #link https://wiki.opendaylight.org/view/Genius:Boron:Release_Review <--- Release Review 15:59:40 #link https://wiki.opendaylight.org/view/Genius:Boron:Release_Note <--- Release Notes 15:59:45 #info VivekSri is representing GENIUS 15:59:51 VivekSri: anything you would like to add? 16:00:00 one thing, our CSIT reviews are not merged yet. 16:00:07 I just got a mail from jamo indicating that since the CSIT is not merged, all genius features should be considered experimental 16:00:26 however, we have all the tests passing in our environment with the tests up for review. 16:00:35 Also NetVirt project is extensivey using genius features, and thus genius features are also tested with NetVirt CSIT. 16:00:48 Do we still consider these features experimental? 16:01:10 so, do you want them to be experiemental? I think if you have the tests and jamoluhrsen or vrpolak can confirm that, ythey don't have to be 16:01:31 VivekSri: Have you tested against RC2 and were there any blockers? 16:01:38 i consider them as non experimental 16:02:19 #link https://lists.opendaylight.org/pipermail/genius-dev/2016-August/000282.html email about CSIT analysis for Genius project 16:02:24 #info CSIT patches are pending merge. 16:02:26 #info NetVirt project is extensivey using genius features, and thus genius features are also tested with NetVirt CSIT 16:02:38 #info there is currently no csit so by definition all features would be experimental. 16:02:51 #info integration team needs to review those patches 16:03:22 #info netvirt is going to be labeled experimental all over the place too, so we can't use that project's CSIT for genius 16:03:24 does genius have reST and/or AsciiDoc docs or plan to? 16:03:44 VivekSri: seems like your project is not meeting test expectations for nonexperimental. 16:04:00 #action jamoluhrsen to review genius csit patches. 16:04:00 AsciiDoc is also up for review 16:04:13 https://git.opendaylight.org/gerrit/#/c/39665/ 16:04:18 VivekSri: that being said, you I think you can request that to be reviewed 16:04:26 if you get the tests in soon 16:04:33 ok, will do 16:04:40 #info genius has pending docs patches for review: https://git.opendaylight.org/gerrit/#/c/39665/ 16:04:52 VivekSri: it looks like we're waiting for more input here: https://git.opendaylight.org/gerrit/#/c/39665/ 16:04:54 #action VivekSri to follow up on docs patches 16:05:10 sure, will follow up 16:05:24 #action VivekSri to follow up on CSIT tests and "experimental" tag for relevant features. 16:06:10 VivekSri: I've added an action for you to follow up with integration team on the CSIT tests and experimental tag. Currently you project features do not meet test expectations to be labeled nonexperimental. 16:06:20 VivekSri: Have you tested against RC2 and were there any blockers? 16:06:32 yes, no blockers 16:07:43 #info genius has tested RC2 and found no blockers 16:08:22 VivekSri: could you please update this spreadsheet with the status of RC2 testing for Genius: https://docs.google.com/spreadsheets/d/1zImtd764e-hOgJAxoJKl85fxHCPu2agLfqsBtf13zQY/edit#gid=199721620 16:08:38 things look good to me 16:08:40 ok, will do 16:09:35 VivekSri: genius provides fcaps? 16:10:07 VivekSri: if genius provides fcaps, are there any security considerations that needs to be spelled out in the release review template? 16:10:16 yes, there are features to include fcaps framework and application 16:10:56 no specific security considerations i can see 16:11:15 #info genius has no security considerations 16:12:45 genius looks good to me, pending action item of follow up on the CSIT tests and experimentatl tag 16:12:59 Do folks have any further concerns or questions? 16:13:55 jamoluhrsen: any additional concerns you would like to raise? 16:15:07 Okay, if there are no other concerns, Let's move on. 16:15:19 #info GENIUS approved for Boron pending action items. Congratulations! 16:15:29 thanks! 16:15:44 Any folks from HONEYCOMB VBD? 16:15:45 anipbu: all good with me. 16:15:52 Any folks from HONEYCOMB VBD? 16:16:38 VBD has been unresponsive, so let's reschedule them. 16:17:01 #topic L2SWITCH 16:17:06 #link https://wiki.opendaylight.org/view/L2_Switch:Boron:Release_Review <--- Release Review 16:17:10 #link https://wiki.opendaylight.org/view/L2_Switch:Boron:Release_Notes <--- Release Notes 16:17:19 #info evanz is representing L2SWITCH 16:17:28 evanz: anything you would like to add? 16:17:45 #link https://lists.opendaylight.org/pipermail/l2switch-dev/2016-August/001260.html csit analysis email. 16:17:50 anipbu: nothing to add 16:18:16 #info looks like all l2switch features should have the experimental label. 16:18:30 "There is a backlog of bugs here waiting for some love. " 16:18:32 love that 16:18:49 evanz: 1) Have you tested against RC2 and were there any blockers? 2) Do you have any features that should be considered experimental? 3) What are the user-facing features in your project? 16:20:51 Only sub-suite for loop remover has failures, but there is only one user-facing feature, so odl-l2switch-switch is experimental from testing point of view. 16:21:19 1. I haven't looked at RC2 myself, but I can take a look and follow up 2. all of them, as per @jamoluhrsen? 16:21:54 vrpolak: also the scale job is reporting zero. 16:22:09 evanz: in your release review template, could you list out the features and whether they are user-facing or experimental or have CSIT code with it https://wiki.opendaylight.org/view/L2_Switch:Boron:Release_Review#Features 16:22:09 is that a regression? 16:22:13 evanz: You can see an example of the listing here: https://wiki.opendaylight.org/view/Sample_Release_Review#Features 16:22:18 anipbu: we should probably ask if there are any known regressions? 16:22:22 the test is "PASS", but the value is 0 which is not good. 16:22:39 #info l2switch to test RC2 and report the status of any blocking bugs 16:23:06 jamoluhrsen: I was curious if it returned more than 0 in the past 16:23:58 evanz: please update the spreadsheet on L2SWITCH testing for RC2: https://docs.google.com/spreadsheets/d/1zImtd764e-hOgJAxoJKl85fxHCPu2agLfqsBtf13zQY/edit#gid=199721620 16:24:18 will do 16:24:19 #action evanz to update the list of features and if they are user-facing or experimental, etc. 16:24:43 evanz, jamoluhrsen, vrpolak anyone know the answer to my question: did the scale test return >0 before? 16:24:45 colindixon: let me try to find out 16:24:47 #action evanz to follow up on RC2 testing and update the spreadsheet 16:24:50 OK 16:24:54 colindixon, I think it did 16:25:06 it doesn't affect this right now, but it would be good to know and understand if it's real or fake 16:25:10 jamoluhrsen: Oh. Yes, and the reason is the same: failed ping check. Not sure which functionality is failing for that one. 16:25:17 colindixon, it was 100 at one point 16:25:30 OK 16:25:47 #action evanz to figure out if the scale test is a real regression or just a test failure 16:25:53 #link https://jenkins.opendaylight.org/releng/view/l2switch/job/l2switch-csit-1node-periodic-host-scalability-daily-only-boron/plot/Inventory%20Host%20Scalability/ scalability test showing zero, but was 100 in the past 16:26:01 tjamls 16:26:02 100 is the first step. Maybe suite with smaller step would measure non-zero. 16:26:16 I can take a look at it. 16:27:24 Sai_: it looks like it happened between 6/22 and 6/24, which is odd because there's nothing of substance here: https://git.opendaylight.org/gerrit/#/q/project:l2switch+status:merged 16:27:36 maybe it's a timing issue 16:27:44 that's about when we migrated 16:29:37 So maybe we can follow up over email on the test failures to determine if there are any regression? 16:30:41 colindixon: yes, the graphs says so, I will go through tests and provide an update. 16:30:57 cool 16:31:12 given that it's experimental and works in manual testing, this isn't a blocker, but would be good to understand 16:31:17 OK 16:31:36 I think it would be worth following up with l2switch over email to cover: rc2 testing, updating features list on release review template, and csit/scale test issues 16:31:44 +1 16:31:54 i will take a look at the l2switch failures later today, at least to a point to know whether this is test or controller issue. 16:32:42 mostly for completeness b/c everything is experimental, I'm not as worried 16:32:48 #info anipbu evanz: l2switch to follow up over email to cover: rc2 testing, updating features list on release review template, and csit/scale test issues 16:33:13 #undo 16:33:13 Removing item from minutes: 16:33:18 #action anipbu evanz: l2switch to follow up over email to cover: rc2 testing, updating features list on release review template, and csit/scale test issues 16:33:31 Do folks have any further concerns or questions for l2switch? 16:33:50 no, thanks anipbu , colindixon 16:33:58 I'm good 16:34:07 Okay let's move on 16:34:20 MDSAL has been unresponsive. 16:34:30 Are there any representatives from mdsal? 16:35:09 my guess is it's the same as controller 16:35:22