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

Merge branch 'master' of https://bitbucket.org/Nubisware/conductor-setup

This commit is contained in:
Mauro Mugnaini 2020-10-27 10:55:49 +01:00
parent 919dccb12f bf8b5ace00
commit 198a14fc59
1 changed files with 10 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

18
README.md
View File

@ -1,6 +1,6 @@
# Conductor Setup # Conductor Setup
**Conductor Setup** is composed by a Docker image script that should be used to build the autodynomite image, and 3 different Docker Compose Swarm YAML files to deploy the Conductor in HA. **Conductor Setup** is composed by a Docker image script that should be used to build the `autodynomite` image, and 3 different Docker Compose Swarm YAML files to deploy the Conductor in HA.
## Structure of the project ## Structure of the project
@ -14,20 +14,22 @@ The Docker Compose Swarm files are present in the `stack` folder.
## Documentation ## Documentation
The provided Docker stack files provide the following configuration: The provided Docker stack files provide the following configuration:
- 4 Dynomites nodes (2 shards with 1 replication each one, handled by Dynomite directly) 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 `autodinomite` image with the `Dockerfile` present in the dynomite folder and launch the three Docker Compose Swarm files is sequence: - 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 - dynomite-swarm.yaml
- elasticsearch-swarm.yaml - elasticsearch-swarm.yaml
- conductor-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]` 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. 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 let unmodified. The `conductor-swarm-config.properties` should be left unmodified.
## Change log ## Change log