Working with Conductor

Using the Conductor Manager

Manage blueprints (a logical representation, or topology) of an application or infrastructure.

Official Plugins

Overview of Conductor Plugins

Using the Conductor Console

The Conductor Management Console provides a streamlined experience for managing and analyzing your applications. It requires a Conductor Manager to run. In addition to being able to upload blueprints, create deployments and execute workflows, the interface provides log and events views, application and network topology visualization, and more. It provides most features available in the command-line interface and more. Getting Started Conductor Manager supports user management, so users must log in with user credentials.

Managing Deployment Workflows

Workflows are automation process algorithms. They describe the flow of the automation by determining which tasks will be executed and when. A task may be an operation (implemented by a plugin), or other actions including running arbitrary code. Workflows are written in Python, using a dedicated framework and APIs. Workflows are deployment-specific. Each deployment has its own set of workflows, which are declared in the Blueprint. Executions of a workflow are in the context of that deployment.

Service Composition

Introduction Applications, network services and most software solutions are typically composed of multiple components. These may be cloud-native micro-services or simply smaller scale services leveraged by the overarching service to create a composite solution. Typically there are two types of such services: A shared resource, is a service used by multiple other services, for example a database which is leveraged by multiple applications. The shared resource is usually an existing entity and deployment of the application service will not provision the shared resource, it will only interact with it.

CI/CD Integration

Studio Conductor provides integration with various CI/CD platforms. Jenkins Plugin Introduction to Jenkins' Conductor integration GitLab CI/CD Introduction to Conductor's GitLab CI/CD integration Specifying Conductor Manager Access (This section does not apply to the Jenkins plugin) When using the standard Conductor CLI, the user is required to create a CLI profile, describing the location of the Conductor Manager as well as credentials. This is traditionally done by using the cfy profiles command: