Project Name:
- Proposed name for the project:
RunTimeConfigDB - Proposed name for the repository:
RunTimeConfigDB
Project description:
The RunTime Config DB is a platform component that is designed to serve as a data repository for Run time data that needs to be persistent. The RunTime Config DB is characterized by the following purpose statements:
PURPOSE OF RUNTIME CONFIG DB:
REPOSITORY - The types of data that is stored in the Run-Time data storage repository for:
(1) CONFIGURATION PARAMETERS - These are configuration parameters that are used by xNFs during run time. For example a 5G Network configuration parameter for a PNFs that sets the mechanical tilt setting upon installation.
(2) OPERATIONAL PARAMETERS - These are parameters that are derived, discovered, computed, requested, or used by xNFs during run time. For example 5G Network PNFs may need to adjust a tower electrical antenna tile. These operational parameters are Exo-inventory information meaning it is information that doesn't belong in A&AI.
- (3) POLICY INFORMATION - This type of information stores policy information that orchestrates how ONAP shall operate. For example, Policy, CLAMP Control Loops, and Operational Views.
- DATA LAKE - RunTime Config DB is designed to be a common services data layer which can serve as a data lake.
- SYNCING - The RunTime Config DB enables the ability to sync data between ONAP & the xNFs. The source of truth can be defined.
- CM FUNCTIONS - Enables OSS configuration, optimization, and LCM operations.
- CM FUNCTIONS - Enables future CM & Data management functions such as xNF Crash restoration, data restoration, data history management and auditing.
- CENTRAL/DISTRIBUTED - Because it is a common service, it is part of an ONAP installation, so it could be deployed with either an Edge ONAP installation or a centralized ONAP installation.
- SCOPE - The Run Time DB could also serve as the data storage to store for example ONAP Policy Rules, CLAMP Control Loop, Operational Views and also accommodate other resources.
