13:30:42 <dmcbride> #startmeeting OPNFV Danube 3 Release Daily
13:30:42 <collabot> Meeting started Mon Jun 26 13:30:42 2017 UTC.  The chair is dmcbride. Information about MeetBot at http://wiki.debian.org/MeetBot.
13:30:42 <collabot> Useful Commands: #action #agreed #help #info #idea #link #topic.
13:30:42 <collabot> The meeting name has been set to 'opnfv_danube_3_release_daily'
13:30:50 <dmcbride> #topic roll call
13:30:56 <dmcbride> #info David McBride
13:31:07 <rpaik> #info Ray Paik
13:31:42 <dmcbride> ping mbeierl
13:31:54 <mbeierl> dmcbride: pong
13:31:56 <rpaik> jose_lausuch are you on?
13:32:20 <dmcbride> mbeierl: what is the status of StorPerf for D3?
13:32:26 <chigang__> #info Justin
13:32:55 <jose_lausuch> rpaik: hi
13:33:04 <jose_lausuch> #info Jose Lausuch
13:33:06 <mbeierl> dmcbride: Danube 3.0?  Ready to tag once it's confirmed that we are releasing.  I could tag an RC now if needed
13:33:08 <dmcbride> mbeierl: you were having some problems with Apex before
13:34:11 <mbeierl> dmcbride: Correct.  I hit a situation which I had encountered before.  If the disks already have an Apex image, it fails to re-install or something.  Still don't know exactly how to reproduce it, but zeroing out all the disks and then running the installer caused it to work again
13:34:18 <dmcbride> chigang__: what's the status of onos-sfc on Compass?
13:34:19 <mbeierl> #info Mark Beierl
13:34:30 <mbeierl> there is no GTM for today is there?  This is IRC only?
13:34:38 <dmcbride> mbeierl: yes
13:35:00 <mbeierl> Just catching up on emails from the weekend and I see that now :)
13:35:08 <dmcbride> #topic StorPerf status
13:35:25 <rpaik> narindergupta are you online as well?
13:35:26 <chigang__> dmcbride: ready for release, test result http://testresults.opnfv.org/reporting/functest/release/danube/index-status-compass.html
13:35:30 <mbeierl> StorPerf daily Danube jobs are running again and passing
13:36:06 <mbeierl> #link http://testresults.opnfv.org/reporting/display/danube/storperf/status-apex.html
13:36:11 <dmcbride> #info mbeierl reports that he is able to run StorPerf on CI again.  Previous Apex issues have not repeated, although we still don't know root cause.
13:36:13 <mbeierl> StorPerf ready to tag and release.
13:36:34 <dmcbride> #info mbeierl reports that StorPerf stands ready to release for D3
13:36:34 <mbeierl> Is anyone from Yardstick on?
13:37:00 <dmcbride> mbeierl: what is Ross' nic?
13:37:18 <mbeierl> dmcbride: good question.   Don't recall at the moment
13:38:17 <dmcbride> #topic installer status
13:38:28 <mbeierl> dmcbride: don't see him in #opnfv-yardstick either
13:38:41 <rpaik> Can I ask a few questions to jose_lausuch on functest?
13:38:54 <jose_lausuch> rpaik: go ahead
13:39:50 <rpaik> not sure if you saw the email from tbramwell on Friday, but I get the impression that the number of iterations have gone down on test results.opnfv.org
13:39:57 <rpaik> am I reading it wrong?
13:41:04 <jose_lausuch> rpaik: side effect of change done by Serena on test API
13:41:12 <jose_lausuch> rpaik: it's our mistake, sorry about it
13:41:12 <rpaik> ahh....
13:41:22 <jose_lausuch> it will be corrected soon
13:41:40 <dmcbride> chigang__: onos-sfc has not built successfully in over a week
13:41:46 <dmcbride> chigang__: why is that?
13:41:53 <rpaik> cool.  just want to make sure jobs/tests were running
13:41:55 <dmcbride> chigang__: https://build.opnfv.org/ci/job/compass-os-onos-sfc-ha-baremetal-daily-danube/
13:43:19 <dmcbride> #info Justin says that Compass is ready for release, however, the last successful build for onos-sfc was over a week ago
13:43:20 <chigang__> it is not daily job, it is trigger by manual
13:44:09 <dmcbride> chigang__: what is the reason for doing that for a scenario that is about to be released?
13:44:19 <dmcbride> chigang__: seems like you would want to have more runs, not less
13:45:11 <jose_lausuch> also, the onos-sfc test case fails
13:45:24 <chigang__> dmcbride: it runs daily in virtual deployment https://build.opnfv.org/ci/view/compass4nfv/job/compass-os-onos-sfc-ha-virtual-daily-danube/
13:45:59 <dmcbride> chigang__: yes, but we agreed that we would release based on baremetal results
13:46:33 <dmcbride> narinder`: ping
13:46:37 <dmcbride> narindergupta: ping
13:46:58 <rpaik> I also sent narindergupta an SMS
13:47:13 <rpaik> hopefully he's made it back....
13:47:26 <rpaik> BTW, Ross' Nic is rbbratta
13:47:52 <dmcbride> that's right
13:47:58 <dmcbride> I remember now
13:48:25 <dmcbride> no sign of trozet
13:48:28 <chigang__> Because run once in BM, in order to save resources, then disable run on baremetal
13:48:58 <rpaik> I don't see trozet on IRC, maybe we can check with frankbrockners on fd.io status on Apex?
13:49:10 <dmcbride> chigang__: it seems that you have an issue to debug with functest, according to jose_lausuch
13:49:24 <chigang__> dmcbride: I am checking
13:49:34 <chigang__> jose_lausuch: dmcbride thanks
13:49:41 <dmcbride> frankbrockners: ping
13:49:42 <jose_lausuch> I can say that for Apex nosdn-nofeature the results are very good, except for Domino, which causes some problems with dependencies. We decided to remove that test case
13:50:04 <jose_lausuch> other scenarios doesn't look that good
13:50:56 <rpaik> not sure which scenarios trozet was referring to, but he said the fix looked good on Thursd
13:51:09 <dmcbride> #info jose_lausuch reports that Apex nosdn scenarios look good, but other scenarios having problems.
13:51:10 <rpaik> Thursday
13:51:41 <jose_lausuch> yes, there was a bug in upstream TripleOOO which was fixed
13:51:49 <jose_lausuch> and we got all the tempest tests passing after that
13:53:02 <jose_lausuch> some tempest errors in odl_l2/3-nosdn scenarios for apex
13:53:43 <dmcbride> jose_lausuch:  odl nosdn scenarios?
13:54:00 <jose_lausuch> yes
13:54:00 <dmcbride> jose_lausuch: is that a typo?
13:54:13 <dmcbride> jose_lausuch: seems like an oxymoron
13:54:14 <jose_lausuch> there is odl_l2 and odl_l3
13:54:21 <jose_lausuch> so, yes, common odl-nofeature scenarios
13:54:54 <rpaik> another question for chigang__
13:55:37 <dmcbride> pma: ping
13:55:43 <rpaik> chigang__ if there's further delay in Danube 3.0, will that impact your work for Euphrates?
13:56:54 <rpaik> I know you're planning to get caught up on Milestone 3 work, but does Danube 3.0 need to be completed for your Euphrates work?
13:57:03 <chigang__> rpaik: yes, have to work in parallel
13:57:49 <rpaik> chigang__ so will you be OK if there's further delay in Danube 3.0?
13:59:09 <chigang__> rpaik: It is best not to delay too long
13:59:21 <rpaik> got it, thanks....
13:59:58 <rpaik> dmcbride, it doesn't looks like we'll hear from Fuel/Apex/JOID teams in the next minute....
14:00:21 <dmcbride> rpaik: agreed
14:00:58 <dmcbride> #topic schedule/logistics
14:00:58 <rpaik> could you follow-up with them today and also ask them to join the TSC mtg. tomorrow?
14:02:10 <dmcbride> #info Reminder that D3 release has been delayed.  New release date will be determined at tomorrow's TSC meeting.
14:02:48 <jose_lausuch> what will be based the date on?
14:03:05 <dmcbride> #info next daily meeting will be held on Thursday, June 29
14:03:33 <dmcbride> jose_lausuch: installer and scenario owner readiness
14:03:50 <jose_lausuch> dmcbride: ok
14:04:20 <dmcbride> #endmeeting