14:30:31 <debrascott> #startmeeting Brahmaputra Daily Standup
14:30:31 <collabot> Meeting started Thu Feb 18 14:30:31 2016 UTC.  The chair is debrascott. Information about MeetBot at http://wiki.debian.org/MeetBot.
14:30:31 <collabot> Useful Commands: #action #agreed #help #info #idea #link #topic.
14:30:31 <collabot> The meeting name has been set to 'brahmaputra_daily_standup'
14:30:40 <debrascott> #topic roll call
14:30:47 <debrascott> #info same agenda as yesterday
14:30:56 <joekidder> #info Joe Kidder
14:31:07 <narindergupta> #info Narinder Gupta
14:31:28 <radez> #info Dan Radez
14:31:38 <debrascott> #link https://wiki.opnfv.org/releases/brahmaputra/minutes
14:31:38 <anac1> #info Ana Cunha
14:31:40 <jose_lausuch> #info Jose Lausuch
14:31:41 <trevor_intel1> #info Trevor Cooper
14:32:49 <debrascott> The weekly technical meeting is still in progress so we may be light on attendence except for those who can multi-task
14:33:03 <debrascott> #topic test status
14:33:16 <debrascott> jose_lausuch: how is functest today?
14:33:23 <jose_lausuch> hi
14:33:27 <jose_lausuch> #info not much progress since yesterday...
14:33:34 <jose_lausuch> #info there was a discussion yesterday during pharos meeting about taking orange-pod2 as reference for results for JOID.. we will continue trobuleshooting the intel pods for the momment, running the 3 target scenarios for JOID and see what happens...
14:33:58 <[1]JonasB> #info Jonas Bjurel
14:34:22 <narindergupta> jose_lausuch: run times are still high on intel labs
14:34:36 <jose_lausuch> #info functest on apex looks more stable now, at least we get a blue ball when executing the functest jjob (which doesnt mean everything works)
14:34:53 <jose_lausuch> #info still trobuleshooting the vping issue with apex+onos scenario
14:35:03 <jose_lausuch> narindergupta: I know, 6 hours last one...
14:35:06 <jose_lausuch> not acceptable
14:35:17 <jose_lausuch> let's see if we fix it with the SSDs...
14:35:18 <radez> #info worked with bob on ONOS Vping lastnight, we have a root cause now
14:35:19 <narindergupta> jose_lausuch: yeah
14:35:37 <narindergupta> jose_lausuch: with SSD it is still high
14:35:47 <debrascott> #info reminder that we have agreed that scenarios working at end of business Pacific time on Friday will be the final release candidates for Brahmaputra 1
14:35:48 <trevor_intel1> #info SSDs were tried but failed to fix it
14:36:14 <jose_lausuch> trevor_intel1 when was that tried?
14:36:17 <radez> #info Apex ONOS and ODL L3 Functest were 90+%  past two runs
14:36:34 <jose_lausuch> radez: I need to update this then https://wiki.opnfv.org/functextnexttaks :)
14:36:43 <trevor_intel1> jose_lausuch: yesterday
14:36:56 <radez> jose_lausuch: yes please :)
14:37:28 <jose_lausuch> trevor_intel1: so, we had deployments using those SSD and still we had long runtimes?
14:37:37 <jose_lausuch> did narindergupta or you checked that?
14:37:39 <narindergupta> jose_lausuch: it was tried yesterday with SSD. yes
14:37:44 <jose_lausuch> ok...
14:38:09 <jose_lausuch> let's take this offline in pharos or joid channel
14:38:26 <narindergupta> jose_lausuch: yes i did and last run was 5 hr 46 min.
14:38:32 <narindergupta> jose_lausuch: sure
14:38:34 <trevor_intel1> I think fair to say that tor Joid to make the deadline would have to accept results on Orange POD
14:39:02 <trevor_intel1> No more slack for debugging
14:39:04 <jose_lausuch> trevor_intel1: that is ok for me, but have only old-l2 results on that pod
14:39:40 <jose_lausuch> we might need to merge this? https://gerrit.opnfv.org/gerrit/#/c/9871/5
14:39:57 <narindergupta> jose_lausuch: yesterday i ran two more times both nosdn and onos
14:40:09 <narindergupta> jose_lausuch: we have more runs now
14:40:24 <jose_lausuch> narindergupta: ok, we need at least 4 to judge something
14:40:43 <narindergupta> jose_lausuch: we have four nosdn, and three onos
14:41:00 <narindergupta> jose_lausuch: but new schedule will help over the weekend
14:41:22 <jose_lausuch> https://build.opnfv.org/ci/view/functest/job/functest-joid-orange-pod2-daily-master/
14:41:24 <narindergupta> jose_lausuch: and i am planning to run manually until then
14:41:28 <jose_lausuch> ok
14:41:44 <jose_lausuch> debrascott: is the friday end of business day already settled?
14:41:55 <jose_lausuch> what about this cases where running over the weekend can help?
14:42:20 <radez> It would help Apex to be able to run over the weekend,
14:42:28 <radez> our daily is taking 12 hours
14:42:34 <radez> and we only have 2 runs so it will be tight
14:42:46 <debrascott> jose_lausuch: this was proposed and there have been no objections. I have not had response from Chris for a few days. Does anyone know if he is traveling? the primary impact is for documentation to get completed & reviewed
14:43:09 <jose_lausuch> he is flying this evening (europe time)
14:43:59 <debrascott> OK so this late evening US time I may be able to get his attention to verify
14:44:25 <[1]JonasB> Will anyone document results over the weekend, if not I dont see why to have Fri as deadline?
14:44:50 <debrascott> anac1: ^^
14:44:54 <jose_lausuch> I can document them sunday evening/monday morning
14:45:13 <anac1> debrascott: yes?
14:45:55 <debrascott> anac1: will anyone be documenting results over this weekend? request is to delay freeze on scenario troubleshooting
14:46:05 <anac1> i'm fine to change the deadline
14:46:22 <anac1> what's the new proposal?
14:46:46 <debrascott> OK if all agree then I propose Sunday 6pm Pacific
14:47:12 <debrascott> anyone disagree?
14:47:53 <trevor_intel1> debrascott: What about other documentation ... I am still working on Pharos docs :(
14:47:54 <jose_lausuch> nop
14:48:14 <trevor_intel1> debrascott: not finding time I need
14:48:53 <jose_lausuch> from Functest, what I can tell is that documenting the results will not be finished before we check the "up to date" results on Sunday/Monday
14:49:21 <debrascott> trevor_intel1: the freeze is for troubleshooting scenarios, does not stop work continuing on documentation
14:50:01 <trevor_intel1> debrascott: ok thx
14:50:15 <debrascott> documentation will continue development & reviews until Wednesday
14:50:25 <debrascott> Thursday stream will be tagged for release
14:51:20 <debrascott> everyone comfortable with moving the scenario troubleshooting freeze to Sunday?
14:52:04 <[1]JonasB> debrascott: The once that should really answer are the feature ptl's
14:52:32 <debrascott> JonasB: OK I will send something out to the mail list
14:52:36 <radez> Apex: sunday +1
14:52:36 <[1]JonasB> Its the feature teams that need to troubleshoot their features.
14:52:50 <[1]JonasB> Fuel: sunday +1
14:53:01 <anac1> Yardstick: sunday +1
14:53:39 <jose_lausuch> Functest: sunday +1
14:54:13 <ChrisPriceAB> #info Chris Price (at the airport only on for a bit)
14:54:34 <debrascott> ChrisPriceAB: hello, some questions for you
14:54:38 <narindergupta> joid sunday +1
14:55:55 <debrascott> chrisPriceAB: proposal is to freeze troubleshooting scenarios on Sunday 6pm Pacific in order to allow time for documentation to finalize and get reviews until Wednesday and then tag stream for release on Thursday
14:56:18 <debrascott> ChrisPriceAB: from documentation perspective do you feel comfortable with that timing?
14:56:25 <ChrisPriceAB> Yes I saw that.  Looks good.
14:56:52 <debrascott> ChrisPriceAB: do you have any updates for us on documentation?
14:57:15 <ChrisPriceAB> ongoing.  Toolchain in place, editorial, structure, release content improving daily.
14:57:35 <ChrisPriceAB> Missing some content, will chase the stragglers.
14:57:56 <debrascott> ChrisPriceAB: are feature projects getting docs done
14:58:06 <debrascott> ChrisPriceAB: you beat me to the punch
14:58:12 <ChrisPriceAB> most, some stragglers.
14:58:44 <debrascott> ChrisPriceAB: send me a list of stragglers and I will also chase them down
14:59:10 <ChrisPriceAB> shall do, once I land in Sweden.
14:59:24 <debrascott> #Action: Debra will send message to lists regarding scenario freeze
14:59:46 <debrascott> OK- we’re at the top of the hour again.
15:00:07 <debrascott> Installers, please send me a short update for the status update
15:00:21 <debrascott> #endmeeting