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
2018-11-20	MusicSqlManager Removal, othe code refactors	Tschaen, Brendan	1	-4/+2
	MusicSqlManager not required in current setup Current code condensed and absorbed into MdbcConnection and MusicMixin Modify deprecated names "CassandraMixin" to "MusicMixin" Change-Id: If68f8937a385c19d901c56e5795ddc0acf45d399 Issue-ID: MUSIC-198 Signed-off-by: Tschaen, Brendan <ctschaen@att.com>
2018-11-16	TxDigest replay and code restructure	Tschaen, Brendan	1	-2/+5
	Spin off replay daemon in its own object Create musictxdaemon test Fix licensing issue MusicRow Info has database partition object Change-Id: I22117f8e9309fb5d8bc99ec35d4145e655f4e5a2 Issue-ID: MUSIC-166 Signed-off-by: Tschaen, Brendan <ctschaen@att.com>
2018-11-05	Modularized mdbc build	Rob Daugherty	1	-0/+12
	The mdbc pom should inherit from oparent. The top-level pom should not build the jar directly. It should be a parent pom for mdbc submodules. The first submodule will be called mdbc-server. Note: the "mdbc" jar will now be called "mdbc-server". Change-Id: I4456e659b7494641e5b3cefd540eb62a149b79a4 Issue-ID: MUSIC-175 Signed-off-by: Rob Daugherty <rd472p@att.com>