Orchestration Plugins

The Ansible plugin enables you to configure Studio Conductor resources with Ansible and provides an agentless method for executing operations on hosts. Playbook Run Operation Similar to the Script Plugin and the Fabric Plugin, there is no one node type associated with the Ansible plugin. Instead, you modify existing node types to perform one or more of their lifecycle operations using the Ansible plugin and any additional inputs that you provide. »

The Docker plugin enables you to interact with docker machine through API integration and that will enable you to: Install docker on a machine. Build Images. Create containers from images. Create mapping volumes to containers. Run Ansible playbooks inside containers. Run Terraform modules inside containers. Requirements You must already have docker installed either on your Conductor Manager or on another machine but with access allowed on port 2375. »

Helm is the first application package manager running on top of Kubernetes. It allows describing the application structure through convenient helm-charts and managing it with simple commands. Helm uses three main concepts: Charts Repository Release A Chart is a Helm package. It contains all of the resource definitions necessary to run an application, tool, or service inside of a Kubernetes cluster. Think of it like the Kubernetes equivalent of a Homebrew formula, an Apt pkg, or a Yum RPM file. »

With the Studio Conductor Kubernetes Plugin you can define Kubernetes resources in your blueprints. Plugin Requirements Python versions: 2.7.x Kubernetes Cluster, see example cluster. Compatibility Conductor Manager, v5.0.5 and higher. Kubernetes, v1.13 and higher. Supports GKE. Supports EKS. Supports AKS. Supports Openshift. Supports Kubespray. Authentication There are two authentication methods: token-based config-based Token-Based Authentication Studio Conductor Kubernetes Plugin v2.1.0+ includes support for token-based authentication. »

The Terraform plugin enables you to maintain Terraform Plan state from Studio Conductor and also to use Terraform resources in your Studio Conductor blueprints. Requirements You must already have the Terraform binary on your Conductor Manager. It should be executable by the cfyuser Linux user. Node Types cloudify.nodes.terraform This is the base node type. The properties are also available in cloudify.nodes.terraform.Module. Properties use_existing_resource: a boolean to indicate if the user want use pre-exising installation of terraform , that will skip the installation , but will download the plugins that is specified in plugins installation_source: Location to download the Terraform installation from. »