Code Review / music / mdbc.git / commit
? search:
summary | shortlog | log | commit | commitdiff | review | tree
(merge: c873e76 6703275)
Merge "CreateNodeConfigurations never exits"
authorBrendan Tschaen <ctschaen@att.com>
Wed, 5 Dec 2018 14:48:19 +0000 (14:48 +0000)
committerGerrit Code Review <gerrit@onap.org>
Wed, 5 Dec 2018 14:48:19 +0000 (14:48 +0000)
commitba7c4ffe49495ad0e2ce986192f65c8ae63bb2bd
treee348634b2ccb0885a4ad0477f00226d677a6623dtree | snapshot
parentc873e7629db2741ab675f2df88ecbc4d53b5215ccommit | diff
parent6703275b1697bd20cc0345a1292314bc4694bfdecommit | diff
Merge "CreateNodeConfigurations never exits"
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.