by James Fryman
This post originally appeared November 16, 2014 on VentureBeat.
Recently, I had the honor of speaking at DevOpsDays Berlin and attending DevOpsDays Ghent 2014. Both conferences included plenty of discussion surrounding the fifth anniversary of the speaking series, with as many enthusiastic ‘State of the (DevOps) Union’ conversations to match.
Attendees expressed varied interpretations of the meaning of DevOps, how companies are approaching implementation of the ideas discussed in DevOps, and the latest technology musings which mostly consisted of inquiries regarding if (and how) Docker was used within respective companies. These topics were examined during my recent talk in Berlin, DevOps Day 2: People and Process.
I’d like to present my perspective about my own experiences in tackling many of the challenges in the DevOps methodology, and many of the subjects I have discussed with others along that journey.
November 4, 2014
With the DevOps movement in full swing, there’s no shortage of automation software. Tools such as Chef, Puppet, Salt, Ansible and others are becoming more popular as enterprises are looking for better ways to automate all of the manual, repetitive tasks.
StackStorm has automation at its core, but goes beyond that. The open source software ties in continuous integration (CI), continuous deployment (CD), troubleshooting and remediation, and is capable of automating tasks triggered by specific events, even across different environments. It connects your existing infrastructure and applications and manages multiple integrations. So a trigger in one part of your infrastructure can set off an automatic process (or a set of processes) in another […]
Like Chef, Puppet, and Ansible, open source StackStorm system helps automate interactions between parts of IT
November 4, 2014
StackStorm, staffed by former members of GitHub, PuppetLabs, SwiftStack, Rackspace, and the Apache Libcloud team, has launched the first public version of its eponymous open source operations automation solution.
Written in Python and available under the Apache 2.0 license, StackStorm gives IT departments a way to automatically trigger or drive behaviors in one part of their infrastructure via events in another. Events ranging from troubleshooting to continuous integration can be made into scriptable processes […]
November 4, 2014
Yesterday, StackStorm announced the release of StackStorm 0.5, an open source software solution for operations automation. To find out more about the company and the new release, I spoke with Evan Powell, co-founder and CEO.
VMblog: Can you start off by giving readers a little background on StackStorm?
Evan Powell: Dmitri Zimine, the former director of R&D and cloud infrastructure at VMware, and I founded StackStorm in 2013 with the vision of creating a truly self-driving data center. StackStorm is sometimes described as the wiring for your Legos – tying together and making sense out of the many loosely coupled components of today’s IT environments. Since coming out of stealth in May, our software has been available in private beta and we’ve learned a huge amount about both the power of operations automation and the challenges to its adoption. Now, we are thrilled to open source StackStorm 0.5, which encapsulates much of what we have learned […]
November 3, 2014
As IT continues to be increasingly complex to manage, more organizations are looking to automate as many management functions as possible. The challenge is that many of them don’t have the budget to do anything more than write a handful of scripts themselves.
Moving to take that issue off the table, StackStorm today at the OpenStack Paris 2014 conference unveiled a namesake IT automation platform that is available as open source software […]
November 3, 2014
The startup StackStorm is taking the first step toward popularizing the software it’s built to help people more efficiently run and update applications in whatever data centers they choose.
Today, in conjunction with the OpenStack Paris conference, StackStorm is releasing the 0.5 version of its software under an Apache open-source license, giving people a way to try it out and discover its capabilities.
And Evan Powell, StackStorm’s chief executive and a cofounder of the startup, is confident that when operations people take the software for a spin, they’ll be blown away. That’s because StackStorm can automatically run processes in data centers based on rules that people can set ahead of time, and these rules can then be sent out to others. Such features distinguish it from other data center automation tools.
November 3, 2014
StackStorm delivers enhanced productivity within highly automated DevOps environments; expands team to drive growth in open source community
PARIS (OpenStack Summit 2014, booth E2) – November 3, 2014 –StackStorm, a software company leading the third wave of operations automation, today announced the release of StackStorm 0.5, open source software for operations automation. Available in private beta since spring 2014, the open source software is now accessible for technology companies and enterprises to manage the integration and automation of their environments, such as tying together continuous integration (CI), continuous deployments (CD), ongoing troubleshooting and remediation and more.
To keep pace with increasing business demands and to expand the company’s presence in the open source community, StackStorm has also brought on new team members that have contributed to progress in DevOps and OpenStack. Former operations hacker at GitHub and PuppetLabs, James Fryman has joined as a DevOps Stormer, and Tomaz Muraus, project chair of Apache Libcloud who most recently worked at Rackspace, has taken on the role of software engineer. In addition, Don Jaworski, member of the board of directors at SwiftStack and a well-regarded leader and advisor of infrastructure companies, has joined as an advisor.
November 3, 2014
by Evan Powell
Today we are excited to announce the open-source availability of StackStorm, our operations automation software.
StackStorm ties together your existing infrastructure and application environment so you can more easily automate that environment — with a particular focus on taking actions in response to events.
With StackStorm you define, and share – as code – your operational patterns from events and triggers through to actions taken in response.
Whether it is wiring together your continuous integration (CI) and continuous deployment (CD) environments in a transparent way, or automating your troubleshooting and even remediation (including responses to security events, or any of the other common patterns you perform each day manually or with the help of siloed automation), StackStorm helps.
November 3, 2014
By Patrick Hoolboom
For this I’ll be using Virtualbox and Vagrant. To use the same environment, just clone this repo:
Once you do, you simply run:
vagrant up
It takes a few minutes for this to fully provision, but one it does you can connect to the host with the vagrant ssh command.
vagrant ssh
November 3, 2014
By Patrick Hoolboom
Within the StackStorm community repo there is a script called metagenerator.py. If you run this script against an existing fabfile, it will generate all the necessary meta data to add the Fabric tasks into St2 as actions. Also included with this integration is an action needed to execute the actions.
To get setup you need to clone this repo to somewhere on your machine:
git clone https://github.com/StackStorm-Exchange/exchange-misc.git
Once you have the repo cloned, cd into fabric/actions
cd exchange-misc/fabric/actions