Implement postgres, fixes to eventual, and many bug fixes - music/mdbc - The most crucial recipe is a multi-site database cache (mdbc) that enable ONAP components that maintain state in a SQL database to avail the benefits of MUSIC without compromising their need to use transactional SQL DBs. These ONAP components can rely on existing db clustering techniques like MariaDB for transactionality and complex querying within a site. mdbc will intercept each of these read/write calls to the db cluster and mirror this state to other geo-distributed sites through MUSIC either synchronously or asynchronously (configurable at a table-level). For example, components like the ONAP Service Orchestrator that use MariaDB to maintain state can directly use this recipe with no change to their SQL code.

diff options

author	Arthur Martella <arthur.martella.1@att.com>	2019-04-29 15:03:07 -0400
committer	Arthur Martella <arthur.martella.1@att.com>	2019-05-03 10:04:56 -0400
commit	52159a510dc31ee1dacf612a1e05cc8612a117e5 (patch)
tree	167fd4e5357ecab6b7a5fa8675dc7c3b63453b38 /INFO.yaml
parent	601050a535e916c0ff52826fbe2c61b798c74530 (diff)

Implement postgres, fixes to eventual, and many bug fixes

Streamline upper and lower cases for Ranges Fix initialization of system Merged version of commit https://gerrit.onap.org/r/#/c/86160/ Change-Id: I169ed56ff79ff0a2e14ab9bc5e0467d1c0b9f0a9 Issue-ID: MUSIC-387 Signed-off-by: Arthur Martella <arthur.martella.1@att.com>

Diffstat (limited to 'INFO.yaml')

0 files changed, 0 insertions, 0 deletions


context:
space:
mode: