14:02:18 <dmcbride> #startmeeting OPNFV Release
14:02:18 <collabot`> Meeting started Tue Jul 11 14:02:18 2017 UTC.  The chair is dmcbride. Information about MeetBot at http://wiki.debian.org/MeetBot.
14:02:18 <collabot`> Useful Commands: #action #agreed #help #info #idea #link #topic.
14:02:18 <collabot`> The meeting name has been set to 'opnfv_release'
14:02:26 <dmcbride> #topic roll call
14:02:29 <chigang__> #info Justin
14:02:52 <Julien-zte> #info Julien
14:02:54 <dmcbride> #info David McBride
14:03:00 <rbbratta> #info Ross
14:03:06 <bertys> #info Bertrand (Proxy for Gerald)
14:03:10 <rpaik> #info Ray Paik
14:03:46 <sofiawallin> #info Sofia Wallin
14:04:43 <trozet> #info Tim Rozet
14:05:58 <NikoHerEricsson> #info Nikolas Hermanns
14:06:25 <uli-k> #info Uli
14:09:29 <dmcbride> #topic Danube 3
14:09:36 <jose_lausuch> #info Jose Lausuch
14:10:06 <dmcbride> #info dmcbride says that his earlier statement about two FDS scenarios not running on CI is in error
14:10:46 <dmcbride> #info os-nosdn-fdio-noha still appears to be failing
14:11:58 <dmcbride> #info Juraj indicates that this scenario has previously passed.  Only the most recent deploy failed.
14:12:28 <trozet> #info the scenario failed due to a generic OOO installer failure, not a scenario specific issue
14:15:35 <dmcbride> #info @trozet says that he believes that we should proceed with the release of Danube 3 this week
14:16:49 <dmcbride> #action @trozet update scenario status page for Danube
14:17:33 <Julien-zte> do we have statistics for each release version downloaded?
14:19:25 <dmcbride> #info @chigang__ says that he wants to proceed with a release this week
14:20:31 <dmcbride> #info @chigang__ indicates that onos-sfc scenario is now successfully deploying to bare metal
14:21:04 <chigang__> #info onos-sfc baremetal deployment link https://build.opnfv.org/ci/view/compass4nfv/job/compass-os-onos-sfc-ha-baremetal-daily-danube/lastSuccessfulBuild/
14:21:33 <dmcbride> #info Bob Monkman indicates that Armband project is prepared to proceed with D3 release this week
14:23:43 <dmcbride> #info @sofiawallin asks about documentation
14:27:31 <sofiawallin> #info Documentation instruction http://docs.opnfv.org/en/stable-danube/how-to-use-docs/index.html and templates are stored under opnfvdocs/docs/templates/release
14:29:52 <dmcbride> #info @rpaik and @dmcbride agree to proceed with TSC vote, based on feedback from TSC and Release calls
14:30:23 <dmcbride> #action @rpaik start TSC vote on Danube 3 release on July 14
14:31:26 <dmcbride> #info if project teams have already tagged their repo with Danube 3.0, advice from the release team is to create a new tag at Danube 3.1
14:31:37 <rbbratta> helpdesk ticket was [OPNFV Helpdesk #42362] update or deleting yardstick git tag for Danube 3.0, response was can't delete a git tag, have to move to 3.1 tag
14:32:37 <dmcbride> #info Schedule for D3:  July 12 complete testing; July 13 complete doc updates and JIRA cleanup; July 14 tag repos
14:33:00 <dmcbride> #info download page to go live on July 17 or 18
14:34:53 <dmcbride> #topic Euphrates MS3.2
14:34:54 <trozet> #info https://build.opnfv.org/ci/job/functest-apex-baremetal-daily-master/79/console
14:35:46 <trozet> FUNCTEST REPORT
14:35:55 <rpaik> will be on IRC only in the next few minutes
14:37:37 <dmcbride> #info @jose_lausuch reports that health check is fully supported in Euphrates
14:38:54 <dmcbride> #info @trozet reports that Apex is mostly passing MS3.2, with some minor cleanup still to complete
14:39:38 <trozet> dmcbride: if MS3.2 is just healtcheck, we are passing all healtcheck, my comments about 3 failures were for more advanced functest tests
14:40:37 <rbbratta> #info https://gerrit.opnfv.org/gerrit/#/c/36537/ draft Kubernetes context for ssh ping test with Yardstick and OpenRetriever
14:40:41 <dmcbride> #undo
14:40:41 <collabot`> Removing item from minutes: <MeetBot.ircmeeting.items.Info object at 0x2707e10>
14:41:07 <dmcbride> #info @trozet reports that Apex is passing requirements for MS3.2
14:42:24 <dmcbride> #info @chigang__ reports that Compass team is on track with their MS exception recovery plan
14:42:51 <dmcbride> #info dmcbride asks Bob Monkman and @chigang__ to be prepared to discuss their respective recovery plans at next weeks TSC call
14:49:29 <dmcbride> #action dmcbride to propose protocol/process for blacklisting tests
14:51:55 <dmcbride> #topic MS5 - scenario integration
14:52:58 <dmcbride> #info scheduled for July 28
14:55:46 <dmcbride> #link https://wiki.opnfv.org/download/attachments/8689511/OPNFV%20Release%20%2522Euphrates%2522%20r7.pdf?version=1&modificationDate=1496707207000&api=v2
14:56:05 <dmcbride> #link https://wiki.opnfv.org/display/SWREL/Euphrates
14:56:47 <dmcbride> #info see "Schedule" link for Gantt chart for Euphrates release
14:58:04 <Julien-zte> hi dmcbride, I checkout danube release notes and I find that pharos does not attend the release, so I have nothing to do for danube 3.0, yet?
14:58:50 <Julien-zte> I don't review these items when Jack is charge of this :)
14:58:50 <dmcbride> Julien-zte: I don't understand your question
14:59:24 <Julien-zte> I find no tag for Danube from pharos' project branches
15:00:15 <dmcbride> does Pharos tag its repo for OPNFV releases?
15:00:36 <Julien-zte> yes, arno to colorado
15:00:43 <Julien-zte> https://git.opnfv.org/pharos/
15:01:10 <dmcbride> ok - I wasn't aware of that
15:01:21 <Julien-zte> no stable branch for danube
15:01:29 <dmcbride> from my point of view, it has not been a problem
15:01:32 <Julien-zte> that's my question, I don't know ither
15:01:45 <Julien-zte> OK, thanks
15:01:50 <dmcbride> however, if Pharos finds it useful to tag their repo for OPNFV releases, then I have no objection
15:02:06 <dmcbride> ok - got it
15:02:07 <Julien-zte> I will focus on Euphrates
15:02:14 <dmcbride> thank you
15:02:24 <Julien-zte> thanks david
15:02:42 <dmcbride> #endmeeting