14:30:07 <debrascott> #startmeeting Brahmaputra Daily Standup
14:30:07 <collabot`> Meeting started Wed Jan 20 14:30:07 2016 UTC.  The chair is debrascott. Information about MeetBot at http://wiki.debian.org/MeetBot.
14:30:07 <collabot`> Useful Commands: #action #agreed #help #info #idea #link #topic.
14:30:07 <collabot`> The meeting name has been set to 'brahmaputra_daily_standup'
14:30:14 <debrascott> #topic roll call
14:30:58 <debrascott> attendees please #  in
14:31:22 <narindergupta_AF> #info Narinder Gupta
14:31:24 <fdegir> #info Fatih Degirmenci
14:31:35 <anac1> #info Ana Cunha
14:32:02 <debrascott> #link agenda https://wiki.opnfv.org/releases/brahmaputra/minutes
14:32:07 <[2]JonasB> #info Jonas Bjurel
14:32:20 <joekidder> #info Joe Kidder
14:33:16 <debrascott> #topic Hardware / POD status
14:33:26 <bin_> #info Bin Hu
14:33:46 <debrascott> fdegir: what’s teh latest?
14:34:03 <morgan_orange> #info Morgan Richomme
14:34:08 <fdegir> #info Ericsson POD2 is back in operation thanks to Dan Smith and others
14:34:16 <fdegir> #info The rest is same as yesterday
14:34:43 <debrascott> Great!!
14:34:53 <debrascott> nice to see all up and going
14:35:28 <debrascott> #topic Scenarios status (Definition, Deployment status)
14:35:46 <debrascott> How is scenario deployment going?
14:35:48 <morgan_orange> am I wrong or do we have only 1 bm POD for apex?
14:36:13 <morgan_orange> we have 2 for all the installers (1 for stable branch and 1 for Master) but not sure for Apex
14:36:17 <fdegir> morgan_orange: yes, that's the status
14:36:23 <ashyoung> #info Ashlee Young
14:36:30 <fdegir> morgan_orange: intel pod2 is still under investigation
14:36:40 <fdegir> morgan_orange: last I heard was trozet was going to give another try on it
14:37:16 <debrascott> #link https://wiki.opnfv.org/brahmaputra_testing_page#candidate_scenarios
14:37:20 <morgan_orange> fdegir: ok thanks 1 stable POD for tests and 1 Master POD for scenario testing is good to have...
14:37:36 <fdegir> here is the chat between trozet and jmorgan1
14:37:37 <fdegir> 19:01 <jmorgan1> trozet: ping - any update on Intel POD 2?
14:37:37 <fdegir> 19:02 <jmorgan1> trozet: checking in to make sure your issues were resolved
14:37:37 <fdegir> 19:32 <trozet> jmorgan1: hi
14:37:37 <fdegir> 19:32 <trozet> jmorgan1: we havent tried it yet, when i get a chance i will do a deployment there
14:37:40 <fdegir> sorry for pasting
14:38:38 <debrascott> are we able to map all scenarios to pods at this time?
14:38:59 <debrascott> which team is responsible for this, pharos??
14:39:10 <fdegir> debrascott: we map branches to PODs
14:39:27 <fdegir> debrascott: as listed on wiki
14:39:29 <fdegir> debrascott: https://wiki.opnfv.org/pharos_rls_b_labs#status_of_production_ci_resources_for_release_b
14:40:00 <fdegir> debrascott: stable -> branch stable/brahmaputra
14:40:06 <fdegir> debrascott: latest -> branch master
14:40:17 <debrascott> OK, so how do we ensure scenarios are supported?
14:40:52 <fdegir> debrascott: by deploying them first
14:41:01 <fdegir> debrascott: and then running tests on deployed scenario
14:41:18 <debrascott> I assume they can’t all be running at same time, is that true?
14:41:23 <fdegir> debrascott: that's right
14:41:26 <morgan_orange> the scenario are frozen now, no? so the reference is the jenkins page? 10 scenarios on Fuel, 5 on Apex, 4 on joid and 3 on Compass...
14:41:46 <debrascott> Yes, scenarios are frozen, it’s deployment that should be finishing
14:41:52 <morgan_orange> so if we consider our first view to have 4 successfull run to validate staibility, if we perform all the Fuel scenario we need almost 7 days
14:41:52 <fdegir> I think we need to follow what we did
14:42:15 <fdegir> candidate scenarios, realized scenarios (=have jenkins job), working scenarios
14:42:22 <fdegir> so we're in between 2 and 3
14:42:32 <fdegir> this needs to be tracked as well
14:42:49 <debrascott> OK that makes sense, just need to make sure there is schedule for each then?
14:42:55 <fdegir> some work (arno scenario for example)
14:43:02 <fdegir> others are either in development or in verification phase
14:43:21 <fdegir> the idea is to run working scenarios during night time (?)
14:43:36 <fdegir> and run the scenarios in progress during day time to see what is broken
14:43:38 <debrascott> whose night :)
14:43:49 <fdegir> that's the (?)
14:44:29 <fdegir> I think we must list which scenarios is deployable right now
14:44:36 <debrascott> and test is troubleshooting 1st batch of scenarios now
14:44:38 <fdegir> and let test teams to focus on them more perhaps
14:45:00 <anac1> and give us time and POD to troubleshoot
14:45:05 <debrascott> OK good, shall we move on to test then?
14:45:07 <fdegir> so they don't get false results and save some time from none-working scenarios
14:45:17 <morgan_orange> not sure it is fully up to date but we have already some indication https://wiki.opnfv.org/tempest_brahmaputra_page
14:45:22 <debrascott> of course
14:45:43 <fdegir> anac1: you ask tricky questions
14:46:08 <anac1> fdegir: someone has to
14:46:19 <debrascott> morgan_orange: good to see
14:46:33 <morgan_orange> yes testing scenario is 1 things, troubleshooting is also another thing
14:46:33 <fdegir> anac1: and I generally do not give good news you know
14:46:43 <morgan_orange> it is not possible to troubleshoot from jenkins logs...
14:47:24 <anac1> fdegir: i know
14:47:37 <fdegir> morgan_orange: that's one of the reasons why we have 2 PODs
14:47:43 <debrascott> Let’s move on to test status then
14:47:43 <morgan_orange> precisely...
14:47:46 <fdegir> morgan_orange: I think we can talk about this outside the meteing
14:47:53 <debrascott> #topic Test Status
14:47:56 <fdegir> morgan_orange: and come back to a workable plan
14:48:16 <debrascott> morgan_orange: latest on functest?
14:48:25 <morgan_orange> #info Functest all tests failed due to problem with pip (we should not the only ones impacted...)
14:48:41 <morgan_orange> installation of rally is not possible...but it is not Rally's fault
14:48:47 <morgan_orange> update of pip last night
14:48:57 <morgan_orange> discussion in progress on OpenStack
14:49:01 <debrascott> what is pip?
14:49:02 <morgan_orange> community
14:49:39 <morgan_orange> A python packet management solution
14:49:45 <debrascott> thanks
14:49:56 <morgan_orange> https://en.wikipedia.org/wiki/Pip_(package_manager)
14:50:28 <morgan_orange> before this, we updated the different tables
14:50:36 <morgan_orange> https://wiki.opnfv.org/vping_brahmaputra_page
14:50:48 <debrascott> Are they still finding root cause or are they attempting to fix ?
14:51:01 <debrascott> OpenStack I mean
14:52:04 <morgan_orange> do not know
14:52:18 <debrascott> OK. Let’s move on.
14:52:27 <debrascott> anac: how is Yardstick today?
14:52:29 <anac1> #info yardstick - troubleshooting ODL and ONOS scenarios
14:52:51 <debrascott> any progress made?
14:53:01 <debrascott> did you get help with SSH issues?
14:53:20 <anac1> as with SW development, find one fault and come to the next
14:53:35 <anac1> yes, we continue
14:54:00 <morgan_orange> anac1: not facing issue during python lib installation in your container?
14:54:08 <debrascott> shall we use snowball analogy or layers of onion? :)
14:54:09 <anac1> no
14:54:22 <anac1> sorry, i meant no to morgan's question
14:54:56 <anac1> debrascott: we continue debugging
14:55:21 <debrascott> OK, do you need help on anything else? Be sure to ask community every time
14:55:29 <anac1> thanks, will do
14:56:00 <debrascott> Shall we move on, only 5 min left?
14:56:15 <debrascott> #Topic installer status
14:56:38 <debrascott> JonasB: how is Fuel looking?
14:57:14 <[2]JonasB> #info still working on rebasing Fuel plugins
14:57:57 <[2]JonasB> #info We will start running masted scenarios on Ericsson POD 2 now that it is up
14:58:24 <[2]JonasB> #info Working on problems with master build
14:58:53 <[2]JonasB> #info Some issues with upstream yet
14:58:59 <[2]JonasB> End
14:59:07 <debrascott> thanks
14:59:16 <debrascott> keep us informed!
14:59:35 <debrascott> narindergupta: JOID?
14:59:40 <[2]JonasB> debrascott: I will
14:59:48 <narindergupta> #info intel pod6 passed with working scario
15:00:14 <narindergupta> #info we have working B erlease
15:00:21 <debrascott> claps and hurrahs!
15:00:22 <narindergupta> #info still working on documentation
15:00:38 <narindergupta> #info and debugging orange pod2
15:00:50 <anac1> have to leave for another meeting
15:01:00 <narindergupta> #info also found an connetivity issue on intel pod5 where node 6 is not connected as expected
15:01:10 <narindergupta> #end
15:01:12 <debrascott> Yes, top of the hour.
15:01:38 <debrascott> Again, everyone please send updated project status if we didn’t get to you today.
15:01:46 <debrascott> Thanks for attending!
15:01:54 <debrascott> #endmeeting