Automate complex IT infrastructures with StackStorm

Causal Chain

Generating Workflows

Automation and management tasks are usually characterized by a sequence of actions. In practice, it makes little sense to initiate only one action and launch a subsequent one based on it at a later time. To bundle different tasks, StackStorm uses workflows that assign actions to a higher level of automation and coordinate their execution by running the right action at the right time with the right input. Information can be passed into and processed in such an execution thread. Like actions, you manage workflows in the automation library and fall back on the configurations stored there, if necessary. In principle, a workflow can even be made up of other workflows.

StackStorm supports two workflow variants: ActionChain and Orquesta. ActionChain is the older variant that uses simple syntax to define a chain of actions. The disadvantage of this variant is that complex workflows are not possible. Orquesta is a new workflow engine that recognizes sequential workflows or complex workflows with forks, links, and sophisticated data transformations and queries. The developers advise that you use Orquesta.

StackStorm provides various tools for creating workflows. In the open source variant, you have to make use of console-based development. The commercial StackStorm variant is known as Extreme Workflow Composer [4] (Figure 3), which has an integrated visual editor you can use to design actions and their sequence in a drag-and-drop process.

Figure 3: The commercial StackStorm variant Extreme Workflow Composer provides a visual editor that simplifies the configuration and management of workflows.

StackStorm is under active development and will see further continuous development. The roadmap [5] summarizes planned innovations. However, advance announcements at press time did not go beyond those of the current version 3.3.0.

Conclusions

StackStorm is pursuing a highly interesting approach that significantly simplifies the automation of complex IT infrastructures. The limitation to events and service states could prove to be a disadvantage. Approaches that can act in event-dependent and -independent ways might be a better solution.

Infos

  1. StackStorm overview: https://docs.stackstorm.com/overview.html
  2. StackStorm homepage: https://stackstorm.com
  3. StackStorm Exchange: https://exchange.stackstorm.org
  4. Extreme Workflow Composer: https://stackstorm.com/stackstorm-6/
  5. StackStorm roadmap: https://docs.stackstorm.com/roadmap.html

Buy this article as PDF

Express-Checkout as PDF
Price $2.95
(incl. VAT)

Buy ADMIN Magazine

SINGLE ISSUES
 
SUBSCRIPTIONS
 
TABLET & SMARTPHONE APPS
Get it on Google Play

US / Canada

Get it on Google Play

UK / Australia

Related content

  • Apache Storm
    We take you through the installation of a Storm cluster and discuss how to create your own topologies.
  • Zuul 3, a modern solution for CI/CD
    The Zuul 3 gating system is a free and flexible solution for continuous integration, delivery, and deployment.
  • CloudStack Up Close
    All the great open source cloud solutions have similar goals, but they all have different histories, different communities, and some subtly different areas of emphasis. We asked CloudStack VP Chip Childers about how Apache CloudStack fits in.
  • CloudStack's Chip Childers

    CloudStack is a versatile cloud alternative that runs in data centers around the world but never seems to get as much press as the ever-popular OpenStack. We talked with CloudStack VP Chip Childers on the state of the CloudStack project and the road into the cloud.

  • Questions about the present and future of OpenStack
    OpenStack has been on the market for 12 years and is generally considered one of the great open source projects. Thierry Carrez and Jeremy Stanley both work on the software and provide information about problems, innovations, and future plans.
comments powered by Disqus