Code Review / music / mdbc.git / commit
? search:
summary | shortlog | log | commit | commitdiff | review | tree
(merge: d3e9867 ac3c312)
Merge "Include connection info in log"
authorThomas Nelson <nelson24@att.com>
Fri, 14 Jun 2019 19:43:38 +0000 (19:43 +0000)
committerGerrit Code Review <gerrit@onap.org>
Fri, 14 Jun 2019 19:43:38 +0000 (19:43 +0000)
commit9e21ff943f11df4c274b29989f5058c8054a9b39
treebec331227a795e11af014bf372375ab650ae014ctree | snapshot
parentd3e986759875605e43acabbb1283270440a1a1a7commit | diff
parentac3c3123a7d660d85bdcbc013e63b439b430ec42commit | diff
Merge "Include connection info in log"
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.