Dmitri Zimine's slides on Design Summit at OpenStack Barcelona 2016. Talked about the history of two projects, technical differences, discussed an overlap and drafted a path forward.
https://www.openstack.org/summit/barcelona-2016/summit-schedule/events/16999/mistral-mistral-and-stackstorm
In conclusion, a shameless plug for StackStorm opensource platform and to it’s commercial twin, Brocade Workflow Composer.
To get a taste of event driven automation, Install and use Stackstorm, try out BWC, that comes with that nice graphical workflow designe.
Please share your experience with our community (we are on slack),
And happy automation!
This is a high level overview of the key Workflow Composer components and architecture.
Workflow Composer is powered by StackStorm
StackStorm is an innovator in event-driven, DevOps-style, cross-domain automation
Powered by StackStorm, Workflow Composer provides nearly 2000 points of integration with popular cross-domain platforms and technologies.
StackStorm provides 3 key technologies: Sensors, Actions, and Rules.\
These technologies work hand-in-hand with workflows to provide true end-to-end, event-driven, cross-domain automation.
Sensors and Actions are points of integration that use APIs to integrate with cross-domain platforms and applications. Sensors listen for specific events while Actions execute commands.
Rules use IFTTT logic to determine what actions to perform based on inputs from Sensors.
This highly flexible, scalable approach enables BWC to easily integrate within any DC process, tool chain, and existing workflows.
This unique, high-scalable, highly flexible approach to enabling cross-domain automation allows organizations of all sizes and maturity to deploy true end-to-end, event-driven automation that meets IT challenges today and into the future.
Assume you run an app on a server in your data center. The server is running out of disk space. Shamefully, it’s much more common source of failure that most care to admit.
The monitoring tool picks that the server is running low in disk, and raises an event.
Automation system catches the event, and fires a “low disk space” trigger
The rule is set to run a “remediate out-of-disk” workflow on “low disk space” trigger’; it matches, so it runs the workflow.
The workflow runs the process as defined. It may goe and checks what the problem is. And if it’s a known problem with known fix, it fixes it automatically. For instance, if the logs didn’t rotate and filled up the space, it cleans the logs. If something unusual happening, it escalates to human.