The Orchestrator is part of the SODALITE Runtime Layer. It is in charge of the deployment and reconfiguration of SODALITE applications. It takes an IaC blueprint (i.e., a TOSCA+Ansible playbooks file) and performs the deployment of the applications on heterogeneous infrastructures.
The most important features of the Orchestrator are:
- It can handle any infrastructure reachable through SSH
- Enables deployments for both HPC and Cloud
- Support of TOSCA declarative workflows
- Support of TOSCA CSAR blueprints
SODALITE built an xOpera dockerized REST API with nginx as an reverse proxy for handling SSL connections. Such setup gives the possibility to use xOpera in a failover cluster or in a load balanced scenario. SODALITE takes a stable version of xOpera and creates a wrapper REST API and internally runs xOpera as a process. The orchestrator endpoint for SODALITE components and integration is therefore the xOpera REST API. The xOpera REST API creates an asyncronous wrapper for handling multiuser deployments through session tokens.
The orchestrator building block is composed of the orchestrator itself and drivers to connect to the different targets. Currently, the orchestrator supports the deployment of applications on Openstack and we have certain support for HPC through Torque.
This repository contains two sub-repositories:
- xOpera as the orchestrator (as a reference point for the internal SODALITE orchestrator)
- ALDE as the HPC driver. ALDE is a fork from the TANGO project. It provides a uniform REST API to manage HPC workload managers and applications deployed on them (currently, Slurm). In SODALITE, ALDE is being extended to support Torque.
- python3 and virtual environments
Both projects contains detailed installation instructions. In general, you need to:
-
Create the virtual environment:
$ python3 -m venv <env-dir> $ source <env-dir>/bin/activate -
Install the pip packages
$ cd <project-dir> $ pip install -
Run!
Check individual repositories on usage guides.