Atlassian uses cookies to improve your browsing experience, perform analytics and research, and conduct advertising. Accept all cookies to indicate that you agree to our use of cookies on your device. Atlassian cookies and tracking notice, (opens new window)
Configuration Persistence Service Meeting Notes & Recordings
Jan 08, 2021
Date Range
May 1, 2020 through December 31, 2020
R6 DISCUSSION
TOPIC
DISCUSSION
TOPIC
DISCUSSION
R6
CCSDK-based Solution
Project as part of CCSDK ( @Yuriy Malakov )
ACTION: @Sandeep Shah Presentation of new architecture with CCSDK (@Yuriy Malakov ). How much bandwidth/capacity does Sandeep Shah have.
ACTION: Development demo & progress (1) ORAN Yang models & data schema not available yet (waiting) & 5G Service Modeling U/C: 3GPP TS28.541/TS28.540. maps to a data structure we want to support. (2) can proceed to Dockerize solution. R4 MariaDB solution. could extend the model. (3) Review work from Ted. waiting for project.
(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 CPS (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.
GET /api/sdnc-config-db/v3/getCell/{cellId}
GET /api/sdnc-config-db/v3/getCellList/{networkId}/{ts}
GET /api/sdnc-config-db/v3/getNbrCellsNetwork/{networkId}
GET /api/sdnc-config-db/v3/getNbrList/{cellId}/{ts}
ACTION: Update ReadtheDocs https://git.onap.org/integration/tree/docs - Jira under Integration - invite team for review - invite PTL (Morgan R.) -Gerrit PTL submission +1 from reviewers. committer/Morgan +2 (someone in Integration project will do the Merge)
New project → Repo → DOC directory (RST) in that Repo @Andreas Geißler → Signoff for R6 May 2020; M0 for R7. If we are approved by TSC as a new project → create a new Repo
ONAP Architecture Review process:Project Architectural Review Requirements and Process (Draft) to M1 Project PTLs/Feature Sponsors request a review by email from the chair of the arch subcommittee. The chair of the arch subcommittee creates a JIRA issue for the review and emails a link to the project PTL. The project PTL/Feature Sponsor adds the JIRA issue link to the architecture review JIRA task in the M1 epic, as confirmation that a review has been requested.
PFB comment from TSC for the OOF SON requirement. With reference to resource commitment:
Policy: Pam - Shall I indicate AT&T shall cover it, while we subsequently discuss what all enhancements we can do in Guilin timeframe, as well as check reg. some of the aspects where you indicated use case team should contribute (e.g., separate Drools file, which would have to be done by Wipro).
SDN-R/CCSDK:Sandeep - Shall I indicate IBM?
CPS: Shankar/Ben - Given the Guilin release timeframe, I think we have to go for the simplest option (1) and indicate no impact to CPS, where we only change the yang models, and SDN-R continues to do the mapping. modify CCSDK solution to extend interfaces (OOF/SON/PCI Team updates). R7 Solution of C&PS (evolution "ConfigDB" = C&PS) Hard code information
(Generic Requirement) to consider Non-Real Time RIC @Pawel Slowikowski
Model Driven C&PS PoC
Proposal (by @Ciaran Johnston (Ericsson) et al) as a step of Model Driven ONAP, Model Driven CPS. See slides in the Project Proposal page, and also in the R7 CPS 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 CPS, uS on-boarding in CCSDK. If you plan to do modeling work in R7, consensus from Arch S/C. Answer: would need CPS 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
May 22, 2020 - Looking at internal sourcing to get development resources. Sync with @johnsont
Jul 3, 2020 - Status ready to cut code off of x CC-SDK repo. Ongoing analysis. Resourcing Toine has started, 2 new people will be added in August 1, 2020. Present to Architecture S/C before end of July. Engaged Modeling S/C. Visible Yang modeled to be consumed in ONAP. Modeling work will happen in
Choice of IT DB (feeds in). Choice of DB to best fit to the use case. Implement TSDB in PostGres or MariaDB, SQL extensions for TS analysis. Issue is how good is the performance. Not as good as specialized Influx DB. Postgres 10 direct it to store TS DB similar to influx. Database derived from postgres. Timescale DB derived from postres.
Bell Canada Leading a PoC related to State management using the CPS project. Communication via Kafka topic (DMaaP).
Question: Are there dependencies on platform components? Answer: TBD
Wiki: in progress
@Former user (Deleted) - Listen to Recording from May 8, 2020
Question from @s.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 CPS to copy inventory data ANSWER: We are going to prepare a public page and share with you.
Network Slicing & C&PS
CPS 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:
The impacts to CPS (which I expect to be persistence & retrieval of some basic RAN slice config related data) can be handled by existing CPS committed resource
(or)
The details are stored ‘locally’ in a DB in SDN-C for example. In the next release, it is moved to CPS.
(EMAIL) from Swami May 27, 2020
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.
ACTION: PERFORMANCE - Open (#@#) open items to get ballpark figures for # API requests.
ACTION: TSC Scheduling & Presentation - Represent at the TSC - May 21, 2020 (TSC canceled); Tues R6 status; Thursday for general topics May 28, 2020 . Stakeholders of TSC presocialization Q&A. Schedule pre-review meeting w/ people who asked questions. SCHEDULE MAY 28 TSC 2020-05-28 and scheduled for JUNE 4 2020 TSC 2020-06-04
ACTION: Deadline? - M0/M1 project proposal objective by the TSC.
ACTION: Peer Review Process Step #1 - ONAP Projects - Presentation to ARCH S/C
TERMINOLOGY DISCUSSION
TOPIC
DESCRIPTION
TOPIC
DESCRIPTION
C&PS versions
CPS 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, "CPS 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.
CPS 1.1- This is the continuation of the CPS 1.0 solution (see above). Updates will involve schema and interface changes for additional data supported in the CPS database. This will be introduced in the R7 Guilin time frame. Thus, when someone refers to CPS, in the R7 time frame they are referring to the CPS 1.1 solution. Additionally, there are two CPS related PoC going on the Model-Driven CPS and State Management PoC (Bell Canada) and when referring to R7 CPS, work done in these PoC are also included.
CPS 2.0- CPS 2.0 is the stand-alone project. In R8 Honolulu, the goal is to have CPS 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.