15:02:49 <dmcbride> #startmeeting OPNFV Colorado release daily
15:02:49 <collabot> Meeting started Mon Sep 19 15:02:49 2016 UTC.  The chair is dmcbride. Information about MeetBot at http://wiki.debian.org/MeetBot.
15:02:49 <collabot> Useful Commands: #action #agreed #help #info #idea #link #topic.
15:02:49 <collabot> The meeting name has been set to 'opnfv_colorado_release_daily'
15:02:56 <dmcbride> #info roll call
15:03:00 <dmcbride> #topic roll call
15:03:07 <morgan_functest> #info Morgan Richomme (Functest)
15:03:09 <dmcbride> #info David McBride
15:03:11 <ulik> #info Uli Kleber
15:03:11 <georgk> #info Georg Kunz
15:03:17 <kubi001> #info kubi(Yardstick)
15:03:18 <JonasB> #info Jonas Bjurel
15:03:25 <sofiawallin> #info Sofia Wallin
15:03:26 <ChrisPriceAB> #info Chris Price
15:04:33 <jmorgan1> #info Jack Morgan (pharos)
15:04:54 <frankbrockners> #info Frank Brockners
15:05:04 <dmcbride> ok - does anyone have any hot topics they'd like to bring up immediately?
15:05:36 <dmcbride> #topic functest and yardstick results
15:06:07 <dmcbride> I was looking at Yardstick results this morning and they still seem not great
15:06:07 <narindergupta> #info Narinder Gupta
15:06:37 <dmcbride> kubi001: are we confident about the status of Yardstick now?
15:06:59 <dmcbride> kubi001: ping
15:07:03 <kubi001> dmcbride: do you mean the reporting ?
15:07:09 <dmcbride> overall
15:07:43 <dmcbride> kubi001: any known issues that might account for the somewhat poor results we are seeing?
15:08:07 <dmcbride> trozet: ping
15:08:22 <trozet> dmcbride: pong
15:08:53 <kubi001> dmcbride: https://wiki.opnfv.org/display/yardstick/Yardstick+Colorado+CI+Status
15:09:36 <kubi001> dmcbride: we pionted out the passed scenario and give the error type of failure scenario
15:09:47 <dmcbride> trozet: we have a few scenarios that are struggling on Apex with functest
15:10:01 <dmcbride> fdio, sfc, bgpvpn
15:10:07 <trozet> dmcbride: i see nosdn and odl l2, passed everything yesterday, has that been consistent?
15:10:25 <dmcbride> I think so, I sent an email to Brady but haven't heard back
15:10:46 <trozet> dmcbride: bgpvpn I've asked Nikolas to look into
15:11:02 <dmcbride> ok - good
15:11:32 <trozet> dmcbride: we are fixing fdio, and aware of those bugs.  For SFC - I'm not sure what hte problem is need to look at htat one
15:12:27 <morgan_functest> trozet: onos & onos-sfc scenario are FAIL on apex (they used to be and used to be OK with Brahmaputra), I contacted onosfw PTL but did not get feedback
15:12:57 <trozet> morgan_functest: yeah I contacted ONOS folks (Bob) and told him about the failures, he said they pass for him in his setup
15:13:15 <trozet> morgan_functest: I don't think anything has been done since then
15:13:28 <dmcbride> Bob?
15:13:44 <trozet> dmcbride: yeah he did all of the integration of ONOS into Apex
15:13:53 <dmcbride> last name?
15:14:34 <trozet> dmcbride: bob.zh@huawei.com
15:14:48 <dmcbride> ok - thanks
15:15:28 <dmcbride> Fuel and JOID seem like they're in good shape with functest
15:15:35 <trozet> dmcbride: I'll look into the SFC one today and work on FDIO as well
15:15:41 <bryan_att> #info Bryan Sullivan
15:15:43 <narindergupta> dmcbride, yes we have all scenario passing
15:15:48 <dmcbride> ok - thanks
15:15:51 <kubi001> dmcbride: For Yardstick, Compass and JOID also looks good
15:16:00 <narindergupta> dmcbride, including LXD
15:16:17 <narindergupta> kubi001, yardstick LXD test cases are failing
15:16:24 <dmcbride> see, Tim, you leave for a week and everything goes to hell ;-)
15:17:08 <dmcbride> narindergupta: does that mean that you're using Boron?
15:17:10 <kubi001> narinder`: yes, only LXD fail in JOID, and we mark the knonw issue in the Release Notes.
15:17:29 <narindergupta> kubi001, ok sounds good to me
15:17:33 <trozet> dmcbride: haha
15:17:46 <trozet> dmcbride: time to go back until after the release :)
15:18:16 <JonasB> As far as I understand, Fuel is passing almost all scenarios with Yardstick.
15:18:30 <kubi001> JonasB: yes, you are right
15:18:43 <dmcbride> trozet: have you had a chance to update the intent to release columns in the scenario status page?
15:18:54 <kubi001> JonasB: ovs scenario need wait more times success
15:19:06 <morgan_functest> I remember dmcbride was a bit afraid of European summer vacations...it seems that vacations are not only European...:)
15:19:11 <trozet> dmcbride: No, not sure what that is, let me check
15:19:22 <kubi001> JonasB: other scenarios in fuel looks good
15:19:32 <dmcbride> trozet: see my email from Friday
15:19:49 <trozet> dmcbride: ok there are 450 in front of that one
15:19:52 <trozet> :)
15:20:12 <dmcbride> trozet: mine are clearly most important :)
15:20:20 <trozet> haha true
15:21:10 <dmcbride> fdegir: any issues related to infra that we should be aware of wrt Col 1.0 release?
15:21:59 <dmcbride> jmorgan1: can you answer that? ^
15:22:08 <JonasB> dmcbride: Can we spend some time on documentation, Sofia is desperatly tryng to finish the docs. But the quality of the input is not up to the standards one could have expected!!!!
15:22:49 <JonasB> dmcbride: I have not seen any scenario release notes yet.
15:22:56 <dmcbride> JonasB: sure - can you be more specific?  Missing? Incomplete? Poorly written? Inaccurate?
15:23:19 <JonasB> dmcbride: Like empty documents, etc.
15:24:12 <jmorgan1> dmcbride: none that i know of
15:24:43 <dmcbride> ok - we have a few scenario owners online
15:24:49 <jmorgan1> JonasB: you are looking for a template for scenrios?
15:25:12 <dmcbride> trozet: scenario documentation?
15:25:18 <dmcbride> frankbrockners: scenario documentation?
15:25:24 <jmorgan1> JonasB: scenario release notes rather
15:25:26 <dmcbride> wei_: scenario documentation?
15:25:34 <trozet> dmcbride: what do I need to do?
15:25:46 <frankbrockners> dmcbride: this is done
15:25:52 <wei_> almost done
15:25:58 <dmcbride> trozet: see Sofia's email on scenario release notes
15:26:04 <trozet> hehe
15:26:05 <wei_> before BOC today
15:26:15 <dmcbride> narindergupta: scenario release notes?
15:26:33 <frankbrockners> dmcbride: http://artifacts.opnfv.org/fds/colorado/scenarios_os-odl_l2-fdio-noha/index.html
15:26:53 <dmcbride> thanks, frankbrockners
15:27:44 <sofiawallin> we currently have 7 scenario descriptions included in the release documentation
15:27:56 <trozet> morgan_functest: what is the status of ODL_L3?
15:27:58 <JonasB> I thought we agreed that we would have scenario release notes at last weeks release meeting, didnt we ?
15:28:11 <sofiawallin> not sure about associated release notes for these...
15:28:13 <trozet> morgan_functest: i see tempest failing...did you ever disable those test cases with floating ip or no?
15:28:14 <dmcbride> JonasB: yes, we did
15:28:26 <frankbrockners> dmcbride - scenario release notes are in as well - https://gerrit.opnfv.org/gerrit/#/c/21293/ - just need to be merged - trozet - could you pull the trigger?
15:28:50 * trozet looks
15:28:50 <morgan_functest> trozet: ODL_l3 status is the same for all the installer, Tempest fails due to ODL bug, we let it failing and document it in the release note
15:28:54 <dmcbride> Ruan888: scenario release notes for moon scenario?
15:28:59 <trozet> morgan_functest: good.  Thanks
15:29:17 <sofiawallin> dmcbride: 24 projects have added their document links https://wiki.opnfv.org/display/DOC/Colorado+documentation
15:29:24 <dmcbride> timirnich: scenario release notes?
15:29:45 <trozet> frankbrockners: i think Feng just fixed the autodetect enic
15:30:20 <dmcbride> Ruan888: ping
15:30:22 <narindergupta> dmcbride, when will do in scenario release notes and how will it be different for different installers. Also is there any template for the scenario release notes?
15:30:24 <dmcbride> timirnich: ping
15:30:58 <dmcbride> narindergupta: scenario release notes should be done by today
15:31:04 <frankbrockners> trozet - ok will amend the patch
15:31:17 <trozet> frankbrockners: ok then will merge
15:31:19 <dmcbride> narindergupta: scenario release notes go with the installer
15:31:29 <narindergupta> dmcbride, is there any template?
15:32:05 <dmcbride> narindergupta: see email from sofiawallin on scenario release notes
15:32:10 <morgan_functest> dmcbride: hmmm scenario release note goes with scenario owner...for generic scenarios usually the owner are installer team but they cannot be responsible of all the scenarios...
15:32:53 <trozet> morgan_functest: so is it correct to say in Apex, odl l2, nosdn and odl l3 are all good now
15:32:55 <trozet> ?
15:33:11 <dmcbride> morgan_functest: scenario release notes are organized by installer type, but the scenario owner is responsible for writing them
15:33:12 <morgan_functest> trozet: yes
15:33:13 <trozet> morgan_functest: can you link me that functest status page with the check marks again?
15:34:01 <morgan_functest> trozet: http://testresults.opnfv.org/reporting/functest/release/colorado/index-status-apex.html
15:34:07 <trozet> morgan_functest: ty
15:34:07 <narindergupta> dmcbride, may be in Artur's Inbox i am not seeing it
15:34:10 <morgan_functest> we put gauge to relax scenario owners...
15:34:22 <trozet> morgan_functest: haha no more red X and a meter
15:34:26 <trozet> morgan_functest: i like it :)
15:35:18 <ChrisPriceAB> +1 :)
15:36:52 <dmcbride> agree - the gauge is cool
15:37:25 <frankbrockners> trozet - updated https://gerrit.opnfv.org/gerrit/#/c/21293/ - nic autodetect issue removed
15:38:32 <dmcbride> narindergupta: sofiawallin will forward her email about release notes to you
15:39:37 <narindergupta> dmcbride, ok will look into it
15:39:48 <dmcbride> JonasB: anything else wrt documentation?
15:40:34 <dmcbride> bryan_att: any issues you'd like to raise?
15:40:51 <morgan_functest> sofiawallin: seems that all links are not working on https://wiki.opnfv.org/display/DOC/Colorado+documentation and repo paths are different <project>/colorado/docs, <project>, <project>/colorado
15:40:57 <bryan_att> not that I can bring mind right now
15:41:49 <morgan_functest> problem with Arno analyzed by fdegir (heritage from Arno and its label on master branch)
15:42:21 <morgan_functest> doc from projects involved in Arno impacted
15:43:23 <bryan_att> sofiawallin: It's unclear what the URLs should be, should they have the /docs/ path, etc
15:44:26 <bryan_att> sofiawallin: I put the /docs/ path in the copper URLs as those are what is generated when I edit comething
15:47:43 <dmcbride> ok - thanks for joining
15:48:09 <dmcbride> I'll be online most of the day if anyone has any questions, comments, threats, accusations, etc.
15:48:22 <bryan_att> sofiawallin: maybe an email to tech-discuss to clarify what the URLs should be, would be useful?
15:48:36 <dmcbride> otherwise, we'll talk again tomorrow at TSC / release meetings
15:50:52 <ChrisPriceAB> On release links.  Please refer to http://artifacts.opnfv.org/opnfvdocs/docs/documentation/index.html for all master links that need to be accurate
15:51:08 <ChrisPriceAB> These will all be updated with /colorado/docs/ links on stable.
15:51:30 <ChrisPriceAB> this is the release reference
15:51:41 <dmcbride> #link http://artifacts.opnfv.org/opnfvdocs/docs/documentation/index.html
15:51:45 <ChrisPriceAB> tell me if they are wrong.  :D
15:52:33 <dmcbride> #endmeeting