Code Review / music / mdbc.git / commit
? search:
summary | shortlog | log | commit | commitdiff | review | tree
(parent: f61985d) | patch
Update INFO.yaml file 27/82327/1
authorJessica Wagantall <jwagantall@linuxfoundation.org>
Fri, 15 Mar 2019 01:21:19 +0000 (18:21 -0700)
committerJessica Wagantall <jwagantall@linuxfoundation.org>
Fri, 15 Mar 2019 01:21:19 +0000 (18:21 -0700)
commit05e72711ca4f45da24c445dec8669877ed31830c
treed50ac75b9f62a634d9ff0940f8be9fd2dcf04c8atree | snapshot
parentf61985dedb975a777bed88fb17c482d0dbb73cd8commit | diff
Update INFO.yaml file

Update missing information blocks and
indentation to pass verify job.

Change-Id: I3ab8994e87aa2bde3374bde0d376ae1ef31dd819
Issue-ID: CIMAN-134
Signed-off-by: Jessica Wagantall <jwagantall@linuxfoundation.org>
INFO.yaml 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.