14:30:06 <debrascott> #startmeeting Brahmaputra Daily Standup
14:30:06 <collabot> Meeting started Wed Feb  3 14:30:06 2016 UTC.  The chair is debrascott. Information about MeetBot at http://wiki.debian.org/MeetBot.
14:30:06 <collabot> Useful Commands: #action #agreed #help #info #idea #link #topic.
14:30:06 <collabot> The meeting name has been set to 'brahmaputra_daily_standup'
14:30:13 <debrascott> #topic roll call
14:30:17 <ashyoung> #info Ashlee Young
14:30:21 <morgan_orange> #info Morgan Richomme
14:30:26 <anac1> #info Ana Cunha
14:30:41 <JonasB> #info Jonas Bjurel
14:31:47 <narindergupta> #info Narinder Gupta
14:32:04 <debrascott> #llink agenda https://wiki.opnfv.org/releases/brahmaputra/minutes
14:32:19 <debrascott> #topic test status
14:32:34 <debrascott> Morgan_orange: functest?
14:32:36 <joekidder> #info Joe Kidder
14:32:50 <morgan_orange> #info functest: vPing/SSH troubleshooting => seems OK now on Fuel and Compass (was already OK on apex and joid)
14:32:50 <radez> #info Dan Radez
14:32:56 <morgan_orange> #info functest: several scenario succesfully run on fuel this morning..
14:33:04 <morgan_orange> #info functest: vIMS troublseshooting in progress
14:33:25 <morgan_orange> #info functest: promise soon available in Test DB
14:33:40 <bin_> #info Bin Hu
14:33:42 <morgan_orange> #info functest: sdnvpn and ovno remaining companion projects to deal with
14:33:58 <debrascott> morgan_orange: what resolved the issue with vPing/SSH?
14:34:01 <ChrisPriceAB> #info Chris Price
14:34:16 <morgan_orange> on fuel it was the creation of a dedicated security group
14:35:04 <morgan_orange> on compass more config PoD adapation I think
14:35:05 <ashyoung> that was needed or causing the issue?
14:35:09 <morgan_orange> and timeout increase
14:35:31 <morgan_orange> for fuel that was needed as port 22 was not allowed
14:35:48 <debrascott> morgan_orange: cool
14:36:15 <jose_lausuch> the vping script now creates its own security group with port 22 open, it didnt use to work on fuel because of that, maybe we it is workiong on more installers now thanks to that change
14:36:27 <morgan_orange> so we have several scenarios that turned green since this morning, and hopefully some will follow (need scenario run to confirm)
14:36:43 <debrascott> morgan_orange: mark that one down to learning setup, please document on wiki
14:37:08 <ashyoung> that's awesome news
14:37:10 <debrascott> morgan_orange: very good news!! claps and applause
14:38:01 <debrascott> morgan_orange: any scenarios still at risk now?
14:38:06 <jose_lausuch> sounds good, but green balls != all-test-passed :)
14:38:26 <morgan_orange> vIMS due to its complexity but assuming that vPings are now OK, it should follow
14:38:39 <morgan_orange> ovno because we did not see one run for the moment
14:39:14 <debrascott> morgan_orange: woohoo! so much better than yesterday prognosis!
14:39:29 <debrascott> morgan_orange: anything else?
14:39:30 <ChrisPriceAB> QQ for morgan_orange
14:39:50 <ChrisPriceAB> I noticed that this page has become stale:  https://build.opnfv.org/ci/view/OPNFV%20Platform%20CI%20-%20Alternative%20View/
14:40:17 <ChrisPriceAB> Was checking in with the teams and the page does not reflect the actual, is this easy to resove as it makes a good reference.
14:40:55 <morgan_orange> it is a good question for releng :) it is true that today we have to go to the installer page to follow the run
14:41:04 <morgan_orange> I can take the point to see why it is not up to date
14:41:20 <morgan_orange> I think KF POD2 is down so we user Ericsson 2 for Stable
14:41:27 <morgan_orange> it is temporary and not reflected in the page
14:41:43 <morgan_orange> and Apex jobs are not following teh same rules than the other installers
14:42:08 <JonasB> LF POD2 is coming up, we will have that for Stable from tonight!
14:42:17 <narindergupta> also there is hardware issue in intel pod5 and pod6 where bmc is not responding is causing joid jobs to fail
14:42:45 <ChrisPriceAB> thanks Morgan.  If the link is not the best way to know it could be good to establish a new method for status.
14:42:54 <debrascott> narindergupta: is there a Jira ticket you can reference for that pod issue?
14:43:19 <narindergupta> debrascott: no i have not opened one. Will do it now.
14:43:22 * ChrisPriceAB stepping away for a bit
14:43:32 <debrascott> narindergupta: thank you
14:43:36 <morgan_orange> ChrisPriceAB: you can use the dashboard..http://testresults.opnfv.org/proto/index2.html
14:44:01 <morgan_orange> even if it is a B plan it reflects the real results pushed by the scenario into the Test result DB
14:44:22 <morgan_orange> http://testresults.opnfv.org/proto/index-pod.html
14:44:26 <debrascott> morgan_orange: the charts still don’t render for me- using Safari browser
14:44:56 <morgan_orange> workinf on FF and Chromium
14:45:19 <debrascott> morgan_orange: I’ll load ff and see if it works then
14:45:36 <debrascott> Ok, let’s move on to yardstick
14:45:46 <anac1> #info odl scenario tested succesfully with workaround patch from yardstick, environent: Compass ODL Li sr2
14:46:09 <anac1> #info many thanks to yardstick kubi, chenshuai and jorgen
14:46:18 <debrascott> anac1: awesome, claps & cheers!
14:46:19 <ashyoung> that's great news too
14:46:25 <anac1> #info this is a workaround and doen NOT solve the problem
14:46:44 <ashyoung> Wow! Totally different day than yesterday
14:46:51 <debrascott> anac1: but it means you narrow in on the problem!
14:46:55 <ashyoung> oh
14:46:56 <anac1> #info we'll continue the troubleshooting with help from cisco & redhat
14:47:17 <debrascott> anac1: do you have ODL person helping now too?
14:47:28 <ashyoung> anac1: We have an entire team willing to help too
14:47:39 <anac1> debrascott: i have the right people and I want to get to the bottom of this issue
14:47:49 <narindergupta> debrascott: https://jira.opnfv.org/browse/PHAROS-101
14:47:51 <anac1> i don't believe in workarounds in log term
14:48:01 <anac1> thank ashyoung, much appreciated
14:48:14 <anac1> your colleagues in china are a great help
14:48:23 <debrascott> anac1: great, just want to know what to tell Phil Robb re: help needed
14:49:04 <debrascott> anac1: good to know you have what you need to move forward on this
14:49:23 <anac1> debrascott: i have contacts from frank and dave, plus ash's team to reinforce
14:49:55 <debrascott> anac1: status on other scenarios?
14:50:33 <anac1> yardstick continue the sfc work
14:50:45 <anac1> and fuel8 uplift
14:51:50 <debrascott> anac1: percent done on fuel 8 uplift?
14:52:05 <anac1> are you serious ?
14:52:33 <debrascott> anac1: just want a guess as to how much more work there is to be done, not exact
14:52:48 <debrascott> anac1: are you closer to 20% done or 60% done?
14:53:56 <debrascott> anac1: or is it purely troubleshooting?
14:55:12 <ChrisPriceAB> Hi debrascott, I understand the deployments are running.  I assume we don't know the answer right now.
14:55:54 <debrascott> chrisPriceAB: ok, just wanting to get a guage
14:56:18 <debrascott> Let’s move on to docs then, we’ll come back to installers via email
14:56:40 <debrascott> ChrisPriceAB: any updates on doc status?
14:58:26 <debrascott> seems we lost ChrisPriceAB: attention again.
14:58:43 <debrascott> JonasB: Fuel status?
14:59:11 <ChrisPriceAB> docs are coming along.  started editorials waiting on the patches to come in from content providing projects
14:59:24 <ChrisPriceAB> fine tuning tools.
14:59:39 <ChrisPriceAB> need to update the wiki tonight
15:00:25 <debrascott> ChrisPriceAB: thanks, overall where you want to be with docs?
15:00:41 <debrascott> or should I say “expected” to be?
15:01:34 <debrascott> ok, top of the hour.
15:01:40 <debrascott> thanks everyone for attending
15:01:52 <ChrisPriceAB> late, no time for testing
15:01:56 <ashyoung> do we need any more resource-based help?
15:02:18 <ashyoung> Sounds like we made great progress since yesterday
15:02:24 <debrascott> will look for more updates via email if I didn’t get to you
15:02:32 <debrascott> ashyoung: +1
15:02:39 <debrascott> #endmeeting