02:29:24 <dmcbride> #startmeeting OPNFV APAC release
02:29:24 <collabot`> Meeting started Wed Apr 18 02:29:24 2018 UTC.  The chair is dmcbride. Information about MeetBot at http://wiki.debian.org/MeetBot.
02:29:24 <collabot`> Useful Commands: #action #agreed #help #info #idea #link #topic.
02:29:24 <collabot`> The meeting name has been set to 'opnfv_apac_release'
02:29:36 <dmcbride> #topic roll call
02:29:41 <dmcbride> #info David McBride
02:29:55 <dmcbride> hey Team - release meeting is starting
02:31:10 <dmcbride> chigang_: ping
02:31:36 <dmcbride> yujunz: ping
02:31:40 <dmcbride> gabriel_yuyang: ping
02:31:51 <dmcbride> hw_wutianwei_: ping
02:32:11 <gabriel_yuyang> #info gabriel_yuyang
02:32:25 <dmcbride> mj_rex: ping
02:32:51 <LindaWang> #info Linda Wang
02:33:00 <chigang_> #info Justin chi
02:33:07 <mj_rex> #info Rex
02:33:31 <r-mibu__> #info RyotaMibu
02:33:35 <yifei> #info Yifei Xue
02:33:57 <dmcbride> hi team
02:34:03 <dmcbride> thanks for joining
02:34:12 <dmcbride> #topic schedule review
02:34:49 <dmcbride> after reviewing the status of the release with the TSC today, I recommended delaying the release by 1 week
02:35:03 <dmcbride> the TSC accepted my recommenation
02:35:36 <dmcbride> #info Fraser 6.0 release date pushed out by 1 week
02:36:18 <dmcbride> #info MS8 - formal testing - April 24
02:36:38 <dmcbride> #info MS9 - final documentation - April 25
02:36:57 <dmcbride> #info MS10 - JIRA cleanup - April 26
02:37:15 <dmcbride> #info MS11 - release - April 27
02:37:29 <dmcbride> #info download page goes live on May 1
02:37:58 <dmcbride> any questions about the schedule change for Fraser?
02:39:09 <dmcbride> ok
02:39:12 <chigang_> clear for me
02:39:25 <dmcbride> moving on to Gambia
02:39:58 <mj_rex> got it, thanks for the info.
02:40:06 <dmcbride> did everyone see my announcement that we are accepting intent-to-participate notifications for Gambia?
02:40:43 <dmcbride> #info intent to participate for Gambia opened April 13
02:41:10 <dmcbride> #info intent to participate will close at MS1 on May 11
02:41:19 <chigang_> yes, I sent a mail to announce Compass4nfv joining Gambia and following traditional track.
02:41:40 <dmcbride> thanks chigang_
02:41:59 <zhihui_wu> I sent a email too
02:42:00 <dmcbride> I haven't updated the participation page with all of the notifications I've received, yet
02:42:09 <dmcbride> I'll probably do that tomorrow
02:42:40 <dmcbride> did you remember to specify which track?  Traditional or continuous delivery?
02:42:53 <dmcbride> or both
02:43:10 <zhihui_wu> QTIP will follow the traditional way.
02:43:15 <dmcbride> a few people have been forgetting to do that
02:43:35 <chigang_> I suggest that it is better for testing projects to support both track
02:43:47 <dmcbride> chigang_: agreed
02:44:12 <r-mibu__> +1
02:44:19 <dmcbride> in fact, I had a conversation with timirnich today where I raised that same issue
02:44:45 <dmcbride> the idea of having two tracks is broken if we don't have support from test frameworks for both tracks
02:44:55 <mj_rex> dmcbride: for yardstick, we discussed about the tradition process and new process in last meeting, there's still some gaps with CD, and we need more discussion about it.
02:45:14 <LindaWang> Functest will plan to verify openstack version first and adjust the version of tests and packages installed(rally, tempest, etc,.)
02:45:38 <dmcbride> mj_rex: can you give me an example of the gaps?
02:47:13 <mj_rex> for testing framework like yardstick, it needs functional test to test the framework itself. There's plan about this in Gambia, but still not done yet.
02:49:38 <dmcbride> ah - right - I've been discussing that with Cedric
02:49:56 <chigang_> If testing projects have a suitable framework, no much dependency on Openstack API, or using upstream test cases, it will be easy to support both track, just my 2 cents
02:50:37 <dmcbride> chigang_: what do you mean by "suitable framework"?
02:51:54 <chigang_> maybe using a adapter to reduce dependency on API in different Openstack version
02:51:56 <dmcbride> do we have anyone from Daisy team available?
02:52:10 <dmcbride> can anyone give me an update on the status of os-nosdn-ovs_dpdk on Daisy?
02:52:24 <dmcbride> it looked like it was failing health check, yesterday
02:53:57 <dmcbride> chigang_: so that you could use the same version of the test framework with multiple versions of OS?
02:56:11 <dmcbride> the CD track is not well defined at this point
02:57:06 <dmcbride> we are determining processes and requirements as we move forward, so we will likely run into many complications like this
02:57:32 <chigang_> dmcbride: Regarding to Compass,  we just use the upstream code to upgrade openstack, so it is not relevant to testing framework
02:57:56 <dmcbride> ok
02:58:19 <mj_rex> I think the CD track need to be defined as several phases and each phase has some requirements to fill the gap.
03:00:13 <dmcbride> #link https://etherpad.opnfv.org/p/release-process2.0 etherpad discussion about revised release process
03:00:52 <dmcbride> #link https://wiki.opnfv.org/display/SWREL/Continuous+Delivery+Release+Planning planning page for developing CD process
03:01:12 <dmcbride> ok - we are out of time
03:01:23 <dmcbride> any questions or comments before we finish?
03:01:54 <dmcbride> ok - thanks everyone for joining the meeting
03:02:02 <chigang_> dmcbride: thanks, bye
03:02:09 <dmcbride> #endmeeting