Versions Compared

Key

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

Table of Contents

Description

5G RAN physical/logical topology information (SDN-R) Core & RAN elements. 5G Configuration, provisioning of a 5G Network. SDN-R should contain the 5G Network Topology. CM Audit. CM Mediation. CM run-time storage / data persistency (MariaDB)

...

TopicWiki Link
PROJECT PROPOSAL

Configuration Persistency Persistence Service Project Proposal (Oct 25 2019)

Target for R7 Guilin

(All Project Proposals)Proposed ProjectsNew Project Proposals
COMPONENT DESCRIPTIONARC RunTime DB Component Description - R6 Frankfurt
ARCHITECTURE FLOWSARCHCOM: InfoFlow - RunTime Config DB Information Flow

BUSINESS DRIVER

This section describes Business Drivers needs.

...

  • CM Audit - Auditing configuration parameters for consistency, accuracy.
  • CM Mediation - Configuration functions to correct and mediate settings.
  • Data Persistency - Storage of run-Time data storage. A configuration database (such as Maria DB) for data persistency and access to configuration information.
  • Topology Management - the configuration and view of a RAN network topology.
  • Standardizing - Harmonizing management between vendors, and alignment to standards bodies such as 3GPP for CM topics.
  • Golden Standard - Managing CM with Golden "Templates" and base-lined parameters.

DEVELOPMENT IMPACTS

The REQ (requirements) epic for this Use Case is 

...

PROJECTPTLUser Story / EpicRequirement
A&AIEpic #1: Base RunTime DB Development

E1: A&AI Provides initial physical inventory info to ConfigDB


AAF

APPC


CLAMP

CC-SDK (Controller)
Epic #1: Base RunTime DB DevelopmentE1a. Provide RunTime DB yang model to RunTime DB.
DCAEEpic #1: Base RunTime DB Development

E1a. VES/DCAE pathway to provide configuration notification RunTime DB

E1b. VES Event Listener Document to be updated.

E1c. New VES Event domain (CM Notify) to be introduced (DCAE VES Listener)

Jira Legacy
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyDCAEGEN2-1769

DMaaPEpic #1: Base RunTime DB DevelopmentE1a. VES/DCAE pathway to provide configuration notification RunTime DB
External API

MODELINGEpic #1: Base RunTime DB DevelopmentE1a. Design-Time modeling; Platform ONAP Model for RunTime DB to build initial structure. Use of onboarded Yang model (in vendor PNF package).

Multi-VIM /

Cloud



OOFShankaranarayanan Puzhavakath Narayanan

POLICY



PORTAL

ControllerEpic #1: Base RunTime DB Development

SDN-R and Controller Impact

E1a. Provide RunTime DB yang model to RunTime DB.

E1a. SO + Controller pathway BACK to the PNF through Netconf to update RunTime DB.

SDC

SO

VID


VNFRQTS

VNF-SDK

CDS

List of PTLs:Approved Projects


ARCHITECTURE DISCUSSION

The architecture discussion held on Sept 10, 2019 and Sept 3, 2019 centered around the discussion about where the RunTime DB should architecturally live.

...

ARC RunTime DB Component Description - R6 Frankfurt

MEETINGS

 - 

DATEMeetingWiki Page

 

RunTime Config DB discussion2019-10-18 Meeting notes

 

RunTime Config DB team meeting Project ProposalRunTime Config DB Meeting notes Oct 25, 2019

 

RunTime Config DB team meeting Project ProposalRunTime Config DB Meeting notes Nov 1, 2019

 

RunTime Config DB team meeting Project ProposalRunTime Config DB Meeting notes Nov 8, 2019

 

RunTime Config DB team meeting Project ProposalRunTime Config DB Meeting notes Nov 15, 2019

 

RunTime config DB team meeting project proposalRunTime Config DB Meeting notes Dec 13, 2019

 

RunTime Config DB team meetingRunTime Config DB Meeting notes Jan 10, 2019

 

RunTime Config DB team meetingRunTime Config DB Meeting notes Jan 24, 2019

 

RunTime Config DB team meetingRunTime Config DB Meeting notes Jan 31, 2019

 

RunTime Config DB team meetingRunTime Config DB Meeting notes Feb 7, 2019

 

Project ProposalRunTime Config DB Meeting notes Feb 14, 2019

 

Project ProposalRunTime Config DB Meeting notes Feb 21, 2019

 


RunTime Config DB Meeting notes Feb 28, 2019

 

R7 ProposalRunTime Config DB Meeting notes Mar 6, 2020

 

R7 ProposalRunTime Config DB Meeting notes Mar 13, 2020

 

R7 ProposalRunTime Config DB Meeting notes Mar 20, 2020

 

TSC

Peer Review

Name Discussion

RunTime Config DB Meeting notes Mar 27, 2020

 

Name DiscussionRunTime Config DB Meeting notes Apr 3, 2020

 

Proposal Review from TSC / IssuesRunTime Config DB Meeting notes Apr 10, 2020

 

Read the Docs

R6 RC0 status

RunTime Config DB Meeting notes Apr 17, 2020

24  

sample-landingpage Project Home Pagehttps://wiki.lfnetworking.org/display/LN/2020+April+Technical+Event+Schedule

 

DiscussionConfiguration & Persistency Service Meeting notes Apr 24, 2020

 

TSC Q&A answersConfiguration & Persistency Service Meeting notes Apr 29, 2020



TBDJoint Discussion with Harmonization Team
TBD

Joint Discussion with Network Slicing Team


TBDJoint Discussion with OOF/SON/PCI team






SUPPORTING FILES:

name250


ANSWERS TO TSC (May 13 2020)

ConfigurationPersistencySvc_13My2020v5.pptx

DocumentFiles
Run Time DB Overview and presentation

View file
nameDataPersistencyRunTimeDB_10162019.pptx
height250

Run Time DB Architecture Presentation (Made to Arch S/C) with discussion
View file
height
Data Persistency Service

View file
nameDataPersistencyRunTimeDB Technology Choices-EricssonOct212019.pptx
height250


INTEGRATION & TESTING

This section discusses the Testing & Integration for R6 PnP

  1. WHO IS TESTING - what company, team, and people will be doing the testing & responsibilities for testing.
  2. TEST ENVIRONMENT - which does the lab & test environment.
  3. RESOURCES NEEDED - what resources are needed.
  4. WHO IS CONTRIBUTING RESOURCES - what resources will be provided and by whom/what company.
  5. NETWORK CONNECTIVITY - Network connectivity
  6. TEST/INTEGRATION LEADERSandeep Shah , Dongho Kim
  7. INTEGRATION LEAD DEFINITION - ONAP "Use Case/Requirement" Integration Lead

RunTime Config DB Integration Test Cases. These can be navigated to from the Integration team page hierarchy.

...