STATUS: Draft
The RunTime DB function provides storage for real-time run-time configuration and operational parameters that need to be used by ONAP.
RunTime DB provides the following interfaces:
Interface Name | Interface Definition | Interface Capabilities | Version | Status | Consumed Models |
---|---|---|---|---|---|
RTDBE-1 | RunTime DB Interface. | An interface to create, update, retrieve, query, delete information from the RunTime DB. CREATE - UPDATE - RETRIEVE - QUERY - DELETE INFORMATION - SDC (Controller) - RTDB DMaaP MR Controller to RTDB RESTful API DCAE VES Collector to RTDB DMaaP MR ACCESS: - SO, DCAE, A&AI, Controllers (CDS, APPC, SDNC) will have default read/write access to RunTime DB - Other components will have default read-only access to RunTime DB but can be given access on a per record basis. | |||
RTDBE-2 | RunTime DB Graphical User Interfaces | Provides the capability to view and edit the data currently in the RunTime DB. This GUI is meant to allow an operations user of ONAP to view the data stored in the RunTime DB during Run Time operation. |
Note: xxxI interface is a Component internal interface. xxxxE interface is a component external interface
The current API documents can be found at:
RTDB consumes the following Interfaces:
Interface Name | Purpose Reason For Use |
---|---|
SDCE-7 | This interface is used to receive the service and resource artifacts (CSAR Package) from SDC. This allows the RunTime DB to process the design-time Yang model artifacts onboarded. STEPS: (1) ONBOARDING - A vendor onboards artifacts describing the parameters supported for their PNFs and VNFs in xNF Package. (2) SDC CATALOG - The onboarded artifacts are stored in the SDC Catalog after onboarding and validated (VNF-SDK). (3) CSAR DISTRIBUTION - The contents of the artifacts are distributed by SDC in a CSAR package onto the DMaaP bus. (4) SETTING UP RUNTIME DB - S/W to setup the RunTime DB using the content of the CSAR package consumes the SDC CSAR Package. |
A more detailed figure and description of the component.
PURPOSE:
REPOSITORY - The types of data that is stored in the Run-Time data storage repository for:
(1) CONFIGURATION PARAMETERS used by xNFs in run time. For example 5G Network run-time instance configuration information. and
(2) OPERATIONAL PARAMETERS used by ONAP and xNFs. Exo-inventory information is information that doesn't belong in A&AI.
ACCESS (READ/WRITE):
READ/WRITE - Parameters can be READ/WRITE from Controllers, DCAE (future), VES Collector/DMaaP, A&AI, Policy/CLAMP (future) and other components with permission settings.
SYNCING (INVENTORY):
ELEMENT SYNC - Software keeps the A&AI elements with the elements in the RunTime DB in Sync.
INDEXING:
RunTime DB uses the following models:
This release, RunTime DB adds the following Capabilities: