03:24:54 <dmcbride> #startmeeting OPNFV release (APAC)
03:24:54 <collabot> Meeting started Wed Feb  8 03:24:54 2017 UTC.  The chair is dmcbride. Information about MeetBot at http://wiki.debian.org/MeetBot.
03:24:54 <collabot> Useful Commands: #action #agreed #help #info #idea #link #topic.
03:24:54 <collabot> The meeting name has been set to 'opnfv_release__apac_'
03:25:10 <dmcbride> #topic
03:25:14 <dmcbride> #undo
03:25:14 <collabot> Removing item from minutes: <MeetBot.ircmeeting.items.Topic object at 0x2266c90>
03:25:19 <dmcbride> #topic roll call
03:25:27 <dmcbride> #info David McBride
03:25:27 <huzhj> #info Zhijiang
03:26:19 <dmcbride> hello Zhijiang!
03:26:34 <huzhj> Hi David
03:26:54 <huzhj> What is the time on your watch?
03:27:09 <dmcbride> 7:27 p.m. PST
03:27:23 <dmcbride> how about you?
03:27:35 <huzhj> 11:27 a.m.
03:27:49 <dmcbride> does this time work for you?
03:27:54 <joehuang> #info joehuang
03:27:58 <huzhj> Little bit late for you
03:28:01 <joehuang> it's ok for me
03:28:10 <huzhj> Yes, thanks
03:29:21 <fuqiao> #fuqiao
03:31:16 <dmcbride> ok - let's get started
03:31:51 <dmcbride> thanks for joining this first APAC OPNFV release meeting
03:32:02 <kubi001> #info kubi(yardstick)
03:32:22 <dmcbride> I wanted to start by just understanding if the time and format are useful to this group
03:32:31 <dmcbride> #topic meeting time and format
03:33:00 <dmcbride> Is this a good time to meet?
03:33:04 <dmcbride> comments?
03:33:07 <joehuang> yes
03:33:13 <fuqiao> Ok
03:33:13 <kubi001> dmcbride: yes, It 's good to me
03:33:20 <huzhj> yes
03:33:22 <fuqiao> Ok for me~
03:33:26 <dmcbride> ok - good to hear
03:33:37 <dmcbride> it was a bit of guess work on my part
03:33:48 <dmcbride> how about the frequency?
03:33:57 <joehuang> where are you based
03:34:00 <dmcbride> current plan is to have this meeting every other week
03:34:13 <joehuang> sounds great
03:34:23 <dmcbride> @joehuang I am in Seattle
03:34:23 <collabot> dmcbride: Error: "joehuang" is not a valid command.
03:34:53 <dmcbride> joehuang: I am in Seattle
03:35:20 <joehuang> Nice place, close to Vancouver
03:35:23 <dmcbride> Northwestern part of the United States for those who are not familiar with the location of the city
03:35:26 <fuqiao> Could be half an hour earlier if this is too late for you.@dmcbride
03:35:49 <yuyang_gabriel> #info yuyang_gabriel
03:35:52 <joehuang> how long the meeting will last? half hour or one hour
03:35:57 <dmcbride> joehuang: true - Vancouver is about a 4 hour drive from Seattle
03:36:40 <dmcbride> joehuang: current plan is for 30 minutes; however, I am open to extending it to an hour, or more if the team would like
03:37:06 <dmcbride> joehuang: how do you feel about 30 minutes?  Should it be an hour?
03:37:30 <joehuang> 30min may be enough,
03:37:31 <dmcbride> #info general agreement on time and frequency of APAC OPNFV release meeting
03:37:40 <joehuang> can be prolong if more topics as needed
03:37:48 <dmcbride> any other thoughts?
03:37:57 <yuyang_gabriel> agree
03:38:09 <kubi001> I prefer to 30 minutes
03:38:28 <dmcbride> fuqiao: thank you, but I pick my son up from his piano lesson at 7, so I would be perpetually late :)
03:38:41 <dmcbride> so, 7:30 works for me
03:38:56 <fuqiao> Ok.
03:39:09 <dmcbride> #info general agreement on 30 minute meeting with option to extend, if necessary
03:40:07 <dmcbride> as we proceed, if anyone thinks that we should adjust the time, duration, or frequency, please don't hesitate to let me know
03:40:16 <dmcbride> I will try to be as accommodating as possible
03:40:32 <chigang> #info Justin
03:40:44 <dmcbride> welcome chigang
03:40:58 <chigang> dmcbride: hi David
03:41:15 <dmcbride> ok - let's dive into the schedule
03:41:39 <dmcbride> #topic Milestone 5 - feature freeze and scenario integration
03:41:59 <dmcbride> how does everyone feel about MS5?
03:42:06 <dmcbride> this has been a challenge for many projects
03:42:19 <zhipengh> dmcbride could we still merge patches ?
03:42:39 <dmcbride> I know that it came at an awkward time, just before New Year celebration and vacations
03:43:43 <chigang> dmcbride: it is in the process of stabilization for us
03:44:23 <kubi001> dmcbride:  does the MS5 applied to testing projects? do we need to provide the CI link?
03:45:01 <dmcbride> #info kubi001 asks whether MS5 applies to testing projects
03:45:30 <dmcbride> kubi001: MS5 applies to any project that uses one or more scenarios to deploy and/or test
03:45:31 <kubi001> dmcbride: I noticed that functest also didn't fill into the table ,but storperf and qtip did
03:45:55 <dmcbride> kubi001: yes - see my previous response
03:46:20 <dmcbride> admittedly, the evaluation and application of the criteria is not perfect
03:46:51 <dmcbride> during the release call today, the point was made that our current set of milestones apply primarily to feature projects
03:47:25 <joehuang> the CI for multisite project after refactoring is not stable yet,
03:47:31 <chigang> zhipengh: I think patches only for bugfix can be merged
03:47:31 <joehuang> #link https://build.opnfv.org/ci/view/multisite/builds
03:47:43 <dmcbride> so, I am going to try to establish another set of milestones for test projects
03:47:43 <dmcbride> for the "E" release
03:47:44 <joehuang> need time to make it stable
03:48:05 <dmcbride> by the way, has everyone had a chance to see the milestone tracking page?
03:48:10 <dmcbride> #link https://wiki.opnfv.org/display/SWREL/Milestone+Compliance+for+Danube
03:48:15 <kubi001> dmcbride: sounds good
03:49:02 <dmcbride> kubi001: I will be looking for input and suggestions from you, Jose, and others about what makes sense for milestones for test projects
03:49:19 <dmcbride> Please feel free to email me with any thoughts or ideas that you have
03:50:14 <kubi001> dmcbride: sure, I will email you after we had a discussion with our project members
03:50:31 <dmcbride> chigang: I think that you were on the main release call earlier in my day
03:50:45 <dmcbride> chigang: there was a lot of talk about CI instability
03:51:04 <dmcbride> chigang: are you seeing that with Compass?
03:51:17 <chigang> dmcbride: yes, It is hard to make baremetal deployment stable
03:51:45 <dmcbride> chigang: is that due to issues with OpenStack integration, or something else?
03:52:29 <chigang> dmcbride: virtual deployment is stable for compass, but for baremetal there are some issues for evironment
03:53:13 <chigang> dmcbride: such as networking connection, hareware
03:53:22 <dmcbride> #info chigang says that virtual deployment is stable, but there are issues with baremetal
03:53:46 <chigang> and there are some probabilistic problem for openstack
03:53:53 <dmcbride> team - feel free to #info your comments as you think is appropriate
03:54:01 <chigang> sure
03:54:44 <dmcbride> chigang: so you think that the issue is the hardware, rather than OpenStack or other software?
03:55:21 <chigang> dmcbride: no, there are still some issues OpenStack
03:56:15 <dmcbride> chigang: in the main release meeting, there were some comments about the v3 keystone API. Has that been an issue for your team?
03:56:39 <chigang> #info there are still some issues for OpenStack and ODL, especially in networking
03:57:32 <chigang> dmcbride: it is fine for Keystone API now, functest team did great work
03:57:49 <dmcbride> chigang: is that a learning issue, or simply bugs in OpenStack?
03:58:20 <chigang> dmcbride: smoke test has been enable for Compass patch verification
03:58:55 <dmcbride> chigang: good to know, thanks
03:59:25 <dmcbride> huzhj: we have not heard from you lately
03:59:46 <dmcbride> huzhj: what is the status of Daisy?
04:00:32 <huzhj> dmcbride: We are still working on solving bm/vm deployment issues
04:00:47 <dmcbride> #info chigang comments that smoke test has been enabled for Compass patch verification
04:01:29 <dmcbride> huzhj: I think that we should consider continuing your work under the E release.  What do you think?
04:01:34 <huzhj> We have sent email to helpdesk to propose a new virtual pod
04:02:29 <huzhj> dmcbride: I am considering this and sorting out tasks remained for Danube in JIRA.
04:02:37 <huzhj> dmcbride: Team will has an internal discussion and the final decision will be made before this Friday. I will send you feedback after that.
04:03:13 <dmcbride> huzhj: I noticed that Escalator has a new PTL.  However, I have not had any communication with him.
04:03:51 <dmcbride> huzhj: given their dependence on Daisy, I believe that they will also need to consider deferring to the E release.
04:04:20 <dmcbride> huzhj: Thank you for your consideration.  Please let me know your thoughts after you meet with your team.
04:04:59 <dmcbride> #topic Milestone 6 - test case implementation and preliminary documentation
04:05:11 <dmcbride> ok - let's talk a little about MS6
04:05:24 <huzhj> dmcbride: I can reach the new PTL of Escalator and disscuss with him.
04:05:42 <dmcbride> huzhj: thank you, I appreciate that
04:06:23 <dmcbride> #info MS6 has two requirements
04:06:52 <dmcbride> #info requirement 1:  implementation of test cases identified in MS2
04:07:44 <dmcbride> #info requirement 2:  (NEW for Danube) directory structure and placeholder documents
04:08:18 <kubi001> dmcbride: Did the  "test cases identified in MS2"  came from new feature projects?
04:09:00 <dmcbride> kubi001: yes, this applies primarily to feature projects
04:09:26 <dmcbride> kubi001: however, test frameworks should be doing self-validation of some sort
04:09:29 <yuyang_gabriel> So new test cases could be add before MS6, right?
04:09:51 <kubi001> dmcbride: In yardstick, we planed some test cases from ETSI TST001 metric. How about those test case?
04:10:18 <dmcbride> yuyang_gabriel: do you mean test cases that were not documented in MS2?
04:10:30 <yuyang_gabriel> dmcbride yes
04:10:39 <dmcbride> kubi001: I should be familiar with that spec, but I am not
04:11:28 <dmcbride> yuyang_gabriel: yes, you should get those test cases documented in the test case database, assuming that you will be able to complete implementation of them by Feb 17
04:11:55 <yuyang_gabriel> dmcbride: Thanks! Will do!
04:12:27 <dmcbride> Sofia Wallin has published a documentation guide
04:12:35 <dmcbride> #link https://wiki.opnfv.org/display/DOC/Documentation+Guide
04:13:07 <dmcbride> this will give you some guidance in setting up your directory structure and creating placeholder documents
04:14:01 <dmcbride> the idea is to force most of the learning process for documentation earlier in the release, in order to reduce confusion and delay toward the end of the release, as we had with Colorado
04:14:39 <dmcbride> this is a new requirement for Danube, so I want to make sure that everyone understands what I'm talking about
04:17:28 <dmcbride> #info if you have questions about documentation, please contact Sofia directly.  Also, there is a documentation working group meeting at 6 a.m. PST tomorrow.  I believe that's 10 p.m. in Beijing.
04:18:15 <kubi001> got it.
04:18:46 <joehuang> Got it. David, sorry to let you konw that it's launch time here.
04:18:56 <fuqiao-laptop> got it
04:18:57 <dmcbride> #info Sofia Wallin email:  sofia.wallin@ericsson.com
04:19:25 <dmcbride> ok guys - I will let you know
04:19:35 <dmcbride> let you "go"
04:19:46 <joehuang> thanks
04:19:47 <dmcbride> good first meeting
04:20:00 <huzhj> Thanks
04:20:02 <yuyang_gabriel> +1
04:20:02 <kubi001> :)
04:20:08 <dmcbride> please email me with questions, agenda ideas, etc.
04:20:23 <yuyang_gabriel> tks!
04:20:29 <fuqiao-laptop> thanks!
04:20:33 <dmcbride> I'm trying to make this meeting as useful as possible for YOU, so let me know what I can do to improve it
04:20:50 <dmcbride> #endmeeting