Before editing please read instructions here.

 Description of Use Case / Requirement:

This use case aims at realizing ONAP-based SON/Automation functionality for radio networks aligned with O-RAN. In the Montreal release, it will focus on:

• Enhancements for RAN-Sim
  • Convert RAN Simulator from docker based deployment to k8s pod deployment.
  • Create Helm charts for RAN Simulator and Honeycomb servers.
  • Integrate RAN Sim Helm chart with the OOM Deployment.
  • Create RAN Service using RAN SIM helm charts
  • Create CDS based workflows for Honeycomb Day-1 Config updates.
• Processing of CM VES update notifications to update CPS DB
  • Use Cloud Events format (CNCF) for CPS event messages, e.g. DMI plug-in to NCMP
  • Persist the CM change in CPS DB (processed by NCMP)
  • Extend the DMI plugin codebase as needed

Owners (one of these should be the Assignee - use @ notation):

nkshankar

Link to HLD/LLD (if any):

Note: We don't know all the details of NFRs. 

Dependency Relationships with Other Projects:

 RAN-Sim IMPACT: C (Simulation Repo, Not ONAP Project)

• Impact Type: C
• Company Engagement: CapGemini
• Resources: xyz (People)
• Support Status: S

Project DCAE IMPACT: No change to API

• Impact Type: Part of test (VES Collector, VES parser)
• Company Engagement: Capgemini
• Resources: xyz (People)
• Support Status: 
• Non-Functional Requirement Support: REQ-xxx, REQ-yyy

Project CPS IMPACT: Code change

• Impact Type: Adaptation of NCMP/DMI. No change to API
• Company Engagement: Ericsson, Capgemini
• Resources: xyz (People)
• Support Status: 
• Non-Functional Requirement Support: REQ-xxx, REQ-yyy

Project CCSDK/SDN-C IMPACT: None

• Impact Type: Part of test
• Company Engagement: CapGemini, AT&T
• Resources: xyz (People)
• Support Status: S
• Non-Functional Requirement Support: REQ-xxx, REQ-yyy

Project Policy IMPACT: None

• Impact Type: Part of test
• Company Engagement: AT&T, Ericsson
• Resources: xyz (People)
• Support Status: 
• Non-Functional Requirement Support: REQ-xxx, REQ-yyy

Project OOF IMPACT: None

• Impact Type: Part of Test
• Company Engagement: TBD
• Resources: xyz (People)
• Support Status: 
• Non-Functional Requirement Support: REQ-xxx, REQ-yyy

Integration Leads (use @ notation): 

 vvarvate 
 

API Impacts in I-release:

Summary: We do not expect changes in APIs. The tasks involve completing carry-over work and creating configuration features for existing modules.