 All right, guys, today we're talking about StackStorm. Thank you for coming here and hearing about what is the if, this, then that for DevOps Automation. And we only have 20 minutes to cover what is StackStorm, show some use cases, and tell you about what is the current state of StackStorm and what's coming next. So what is the StackStorm? Well, we build something which is a very generic event driven automation platform. And this thing is very difficult to explain. So to explain that simply, we're usually trying to say what StackStorm is like. And StackStorm is like if, this, then that, but for DevOps. And like in this, then that, something happens and then you take some action. Just like in this, because it is for DevOps, in DevOps, all the artifacts are code. It is exactly like that. There is a trigger, something happens, maybe sensor or Nuggets when handler. Here is a criteria, the pattern match. Here is an action, take some remediation things. Of course, we have a nice UI that we hammer home the same point. StackStorm is, if this happens, run this action. And I think at this point, we're done. You know what StackStorm is, and you can go around and enjoy the show. But you know what, let's give a little bit more details. So the main ingredients of StackStorm is that's again, there's an open source platform that sits on top of your existing infrastructure. You have clouds, you have Kubernetes, Docker, OpenStack, Amazon being where, you have the typical DevOps tools like ChefPuppet, Ansible. You have a lot of your scripts. You have the business things like Slack or JIRA or GitHub. And on top of that, we have the sensors that are responsible for inbound integrations. That means something happens. It might be a monitoring event, or it might be the change in the temperature in this room. Or it might be someone came by the StackStorm booth and tweeted about StackStorm. And then it goes into the rules when this happens, what kind of action do we take? And then it takes the actions. And actions are usually simple and atomic. And to stitch them all together, you require the workflows. We use Mistral as a workflow engine. We actually, one of the Mistral contributors. And then the actions, again, we have a bunch of actions out there on the StackStorm exchange. They are ready for you, but it takes only few lines of metadata to turn your existing script into the action. You tell the StackStorm that these are the positional arguments. These are the key well arguments. And then you run StackStorm action create and your existing scripts is now in action and it has an API. It has the UI. And it can be stitched with other actions with the workflow. So canonical example, a monitoring thing. You know, like we, for instance, we have a service. When we have a monitoring system, by the sense we're not use, something happens. The sensor goes to StackStorm and says, well, there's a problem. We are running out of disk space. The automation checks if it is something that we can fix. And if it is, we fix that. If it is something that requires human intervention, we call the platform maybe VictorObsware or PagerDuty and like wake up body, you need to take a look at that. And these, the simplest thing, the outer mediation, you know, takes wonders. Now, what can be automated? StackStorm is pretty generic and like I got a hammer, I probably can automate everything. So the right question is what have been, what we should automate? And we should automate things within the reason. And as the book, the kind of practice of cloud automation system says, we need to automate the irritating things which irritate us too often. You know, things that are easy to automate and then happens often. And what has been automated with StackStorm? In fact, a lot of things. We, StackStorm team are supporting the OpenStack platform and we promote some of the use cases like outer mediation, network automation, but there is a number of things that community is doing with StackStorm. And I'll just highlight a few of them. Outer mediation probably is the biggest one. You know, of all the outer mediation tool, Facebook's F-bar is probably the most notorious and it is notorious because they outer mediate 94% of the incidents. And what they say is it is still a lot. Like for the record, they're not using StackStorm, but we are friends and we inspire each other architecture. And on the other hand, StackStorm has been used for out remediating OpenStack installations. Last year in Barcelona, Mirantis presented using StackStorm to out remediate the semantic cloud. The most well-known example of StackStorm based on the remediation is Netflix. They have Winston, which is the application on top of StackStorm, they put some specific on that. And they really hammer home on why outer mediation is better. It compresses the time, it reduces the burnout on the people, and it has the kind of overall positive impact. And sometimes it avoids the accidents all together because the things are remediated at computer time, not at the human time. Network automation. We are part of the bracket. And of course we're doing network automation and not only with the network, bracket network, we recently launched the integration with Napalm. And Napalm is the similar thing that is the cloud leap for cloud computing that enables you to automate a number of the network operation systems. And we introduced the automation pack, integration pack for Napalm. And people right now are using StackStorm to automate a variety of networking devices. Of course, when it comes to bracket and working devices, we are doing even more. Integration. Automation switch, sorry. Integration. One of our partner dimensional data put up this slide. They're using StackStorm to deal with what we call an integration spaghetti. You know that every monitor and tool has an ability to launch the script. And everything nowadays have an ability to receive the webhooks and shoot the webhooks. And once you begin to integrate one thing to another, another thing to another, soon you have a picture like that. And these guys actually got into this mess. The way out of that is like, and the problem with this is once things go south, you want to turn off your automation sometimes. And where exactly do you turn it off here? And using StackStorm to integrate a variety of IT systems is one of the big use case. And there is more to that. People are using StackStorm, dimensional data specifically, doing some security automation. They're replacing the legacy runbook systems, Microsoft System Center Orchestrator with StackStorm and say that delivers a lot of kind of DevOps goodies like infrastructure and code and others. And the guys also the contributors, they joke that StackStorm is like the duct tape for the data center. And once you have that, you find a lot of usage for that. Fun stuff. I mean, if you look at StackStorm Exchange, you will see that there is a variety of interesting packages here is, you know, the Tesla Park for StackStorm right now not only can honk the Tesla but does pretty advanced things with that. And do check out the booth show where our guys are using StackStorm to control their robotic arm as a response on your Twitter tweets about the StackStorm. So check it out. Serverless becomes a trend right now and it's right now more than a trend. It's actually delivers massive value. And this is a picture of OpenWisk. And if you screen a little bit and compare that with StackStorm, like we have events, triggers, rules, results, that's what we do in StackStorm. And now I'm actually, it's easy for me to explain what StackStorm is effectively. What is the Amazon Lambda and Amazon Step Functions? Lambda is actions and sensors and Step Functions is the initial workflow that we use. Exactly like that. So, and in fact, we are seeing people using StackStorm for the do-it-yourself serverless implementations. To more Wednesday 9 a.m., we have a session dedicated to StackStorm and serverless as it is related to OpenStack. So please check it out if you're interested, but this is a big and interesting trend. Like as I say, there is a variety of the use cases for StackStorm. We have a big platform and we support some of the use cases and we do invite people to try it out and see if it applies to their use cases as well and supply them and maintain them. So, when people look at the workflow-based solution and say, why don't I just, like now one is actually saying, why don't I do that manually? Everyone wants to automate stuff. But people are asking, why don't I, for instance, why don't I use scripts? Well, everyone is doing scripts. Like there are some problems with those. Like scripts are great. And StackStorm is not saying that scripts shouldn't be used. We're just placing them in the right place, which is your script is an action. However, stitching things together with scripts has drawbacks. The workflows are harder to write because we all know how to write scripts. Workflow is a little bit awkward, but workflow is superior in operations. Workflow is very reasonable. Yet it is transparent. It is not two-in-compliant language. It is just the serious events. And when something happens, you know that. I have a workflow that takes five steps. I'm on step three and I'm failing. Workflows are resilient. So if the system that runs your workflow goes down, workflow is resilient to continue execution when the system goes back up. And again, this is the virtue of StackStorm as a system, as a reliable system because some of the workflow tools out there cannot survive the failure as StackStorm can. And more interestingly, it can survive the failure of the environment. For instance, at the time of the call, the networking may be not available. And StackStorm is trying to reach out to there, but I cannot create the last VM out of the 100 and my workflow is failing. I don't want to start from the beginning. So we have an ability to restart the workflow from the point of failure. For instance, there is networking failure. You fix the networking, it's back. I just go and workflow continues to execute from this point. So workflows are superior in operations. StackStorm and the future. So first of all, we have, you know, it's a hundred million come through but it's 256. It's in binary form. So it's, but yeah, it's an active Apache to open source project. We're fortunate to have brocade support in this. And we have an active community on that. We have a lot of contributions on StackStorm. There is a commercial version of StackStorm to respect the fact that a number of companies has policies in place. They don't let them run anything in production that doesn't have a commercial support. But the open source StackStorm is fully functional not cripple, check it out. We have quite substantial user base. We have about 3000 installations a month. And the StackStorm exchange, the place where we have the integration box is filled up with integration with everything you can imagine. Again, full disclosure, some of these integrations are heavily used there for good. And some of them are just a folding on that. We don't have much of the test coverage on that. But the ones which have the test coverage has a special icon on that. So look at them. And each of them is represented by GitHub repository. And recently we introduced the community maintainers. Notably, there is an open stack back there that automates all open stack actions. So the takeaway here is, if you haven't heard about StackStorm, you just did. I invite you to try it out to use that and to contribute that because this is the community effort and without you, we cannot just bring that. We cannot integrate with everything. So please invite you to contribute. And when we say contribute, everything counts. You're trying out StackStorm, getting the S2 Vagrant and getting the top in 20 minutes or grabbing the StackStorm docker image and getting up and running in five minutes is the easiest thing. Try it out, read the documentation, try to do something with StackStorm. Tell us what doesn't work for you. We actually, we grow on negative feedback. Don't tell us what's good for you, we know. Tell us what doesn't work, help us improve. Commit the code. We have people who are contributing to the main code but we also inviting you to contribute to the integrations. You are using JIRA, help out to make the JIRA integration better. You're using kind of OpenStack, using some particular products, please do help us do that. And then spread the word. Like we have about 60 people here in the theater. If each of you will tweet about StackStorm, there will be someone who will know that StackStorm is an interesting project worth checking out these accounts and contribution as well. With that, thank you. And lastly, we are 50 stars away from crossing the 2000 stars on GitHub. Me, I rate my talks by the number of GitHub's I gather after the talk. So, if you don't mind, go to StackStorm, S2, and give me a star and I'll see how did I do. Thank you.