Go to file

Mauro Mugnaini 1aa5a12e26 Revised configuration templates to use rack topology names AWS oriented		2020-11-02 13:27:22 +01:00
ansible	Revised configuration templates to use rack topology names AWS oriented	2020-11-02 13:27:22 +01:00
dynomite	Fixes and renaming for the alpha release	2020-10-28 09:38:31 +01:00
stack	First commit	2020-10-26 13:27:25 +01:00
.gitignore	Initial commit	2020-10-26 12:19:58 +00:00
CHANGELOG.md	First commit	2020-10-26 13:27:25 +01:00
FUNDING.md	First commit	2020-10-26 13:27:25 +01:00
LICENSE.md	First commit	2020-10-26 13:27:25 +01:00
README.md	README.md edited online with Bitbucket	2020-10-26 12:44:18 +00:00

README.md

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.

Structure of the project

The AutoDynomite Docker image script file is present in dynomite folder. The Docker Compose Swarm files are present in the stack folder.

Built With

Docker

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 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

See CHANGELOG.md.

Authors

Marco Lettere (Nubisware S.r.l.)
Mauro Mugnaini (Nubisware S.r.l.)

How to Cite this Software

[Intentionally left blank]

License

This project is licensed under the EUPL V.1.1 License - see the LICENSE.md file for details.

About the gCube Framework

This software is part of the gCubeFramework: an open-source software toolkit used for building and operating Hybrid Data Infrastructures enabling the dynamic deployment of Virtual Research Environments by favouring the realisation of reuse oriented policies.

The projects leading to this software have received funding from a series of European Union programmes see FUNDING.md

Acknowledgments

[Intentionally left blank]