·Version: QCT uses master branch version to deploy on 2 VMs successfully.
VM1: Feeder + Couchbase
VM2: Druid + Elastic search
·Using MVN build and Intelij to trace the source code and compile successfully
·Build QCT ONAP Casablanca version environment
2.
DataLake Project Scope of Work
[Updated] QCT will take Admin UI as well.
Both parties QCT and CMCC-US got consensus in the meeting that the SOW of this project is as below
·CMCC-US: Datalake Abstraction APIS, Feeder, and Kibana
·QCT: Kafka, DB Conductors, OLAP, and Grafana, UI (Admin)
3.
Use Case
[CCVPN]
·Current status: it’s still under developing and evaluation process.
Template design is done.
SDC onboarding status-ok.
UUI and SO are under development.
Target to freeze code by mid of April (4/11)
Co-work with Huawei and ZTE.
·Data info: There will be multi-cloud data (OpenStack) when Dublin version release. However, network performance data is not included.
·Timeline for getting data: Confirmed in the meeting that QCT can access BJ-lab to get the CCVPN use case data after code freezing. Target to be ready by end of April.
4.
Admin UI
·Admin UI
VNF data modeling (YANG)
Grafana templates
Topic listening
Topic data flow to DB
Topic data processing (Datalake project focuses on monitoring and viewing purpose, the processing and analytics should not be included in it.)
·Prioritize Data info: Need to prioritize what kind of data we would like to show at the overview dashboard since there will be only one page to show on Grafana
·API: RestAPI
5.
Project governance Updated
·Plan to change fromBi-weekly meeting to weekly meeting for closer discussion. Same time @ Tuesday 11:00am-12:00pm (GMT+8)
6.
Others
·Shentao will share UI mockup to QCT next week
7.
Survey
·Guobiao suggested QCT to studyM3DB and Prometheus to see which DB will be more suitable for datalake project.
2 Comments
Yen-Tzu Chu
Date: 2019.03.12
Time: 11:00am-12:00pm
Attendance:
l CMCC-US: Guobiao Mo, Liuman, 田彬彬, 郭春萌, 龔杰
l QCT: H.C, Lee-US/ Dustin-US, Karl, Kate, Ekko, Jeffrey, Rachel Chu
[MM]
NO
Items
Detail
1.
DataLake Framework
Need further discussion on whether adding second Kafka to avoid bottleneck.
2.
Scope of Work
Both parties QCT and CMCC-US got consensus in the meeting that the SOW of this project is as below
· CMCC-US: UIs (Admin), Datalake Abstraction APIS, Feeder, and Kibana
· QCT: Kafka, DB Conductors, OLAP, and Grafana
3.
Use Case
To be discussed
4.
Environment
CMCC currently use ONAP-C version to build up environment.
5.
Project governance
· Build up wechat group for instant message communication
· Setup Bi-weekly meeting on Tuesday 11:00am-12:00pm (GMT+8)
6.
Deliverable
Both parties CMCC-US and QCT agreed that we will do the joint-promotion/ showcase of this project @ ONAP summit and MWC S.H.
· Call-for-paper
· Whitepaper
7.
Survey
· Guobiao suggested QCT to study M3DB, since Hadoop might have scalability issue.
[Next Meeting Topic]
l CMCC share the latest code of this project
l Discuss the framework regarding adding the other Kafaka or not
Yen-Tzu Chu
Date: 2019.03.26
Time: 11:00am-12:00pm
Attendance:
l CMCC-US: Guobiao Mo, Liuman, 田彬彬, 郭春萌
l QCT: H.C, Lee-US, Dustin-US, Karl, Kate, Ekko, Jeffrey, Rachel Chu
[MM]
NO
Items
Detail
1.
Environment Build-up Status Update
· Version: QCT uses master branch version to deploy on 2 VMs successfully.
· Using MVN build and Intelij to trace the source code and compile successfully
· Build QCT ONAP Casablanca version environment
DataLake Project Scope of Work
[Updated] QCT will take Admin UI as well.
Both parties QCT and CMCC-US got consensus in the meeting that the SOW of this project is as below
· CMCC-US: Datalake Abstraction APIS, Feeder, and Kibana
· QCT: Kafka, DB Conductors, OLAP, and Grafana, UI (Admin)
3.
Use Case
[CCVPN]
· Current status: it’s still under developing and evaluation process.
· Data info: There will be multi-cloud data (OpenStack) when Dublin version release. However, network performance data is not included.
· Timeline for getting data: Confirmed in the meeting that QCT can access BJ-lab to get the CCVPN use case data after code freezing. Target to be ready by end of April.
4.
Admin UI
· Admin UI
Topic data processing(Datalake project focuses on monitoring and viewing purpose, the processing and analytics should not be included in it.)· Prioritize Data info: Need to prioritize what kind of data we would like to show at the overview dashboard since there will be only one page to show on Grafana
· API: RestAPI
5.
Project governance Updated
· Plan to change from Bi-weekly meeting to weekly meeting for closer discussion. Same time @ Tuesday 11:00am-12:00pm (GMT+8)
6.
Others
· Shentao will share UI mockup to QCT next week
7.
Survey
· Guobiao suggested QCT to study M3DB and Prometheus to see which DB will be more suitable for datalake project.
[Next Meeting Topic]
l CMCC UI Mock-Up Info Sharing
l QCT Environment Status Update