14:31:20 #startmeeting release daily sync 14:31:20 Meeting started Thu Sep 18 14:31:20 2014 UTC. The chair is gzhao. Information about MeetBot at http://ci.openstack.org/meetbot.html. 14:31:20 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:31:20 The meeting name has been set to 'release_daily_sync' 14:31:32 #topick roll call 14:31:44 #topic roll call 14:31:46 #info goldavberg for lispflowmapping 14:31:59 #info gzhao for release 14:32:21 #info tbachman for groupbasedpolicy 14:34:06 please #info in 14:34:11 #info abhijitkumbhare OpenFlow plugin 14:34:23 #info Hideyuki for VTN 14:34:24 #info edwarnicke 14:34:47 * tbachman thanks gzhao profusely for running these meetings, and for all the cat-herding that he does so well! :) 14:35:00 * edwarnicke second tbachman in thanking gzhao :) 14:35:01 #info thomas packetcable 14:35:07 1 more minute 14:35:19 * gzhao thanks tbachman edwarnicke 14:35:54 #topic auto-release 14:36:25 #link https://wiki.opendaylight.org/view/Karaf:Step_by_Step_Guide#Download_the_RC <- now with the link for last nights nightly, RC1-2 14:36:37 info: gershon defense4all 14:36:44 Hi everybody! 14:36:52 #info gershon defense4all 14:37:01 gershon: needs the ‘#’ sign :) 14:37:11 Ok, thanks, sorry:) 14:37:16 np! :) 14:37:17 the last daily build failed after 5 successful built 14:37:23 https://www.irccloud.com/pastebin/KMTYIonZ 14:37:33 gershon: No worries, you'll get the hang of it :) 14:37:42 gzhao: Someone is already working on that :) 14:37:55 edwarnicke: ok 14:38:11 gzhao: Now quite sure what happened yet, but the patch verified, seems to have become grumpy on that one test on merge 14:38:45 edwarnicke: do you know which project is working on the fix? 14:38:46 #link : https://www.irccloud.com/pastebin/KMTYIonZ <= trace showing daily build failed 14:39:20 #info gzhao says the last daily build failed after 5 successful builds 14:40:40 #info edwarnicke said someone is already working on that 14:40:44 #undo 14:40:44 Removing item from minutes: 14:40:45 gzhao: controller 14:41:10 #info edwarnicke said controller team is already working on the fix 14:41:42 #Info colindixon for TTP 14:41:58 any other thing worth to mention about autorelease? 14:42:12 * edwarnicke hope the autorelease is becoming boring :) 14:42:33 edwarnicke: that would be the hope 14:42:34 #topic issues and status 14:42:49 any blocking issues 14:43:45 I could use a windows expert 14:44:04 edwarnicke: the only windows expert we have that I know of is regXboi 14:44:16 the permgen and memory sizes have been raised for the linux karaf... but I need someone who understands windows to do the same for the windows side 14:44:52 How about we use this standard for status: blocking issue-> red, testing feature alone , comparability and document not started ->yellow, testing on schedule to be finished before RC2, document type identified and started ->green 14:47:40 #info defense4all, sdni, ovsdb, pcmm, plugin2oc, sfc are current projects in yellow status, do we have reps from these project to report status 14:47:59 #info: AsafOron D4A 14:48:28 AsafOron: using the above standard, is D4A still yellow? 14:48:56 #info gzhao proposes using the following standard for status: blocking issue-> red, testing feature alone , comparability and document not started ->yellow, testing on schedule to be finished before RC2, document type identified and started ->green 14:49:23 #chair edwarnicke tbachman colindixon 14:49:23 Current chairs: colindixon edwarnicke gzhao tbachman 14:49:32 sorry forgot to do that 14:49:33 :) 14:49:54 D4A is green 14:49:58 AsafOron: thanks 14:50:30 xsited1: how about pcmm 14:51:01 asaforon: can you info that? 14:51:27 pound-info 14:51:28 ? 14:51:33 gzhao: what makes sfc yellow? as far as i know we are code freezed. and fully Karafed 14:52:01 #info D4A is green 14:52:14 edwarnicke: will you be able to answer status for SFC? they haven't sent status for M5, nor documentation. 14:52:31 tx tbachman 14:52:34 gzhao: I think goldavberg is trying to answer status right now :) 14:52:37 asaforon: np! 14:52:49 goldavberg: unless project contact report status change, otherwise it uses M5 status(last reported status) 14:52:51 * tbachman has managed to be on just one meeting atm… for once! ;) 14:52:51 gzhao: goldavberg is an SFC commiter :) 14:53:14 gzhao: so, you only accept these from the project contact? 14:53:23 (makes sense, just wanted to make sure we all understand) 14:53:45 tbachman: no, anyone can represent the project can report their status. 14:53:52 excuse me that I join late. Is it reporting each project's status? 14:53:53 gzhao: our weekly meeting starts in 7 minutes, so will probably discuss it then :) 14:54:03 ChristineH: can you # info in? 14:54:10 gzhao: Just pinged paulq... he's on his way 14:54:12 #info Christine for SNMP4SDN 14:54:18 ChristineH: thx! :) 14:54:20 i don't really know what our documentation or testing status is 14:54:25 gzhao: yellow: first draft of docs laid out, heading back to unit testing 14:54:33 goldavberg: ok, ask paulq to send me email with documentation types as well for SFC 14:54:39 xsited: want to # info that? 14:54:50 paulq is here 14:54:51 :) 14:54:52 gzhao: looks like Paul just joined us 14:55:04 * tbachman notes its good to have the status updates as info’s for meetbot meeting minutes 14:55:06 paulq: Please #info in :) 14:55:10 hey paulq ! :) 14:55:14 #info paulq for sfc 14:55:26 morning tbachman 14:55:28 :D 14:55:31 :) 14:55:52 paulq: hello, we need to know SFC is till in yellow status or not as well as what document types need to produce for Helium for SFC 14:56:18 #info xsited1 said PCMM remains in yellow 14:56:21 gzhao: just got back from travel..I'll check the status today and send email asap 14:56:21 #info packetcable status: yellow: first draft of docs laid out, heading back to unit testing, praying for longer RC cycle 14:56:35 xsited1: thanks 14:56:38 xsited: thx! 14:56:59 sfc group call is in 4 mins, I'll know more then :) 14:57:23 paulq: ok, could you email me after? 14:57:36 gzhao: yes! 14:57:38 paulq: +release 14:57:43 paulq: thanks a lot 14:58:05 any project has any blocking issues 14:58:23 is there any project hasn't started testing RC1 feature alone 14:59:26 is there any project hasn't started testing RC1 compatibility test? 14:59:39 snmp4sdn has started but has problem 14:59:44 gzhao: do you have the link to that spreadsheet? 14:59:45 VTN project has detected some bugs in controller. Bug 1491, 1866, and 1939. VTN project hopes that these bugs are fixed in Helium. 14:59:49 ChristineH: What is your issue? 14:59:58 hideyuki: I thought 1491 was resolved? 15:00:14 edwarnicke: I wrote some commands in Karaf for snmp4sdn, but the console said no such command 15:00:28 #info VTN project has detected some bugs in controller. Bug 1491, 1866, and 1939. VTN project hopes that these bugs are fixed in Helium 15:00:34 edwarnicke: No. 15:00:43 hideyuki: 1939 looks like it came in this morning? 15:00:59 #info snmp4sdn has started testing but has problem 15:01:07 hideyuki: Checking... 15:01:33 hideyuki: OK... let me see what's going on with 1491 :) 15:01:45 ChristineH: details about the problem? 15:01:45 hideyuki: I know michal_rehak is working on 1866 as we speak 15:01:46 hideyuki and edwarnicke - about 1491 - 15:01:54 abhijitkumbhare: yes? 15:01:55 ETA is tomorrow 15:02:11 #info gzhao asks if there are any projects that haven't started testing RC1 feature alone or with compatibility 15:02:23 hideyuki: Just got back that 1491 is being worked, ETA tomorrow 15:02:29 sorry - had to step away from the desk for a min 15:02:41 #info TTP hasn’t tested in RC1 yet, but expects it to be straightforward 15:02:42 #info Bug 1491 is partially fixed. But, as I wrote in Bugzilla, it is failed to change UDP port and ICMP type/code. 15:02:47 abhijitkumbhare: I am going to just stop answering for OFplugin now and let you do it :) You actually know what you are talking about :) 15:02:49 #info abhijitkumbhare says that a fix for BUG 1491 is ETA romorrow 15:02:58 hideyuki: thx! 15:03:00 #undo 15:03:00 Removing item from minutes: 15:03:07 (removed my redundant one) 15:03:23 edwarnicke: btw, do you have the bug number to fix the issue auto-release encoutered? 15:03:24 edwarnicke - I had asked michal the status today morning for 1491 :) 15:03:26 gzhao, edwarnicke: for example, there is a command 'snmp4sdn:ReadDB ' for karaf console, but the console shows 'No such command' (I can't remember exactly the error message, anyway) 15:03:41 #info edwarnicke says michal_rehak is working on 1866 15:04:18 ChristineH: feature:list -i shows it has been installed? 15:05:06 gzhao: defense4all has started testing... 15:05:29 gershon: thanks 15:06:20 just confirming with hideyuki & edwarnicke - https://bugs.opendaylight.org/show_bug.cgi?id=1759 is not blocking - right? michal has the fix - but its not merged because edwarnicke thinks its a little risky for Helium at this stage 15:06:44 abhijitkumbhare: I thought I *did* merge the fix for 1759... 15:06:56 abhijitkumbhare: I might have put it off till after RC1 though... ;) 15:07:00 abhijitkumbhare: I don't remember 15:07:02 OK 15:07:15 hideyuki: Can you confirm you see 1759 fixed in master? 15:07:22 On the bug it still says "Also we agreed with Ed that AD-SAL code should not be touched this late before helium." 15:07:27 Do we have a convention for putting the gerrits into the bug log if/when they’re closed? 15:07:48 OK - edwarnicke its merged 15:08:03 Good to knock off that bug :) 15:08:04 edwarnicke: Yes, I've confirmed that 1759 is fixed. (but, 1759 is fixed only for MD-SAL OF plugin. it is not fixed for AD-SAL OF plugin yet.) 15:08:37 #info hideyuki confirms that 1759 is fixed. (but, 1759 is fixed only for MD-SAL OF plugin. it is not fixed for AD-SAL OF plugin yet.) 15:08:53 tbachman: Thanks. I forgot #info. 15:08:58 :) 15:09:07 other other issues? 15:09:20 any other issues? 15:10:31 #topic documentation and other things 15:12:19 #info controller of plugin, ofjava, p2oc, sfc and integration need to tell gzhao their document types. 15:12:34 #undo 15:12:34 Removing item from minutes: 15:13:03 #info controller of plugin, ofjava, p2oc, sfc, ttp and integration need to tell gzhao their document types. 15:14:12 also, any preferred date time each project like to do their release view? 15:14:36 gzhao: I think we need to get confirmation from the TSC first on the times/dates? 15:14:43 gzhao: I think preferred times are going to have to be sussed out offline or at least by one-on-one calling people out 15:14:51 and I don’t think we have confirmation about times we can use for the TSC 15:14:53 yeah 15:15:26 tbachman: yes, I just want let people to select a time fits them the best 15:15:32 ah 15:16:02 gzhao: that’s not how it’s going to work 15:16:09 the TSC is likely to block out 2-3 hour-long slots 15:16:13 and you’ll get to pick one 15:16:23 or say which ones work best 15:16:26 tbachman: colindixon since we will schedule each project for 10 minutes, if no preference, phrobb and I will just assign them 15:17:38 however, project from different timezone, I hope they can give a range works better for them 15:19:01 colindixon: ok, we let TSC decide date time first, then ask for project if they want to do it at certain time. 15:19:12 Yea, my suggestion would be for George and I to produce a schedule (keeping in mind the Time Zones of the project contacts) and put it out there and if someone has a problem with the proposed time, we'll work to reschedule them as best we can. 15:19:28 phrobb: gzhao +1 15:20:20 #action gzhao and phrobb to produce a release review schedule (keeping in mind the Time Zones of the project contacts) and put it out there and if someone has a problem with the proposed time, we'll work to reschedule them as best we can. 15:20:27 Do we have anything to discuss for documentation and anything related to release? 15:20:33 For the TSC, as I mentioned on the email to the TSC, a quorum of TSC members is not needed for the Release Reviews but we will do our best to accommodate as many TSC member's participation as we can. 15:23:15 ok, will end meeting unless someone has objection 15:23:31 * tbachman watches gzhao raise gavel 15:23:50 gzhao: my laptop was down, now finally come back. 15:23:59 tbachman: haha , you do it better than me 15:24:03 lol 15:24:23 gzhao: you’re doing great! :) 15:24:39 ChristineH: no problem, are you able to pin point where is wrong? 15:24:53 gzhao: I haven't used 'feature:list -i', but I use 'feature:list|grep snmp', and I see odl-snmp4sdn-all and odl-snmp4sdn-snmp4sdn marked with 'x' 15:26:08 Actually a general question, when people encounter this issue, which ML is best for asking for help? 15:27:23 Truly, snmp4sdn needs expert's help for trouble shooting :) 15:28:04 ChristineH: could you put down the steps you did, error you saw and send to integration-dev, where probably knows most for Karaf testing AFAIK 15:28:07 ChristineH: are you able to see/use any commands? 15:28:33 (commands you’ve created) 15:29:42 ok 1 minute to go 15:30:11 3 15:30:38 tbachman: I created 5 (or 6) commands, well, I haven't tried each of them since the first command already fails (console said no such command). However, actually, in my local computer, one command can be executed and others are 'no such command' 15:31:22 tbachman: typo. In my local computer, one command was able to be executed and others are 'no such command' 15:31:43 ChristineH: is there any relationship to that command and an order in a list? 15:31:47 (e.g. first, last, etc.) 15:32:43 gzhao: you can end the meeting if you want — I can stay on and try to help out ChristineH 15:32:54 tbachman: I think no. These commands are independent. 15:33:16 * tbachman has to read up on how commands are added to karaf cli 15:33:37 tbachman: thanks 15:33:45 #endmeeting