January 23, 2015
by Lakshmi Kannan
This week was crazy good at StackStorm. We blogged about the 0.7 release. Though our main focus was around the release, we managed to get some nifty changes in our integrations and platform.
Changes to StackStorm Exchange include:
Linux Pack Improvements
Changes to our development integration repo, st2incubator, include:
Mistral Pack
StackStorm-mistral integration is something we are constantly working on. Some of these integrations are now captured as actions in the mistral pack. We’ll be adding more such actions in the future.
CI/CD Pack
We are an agile team and we iterate fast. With 0.7 release, we added some platform features (like referring to keys in key-value store in action chain). CI/CD pack was updated to use some of the 0.7 features and also got some bug fixes.
RHEL packages
We are constantly working towards increasing the number of platforms we support. In this vein, we now release RHEL packages of st2.
Mistral
We are active contributors to mistral. This week, we added support of complex YAQL expressions in mistral workflows that allows for more sophisticated branching conditions and complex calculation of inputs, outputs, and published variables. We improved StackStorm-Mistral integration. st2 now captures the workflow output from mistral and saves it in the st2 database. So when you kickoff mistral workflow via st2, you get all the task results as well as the workflow output. This allows for multiple workflows to be chained together. We also fixed some critical bugs.
Distributed Deployment
We have an architecture that allows us to scale across multiple virtual or physical servers. We have users actually doing that with us now, and we are polishing this design as we go.
If you haven’t already, we invite you to check out our product by installing StackStorm and following the quick start instructions — it will take less than 30 minutes to give you a taste of our automation. Share your thoughts and ideas via moc.spuorgelgoognull@mrotskcats, #stackstorm on irc.freenode.net or on Twitter @Stack_Storm.