This is discussing a new ONAP platform component as a Runtime DB for storing run-time configuration and information that doesn't belong to A&AI inventoary (exo-inventary data).

Use for change management, facilitate real-time operation LCM, ..... allowing e.g. sync data, golden parameter templating etc.  Proposing to start in ONAP R6 for 5G RAN network configuration data.  While originally it was config DB, it is pivoting to be referred to as "runtime DB".

2019-10-29 Archcom

• Ben walked through the draft project proposal. https://wiki.onap.org/pages/viewpage.action?pageId=71834216
• Ben invited people to attend his Friday meeting.

2019-10-15 Archcom

• Ben presented a bit about the flows.
• There wasn't enough time to go over all the flows.
• It starts to have some logic for interpreting the subscription information from events and what to store.  This is a cause for concern.

2019-09-17 Archcom

Ben showed the work of describing the run-time DB.https://wiki.onap.org/display/DW/ARC+RunTime+DB+Component+Description+-+Frankfurt 

Next step is to show a flow.

 2019-09-10 ArchCom: Ben presented the following slides:  xyz

• Gil brought up the storage of polices for the non-realtime RIC.
• Tony brought up that the access control is very important in order to ensure that we don't have uncontrolled communication between the uses.  The governance is important.
• Proposal: draft up a definition phase, assuming that it could be used by multiple components.
• There was a feeling that we should avoid placing data into this database that should go in A&AI.  One use of the Database was to retain the data that a network function would need to be provided with if it was to fail and be restored.
• It was suggested by Gil that it is a global service management and resource management database
• Capture some pros and cons.
• Leaning towards a capability as a common service as a working assumption.
• Need to look at existing databases and see their relationships.

2019-09-3 ArchCom: https://wiki.onap.org/download/attachments/50202249/DataPersistencyRunTimeDB_03Sep2019v1.pptx?api=v2

Ben presented the following the slides:

• It is data layer, or something else?
• this comes into "how would we use it now" and how might we use it in the future?
• There was a discussion on how to represent this in the architecture - but it is required to clarify how it is used first.
• Is it intended be something that different components can share data between components, or each component owns their own namespace and the data is just for them.
• What is the overlap with A&AI?
• There was a discussion about the configuration DB/Runtime DB being an PNF inventary