Date
May 1, 2020 through December 31, 2020
R6 DISCUSSION
TOPIC | DISCUSSION |
---|---|
R6 CCSDK-based Solution | Project as part of CCSDK ( Yuriy Malakov )
|
R6 Integration Updates | (Swami) For the CPS requirement in Guilin (REQ-322), we noticed that Reshma/my name is included as Integration Leads. For the impacts related to SON use case, which will be covered as part of the SON use case testing, this is OK for us. However, we are not be able to commit resources at this time for testing additional aspects (if any) – of course, I can still check during the time of testing reg. the feasibility to cover any additional aspects. (Swami): June 10, 2020: The Config DB which is the predecessor C&PS (or as we knew it earlier) supports CRUD operations – in particular it supports APIs such as the foll. It’s APIs are used by SDN-C (R) to write into it, and by SDN-C (R), OOF and DCAE (SON-Handler MS) to read from it. I am not sure if there is a formal documentation in readthedocs – perhaps Sandeep can confirm.
|
R7 DISCUSSION
Topic | Discussion | ||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
R6 / R7 ReadtheDocs | Read the Docs
| ||||||||||||||||
R7 TSC / Project Proposal | Configuration Persistency Service Project Proposal (Oct 25 2019)
| ||||||||||||||||
R7 Guilin Content / requirements | Requests for R7 Requirements are up. Guilin release - functional requirements proposed list Timeline - Sign-off for R6 is May 7. Historically M0 kickoff for R7 is May 7th PROPOSALS FOR R7 GUILIN FOR WHAT WE PLAN TO BE DOING IN R7:
SUMMARY OF THE STEPS FOR RTCDB "HOW IT OPERATES" (Reference):
A&AI FLOWS: STEP 1...6: Initial A&AI setup of DB (the setup of the DB with the initial set of all xNFs a "getall") STEP 1...6: A&AI Update (e.g. a new xNF is added or deleted)
For Honolulu REQ-Jira (copied from REQ-322) Configuration & Persistency Service: (Code Impact)
Email Swami: PFB comment from TSC for the OOF SON requirement. With reference to resource commitment:
| ||||||||||||||||
R7 GuiLin Development | CMNotify specification
| ||||||||||||||||
Model Driven C&PS PoC | Proposal (by Ciaran Johnston et al) as a step of Model Driven ONAP, Model Driven C&PS. See slides in the Project Proposal page, and also in the R7 C&PS Wiki. Question: Graph DB? Answer: type of data from xNF to be hierarchical which would fit in a Graph DB. doesn't have to be that though. Likely to be one or more underlying database technologies. time series. Question: Model driven C&PS, uS on-boarding in CCSDK. If you plan to do modeling work in R7, consensus from Arch S/C. Answer: would need C&PS team, modeling, Arch S/C to be aligned. Want something that can be demonstrated/delivered in R7. Question: Are there dependencies on platform components? Answer: TBD - Looking at internal sourcing to get development resources. Sync with theodore johnson https://en.wikipedia.org/wiki/Master_data_management
| ||||||||||||||||
State Database PoC | Bell Canada Leading a PoC related to State management using the C&PS project. Communication via Kafka topic (DMaaP). Question: Are there dependencies on platform components? Answer: TBD Wiki: in progress Bruno Sakoto - Listen to Recording from Question from Samuli Silvius - State Management was interesting could we get the basic arch picture and def lines of description? Having references e.g. to A&AI is better solution than planned C&PS to copy inventory data ANSWER: We are going to prepare a public page and share with you. | ||||||||||||||||
Network Slicing & C&PS | C&PS w.r.t. Network Slicing: (Swami) For the Network Slicing use case, we are still working out the details w.r.to RAN slicing, and are also in discussion with O-RAN folks. We expect it to take 1-2 weeks to conclude. Once it is fairly clear, we should discuss reg. the CPS impacts for Guilin. For now, we have created Jira SDNC-1199 for the CPS requirements for this use case. As of now, we may not have resources to commit for implementing the updates in CPS (but still checking), in this scenario, there are 2 alternatives:
(or)
(EMAIL) from Swami For Network Slicing use case, for RAN Slicing, we will be needing a minimal set of information elements for initial RAN configuration and network slice-subnet specific configuration. Our current R7 GUILIN proposal is to extend ConfigDB with the required aspects for Guilin release, and once CPS takes off as an official ONAP project in HOLULU R8 H-release, the work can be taken over into CPS. |
TERMINOLOGY DISCUSSION
TOPIC | DESCRIPTION |
---|---|
C&PS versions | C&PS 1.0 - This is the evolution of ConfigDB in the CC-SDK / SDN-C. this solution was initially coded in R3 for the OOF/SON/PCI Use Case and was referred to as "ConfigDB" using a MariaDB ITDM solution. Because in R7 GuiLin planning, there is some clarity needed to identify the different tracks of development, the notation is introduced here, "C&PS 1.0" to allow people to have a common "language" to refer to a body of work. This was done in the R6 time frame. C&PS 1.1 - This is the continuation of the C&PS 1.0 solution (see above). Updates will involve schema and interface changes for additional data supported in the C&PS database. This will be introduced in the R7 Guilin time frame. Thus, when someone refers to C&PS, in the R7 time frame they are referring to the C&PS 1.1 solution. Additionally, there are two C&PS related PoC going on the Model-Driven C&PS and State Management PoC (Bell Canada) and when referring to R7 C&PS, work done in these PoC are also included. C&PS 2.0 - C&PS 2.0 is the stand-alone project. In R8 Honolulu, the goal is to have C&PS become its own stand-alone project. Thus, a presentation to the Architecture S/C and TSC will be made again to petition for a stand-alone project. |
RECORDING
Date | Zoom Recording | Audio Only | |
---|---|---|---|
| |||
| |||
| TSC Answers | ||
| PoC | ||
| |||
| C&PS May 28 Recordings | ||
| C&PS May 29 Recordings | ||
| |||
| |||
| |||
| VDDF C&PS Overview | ||
| VDDF MD C&PS PoC | ||
| |||
ATTENDEES WEEKLY ROSTER