Code Review / music / mdbc.git / commit
? search:
summary | shortlog | log | commit | commitdiff | review | tree
(merge: fa078d2 e91e943)
Merge "Fix node configuration/executable, and minor bugs"
authorThomas Nelson <nelson24@att.com>
Thu, 24 Jan 2019 17:45:43 +0000 (17:45 +0000)
committerGerrit Code Review <gerrit@onap.org>
Thu, 24 Jan 2019 17:45:43 +0000 (17:45 +0000)
commitb357ddb0869c2cc44eb0bd5800ed66914f49c468
treea8e69a40ae34accc7c4f5290f7b508f116af4741tree | snapshot
parentfa078d24e835af497d3286c4525ae09a6de8f3d9commit | diff
parente91e9430fd80cbb9b5ae617857d1989f9ff24bf0commit | diff
Merge "Fix node configuration/executable, and minor bugs"
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.