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.

Age	Commit message (Collapse)	Author	Files	Lines
2019-03-14	Update INFO.yaml file	Jessica Wagantall	1	-27/+38
	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>
2018-11-19	Query processing with Calcite	Vikram Potturi	1	-0/+0
	Change-Id: Id8ebbc48159810ca782081bb4f63071071c926dd Issue-ID: MUSIC-164 Signed-off-by: Vikram Potturi <vikramaditya.potturi@att.com>
2018-05-10	Add INFO.yaml file	Jessica Wagantall	1	-0/+52
	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>