Hello fellow automators and welcome back to the series of meetups, now that the summer is almost gone, and we are starting up the new season.
We got two speakers with really interesting topics:
Mirantis, who will share how they auto-remediate 1,000 node OpenStack cloud at Symantec using StackStorm platform.
Netflix, who will present (and demo!) Winston Studio – you might have read about it on Netflix tech blog, now you will hear from the source and actually see it.
WHEN: Thursday, October 20, 6:30 PM – 9:00 PM
WHERE: Theater @ Brocade, 130 Hoger Way, San Jose, CA
Sep 30, 2016
by Lindsay Hill
Hey folks, StackStorm v2.0.1 has been released, with a few small fixes and enhancements. We’ve also had some great code contributions recently, with a new integration for Datadog, and improvements to our Github and Nagios packs.
Read on for details, plus a few hints on what we’re up to next.
Sep 20, 2016
by Dmitri Zimine
I set up a sensor to watch for a trigger (trigger represents an external event; sensor will fire a trigger-instance of the trigger type when the event is detected). I created a rule: if the trigger happens, and matches the criteria, it should fire an action. I see that event had happened. I expected the actions to fire. But it didn’t happen. Where did it break?
This is a long read, and may look complicated. But really, it’s just three debugging steps. And it’s long because I refuse to write briefly, drop bunch of hints on the way and get you distracted. But as they say in math, the thicker the math book the faster it reads. Brace yourself.
In the example below, I’ll be showing you how we debugged our Twitter automation that scans tweets for mentions and posts it to Slack. A pretty good way to keep track on who is trash talking about us! The debugging “runbook” is generic and applies to troubleshooting other rules just fine.
First, let’s look at the trigger chain and review how it works.
September 1, 2016
by Lindsay Hill
StackStorm Enterprise is back, and it’s now Brocade Workflow Composer. We’ve just shipped version 2.0. The platform has had a look & feel update, the usual round of bugfixes and enhancements, and we’re introducing “Network Automation Suites” for our networking friends. More on those in a minute.
Did you miss me?
We know that you’ve been asking about the future of StackStorm, where the project is going, when you can buy StackStorm Enterprise again, etc. Well, today we should be able to answer all of those questions.
READ MORE…
August 10, 2016
By Tomaz Muraus
A good month after releasing StackStorm v1.5.0 we are happy to announce the release of StackStorm v1.6.0.
This release includes various new features and improvements described below.
We have listened to feedback from our users and updated action concurrency policies to allow action execution to be canceled instead of just delayed when a concurrency threshold is reached.
This feature comes handy in situations where multiple users request the same action, but the action is already running because of the first request.
July 26, 2016
by Lindsay Hill
We love our users. We love them even when they report bugs. We love them because they report bugs. But we really, really love our users when they report bugs, along with complete configurations, how to reproduce the bug, and logs. Recently Brian Martin did just this, helping us resolve a tricky deadlock bug. Thank you Brian!
When you’re investigating a bug report, the first thing you want to do is to try to reproduce it. This helps you see what’s going on, and it gives you a clear test case to see if you’ve resolved it. Deadlocks & race conditions can be horrible bugs to work with, as they are often difficult to reproduce. They might depend upon your hardware resources, or what other jobs are running at the same time. Even reproducing it on the exact same setup is tough.
July 13, 2016
By Tomaz Muraus
Today we are happy to announce the release of StackStorm v1.5.1.
This is primarily a bug-fix release which includes bug fixes and improvements for some of the features which have been introduced in StackStorm v1.5.0.
We would like to thank Cody A. Ray for reporting the first two issues and also helping us debug and troubleshoot the second one. In addition to that, we would also like to thank lbogardi and Steven Bakker for reporting the LDAP backend limitation and also proposing a solution for it.
If you are running StackStorm v1.5.0 we would like to encourage you to upgrade to the latest release and if you are not running StackStorm v1.5 yet, we would also encourage you to upgrade so you can utilize cool new features such as Improved Pack Configuration, Datastore Secrets and more.
The StackStorm documentation is pretty good. But it’s not always enough. Sometimes you need a bit of help. Sometimes you think you’ve found a bug, and want to talk with the developers about it. That’s where our StackStorm community support can help.
I’m sure you’ve heard us talk about our Slack channel. It’s a great place for StackStorm users to get together, share ideas, and solve problems. But did you know that our Stormers are in this channel, and do their best to help support the community?
Our engineers hang out here from 9:00 -> 17:00 PST, and often later. They’re happy to answer whatever questions you have. Just in the last few days, we’ve had questions about installation, ChatOps setup, writing sensors, purging history, creating actions, etc. Because the core engineers are involved in those discussions, not only can they help fix problems, they can also explain the design thinking.
June 30, 2016
By Tomaz Muraus
The last couple of months, since the Brocade acquisition, have been pretty busy for us here at StackStorm. We have been getting to know our new friends at Brocade, learning the typical networking use-cases and figuring out how we can use StackStorm to automate them and bring all the DevOps and data-center automation goodness to the networking space, while keeping StackStorm a generic DevOps automation platform.
As always, we have continued to support our users and the community. We also haven’t been slacking with the StackStorm feature development and improvements. We have worked hard to bring you two new releases in the last 2 months – StackStorm v1.4 and StackStorm v1.5.
StackStorm v1.5 which has been released just recently includes many new features and improvements so if you haven’t already, I would encourage you to go check it out.
Today I will talk about the one of the major new features in StackStorm v1.5 which has been discussed and requested many times in the past already. That is improved pack configuration.
