andrea.dellamico
/
conductor-setup
forked from gCubeSystem/conductor-setup
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

README.md edited online with Bitbucket

This commit is contained in:
Mauro Mugnaini 2020-10-26 12:44:18 +00:00
parent 110a678cdc
commit bf8b5ace00
1 changed files with 4 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
README.md
View File

@ -14,20 +14,22 @@ The Docker Compose Swarm files are present in the `stack` folder.
## Documentation
The provided Docker stack files provide the following configuration:
- 4 Dynomites nodes (2 shards with 1 replication each one, handled by Dynomite directly) based on `autodynomite` image that is backed by Redis DB in the same container
- 2 Conductor Server nodes with 2 replicas handled by Swarm
- 2 Conductor UI nodes with 2 replicas handled by Swarm
- 1 Elasticsearch node
Build the Docker `autodynomite` image with the `Dockerfile` present in the dynomite folder and launch the three Docker Compose Swarm files is sequence:
- dynomite-swarm.yaml
- elasticsearch-swarm.yaml
- conductor-swarm.yaml
The command to be executed should looks like: `docker stack deploy -c dynomite-swarm.yaml -c elasticsearch-swarm.yaml -c conductor-swarm.yaml [your stack name]`
If you plan to deploy more than 4 nodes for dynomite you should modify the `dynomite-swarm.yaml` and the `seeds.list` files as per your needs.
The `conductor-swarm-config.properties` should be let unmodified.
If you plan to deploy **more than 4 nodes** for dynomite persistence you should modify the `dynomite-swarm.yaml` and the `seeds.list` files as per your needs.
The `conductor-swarm-config.properties` should be left unmodified.
## Change log