You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 6 Next »

STATUS: Draft

RunTime DB:

1 High Level Component Definition and Architectural Relationships 



The RunTime DB function provides storage for real-time run-time parameters that need to be used by ONAP. It provides

  • Run-Time data storage repository for configuration and operational parameters.

  • It is architected to be a common services data layer.
  • Data Records will be indexed by xNF (VNF, PNF, ANF).
  • Run-Time parameters can be READ by any ONAP platform component and any plug-in.
  • Parameters can be READ/WRITE from Controllers, DCAE/DMaaP, A&AI and other components with permission settings.

  • Software keeps the A&AI elements (master of valid entities in the network, dynamic view of the xNF) with the elements in the RunTime DB in Sync (master of data associated with entities). 

  • Enables sync data with xNFs. (source of truth, sync data, restore/initialize). Can be used for xNF crash restoration, history management and auditing.
  • Enables OSS configuration, optimization, and LCM operations.

2. API definitions

RunTime DB provides the following interfaces:

Interface NameInterface Definition Interface CapabilitiesVersionStatusConsumed Models
RTDBE-1RunTime DB Interface. An interface to create, update, retrieve, query, delete information from the RunTime DB.


RTDBE-2RunTime DB Graphical User Interfaces Provides the capability to view the data currently in the RunTime DB


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 NamePurpose Reason For Use
SDCE-7

To receive the service and resource artifacts from SDC.

Artifacts (vendor onboarded) into SDC will be eventually stored, validated (VNF-SDK) into the SDC catalog, those will be sent out over DMaaP in a CSAR package, and S/W will setup the RunTime using these artifacts.


3. Component Description:

A more detailed figure and description of the component.

FFS

4. known system limitations


5. Used Models

RunTime DB uses the following models:

  • Inventory Model


6. System Deployment Architecture

FFS


7. New Capabilities in this Release

This release, RunTime DB adds the following Capabilities:

  • -

8. References

  1.  
  • No labels