Unleash the power of IoT with Event-Driven Automation (ST2 & BWC @ SuperComputing16)

By Chip Copper, PhD; Principal Technology Evangelist, Brocade
Nov 14, 2016

The pattern is the same: “I can’t because we don’t…”, “But we are also…”, “Can I …”, and finally “How do I get it?”

We’re demonstrating Brocade Workflow Composer (BWC), powered by StackStorm, at SuperComputing16 in Salt Lake City. When you stop by booth 1131, we will give you a token of our appreciation. It’s an NodeMCU microcontroller. It’s pretty cool – WiFi built in, ARM microcontroller, lots of GPIO pins, and it can easily be programmed using the freely-available Arduino IDE. It gets you into the world of IoT quickly and easily, and it’s a lot of fun! Bonus!

But there is a catch – you have to watch a demo to get it.


The StackStorm/BWC demo shows how to automate the acquisition and analysis of data from a number of sensors running on a test stand. To start the workflow, all you have to do is message the system. Picture yourself on your way into the office to start the day’s work. To get last night’s data, you open Slack (or your favorite chat tool) on your phone and send the message “!build the graph.” StackStorm/BWC is a member of the chat group, and it responds by telling you that it’s getting started. A few minutes later while standing in line at your favorite coffee shop, you get another chat message from StackStorm/BWC letting you know that the latest set of data is sitting on your virtual desktop ready for analysis. That’s the way to gather data!

So what happened in the background to make that happen? When StackStorm/BWC got the message to get the data, it kicked off a workflow. The first step was to provision the network to allow the data to be read from the sensors. For security reasons we don’t want to leave the sensor data acquisition machine on the data vlan all the time, and so the automation begins by provisioning the network port that is attached to the sensors onto the data vlan.

This where I typically get the first bit of feedback – “I can’t because we don’t use Brocade switches on our data acquisition network.” That’s ok, this is open source software. Even though using BWC with Brocade VDX or SLX switches and network automation suites would make this a WHOLE LOT SIMPLER, you don’t have to. We’d really like you to use Brocade VDX or SLX switches and our network automation suites, you don’t have to. The odds are that someone else has already written the sensors and actions that work for your network platform. If they haven’t, you can do it pretty easily and you can contribute it back to the open source community just as many others have done. This means that you are not locked into any platform or API. You can use whatever you have.

The next step is to validate network connectivity to the sensors. The sensor platform takes a few minutes for the network port to come up. BWC waits patiently until it receives confirmation that the sensors are ready. The sensor platform that we’re running here is based on Linux. Time for the second question:

“But we are also running experiments on dedicated lab devices with their own APIs. I can just interface with them the same way that I’m talking to any network device I want. right?” Right! Suddenly the reality of platform independence comes through. People stop thinking the limitations imposed by brands of equipment and start thinking about workflows that can be built on whatever has been deployed.

BWC then transfers the data file from the sensor platform to the analytics platform using the native scp tools available in Linux, but again, that could be anything available on the platform you are using. Upon completion, the network port for the sensors is once again turned off. Heads shaking. They get it.

“Can I have the analytics chain be driven by StackStorm/Workflow Composer as well?” Yup, that’s the next step in the workflow. The data can be submitted to a work queue, the analytics can be done immediately, or in this case, the data is simply handed off to gnuplot for some quick validation.

The last step is to let you know that everything has been completed and is ready for your examination, and so you get the final chat while you are still in line in the coffee shop. If you like, it can even remind you to put some of that flavor stuff on top of your coffee when it is ready. (I’m not a coffee drinker so I don’t know what that stuff is, but I see people doing it all the time so it must be pretty good.)

Finally, the smile. The person watching the demo gets it. Platform independent workflow management with an interface as easy as a chat session. “How do I get it?” Glad you asked! Just head over to StackStorm.com and off you go. Install StackStorm, and join the community. You’ll be inspired to hear the innovative use cases our community has for StackStorm/Workflow Composer

“And here is your NodeMCU. Thanks for stopping by.” They smile. “Of course, I can automate this with StackStorm/BWC too.” “Of course!”