03:31:20 <dmcbride> #startmeeting APAC OPNFV release
03:31:20 <collabot`> Meeting started Wed Mar  8 03:31:20 2017 UTC.  The chair is dmcbride. Information about MeetBot at http://wiki.debian.org/MeetBot.
03:31:20 <collabot`> Useful Commands: #action #agreed #help #info #idea #link #topic.
03:31:20 <collabot`> The meeting name has been set to 'apac_opnfv_release'
03:31:30 <dmcbride> #topic roll call
03:31:35 <dmcbride> #info David McBride
03:31:42 <chigang> #info Justin chi
03:31:51 <dmcbride> hi Justin
03:31:58 <chigang> hi David
03:32:18 <kongwei_> hi David
03:32:55 <joehuang> hello
03:33:03 <joehuang> #info joehuang
03:33:08 <kongwei_> #info kongwei
03:33:27 <fuqiao> #inf9
03:33:35 <fuqiao> #info fuqiao
03:33:46 <dmcbride> hi guys
03:34:01 <dmcbride> I made some last minute updates to the agenda
03:34:07 <dmcbride> #link https://wiki.opnfv.org/pages/viewpage.action?pageId=8690599
03:34:24 <dmcbride> let me know if there is anything that you would like to add
03:34:40 <dmcbride> #topic MS7 stable branch
03:35:10 <kubi001> #info kubi
03:35:15 <dmcbride> #info Friday, March 10, 12 p.m. PST
03:35:24 <dmcbride> hi Kubi
03:36:07 <dmcbride> ideally, you will have as much work done as possible to minimize cherry picking after stable branch
03:36:21 <chigang> just one question, after creating stable branch, Could i cherry pick patch into stable branch?
03:36:31 <kubi001> yardstick team decided checkout the branch at Mar. 9th , 4.am UTC
03:36:46 <dmcbride> chigang: yes, of course
03:36:59 <dmcbride> this is NOT a code freeze
03:37:08 <chigang> dmcbride: thanks.
03:37:25 <dmcbride> you may continue with bug fixes, as necessary
03:37:50 <joehuang> ok. I heard that Aric will create the branch for all projests, isn't it? or each project create stable branch himself
03:37:52 <dmcbride> however, as I said, you will need to do cherry picking
03:38:21 <dmcbride> joehuang: yes, Aric will create the branch
03:38:38 <chigang> I will merge bugfix patch into branch, and new feature patch are only merged into master
03:38:50 <dmcbride> however, projects with admin privileges may create their own branch
03:39:04 <kubi001> dmcbride: so we needn't to checkout the stable branch by ourself ?
03:39:06 <dmcbride> you may also ask Aric to create the branch now if you are reqady
03:39:37 <dmcbride> kubi001: do you mean create the stable branch?
03:39:46 <kubi001> dmcbride: yes,
03:40:03 <dmcbride> kubi001: yes, Aric will create it for you
03:40:06 <joehuang> thanks David
03:40:14 <chigang> dmcbride: before asking Aric to create branch, Should I make a tag for the branch?
03:40:24 <chigang> dmcbride: before asking Aric to create branch, Should I make a tag for the master?
03:40:47 <dmcbride> chigang: you may do that if you wish, or you may just specify HEAD, or a particular commit ID
03:41:52 <chigang> dmcbride: thanks, clear for me.
03:42:19 <dmcbride> ok - any other questions about stable branch?
03:42:32 <dmcbride> otherwise, let's discuss the E-release
03:42:42 <dmcbride> #topic E-Release
03:43:11 <dmcbride> #info in case you did not see the email, the name for the new release is "Euphrates"
03:43:18 <dmcbride> #link https://en.wikipedia.org/wiki/Euphrates
03:43:52 <chigang> yes, I vote for Edison, but....
03:43:58 <dmcbride> #info the release will be based on OpenStack "Ocata", which was just released two weeks ago
03:44:29 <dmcbride> #info the release will utilize Keystone API v3 (v2 was deprecated in Mitaka)
03:44:55 <r-mibu> that's good new
03:45:08 <dmcbride> #info also, we are changing the versioning to a more standard nomenclature
03:45:36 <dmcbride> #link https://wiki.opnfv.org/display/releng/Artifact+Versioning
03:46:16 <dmcbride> #info OLD = euphrates.1.0 / NEW = 5.0.0
03:46:42 <dmcbride> #info OLD = euphrates.2.0 / NEW = 5.1.0
03:46:44 <r-mibu> should we apply this in JIRA as well?
03:46:46 <dmcbride> etc
03:47:11 <dmcbride> I will update JIRA projects with new version strings
03:47:17 <dmcbride> just select from those
03:47:45 <r-mibu> ok
03:47:48 <kubi001> how about the "Danube 2.0"?
03:48:06 <dmcbride> the "old" versioning will continue for Danube
03:48:07 <kubi001> = 4.1.0?
03:48:13 <kubi001> ok, got it
03:48:20 <dmcbride> the new nomenclature will not take effect until Euphrates
03:49:26 <dmcbride> #info new nomenclature will not take effect until Euphrates
03:50:25 <dmcbride> #info the TSC will likely vote on the Euphrates schedule next week
03:50:26 <kubi001> dmcbride:  shall we have "5.1.1"?
03:51:13 <dmcbride> kubi001: that would be a patch to 5.1.0
03:51:46 <dmcbride> this would likely occur if there was some problem identified with 5.1 at the last minute
03:51:56 <kubi001> dmcbride:  got it
03:53:02 <dmcbride> ok - last topic is stability and functest results
03:53:17 <dmcbride> #topic stability / functest
03:54:24 <r-mibu> http://testresults.opnfv.org/reporting/yardstick/release/master/index-status-apex.html ?
03:55:30 <dmcbride> any particular issues or problems reaching stability?
03:55:49 <dmcbride> I had an exchange with joehuang earlier today about multisite
03:56:52 <dmcbride> joehuang:  or chigang could you please clarify
03:57:01 <dmcbride> "The CI is in this page, and Juha from Functest is working on fixing it, hope it could be solved before this Friday."
03:57:33 <r-mibu> doctor test case need some fixes, but the doctor team can handle it
03:57:50 <r-mibu> the concern is we need at relase three success in ci
03:58:04 <r-mibu> which means we need fix them by today
03:59:27 <chigang> dmcbride: I am not sure the multisite scenario is running on Compass, I need to check it.
03:59:56 <r-mibu> in genral, we need three success by friday, is that correct?
04:00:17 <dmcbride> chigang: I see it on the functest dashboard:  http://testresults.opnfv.org/reporting/functest/release/master/index-status-compass.html
04:00:36 <dmcbride> chigang: but it doesn't look like anything is happening
04:01:12 <dmcbride> r-mibu: there is no test requirement gate for Friday that I know of
04:02:24 <chigang> dmcbride: yes, I see that, but for now we dont have PODs for multisite running, as I know, if you want to test multisite, 2 PODs are need
04:02:25 <dmcbride> chigang: multisite is the only feature scenario that I see running on compass right now, shouldn't there be others?
04:02:27 <r-mibu> dmcbride, ok - i just though as we had such criteria at the end of colorado
04:03:01 <dmcbride> r-mibu: yes, but his is not the "end".  This is just the stable branch creation.
04:03:21 <dmcbride> r-mibu: we still have a few weeks until the release
04:03:52 <joehuang> to David
04:03:56 <joehuang> https://jira.opnfv.org/browse/FUNCTEST-742
04:04:22 <joehuang> Juha found the root cause for the multisite CI failure
04:04:29 <joehuang> and will fix it soon
04:05:52 <dmcbride> #info joehuang reports that FUNCTEST-752 is blocking multisite scenario
04:05:56 <dmcbride> #link https://jira.opnfv.org/browse/FUNCTEST-742
04:06:06 <dmcbride> joehuang: good to know - thanks
04:07:56 <joehuang> sorry, have to leave now. Thanks for the meeting
04:08:02 <dmcbride> during the TSC call today, we had a discussion about the roadmap for CI evolution in Euphrates
04:08:27 <dmcbride> you guys may want to look at this flowchart that describes how dynamic allocation will roll out
04:08:32 <dmcbride> https://wiki.opnfv.org/download/attachments/2925933/dynamic_allocation.pdf?version=1&modificationDate=1488925316000&api=v2
04:08:44 <dmcbride> ok - that's all I have
04:08:57 <dmcbride> any questions or comments before we wrap up?
04:09:25 <dmcbride> ok - thanks again for participating
04:09:38 <dmcbride> please email me or contact me on IRC if you have questions or concerns
04:09:44 <dmcbride> #endmeeting