You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
dcore94 d185681fef renamed 2 years ago
group_vars moved one level up 2 years ago
inventory moved one level up 2 years ago
roles renamed 2 years ago
.gitignore Initial commit 2 years ago
CHANGELOG.md complete refactoring and removal of dynomite 2 years ago
FUNDING.md First commit 2 years ago
LICENSE.md First commit 2 years ago
README.md Merge branch 'master' of https://bitbucket.org/Nubisware/conductor-setup 2 years ago
ansible.cfg Proposed changes to better separate the environments. 2 years ago
run.sh made vault file visible 2 years ago
site-prod.yaml made vault file visible 2 years ago
site.yaml Adeguata la lista di host in site.yml 2 years ago

README.md

Conductor Setup

Conductor Setup is composed of a set of ansible roles and a playbook named site.yaml useful for deploying a docker swarm running Conductor microservice orchestrator by Netflix OSS.

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

Documentation

The provided Docker stack files provide the following configuration:

  • 2 Conductor Server nodes with 2 replicas handled by Swarm
  • 2 Conductor UI nodes with 2 replicas handled by Swarm
  • 1 Elasticsearch node
  • 1 Database node that can be postgres (default), mysql or mariadb
  • 2 Optional replicated instances of PyExec worker running the tasks Http, Eval and Shell
  • 1 Optional cluster-replacement service that sets up a networking environment (including on HAProxy LB) similar to the one available in production. By default it's disabled.

The default configuration is run with the command: ansible-playbook site.yaml Files for swarms and configurations will be generated inside a temporary folder named /tmp/conductor_stack on the local machine. In order to change destination folder use the switch: -e target_path=anotherdir If you only want to review the generated files run the command ansible-playbook site.yaml -e dry=true In order to switch between postgres and mysql specify the db on the proper variable: -e db=mysql In order to connect to an external postgres withouth pulling up a service in the stack use -e db=remote-postgres In order to skip worker creation specify the noworker variable: -e noworker=true In order to enable the cluster replacement use the switch: -e cluster_replacement=true If you run the stack in production behind a load balanced setup ensure the variable cluster_check is true: ansible-playbook site.yaml -e cluster_check=true

In order to avoid confusion of all variables a proper site.yaml has been created for prod environment. Run ansible-playbook site-prod.yaml and this should deploy a stack with prod setup.

Other setting can be fine tuned by checking the variables in the proper roles which are:

  • common: defaults and common tasks
  • conductor: defaults, templates and tasks for generating swarm files for replicated conductor-server and ui.
  • elasticsearch: defaults, templates and task for starting in the swarm a single instance of elasticsearch
  • mysql: defaults, template and tasks for starting in the swarm a single instance of mysql/mariadb
  • postgres: defaults, templates and tasks for starting in the swarm a single instance of postgres
  • workers: defaults and task for starting in the swarm a replicated instance of the workers for executing HTTP, Shell, Eval operations.

Examples

The following example runs as user username on the remote hosts listed in hosts a swarm with 2 replicas of conductor server and ui, 1 postgres, 1 elasticsearch, 2 replicas of simple PyExec, an HAProxy that acts as load balancer. ansible-playbook -u username -i hosts site.yaml -e target_path=/tmp/conductor -e cluster_replacement=true

Change log

See CHANGELOG.md.

Authors

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]