Code Review / music / mdbc.git / commit
? search:
summary | shortlog | log | commit | commitdiff | review | tree
(parent: 04ab889) | patch
Update oparent version 69/86769/1
authorJessica Wagantall <jwagantall@linuxfoundation.org>
Thu, 2 May 2019 02:16:05 +0000 (19:16 -0700)
committerJessica Wagantall <jwagantall@linuxfoundation.org>
Thu, 2 May 2019 02:16:05 +0000 (19:16 -0700)
commit8a3db86e697de59a29e712d23e771c8718f9778a
treea6eac3df6418b871cbc531aaebe088628c260b25tree | snapshot
parent04ab8895cde445cb3895d6875e5040921f2a38cacommit | diff
Update oparent version

Update oparent version to 2.0.0 which supports
global-jjb maven-stage job.

Change-Id: Ib9f38fbae9e95099856e6dda1d3ace2dc236c747
Issue-ID: CIMAN-234
Signed-off-by: Jessica Wagantall <jwagantall@linuxfoundation.org>
pom.xml diff | blob | history
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.