08:02:50 <yujunz> #startmeeting QTIP weekly meeting
08:02:50 <collabot> Meeting started Wed Oct 12 08:02:50 2016 UTC.  The chair is yujunz. Information about MeetBot at http://wiki.debian.org/MeetBot.
08:02:50 <collabot> Useful Commands: #action #agreed #help #info #idea #link #topic.
08:02:50 <collabot> The meeting name has been set to 'qtip_weekly_meeting'
08:03:02 <yujunz> #topic rollcall
08:03:06 <yujunz> #info Yujun Zhang
08:05:17 <yujunz> Agenda here
08:05:19 <yujunz> #link https://etherpad.opnfv.org/p/qtip-meetings-2016-10-12
08:07:39 <yujunz> Seems she is busy now. Let's start. Taseer SerenaFeng
08:07:49 <yujunz> #topic action followup
08:08:19 <yujunz> #info AP1: @zhihui_wu contact Taseer to follow up on selecting test suites
08:08:24 <yujunz> It seems already done
08:08:32 <Taseer> yes.
08:08:51 <yujunz> Thanks Taseer
08:09:10 <Taseer> no problem. Any time.
08:09:18 <yujunz> #link https://jira.opnfv.org/browse/QTIP-104
08:09:31 <yujunz> This patch allows us to select a single benchmark to run.
08:09:36 <yujunz> Which will be more flexible.
08:09:53 <yujunz> #info AP2 @yujunz to confirm RESTful api progress
08:10:24 <yujunz> As far as I know, Zhifeng has finished most part of it.
08:10:52 <yujunz> But we shall continue with new APIs when required.
08:11:17 <yujunz> The restful api will allow more detail execution result to be retrieved.
08:11:32 <yujunz> #topic Danube release plan
08:11:49 <yujunz> #link https://wiki.opnfv.org/display/qtip/Danube
08:12:23 <yujunz> OK, I see zhihui_wu
08:12:31 <zhihui_wu> #info zhihui
08:12:33 <yujunz> Put the link again
08:12:35 <yujunz> #link https://wiki.opnfv.org/display/qtip/Danube
08:12:40 <zhihui_wu> sorry for delay
08:13:32 <yujunz> Before we go detail into the release plan. Let's have an overview of the QTIP roadmap in next years.
08:14:09 <yujunz> #link https://wiki.opnfv.org/display/qtip/Vision
08:14:32 <yujunz> Err, I forgot the desktop sharing
08:14:33 <yujunz> Let
08:14:39 <yujunz> Let's try zoom
08:14:51 <yujunz> https://zoom.us/j/539828803
08:15:35 <yujunz> So QTIP will focus on the performance index
08:16:30 <yujunz> Can you see my screen?
08:16:50 <Taseer> yes.
08:17:08 <yujunz> So it a "T"
08:17:29 <yujunz> The project shall be driven by application (the blue part)
08:17:52 <yujunz> And supported by some external projects (the brown part)
08:18:17 <yujunz> Developing the framework (the green part)
08:18:47 <SerenaFeng> are you speaking?
08:19:03 <yujunz> No
08:19:04 <yujunz> No audio
08:19:28 <yujunz> I didn't book a meeting room
08:19:53 <SerenaFeng> that's strange
08:20:11 <yujunz> Will this be better.
08:20:15 <yujunz> Sorry, next time
08:20:17 <yujunz> Try to book one
08:20:28 <SerenaFeng> next time you want to have audio meeting, told us first, then we can prepare the ear phone
08:20:35 <SerenaFeng> zoom is ok, I think
08:21:02 <yujunz> Not used before. Not sure what you will see when I enter full screen
08:21:06 <zhihui_wu> I will miss the zoom since I do not install the app .
08:22:22 <yujunz> OK, let's continue
08:22:23 <zhihui_wu> It will spend  12m to download the app :(, low speed, long time~
08:22:32 <yujunz> Any question on the vision?
08:22:49 <yujunz> The text in bold are category
08:22:56 <yujunz> Each category is expandable
08:23:06 <yujunz> For example on evaluation part
08:23:18 <yujunz> We have already some comparison between VM and BM
08:23:36 <yujunz> And we may also evaluate some dedicated technique in the future
08:23:44 <SerenaFeng> why yuanyue is there?
08:23:54 <yujunz> I'm using his account
08:23:58 <SerenaFeng> sharing meeting?
08:24:01 <yujunz> That's me :-)
08:24:44 <yujunz> For this release, we will not spend too much time on it
08:25:17 <yujunz> The italic text are things not yet implemented
08:25:50 <yujunz> for compliance, it means we shall define dedicated index for the project
08:26:00 <yujunz> For Pharos, we shall have a Pharos qpi
08:26:08 <yujunz> qpi stands for QTIP Performance Index
08:26:39 <yujunz> How the index is calculated will be defined with Pharos team
08:26:47 <yujunz> Doctor is another example.
08:27:29 <yujunz> Currently it evaluates the performance of fault management and give a total time cost as result
08:28:00 <yujunz> So we want to help them answer the question: is current NFVI qualified for doctor application?
08:29:05 <yujunz> Mapping to the framework, it is benchmark and reporting
08:30:00 <yujunz> When things go further, we want to assist in analyse what are the factors affecting the result
08:31:19 <yujunz> When enough data is collected, we might be able to predict the limit on a given hardware
08:31:34 <yujunz> And giving advice on how to improve the performance
08:32:10 <yujunz> That's how we will go deeper in the performance benchmark.
08:32:50 <yujunz> To achieve that, we shall need all the supporting blocks.
08:33:17 <yujunz> test tools, installers, and infrastructure for development and demonstration
08:33:33 <yujunz> That would complete the whole map of QTIP
08:34:11 <yujunz> Any questions?
08:34:50 <SerenaFeng> A big blueprint
08:34:59 <SerenaFeng> many rivers to cross
08:35:16 <SerenaFeng> :)
08:35:19 <yujunz> Yes, many many rivers
08:35:54 <SerenaFeng> but need to achieve it step by step :)
08:36:07 <yujunz> OK, let's head for the next river: Danube
08:36:45 <yujunz> Each release cycle is about six months
08:37:00 <yujunz> So we can not put all into one release.
08:37:34 <yujunz> In release D, we shall go as far as benchmark->report
08:37:51 <yujunz> Maybe some analysis
08:38:05 <yujunz> Because there are some cross project issue with doctor
08:38:12 <yujunz> Let me find the link
08:38:50 <yujunz> #link https://jira.opnfv.org/browse/DOCTOR-72
08:40:19 <yujunz> If this ticket can provide some data on analysis, then we can provide a platform for performance analysis
08:41:18 <yujunz> But honestly, I'm not sure I will have enough time to complete it in release D
08:42:08 <yujunz> So on features and enhancement, they are mostly infrastructure construction
08:42:16 <yujunz> So it will be easier to develop application
08:42:43 <yujunz> We may use doctor and Pharos as sample, let's see how far we can go.
08:43:17 <yujunz> On the supporting part, I have contacted the PTLs of installers
08:43:24 <yujunz> Four of them has promised some kind of supporting
08:43:53 <yujunz> But we don't have too much resource, maybe one or two to make the framework complete will be enough
08:44:17 <yujunz> Documentation is another delivery, one for developer and one for user
08:44:33 <yujunz> Security is something we need to followup with OPNFV policy
08:44:44 <yujunz> to meet the release criteria
08:44:55 <yujunz> Any questions?
08:45:24 <Taseer> Where do we stand now ?
08:45:50 <yujunz> The non-italic part
08:46:44 <yujunz> We have some sample test suite
08:46:49 <yujunz> Some test tools
08:46:55 <yujunz> And supported by fuel installer
08:47:17 <yujunz> The CI is in place
08:47:19 <yujunz> Benchmark can be done.
08:47:23 <yujunz> Report is on going
08:47:42 <Taseer> Ok. I understand.
08:48:23 <yujunz> For this release, we want to make the existing things more mature and easier to expand
08:48:56 <yujunz> The we can have a solid base to go wider in future releases
08:49:22 <yujunz> OK, it seems I have used too much time
08:49:47 <yujunz> Let's have a quick review on active sprint
08:50:14 <yujunz> SerenaFeng I'll talk with you on the docker CI issue offline
08:50:24 <yujunz> It comes from releng
08:50:43 <yujunz> #topic active sprint followup
08:50:48 <yujunz> #link https://jira.opnfv.org/secure/RapidBoard.jspa?projectKey=QTIP&rapidView=135
08:51:00 <SerenaFeng> I have solve it
08:51:16 <SerenaFeng> I will submit the patch soon
08:51:21 <yujunz> Thanks.
08:52:11 <yujunz> In the active sprint due next week
08:52:18 <yujunz> some tasks has been done
08:53:31 <yujunz> Zhifeng is not online, I will check with the issues assigned to her later
08:54:09 <yujunz> The kibana instance for dev is up on kibana.qtip.openzero.net
08:54:40 <yujunz> Taseer how could we submit data to this instance?
08:54:50 <yujunz> Credential required?
08:56:03 <Taseer> curl -X PUT http://qtip.openzero.net:9200/db/type filename
08:56:23 <yujunz> Looks good to you? SerenaFeng
08:56:27 <SerenaFeng> I think he just has deployed elk
08:56:42 <Taseer> this is the default way of pushing data.
08:56:51 <SerenaFeng> I will need to deploy kibana_dashboard project on the vm
08:57:11 <SerenaFeng> then I need the whole access to the vm
08:57:20 <yujunz> OK, send me your public key and I will grant you access
08:57:28 <SerenaFeng> ok
08:57:50 <yujunz> But I would prefer you do the configuration in a managed way
08:58:12 <SerenaFeng> no need special configuration
08:58:19 <SerenaFeng> just need to run the software
08:58:44 <SerenaFeng> get data from TESTDb, and transfer to elasticsearch, then show on kibana
08:58:53 <SerenaFeng> still lots of need to be done
08:59:05 <SerenaFeng> but it can be deployed now
08:59:20 <yujunz> OK.
08:59:57 <yujunz> Time is up.
09:00:07 <yujunz> The dashboard is the main target for this sprint
09:00:40 <yujunz> Thanks all. Any issues we can continue discussion in IRC and email
09:00:43 <yujunz> #endmeeting