You cannot select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Marco Lettere e4585299d4 added env var for smtp_user and added as vhost 1 year ago
inventory inventory fix 3 years ago
local-site corrected local site 3 years ago
roles fixed support for client_credentials when basic auth 2 years ago
v3.4 added env var for smtp_user and added as vhost 1 year ago
.gitignore Initial commit 3 years ago complete refactoring and removal of dynomite 3 years ago First commit 3 years ago First commit 3 years ago tuned generation for all environments and added local-site 3 years ago
ansible.cfg Proposed changes to better separate the environments. 3 years ago
site-dev.yaml scaled down otriginal conductor replicas to two to help startup. 3 years ago
site-local.yaml conductor 3.0.4 with oauth2 and pep 3 years ago
site-nw-cluster.yaml scaled down otriginal conductor replicas to two to help startup. 3 years ago
site-pre.yaml changed oauth2 strategy to work around multiple role bug 3 years ago
site-prod.yaml added external postgres vault 3 years ago

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.

Current setup is based on Conductor 3.0.4 version adapted by Nubisware S.r.l. It uses the docker images on dockerhub:

  • nubisware/conductor-server:3.0.4
  • nubisware/conductor-ui-oauth2:3.0.4 (which has been improved with Oauth2 login in collaboration with Keycloak)

Besides the basic components Conductor itself (server and ui) and Elasticsearch 6.1.8, the repository can be configured to launch postgres or mysql persistence plus basic python based workers for running PyRest, PyMail, PyExec and PyShell in the same Swarm. In addition a nginx based PEP can be executed to protect the conductor REST API server. It is also possible to connect to an external postgres for stateful deployments.

Structure of the project

The folder roles contains the necessary roles for configuring the different configurations There are 4 file for deploying to local, nw-cluster or D4SCience dev, pre and prod environments.

To run a deployment

ansible-playbook site-X.yaml


ansible-playbook site-X.yaml -e dry=true

only generates the files for the stack without actually deploying it.

The folder local-site contains a ready version for quickly launching a conductor instance with no replications (except workers), no auth in the Conductor UI and no PEP.

docker stack deploy -c elasticsearch-swarm.yaml -c postgres-swarm.yaml -c conductor-swarm.yaml -c conductor-workers-swarm.yaml -c pep-swarm.yaml conductor

When you have ensured that Postgres and Elasticsearch are running, execute:

docker stack deploy -c conductor-swarm.yaml conductor

This will create a local stack accessible through permissive pep at port 80. Please add two mappings for localhost in your /etc/hosts conductor-server conductor-ui

and point your browser to http://conductor-ui.

Built With


Checkout the files site-X.yaml as a reference for different configurations.

Change log



How to Cite this Software

[Intentionally left blank]


This project is licensed under the EUPL V.1.1 License - see the 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


[Intentionally left blank]