March 15, 2017
by Edward Medvedev
The majority of StackStorm packs are created and submitted by our community. While we do code reviews and give advice, it is our users that helped us reach over 100 integrations.
But a lot of people do not just stop there. Even after submitting packs, they are continuously putting effort into keeping the codebase up to date, reviewing contributions, and helping others. This effort does not go unnoticed—and in the recent post about StackStorm Exchange we have announced that we will be granting pack maintainers full collaboration rights in the Exchange repositories. We are happy to introduce the first maintainers, together covering around 20 packs.
Mar 03, 2017
by Dmitri Zimine
Hey, it’s Dmitri here, back from Scale15x with a short report of what I enjoyed the most.
My talk 🙂 It was a bit symbolic for me. I spoke at Scale13x, comparing and contrasting Enterprise Suites and OpenSource, and stated the free pillars of “Designed for DevOps”:
In my talk this time, I reported back on how we put these three principles in practice with StackStorm, redefining Runbook automation for the time of clouds and Devops. The core of the talk was a live demo of StackStorm, auto-remediation, and ChatOps. Thank you who came for my talk on this late Sunday afternoon and gave me warm welcome and great questions. For the rest, here are the the slides and the video recording.
Feb 27, 2017
by Lindsay Hill
Here’s a nice way to start your week: StackStorm 2.2 has been released! Mistral updates, Jinja in Mistral workflows, Jinja in complex objects, new st2 login and st2 whoami commands, security improvements and more! Our release master put in some hard work over the last few days to get this out the door. Read on for more details.
Feb 10, 2017
by Siddharth Krishna
Want to install StackStorm on a machine that doesn’t have access to the internet? If you’ve got another box on your local network that connects to the public network, you can do this by making it a local package repository server. In this post, we’ll walk you through steps for setting up an apt-mirror server with the required packages and configuring the offline client machine to quickly get a full StackStorm installation up and running!
Feb 06, 2017
by Dmitri Zimine, @dzimine
Last Thursday, we had another great meetup session on Auto Remediation and Event Driven Automation. This time it was in San Francisco at Make School, thanks to our new sponsors Neptune.io. The drive from South Bay was totally worth it!
Feb 2, 2017 by Eugen
Did you know we have Ansible playbooks to deploy StackStorm?
It’s something we’ve been working on quietly for a while:
github.com/StackStorm/ansible-st2
Well, now you know!
Jan 30, 2017
by Edward Medvedev
Warning: this post describes a long set of important changes. It is enormous in size and full of cheesy puns, feelings, and heart emojis. You might prefer to read the documentation if that is not what you are into. Otherwise, grab a favorite caffeinated drink of your choice and let’s begin!
A little while ago we rolled out StackStorm 2.1, a release focused on one primary theme: integration packs.
StackStorm pack management infrastructure is evolving with the demand. As the number of integration packs grows, we want to provide means for faster and easier deployment, make pack development more productive, and encourage collaboration. There are dozens of changes making it happen—both in our internal infrastructure and the StackStorm core—and we are excited and hopeful that through better experience with integration packs, working with StackStorm will become even more efficient, easy, and fun.
As it is the case with all “thematic” releases, 2.1 is more than just a set of features and changes. It has a lot of context around it, and more importantly, it has a story—and this is a story we are now going to tell.
Jan 24, 2017
by Dana Christensen
At DevOps Enterprise Summit 2016, DevOps leaders like Target, American Airlines, Disney, and Quicken Loans spoke of the importance of managing/optimizing operations, addressing technical debt, eliminating silos, collaboration, and the importance of open source and community to drive innovation. I was especially struck by Jason Cox of Disney, who stressed the importance of “creating a culture of courage” where teams are encouraged to be curious, to experiment, explore and embrace change across process, roles, and technology-all for the purpose of enabling meaningful work.
It turns out that these themes are being talked about not only by these large Enterprise DevOps leaders. These themes are being repeated in conversations around the globe with IT leaders who are looking to leverage DevOps practices to successfully drive innovation and digital transformation.
Anthony Shaw, Group Director of Innovation and Technical Talent at Dimension Data has seen this first hand. Anthony not only leads innovation efforts within Dimension Data-but he also travels the world speaking with customers about their business priorities, their Digital Transformation goals, and how the innovative use of technology, organizational structure, community, and transforming day to day operational practices can accelerate their Digital Transformation journey.READ MORE…
Jan 12, 2017
by Siddharth Krishna
Recently we explained how to use Syslog with Splunk & StackStorm to auto-remediate a link going down on a switch. Splunk is a widely used log management tool but there’s also a popular open source alternative – Elastic Stack (formerly the ELK Stack: Elasticsearch, Logstash and Kibana). So if you’re using the Elastic Stack, and are looking to automate event remediation in your environment, you’re at the right place! In this post, we’re taking the same use case as before and talking about how to set up the Elastic stack to collect syslog data and trigger event-based network remediation workflows using StackStorm.
December 20, 2016
by Lindsay Hill
Just in case you missed it, we published StackStorm v2.1.1 late last week. This is a minor update, on top of the major changes to pack management we made with 2.1.
There’s a few small bugfixes and enhancements:
core.http now supports HTTP basic auth and digest authentication.packs commands and APIs.Full details in the Changelog.
This is a recommended update for all v2.1.0 users. Use yum or apt to upgrade your system. If you’re not yet running v2.1.0, make sure you read all the Upgrade Notes. There were some significant changes in v2.1, and it may break your custom packs. It’s worth it though, we promise.