Infrastructure Plugins

The AWS plugin enables you to manage AWS resources with Studio Conductor. Authentication with AWS Each node template, has a client_config property which stores your account credentials. Use an intrinsic function to assign these to the values of secrets in your manager. my_vpc: type: cloudify.nodes.aws.ec2.Vpc properties: client_config: aws_access_key_id: { get_secret: aws_access_key_id } aws_secret_access_key: { get_secret: aws_secret_access_key } aws_session_token: { get_secret: aws_session_token } region_name: { get_input: aws_region_name } resource_config: CidrBlock: '10. »

Conductor StarlingX Plugin enables users to orchestrate StarlingX workflows from a Cloudify manager. Pre-Check workflows Set up the Pre-Check Download the provided starlingx plugin. Download the provided blueprint. Upload the starlingx plugin and the blueprint. Create a deployment using the blueprint. On that new deployment, run the “Audit Host Upgradable” workflow. The pre-check report will be available in the output/capabilities in the key pre_check_report. Pre-Check Merge This plugin implements a workflow to fetch all pre-check reports from all wrcp deployments and merge them. »

Requirements Python versions: 3.6.x Dell BMO Orchestrator plugin 1.0.0 or higher Workflows The following workflows are available in Infrablock plugin: provision_sysctrl provision_subclouds Decommission subclouds 1. Provision Sysctrl Comments in the code: # assumption: # 1, install workflow executed successfully, # 2, during install workflow, bmo_node_instance # has stored 'site_name', 'ciq_values' to runtime_properties # 3, there must be 1 and only 1 bmo_node_instance # bmo discover servers, wrcp audit servers, bmo update hwprofiles # subgraph_name = 'predeploy_wrcp' Objective: »

The StarlingX plugin enables you to discover StarlingX systems and manage resources on StarlingX systems. Start out by providing the credentials for an existing StarlingX system. The install workflow will gather information from the system, for example type and location. To discover subclouds, execute the discover_and_deploy workflow over a Controller deployment. This workflow performs the following tasks: Discover all subclouds that are managed by the system controller (parent). Create a deployment group. »

Plugin that supports automation of StartlingX. As part of this plugin Redfish discovery procedure for Redfish data from Dell, Intel and HP devices was automated. Redfish discovery During the process Redfish client from redfish library is used to obtain the data present in paths indicated in redfish_keys_tree (property of every discovery node). Data Types windriver.types.redfish.ClientConfig properties: ip - IP address of Redfish server username - name of the user to be used for authentication to Redfish server password - password to be used for authentication to Redfish server auth_type - type of authentication used for RedfishClient (default: session, can be changed to basic) Node Types windriver. »

The Azure plugin enables you to use Studio Conductor to manage cloud resources on Azure. See below for currently supported resource types. Plugin Requirements Python Versions 2.7.x. Azure account. Compatibility The Azure plugin has two methods for interacting with Azure services: legacy and SDK based. The legacy library is tested against these Azure API Versions: RESOURCES = ‘2017-05-10’ STORAGE = ‘2015-06-15’ NETWORK = ‘2016-03-30’ COMPUTE = ‘2016-03-30’ »

The GCP plugin enables you to use Studio Conductor to manage Cloud resources on GCP. The currently supported resource types are listed later in this topic. Note that some services and resources vary in availability between regions and accounts. Plugin Requirements Python versions: 2.7.x GCP account Compatibility The GCP plugin uses the official Google API Python Client. Accessing Secrets It is recommended that you store your credentials as secrets. »

The vSphere plugin enables you to use a vSphere-based infrastructure for deploying services and applications. Plugin Requirements Python versions: 2.7.x Permissions on vCenter: To create and tear down virtual machines and storage: On the datacenter: Datastore/Allocate Space Network/Assign Network Virtual Machine/Configuration/Add or remove device Virtual Machine/Configuration/Change CPU count Virtual Machine/Configuration/Memory Virtual Machine/Interaction/Power On Virtual Machine/Inventory/Create from existing On the specific resource pool: Full permissions recommended On the template(s) to be used Virtual Machine/Provisioning/Customize Virtual Machine/Provisioning/Deploy template To create and tear down port groups: On the datacenter: Host/Configuration/Network configuration To create and tear down distributed port groups: On the datacenter: dvPort group/Create dvPort group/Delete vSphere Environment You require a working vSphere environment. »

The vCloud Plugin 2 enables you to use a vCloud-based infrastructure for deploying services and applications. Plugin Requirements Conductor Manager 5.1 or greater. (Python version 3.6.) vCloud Directory 29.0 or greater. The plugin is not compatible with blueprints written for tosca-vcloud-plugin. Authentication with vCloud Director Each node template, has a client_config property which stores your account credentials. Use an intrinsic function to assign these to the values of secrets](/working_with/manager/using-secrets/) in your manager. »

Studio Conductor NSX-T Plugin enables users create NSX-T Resources in NSX-T manager. Release History See releases. Authentication with NSX-T Each node template, has a client_config property which stores your account credentials. The client_config consists of the following: host: Required.: Your NSX-T Manager Host IP. port: Required.: Your NSX-T Manager Port that listen on. username: Required.: Your NSX-T Manager Username. password: Required.: Your NSX-T Manager Password. auth_type: Authentication Type. It supports the following: basic: Default value. »