14:30:05 #startmeeting Brahmaputra Daily Standup 14:30:05 Meeting started Mon Feb 22 14:30:05 2016 UTC. The chair is debrascott_. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:30:05 Useful Commands: #action #agreed #help #info #idea #link #topic. 14:30:05 The meeting name has been set to 'brahmaputra_daily_standup' 14:30:13 #topic roll call 14:30:24 #info Jonas Bjurel 14:30:27 #info Dan Radez 14:30:32 #info Morgan Richomme 14:30:58 #indo Ana Cunha 14:31:07 #info Ana Cunha 14:31:08 #info HEather Kirksey 14:31:42 #link agenda same as Th/Fri https://wiki.opnfv.org/releases/brahmaputra/minutes 14:32:18 #info the PTLs approved freeze of scenario troubleshooting on Sunday 2/21 14:32:20 #info Narinder Gupta 14:32:24 #info Bin Hu 14:32:56 #Topic Test Status and final scenario list for this release 14:32:59 #info Frank Brockners 14:33:18 #info Ashlee Young 14:33:19 morgan_orange welcome back! 14:33:38 #info page on the status updated this morning https://wiki.opnfv.org/functextnexttaks 14:34:21 #info scenario ready for B: - apex/odl_l2 14:34:21 - compass/odl_l2 14:34:21 - compass/onos 14:34:21 - compass-nosdn 14:34:21 - fuel/nosdn 14:34:22 - fuel/old_l2 14:34:22 - fuel/onos 14:34:23 - fuel/nosdn-ovs 14:34:23 - joid/odl_l2 14:34:24 - joid/nosdn 14:34:40 morgan_orange: joid/onos will that pass? 14:35:44 narindergupta1: joid/onos still issue with vPing + high error rate on tempest and run only 2 times over the week end 14:35:59 morgan_orange: ok 14:36:09 morgan_orange: these all pass functest, do the same also pass yardstick? 14:36:18 debrascott: no 14:36:39 not all 14:36:45 anac1: which do not pass yardstick (assume that is the shortest list) 14:37:08 joid, no scenarios verified 14:37:43 fuel: is there any difference from nosdn and ovs until last week ? 14:38:20 anac1: for joid the issue is probably linked to authentication issues on heat 14:39:03 anac1: it was in your to do list to debug last week. Any status? 14:39:09 morgan_orange: yes, probably - but i don't have 4 runs paseed 14:39:39 narindergupta: we found no issues in yardstick, works for apex, compass and fuel 14:39:45 anac1: billyoma fixed a bug, but we didnt have resources to run the ovs scenarios 14:40:24 jonasburel: thanks, so the above listed nosdn-ovs is not yet ready, right? 14:40:48 anac1: Correct, not yet ran. 14:42:05 OK so I think these can be noted it release notes: what was not fully tested 14:42:15 From functest perspective, I shall also precise that I do not respect stricly our Tempest criteria (> 90% OK) otherwise only compass scenario will be OK. fuel is (80-90 depending on the scenario but reproducible from one run to another), apex variable (60-90, not very reproducible but less tests run that on the other installers) 14:43:18 morgan_orange: also good for release notes 14:43:54 morganorange: I have a lab-config patch that will likely make fuel pass more Tempest, (too few floating IPs currently) - havnt had resources to run that patch yet 14:43:55 Are there any features that are not supported by at least one scenario? 14:44:50 debrascott_ NFVOVS, KVM4NFV, SFC, BGP-VPN 14:45:39 jonasbjurel: thank you, this will be important for marketing to refine their messaging 14:45:41 jonasbjurel: cool it shall fixe almost 5-10 errors - but I put a clear status because the number of errors is limited, one dealt with the nb of floatting IP, there is another one linked to heat 14:46:25 doctor is also in progress in any apex scenario but not supported yet 14:47:02 any additional discussion about what it/is not in first release of B? 14:47:17 morgan_orange: thanks 14:47:45 OK lets move on to docs 14:48:01 ChrisPriceAB: are you with us today? 14:48:10 not quite... 14:48:19 :) 14:48:29 #info opnfvdocs call scheduled for 16:00 to review content and status of all release docs. 14:48:55 16:00 which time zone? 14:49:48 CET just after this meeting 14:49:59 ChrisPriceAB: I will join at 16h30.. 14:50:08 morgan_orange: thanks 14:50:16 ok thanks morgan_orange 14:50:21 ChrisPriceAB: same for me, join at 16:30 14:50:58 anac1, morgan_orange: are you feeling confident with the remaining time to document test results? Do you have resources you need? 14:51:15 debrascott_: yes 14:51:28 #info opnfvdocs goto meeting details: https://global.gotomeeting.com/join/156364589 14:51:41 debrascott_: yes ... copy/paste of jenkins logs... 14:52:15 anac1, morgan_orange: good! 14:52:48 OK we are down to the end of 1st release do we need to start talking about 2nd release? 14:53:17 We target end March for that 14:53:29 Which scenarios are likely to make it in by that time? 14:54:33 This is not 1'st release, its the 3'rd :-) 14:54:34 debrascott_: is it possible to add the scenarios like onos for joid 14:54:36 ? 14:55:21 jonasbjurel: I mean 1st release of B and 2nd release of B (not C release) 14:55:35 just to be sure..for joid scenario, heat shall be fixed to allow yardstick on joid scenarios 4 times until when? otherwise no joid scenario will be in B release...Do I understand correctly? 14:55:41 debrascott_: I understand 14:57:19 morgan_orange: i think odl_l2 and nosdn is in as those passes other test and heat issue need to find the root cause as it started failing. 14:57:52 morgan_orange: who will fix heat ? 14:58:16 morgan_orange: i have the same understanding as you 14:59:06 narindergupta1, morgan_orange: vIMS is the issue for JOID in functest, correct? the fix for vIMS is in already or not? 14:59:26 vIMS is not a critical criteria for release 15:00:02 restriction must be documented 15:00:33 i have to leave for another meeting 15:00:51 If not troubleshooting, but test run only then I don’t have a problem with having the test run but if fix is not in then I think we document and release without it being supported 15:01:14 it can be in next B release 15:01:34 OK, time to go. Thanks everyone for joining 15:01:38 #endmeeting