music/mdbc - 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.

Branch	Commit message	Author	Age
master	Merge "History of range tool"	Bharath Balasubramanian	4 years


Age	Commit message	Author	Files	Lines
2020-01-21	Merge "History of range tool"HEAD master	Bharath Balasubramanian	2	-1/+124
2019-10-22	Hot restart	Tschaen, Brendan	14	-68/+219
2019-10-09	Various bug fixes and code cleanup	Tschaen, Brendan	12	-102/+102
2019-09-27	Deadlock detection and recovery with new Music version	Arthur Martella	18	-55/+154
2019-09-19	Remove duplicate table creation	subhash.kumar.singh	2	-26/+2
2019-09-10	Merge "Dependency missing in nexus"	Brendan Tschaen	1	-1/+1
2019-09-04	Merge "Replay Transaction Updates"	Bharath Balasubramanian	12	-130/+144
2019-08-28	Dependency missing in nexus	subhash kumar singh	1	-1/+1
2019-08-12	Merge "Update MUSIC version"	Bharath Balasubramanian	1	-2/+2
2019-08-07	Configurable "write only locks"	Tschaen, Brendan	4	-0/+14
[...]

Clone
https://git.onap.org/music/mdbc