Note

The documentation you're currently reading is for version 2.8.1. Click here to view documentation for the latest stable version.

Roadmap

EWC is still under active development. We welcome community feedback, and encourage contributions. Here’s our plans for the next few releases:

2.9 - ETA September 2018

  • Orchestra Second Beta: Second beta of new “Orchestra” workflow engine.
  • Action Output Structure Definition: Enable optional definition of action payload, so that it can be inspected and used when passing data between actions in workflows.
  • WebUI: Add st2.ask and streaming output to the web UI.
  • ChatOps: Update ChatOps components, and add support for Microsoft Teams.
  • k8s: Reference configuration for running EWC on k8s.
  • Ubuntu 18.04: Support Ubuntu 18.04 LTS.
  • Windows Runners: Add pywinrm-based Windows runner.

3.0 - ETA November 2018

  • Orchestra GA: GA version of Orchestra.
  • WebUI: Datastore viewer/editor, and RBAC UI.
  • ChatOps: RBAC support.
  • HA: Simplify & streamline running EWC in HA mode.
  • Workflow Designer: Updated Workflow Designer.
  • SAML: Support SAML authentication.

This list above is subject to change, based upon customer feedback, and development progress. Monitor the master branch to see how we’re progressing.

See something you really like? Make sure to get involved with testing and PR feedback.

Backlog

Here’s some more things on our list that we haven’t scheduled yet:

  • History and Audit service: History view with advanced search over years worth of execution records, over multiple versions of continuously upgraded EWC.
  • At-scale refinements: Ensure event handling reliability, and event storm resilience. Complete support for multi-node deployment of sensor containers and rules engines for resilience and throughput.
  • RHEL 8.x: Support RHEL/CentOS 8.x when it is released. Drop RHEL 6.x at that time.
  • DB/Filesystem Consistency: Provide better tooling for managing consistency between database and filesystem consistency for rules, actions, sensors, etc.
  • Configurable Sensors: Run multiple instances of the same sensor, with different configurations.
  • Pack Dependency: Better automatic handling of pack dependencies.
  • Python 3: Complete Python 3 support. We are progressively updating code and adding support, but do not yet have a final date for when everything can run via Python 3.
  • RBACv2:
    • Filters: Tag and property based filters, more refined and convenient access control.
    • Permissions: Permissions on key value objects, arbitrary triggers, support for a default role.

Something else you’d like to see on the backlog? Submit an issue. Or want to see something implemented sooner? Submit a PR!

Release History

Done in v2.8

  • Orchestra Beta: Public beta of new “Orchestra” workflow engine.
  • WebUI: Update look & feel of Web UI, and add “Triggers” tab for troubleshooting rules.
  • Python3 Actions: Support Python 3 actions on a per-pack basis.
  • Metrics Framework: New framework for metrics collection for action results, time, etc.

Done in v2.7

  • Action Versioning: Allow running specific action version - better management of rolling upgrades.
  • Mistral Callbacks: Refactor Mistral to support callbacks instead of polling.
  • UTF-8/Unicode: Allow UTF-8/Unicode characters in pack config files.
  • Virtual Appliance: Vagrantbox/Virtual Appliance with ST2 already installed, for quicker testing.

Done in v2.6

  • React Web UI: Rewrote st2web Web UI to use React framework.
  • Streaming Output: Streaming output enabled by default.
  • Pack Development: Shared lib directory for actions and sensors.
  • st2client: Python 3 support for st2client.

Done in v2.5

  • st2.ask: Support ability to request/provide permission to proceed with workflow.
  • Streaming Output: Provide streaming output from long-running actions as it is received.

Done in v2.4

  • Pack UI: Web interface for pack management.
  • Pause and Resume: Pause and Resume Workflows and ActionChains.

Done in v2.3

  • API Docs: Auto-generated REST API docs - see api.stackstorm.com.
  • Monitoring Docs: Create EWC monitoring guidelines.
  • Docker based installer: Complete the vision of OS independent, layered Docker-based installer, to increase reliability, modularity, and speed of deployment.

Done in v2.2

  • Mistral Jinja support: Mistral workflows now support Jinja notation.
  • Security improvements: Better default security posture for MongoDB, RabbitMQ, PostgreSQL.

Done in v2.1

  • StackStorm Pack Exchange: Make integration and automation packs discoverable, continuously tested, and community rated. Solve the problem of packs spread all over GitHub.
  • Ubuntu Xenial (16.04) support

Done in v1.6

  • MongoDB: MongoDB 3.x support.
  • Datastore: Access K/V datastore from the Mistral workflows.

Done in v1.5

  • Pack configuration: Configuration separated from the pack code.
  • Datastore: Key/value datastore secrets.

Done in v1.4

  • Packaging: Deprecation of All-in-One Installer.
  • Packaging: Native deb/rpm packages with bundled python dependencies.
  • ChatOps: ChatOps API support for Slack/HipChat providers.

Done in v1.3

  • Workflows: st2 re-run - resume failed workflows.
  • Scale: Garbage collection service.

Done in v1.2

  • Packs: Pack Testing support.
  • ChatOps: Fully reworked ChatOps with Jinja templating.
  • Policies: Timeout and retry policies.

Done in v1.1

  • FLOW: Visual workflow representation and drag-and-drop workflow designer.
  • RBAC: Role based access control for packs, actions, triggers and rules.
  • Pluggable authentication backends including PAM, Keystone, Enterprise LDAP.
  • All-in-one installer: production ready single-box reference deployment with graphical setup wizard.
  • RHEL 6 and 7 support
  • Trace-tags: ability to track a complete chain of triggers, rules, executions, related to a given triggering event.
  • Native SSH: replace Fabric; Fabric based SSH still available and can be enabled via config.
  • WebUI major face-lift

Done in v0.11

  • ChatOps: two-way chat integration beyond imagination.
  • More integration packs: Major integrations - Salt, Ansible, some significant others. Check the full list.

Done in v0.9

  • Experimental windows support: windows runner, and windows commands.
  • Web UI complete basics: rule create/edit/delete in UI.

Done in v0.8

  • Web UI: refactor history view, create and edit rules and workflows, add graphical representations for workflow definitions and executions.
  • Improved Mistral integration: simplified Mistral DSL for EWC actions, visibility of workflow executions, and reliable of EWC-Mistral communication. Includes Mistral improvements, features, and fixes.
  • Operational supportability: Better output formats, better visibility to ongoing actions, better logs, better debugging tools.
  • Scale and reliability improvements: deployed and run at scale, shown some good numbers, and more work identified.

Done in v0.6.0

  • YAML: complete moving to YAML for defining rules, action and trigger metadata, configurations, etc.
  • Plugin isolation and management: Improved managements of sensors, action runners and provide isolated environments.
  • Reliability: improvements on sensor and action isolation and reliability.

See Changelog for the full gory history of everything we’ve delivered so far.

Questions? Problems? Suggestions? Engage!