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.
Marco Lettere 1cc1f1bb8c support IAM sending gunzipped tokens 1 month ago
inventory inventory fix 7 months ago
local-site corrected local site 6 months ago
roles support IAM sending gunzipped tokens 1 month ago
.gitignore Initial commit 1 year ago
CHANGELOG.md complete refactoring and removal of dynomite 1 year ago
FUNDING.md First commit 1 year ago
LICENSE.md First commit 1 year ago
README.md tuned generation for all environments and added local-site 7 months ago
ansible.cfg Proposed changes to better separate the environments. 1 year ago
site-dev.yaml scaled down otriginal conductor replicas to two to help startup. 6 months ago
site-local.yaml conductor 3.0.4 with oauth2 and pep 7 months ago
site-nw-cluster.yaml scaled down otriginal conductor replicas to two to help startup. 6 months ago
site-pre.yaml changed oauth2 strategy to work around multiple role bug 6 months ago
site-prod.yaml added external postgres vault 6 months 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.

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

whereas

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

127.0.1.1 conductor-server conductor-ui

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

Built With

Examples

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

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]