Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

TOPICDISCUSSION

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.
  •  ACTION: Give RC0 status - Sandeep Shah on RC0 status. Set up call with Sandeep Shah  2: Frankfurt Release Integration Testing Status
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.

  • 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}
  • GET /api/sdnc-config-db/v3/getPCI/{cellId}/{ts}
  • GET /api/sdnc-config-db/v3/getPnfId/{cellId}/{ts}
  • PUT /api/sdnc-config-db/v3/createNbr/{cellId}
  • PATCH /api/sdnc-config-db/v3/modifyNbrHO/{cellId}/{targetCellId}
  • PATCH /api/sdnc-config-db/v3/modifyPci/{cellId}
  • PATCH /api/sdnc-config-db/v3/modifyPnfId/{cellId}
  • DELETE /api/sdnc-config-db/v3/deleteNbr/{cellId}/{targetCellId}

R7 DISCUSSION

TopicDiscussion

R6 / R7

ReadtheDocs

Read the Docs

  •  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 Geissler  → Signoff for R6 May 2020; M0 for R7. If we are approved by TSC as a new project → create a new Repo

R7 TSC /

Project Proposal

Configuration Persistency Service Project Proposal (Oct 25 2019)

  •  ACTION: PERFORMANCE - Open (#@#) open items to get ballpark figures for # API requests.
  •  ACTION: TSC Scheduling & Presentation - Represent at the TSC -   (TSC canceled); Tues R6 status; Thursday for general topics . 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

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:

  1. R7 Project Proposal (identify PTL, Project proposal, setup repo)
  2. =STEP 0= Initial Database Setup
  3. =STEP 0= (Design time), (Setup DB) Yang Model development ORAN specification Yang Model in line with 3GPP. SQL structure.
  4. =STEP 0= Schema design & API
  5. =STEP 1= CMnotify generated by RanSIM extended (final standard format).
  6. =STEP 1= VES generation, Nokia Simulate DU → simulate VES CMNotify message.
  7. =STEP 1-6= CMNotify (Nokia) Integration Step 2,3,4 with SON work Step 1,5,6
  8. =STEP 5/6= Mapping CMnotify contents into DB
  9. =STEP 5a= New Development for Independent component to get VES off of DMaaP
  10. =STEP 6= API Updates
  11. =STEP 6= Interface to RTCDB (writing DB from SDN-R or RCDB-stand-alone-component)

SUMMARY OF THE STEPS FOR RTCDB "HOW IT OPERATES" (Reference):

  • STEP 0: Design time, Setup DB schema & API (Onboarding).
  • STEP 1: xNF (RAN Simulator) GENERATES a VES CMNotify - Wipro SON (R6 Done)
  • STEP 1a: Simulator of VES CMNotify/"Standardsdefined/CM" (Nokia) (R7)
  • STEP 2: DCAE VES Collector RECEIVES the CMNotify (VES) - Nokia (R7)
  • STEP 3: DCAE PROCESSES VES Event- Nokia (R7)
  • STEP 4: DCAE PUBLISHES onto DMaaP - Nokia (R7) 
    Jira
    serverONAP JIRA
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId425b2b0a-557c-3c0c-b515-579789cceedb
    keyREQ-327

  • STEP 5: CCSDK (Controller) LISTENS to DMaaP - Sandeep Shah  (R6 Done) → (R7)
    Jira
    serverONAP JIRA
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId425b2b0a-557c-3c0c-b515-579789cceedb
    keyCCSDK-2392

  • STEP 5a: RTCDB (stand-alone component) LISTENS to DMaaP (R7 new)
  • STEP 6: RTCfgDB UPDATES DB with info - Sandeep Shah / Techmahindra (R6 Done) → (R7)

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)


R7 TopicDescription & Links

Usage of CPS -

OOF/SON/PCI (Cell info)

E2E Network Slicing (Slicing info)

Harmonization (Stnd-Def VES)

Virtual F2F mentioned the C&PS project.

Those other use cases have dependency to Use cases.

We need to attend U/C weekly meetings; sync

Guilin (R7) - Use Cases

Guilin release - functional requirements proposed list

Interaction & Dependencies Use Case

Interaction spreadsheet

Sync between these teams.

Joint meeting - Invitee on a particular in the schedule

TSC Project Proposal

Configuration Persistency Service Project Proposal (Oct 25 2019)

Project Home Pagesample-landingpage Project Home Page
Project Repository

Create Repo: Resources and Repositories

Process to create Repo. Ticket

Architecture S/C

Architecture Proposal

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.

R7 Wiki PageConfiguration & Persistency Service R7


R7 GuiLin Development

CMNotify specification

  •  (Watch for): R6 VES 7.1.1 Baselined https://gerrit.onap.org/r/c/vnfrqts/requirements/+/100876  (VES Event Reg review) and https://gerrit.onap.org/r/c/vnfrqts/requirements/+/100867 (VES Event Listener review)
    R7 VES 7.2 review open new updates to the VES listener should include CM VES event. Participate review.
  •  ACTION: R7 VES Common Header update to align with 3GPP SA5 (CR) Nokia/ ATT/ Orange/ Ericsson. Presentation for Monday 2PM UTC on Alla's Req S/C call. "ONAP-ORAN Harmonization". Vimal, Marge, Cormac, Damian. Domain "Standards-Defined" NameSpace "3GPP-CM-xxxx"
State Management

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.

Cell Introduction

Michela Bevilacqua  - Introduction of a Cell

Slides from SON Use Case -  How do we think of LCM of a Cell from SON PoV & C&PS PoV.

How will a cell be managed?

a new cell is provisioned from a CU/DU. a "read" operation that a cell exists.

CELL is a LOGICAL ENTITY ... Should a cell be seen xNF (PNF, VNF, ANF)

How could ONAP discover there is a cell? does it need to be on-boarded? when creating a service, do you need to create a cell?

with resources, will you also have a cell instance?

today when we have a PNF we onboard the PNF package, create res descriptor & service descriptor containing the resource descr; done for any xNF.

package is distributed at run time.

Yang model for CU/DU has notion of Cell. process to sync up, discovering whether there is a new cell.

OOF / SON / PCI - Need know about existence of a Cell. In that U/C "yes we need to know the cell, we assume that info is in C&PS"

two kinds of errors - #1 go to config a cell "i don't have this cell" -  #2 new cell exists and ONAP doesn't know about it. sync mechanism.

What is the relation to C&PS, how could cell info be updated?

Onboarding a xNF, when the xNF instance, the configuration mechanism you can get info about cells associated with a xNF.

Cell is a service? that configures xNFs.

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

State Database PoC

Bruno Sakoto  , Olivier Phénix

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

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:

  1. 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)

  1. The details are stored ‘locally’ in a DB in SDN-C for example. In the next release, it is moved to CPS.

...