Skip to content
StackStorm with Tomaž Muraus and Patrick Hoolboom episode artwork

Apr 16, 2016 59 min

StackStorm with Tomaž Muraus and Patrick Hoolboom

from The Python Podcast.__init__ Hosted by Tobias Macey

Visit our site to listen to past episodes, support the show, join our community, and sign up for our mailing list. Summary If you are responsible for managing any amount of servers, then you know that automation is critical for maintaining your sanity. This week we spoke with Tomaž Muraus and Patrick Hoolboom about their work on StackStorm, which is a platform for tracking and reacting to events in your infrastructure. By allowing you to register actions with event triggers it frees you from having to worry about a whole class of concerns so that you can focus on building new capabilities rather than babysitting what you already have. Brief Introduction Hello and welcome to Podcast.__init__, the podcast about Python and the people who make it great. Subscribe on iTunes, Stitcher, TuneIn or RSS Follow us on Twitter or Google+ Give us feedback! Leave a review on iTunes, Tweet to us, send us an email or leave us a message on Google+ Join our community! Visit discourse.pythonpodcast.com for your opportunity to find out about upcoming guests, suggest questions, and propose show ideas. I would like to thank everyone who has donated to the show. Your contributions help us make the show sustainable. For details on how to support the show you can visit our site at pythonpodcast.com Linode is sponsoring us this week. Check them out at linode.com/podcastinit and get a $20 credit to try out their fast and reliable Linux virtual servers for your next project I would also like to thank Hired, a job marketplace for developers and designers, for sponsoring this episode of Podcast.__init__. Use the link hired.com/podcastinit to double your signing bonus. ODSC East in Boston is happening on May 21st – 22nd. Your hosts as usual are Tobias Macey and Chris Patti Today we are interviewing Tomaž Muraus and Patrick Hoolboom about the StackStorm project, which is an event-driven system automation framework. Interview Introductions How did you get introduced to Python? – Chris What is StackStorm and what problems does it solve? – Tobias What was your inspiration for creating StackStorm and what were some of the biggest architectural and design challenges? – Tobias What made you choose Python for StackStorm’s implementation rather than another language like Go? – Chris Can you describe the architecture of StackStorm and what the setup looks like? – Tobias Other than chat driven events, what types of event sources does StackStorm support, and what use cases do those alternate event streams enable? – Chris The home page describes StackStorm as being an event-driven framework for automating the users infrastructure. What kinds of capabilities are made possible by this and do you think that it simplifies or complicates the work of operations engineers? – Tobias Is there a minimum or maximum size of infrastructure for which it would make sense to use StackStorm? – Tobias It looks like StackStorm is made up of a number of discrete components. What do the components use to communicate, and how did those choices influence the design of StackStorm’s overall architecture? – Chris I use SaltStack in my work which is a tool that also focuses on event-driven architecture. Can you compare and contrast the capabilities and focus of StackStorm with the features of SaltStack? Would it make sense to use both frameworks in the same infrastructure? – Tobias One of the advertised features of StackStorm is a strong focus on ChatOps. Can you explain that concept for people who might not be familiar with it and describe why it is such a useful paradigm? – Tobias Extensibility is a critical capability for an operations platform due to the wide variety of environments that people are inclined to build. In StackStorm the unit of extensibility is a pack. Can you describe what a pack is and how you arrived at that abstraction? – Tobias Have you encountered any situations in which the concept of a pack has been the wrong abstraction and made something more difficult than it may have been otherwise? – Tobias In very large scale environments like Netflix, how would one build a StackStorm cluster to handle the immense load. More specifically, how does one determine what kinds of machine resources each component needs? – Chris Management of credentials is always a difficult problem in operations. Does StackStorm attempt to tackle that issue or does it defer that responsibility to other systems, such as the user’s configuration management platform? – Tobias Does StackStorm interface with Kibana, Splunk or other log / metric aggregation packages? – Chris What are some of the most surprising uses that you have heard of from people using the platform? – Tobias Keep In Touch Tomaž Twitter website/blog Patrick Twitter Picks Tobias SAWS Bill Peet Chris Grimm Brewing Subliminal Message Sour Red Ale Lobste.rs Medium Tomaž Understanding Air France 447 Aviation Herald Patrick True Nutrition JP Cycles The intro and outro music is from Requiem for a Fish The Freak Fandango Orchestra / CC BY-SA

Episode details come from the podcast's RSS feed.

Embed this episode

Ready to play

StackStorm with Tomaž Muraus and Patrick Hoolboom

0:00 59:22

Chapters

  1. 0:13 Introduction and Podcast Information
  2. 1:23 Meet the Hosts and Guests
  3. 2:02 Guest Introductions: Tomasz and Patrick
  4. 5:02 Overview of StackStorm
  5. 11:43 StackStorm Architecture and Design Challenges
  6. 20:50 Event Sources and Use Cases
  7. 28:58 Simplifying Operations with StackStorm
  8. 35:03 Comparison with Other Tools
  9. 38:36 ChatOps and Its Benefits
  10. 41:18 Extensibility with Packs
  11. 43:35 Scaling StackStorm in Large Environments
  12. 46:07 Managing Credentials and Future Features
  13. 50:00 Community Contributions and Getting Involved
  14. 51:26 Contact Information and Closing Remarks
  15. 51:54 Picks of the Week

No transcript yet.

Requests help us decide what to transcribe next.

Frequently asked questions

How long is this episode of The Python Podcast.__init__?

This episode is 59 minutes long.

When was this The Python Podcast.__init__ episode published?

This episode was published on April 16, 2016.

Is there a transcript available for this episode?

Yes, a full transcript is available for this episode. You can read the complete transcript on the episode page.

Can I download this The Python Podcast.__init__ episode?

Yes. Use the download control on the episode player to save the publisher-provided media file.