02:30:54 <dmcbride> #startmeeting OPNFV APAC Release
02:30:54 <collabot`> Meeting started Wed Jul 12 02:30:54 2017 UTC.  The chair is dmcbride. Information about MeetBot at http://wiki.debian.org/MeetBot.
02:30:54 <collabot`> Useful Commands: #action #agreed #help #info #idea #link #topic.
02:30:54 <collabot`> The meeting name has been set to 'opnfv_apac_release'
02:31:03 <dmcbride> #topic roll call
02:31:09 <dmcbride> #info David McBride
02:31:32 <huzhj> #info Zhijiang Hu
02:31:55 <huzhj> Hi David
02:32:37 <dmcbride> hi Zhijiang
02:33:01 <dmcbride> did you see my email about Milestone 3.2?
02:33:11 <dmcbride> I need your compliance evidence for Daisy
02:33:40 <huzhj> Oh, forgot to check mail... I will send infomation to you now
02:33:48 <dmcbride> ok - great
02:34:20 <huzhj> latest result for Bare Metal
02:34:33 <huzhj> os-nosdn-nofeature-ha scenario (passed healthcheck) #link https://build.opnfv.org/ci/job/functest-daisy-baremetal-daily-master/7/console
02:34:46 <huzhj> os-odl_l3-nofeature-ha scenario (api_check failed) #link https://build.opnfv.org/ci/job/functest-daisy-baremetal-daily-master/8/console
02:34:54 <huzhj> latest result for Virtual
02:35:02 <huzhj> os-nosdn-nofeature-ha scenario (api_check failed) #link https://build.opnfv.org/ci/job/functest-daisy-virtual-daily-master/113/console
02:35:10 <huzhj> os-odl_l3-nofeature-ha scenario (passed healthcheck) https://build.opnfv.org/ci/job/functest-daisy-virtual-daily-master/111/console
02:35:46 <huzhj> failure during api_check test case is caused by functest testcase change(https://gerrit.opnfv.org/gerrit/#/c/37023/), and change has bug. I believe the change owner is working on that.
02:36:44 <dmcbride> ok - good news
02:37:22 <huzhj> and odl-l2 we tested without problem , just it haven't online
02:38:14 <dmcbride> #link https://wiki.opnfv.org/pages/viewpage.action?pageId=8690599
02:38:25 <dmcbride> ^^ agenda
02:39:32 <dmcbride> #topic Milestone 3.2 - installers able to successfully deploy scenario with integrated SDN and pass health check
02:40:12 <dmcbride> #info huzhj reports success with Daisy in meeting the requirements of MS3.2 - see previous links posted by huzhj
02:41:27 <dmcbride> Justin attended the main release meeting today, so we've already discussed MS3.2
02:42:29 <yujunz-zte> Meeting in progress dmcbride? Sorry I'm late
02:42:36 <dmcbride> #topic Milestone 5 - scenario integration
02:42:48 <dmcbride> hi Yujun
02:42:57 <dmcbride> I can move the time of the meeting if that would help
02:43:16 <dmcbride> I'm a little concerned about the turnout the past couple of meetings
02:43:33 <yujunz-zte> Current time is perfect for me. Just didn't notice my IRC client is offline
02:44:02 <r-mibu> apologies for being late...
02:44:19 <huzhj> I was on a little sick leave last meeting...
02:44:30 <dmcbride> hello Ryota
02:44:44 <r-mibu> dmcbride, hi
02:45:04 <dmcbride> ok - just to recap
02:45:15 <yujunz-zte> I guess sometimes people are confused by pacific time and daylight saving things, dmcbride
02:45:29 <yujunz-zte> Changing the invitation to UTC time may help
02:45:54 <yujunz-zte> Because the date is different, I saw r-mibu ask about meeting yesterday
02:46:14 <dmcbride> ok - I can do that
02:46:28 <dmcbride> I'll update the meeting date to UTC
02:46:45 <r-mibu> dmcbride, I'm reading log and agenda, no need to recap only for me
02:46:46 <dmcbride> I just need to figure out how to make google calendar do that ;)
02:47:21 <dmcbride> ok - fair enough
02:47:33 <dmcbride> let's continue with MS5, then
02:47:46 <huzhj> Google calendar is awesome, but seems it does not remove outdated meeting schedule automatically ?
02:48:15 <dmcbride> #info Milestone 5 is scheduled for July 28
02:48:38 <dmcbride> #info this is the point at which feature development should be completed
02:48:55 <dmcbride> #info however, it's understood that testing and bug-fixing continues
02:50:11 <dmcbride> #info MS6 - test case implementation - falls two weeks after MS5 on Aug 11
02:51:33 <dmcbride> #info based on the results of MS3.0, 3.1, 3.2, and 4, we should be able to say right now that installers are stable and functest may be used to implement new test cases
02:51:55 <dmcbride> If this is not the case, I need feedback from you
02:52:05 <dmcbride> this has been a problem in the past
02:52:27 <dmcbride> I believe that the installers are stable, then I find out too late that they're not
02:52:37 <r-mibu> right, so I've been waiting the installers become ready
02:52:52 <dmcbride> so, if you have any concerns about the state of the installers, I need to know that as soon as possible
02:52:55 <r-mibu> does anyone have tried? anyhow, I'll test today
02:53:24 <dmcbride> @r-mibu we were talking about MS3.2 at the start of the meeting
02:53:24 <collabot`> dmcbride: Error: "r-mibu" is not a valid command.
02:53:45 <dmcbride> r-mibu: we were talking about MS3.2 at the start of the meeting
02:54:04 <yujunz-zte> #link http://ircbot.wl.linuxfoundation.org/meetings/opnfv-release/2017/opnfv-release.2017-07-12-02.30.log.txt
02:54:09 <yujunz-zte> The recap of current meeting
02:54:25 <dmcbride> MS3.2 requires installers to successfully deploy a scenario with an integrated SDN controller and pass health check
02:54:26 <r-mibu> ah, ok
02:55:11 <dmcbride> I haven't finished, but the compliance evidence I've received from the installer teams suggests that they are meeting this requirement
02:55:27 <dmcbride> but if I'm wrong, I need you to tell me
02:56:15 <dmcbride> r-mibu: how is your work for Euphrates proceeding?
02:56:48 <r-mibu> not so good so far
02:57:04 <r-mibu> one member from ZTE is working very hard
02:57:20 <r-mibu> but, we still need more contribution from the community
02:57:35 <r-mibu> and I'm working on testing from this week
02:58:20 <dmcbride> which community are you referring to?  Doctor? OPNFV?
02:58:30 <r-mibu> Doctor...
02:59:23 <r-mibu> well, we have good number of contributors though
02:59:55 <r-mibu> anyhow, I'll control the tasks and avoid making exceptions for MS5
03:00:37 <dmcbride> perhaps you can defer some of the new features to the next release?
03:00:56 <shangxdy> The current tricky thing is fuel can not be used.
03:01:06 <r-mibu> yes, we'll do, actually we deferred some tasks in danube as well
03:01:51 <dmcbride> shangxdy: what's the issue with Fuel?
03:02:38 <shangxdy> There is no fuel iso available
03:03:49 <dmcbride> shangxdy: for Euphrates?
03:04:12 <shangxdy> yes, for release E
03:04:42 <dmcbride> shangxdy: could you send me an email that describes the problem?
03:05:28 <dmcbride> #topic Danube 3 release
03:05:29 <shangxdy> OK
03:05:33 <dmcbride> ok - final topic
03:06:43 <dmcbride> #info @rpaik has called for a vote from the TSC on the July 14 release date
03:07:39 <dmcbride> #info there was some question about whether we would defer again, but the feedback I've received is to go ahead with the release on Friday
03:07:56 <dmcbride> does anyone have any concerns about releasing on Friday?
03:08:37 <dmcbride> #info July 12 - complete testing
03:09:05 <dmcbride> #info July 13 - complete updates to documentation / JIRA cleanup
03:09:19 <dmcbride> #info July 14 - tag repos
03:10:02 <yujunz-zte> I have a small question. If we don't plan to update anything in Danube 3.0, is it OK to skip it silently? I mean for testing project like QTIP
03:10:55 <dmcbride> yujunz-zte: the agreement we reached last fall was that any project or scenario released in 1.0 would be released in 2.0 and 3.0
03:11:48 <dmcbride> basically, this means that you need to continue to support the project or the scenario through 3.0, even if you aren't doing any new development
03:12:33 <dmcbride> for example, if a scenario starts failing to deploy leading up to 3.0, the scenario owner needs to diagnose it and make corrections
03:13:14 <dmcbride> yujunz-zte: in your case, I would say that if QTIP was not functioning correctly for some reason, then you would need to fix it
03:13:47 <yujunz-zte> I see. I'll check the status and try to catch up with the schedule
03:13:49 <dmcbride> yujunz-zte: otherwise, all you need to do is to configure your documentation for Danube 3.0
03:13:56 <yujunz-zte> Since we don't rely on scenario that much
03:15:01 <dmcbride> yujunz-zte: understood - just make sure that your documentation is setup for D3
03:15:30 <yujunz-zte> OK, thanks for the clarification
03:16:00 <dmcbride> #info Sofia is having a documentation meeting at 6 a.m. Pacific
03:16:28 <dmcbride> I guess that would be 9 p.m. CST
03:17:14 <dmcbride> ok - thanks for attending
03:17:33 <dmcbride> e-mail me, or catch me on IRC if you have questions or concerns
03:17:40 <dmcbride> #endmeeting