Versions Compared

Key

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

...

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

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 and (2) operational parameters used by ONAP and xNFs.

  • DATA LAKE - It is designed to be a common services data layer which can serve as a data lake.
  • Enables SYNCING - The RunTime DB enables the ability to sync data with between ONAP & the xNFs. (The source of truth , sync data, restore/initialize). Can be used for xNF crash restoration, can be define).
  • CM FUNCTIONS - Enables OSS configuration, optimization, and LCM operations. (FUTURE)
  • CM FUNCTIONS - Enables future CM & Data management functions such as xNF Crash restoration, data restoration, data history management and auditing.
  • Enables OSS configuration, optimization, and LCM operations.

ACCESS:

  • (FUTURE)
  • 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. (FUTURE)
  • SCOPE - The Run Time DB could also serve as the data storage to store for example ONAP Policy Rules, CLAMP Control Loop, Operational Views (FUTURE)

ACCESS (READ/WRITE):

  • READ ONLY - Run-Time parameters can be READ by any ONAP platform component and any ONAP plug-in. Examples of ONAP platform components are A&AI, SDC, SDNC etc.
  • 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.

  • DEFAULT - SO (future), DCAE, A&AI, Controllers (CDS, APPC, SDNC) will have default read/write access to RunTime DB
  • DEFINABLE - Other components will have default read-only access to RunTime DB but can be given Read/Write access on a per record basis.

INDEXING & SYNCING (INVENTORY):

  • ELEMENT SYNC - Software keeps the A&AI elements with the elements in the RunTime DB in Sync. 

  • A&AI - A&AI is still the master of valid entities in the network and provides a dynamic view of the assets (xNFs) available to ONAP
  • RUNTIME DB - The RunTime DB is a master of the associate (exo-inventory) data associated with the entities.
  • DYNAMIC VIEW - When a xNF appears or is removed from the system, RunTime DB records will be added/removed based on A&AI entries.

INDEXING:

  • INDEXING - Data Records will be indexed by xNF (VNF, PNF, ANF).
  • RETRIEVAL - How are data records retrieved efficiently. This relates how the records are indexed.

2. API definitions

RunTime DB provides the following interfaces:

...