Code Review / music / mdbc.git / commit
? search:
summary | shortlog | log | commit | commitdiff | review | tree
(parent: fc12ebd) | patch
Add INFO.yaml file 93/47093/1
authorJessica Wagantall <jwagantall@linuxfoundation.org>
Thu, 10 May 2018 17:41:16 +0000 (10:41 -0700)
committerJessica Wagantall <jwagantall@linuxfoundation.org>
Thu, 10 May 2018 17:41:16 +0000 (10:41 -0700)
commit389265e6342302ce5a8db5d4a3cc215e2c24c97a
tree46e08dac3e5b748e708a41545f4a7be166f3afeftree | snapshot
parentfc12ebdd86470ad62036e6b0660179f90253f63fcommit | diff
Add INFO.yaml file

Add INFO.yaml to list:
- Project description
- Properties
- PTL information
- Meeting information
- Committer information

Change-Id: Ida057d32e23bf0a12d79d64f5fe3610ded2ff687
Issue-ID: CIMAN-134
Signed-off-by: Jessica Wagantall <jwagantall@linuxfoundation.org>
INFO.yaml [new file with mode: 0644] blob
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.