Code Review / music / mdbc.git / commit
? search:
summary | shortlog | log | commit | commitdiff | review | tree
(parent: ba7c4ff) | patch
Docker compose scripts for two mdbc sites 31/74631/1
authorRob Daugherty <rd472p@att.com>
Thu, 13 Dec 2018 18:58:11 +0000 (13:58 -0500)
committerRob Daugherty <rd472p@att.com>
Thu, 13 Dec 2018 19:02:57 +0000 (14:02 -0500)
commite162ac7ac117d2a1948ec2ea6845d0e132b2967e
tree02386bdd5e7bcabac1a9821e892b842d3226838etree | snapshot
parentba7c4ffe49495ad0e2ce986192f65c8ae63bb2bdcommit | diff
Docker compose scripts for two mdbc sites

This is a two site installation, with a single cassandra
container,  two mariadb containers, and two mdbc-server
containers.

Server 1 exposes port 30001 and server 2 exposes port 30002.

To build the docker images, first build mdbc software
normally, then use the 'docker' maven profile:

mvn -P docker clean install

To bring up the environment:

cd mdbc-packages/mdbc-docker/compose/two-sites

docker-compose up

Change-Id: I10155ebf47dec4e787d44b23886ab8453ac4315f
Issue-ID: MUSIC-263
Signed-off-by: Rob Daugherty <rd472p@att.com>
12 files changed:
mdbc-packages/mdbc-docker/compose/one-site/docker-compose.yml diff | blob | history
mdbc-packages/mdbc-docker/compose/one-site/volumes/mdbc-server-1/config/music.properties [moved from mdbc-packages/mdbc-docker/compose/one-site/volumes/mdbc-server/config/music.properties with 100% similarity] blob | history
mdbc-packages/mdbc-docker/compose/one-site/volumes/mdbc-server-1/config/tableConfiguration.json [moved from mdbc-packages/mdbc-docker/compose/one-site/volumes/mdbc-server/config/tableConfiguration.json with 94% similarity] diff | blob | history
mdbc-packages/mdbc-docker/compose/two-sites/.env [new file with mode: 0644] blob
mdbc-packages/mdbc-docker/compose/two-sites/docker-compose.yml [new file with mode: 0644] blob
mdbc-packages/mdbc-docker/compose/two-sites/volumes/cassandra/docker-entrypoint-initdb.d/01-create-music-internal-keyspace.cql [new file with mode: 0644] blob
mdbc-packages/mdbc-docker/compose/two-sites/volumes/mariadb/conf.d/mariadb1.cnf [new file with mode: 0644] blob
mdbc-packages/mdbc-docker/compose/two-sites/volumes/mariadb/docker-entrypoint-initdb.d/01-create-test-database.sh [new file with mode: 0644] blob
mdbc-packages/mdbc-docker/compose/two-sites/volumes/mdbc-server-1/config/music.properties [new file with mode: 0644] blob
mdbc-packages/mdbc-docker/compose/two-sites/volumes/mdbc-server-1/config/tableConfiguration.json [new file with mode: 0644] blob
mdbc-packages/mdbc-docker/compose/two-sites/volumes/mdbc-server-2/config/music.properties [new file with mode: 0644] blob
mdbc-packages/mdbc-docker/compose/two-sites/volumes/mdbc-server-2/config/tableConfiguration.json [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.