<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Todd Wells on Medium]]></title>
        <description><![CDATA[Stories by Todd Wells on Medium]]></description>
        <link>https://medium.com/@toddwells?source=rss-4c0e68851c6d------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*sm15Xrx_VuFnue7D.png</url>
            <title>Stories by Todd Wells on Medium</title>
            <link>https://medium.com/@toddwells?source=rss-4c0e68851c6d------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 18:50:10 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@toddwells/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[ChatOps Integration with Automation Tools]]></title>
            <link>https://medium.com/@toddwells/chatops-integration-with-automation-tools-3bb6d539150c?source=rss-4c0e68851c6d------2</link>
            <guid isPermaLink="false">https://medium.com/p/3bb6d539150c</guid>
            <category><![CDATA[chatops]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[Todd Wells]]></dc:creator>
            <pubDate>Wed, 23 Mar 2016 17:06:01 GMT</pubDate>
            <atom:updated>2016-03-23T17:06:01.181Z</atom:updated>
            <content:encoded><![CDATA[<p>ChatOps Integration with Automation Tools</p><p>My <a href="https://medium.com/@toddwells/chatops-fomo-ff46ca16c9fa#.np64ycgmn">previous post</a> of “discovering ChatOps” and being convinced of its value lead me down the garden path of how to Integrate. I am using <a href="http://saltstack.com/">SaltStack</a> for IT Automation and SaltStack has served that role admirably ( sorry no Puppet/Chef here). And now I want to move forward with ChatOps. To do that of course ChatOps needs to talk to SaltStack, which means a bot. And the bot that seemed the best to me was <a href="https://hubot.github.com/">Hubot</a> from those fine people at github that started this whole ChatOps thing.</p><p>Unfortunately, when I looked at how to get Hubot and <a href="https://slack.com/">Slack</a> talking I let scope creep come in. I decided that a job scheduling tool would be a good gateway between Salt and Chat Ops. This was a best intention for I wanted to make sure I was not contributing to integration hell with dozens of different integrations to our chat software Slack. There are already several different sources sending data into Slack. And ChatOps will be another one. And then there is SalesForce integration to slack. And I am sure many more to come. What If I could put a tool in place that would be the gateway between Slack and all of these tools. It would be a layer of abstraction that could be good to have.</p><p>And so I ended up trying two options: <a href="https://stackstorm.com/">StackStorm</a> and <a href="http://rundeck.org/">Rundeck</a>. I liked both of these tools for different reasons, but I thought that the more dynamic event driven jobs scheduling model of StackStorm fit better. After all, ChatOps is also event driven so using StackStorm with its integrations to the major chat platforms seemed like a good solution. The StackStorm all-in-one installer got me up and running quickly, but with a few problems with the integration to SaltSack. Thanks to the very responsive ( and Slack based) <strong>#community</strong> group at StackStorm I was able to get it working.</p><p>And by working I mean I now have every salt command available inside of my Slack, including the ability to run arbitrary commands against any server … test, staging, PROD. Nope, not going to leave that in place. ChatOps needs some limits, so I set forth to figure out how to limit it to just what I wanted to expose. But hours later I was not really making progress on those limits. The integration layer between StackStorm and the Hubot bot that actually connected to Slack did not really seem to have the flexibility to do what I wanted. Or if it did it was going to take a lot of work to figure out and there was not a lot of information out there to help me. ( And I am certain that if I come back to StackStorm in a year there will be a lot of improvement in this area )</p><p>Time to regroup and re-assess. The gateway ( StackStorm ) was making the job of integrating my SaltStack and Slack harder, and I was not convinced that my goal of using it as a single point of integration was really going to work. And so I jettisoned the scope creep and went back to a simple integration between SaltStack and Hubot.</p><p>tbc</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3bb6d539150c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[ChatOps FOMO]]></title>
            <link>https://medium.com/@toddwells/chatops-fomo-ff46ca16c9fa?source=rss-4c0e68851c6d------2</link>
            <guid isPermaLink="false">https://medium.com/p/ff46ca16c9fa</guid>
            <category><![CDATA[chatops]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[Todd Wells]]></dc:creator>
            <pubDate>Mon, 21 Mar 2016 01:02:16 GMT</pubDate>
            <atom:updated>2016-03-21T01:02:16.457Z</atom:updated>
            <content:encoded><![CDATA[<p>ChatOps FOMO</p><p>A month ago I “discovered” the term <strong>ChatOps</strong> and was a little surprised it has been around for over 3 years. Guess I have missed out, but not any more. Time to get me some ChatOps. But first, thanks to the <a href="https://speakerdeck.com/jnewland/chatops">githubbers who came up with this idea</a>.</p><p>I liked <a href="https://www.pagerduty.com/blog/what-is-chatops/">this definition of ChatOps</a>. It starts with a culture where chat is <strong>the</strong> method of development collaboration and adds in tools so that actions are part of the conversation. If you don’t already have the culture adding tools will not really help. But if you do have the culture then adding in the tooling will just make collaboration that much better.</p><p>It only took a few minutes of research for me to understand how valuable this could be. There was definitely coincidence involved in that quick understanding. As the DevOps engineer for a &gt; 20 developer shop, I was used to the requests “can you change staging server xxx-xxxxx-xxx-1 to track branch feature/yyyyyyyyy” happening a few times per week. But in the 2 days before I discovered “ChatOps” it started happening several times per day. The “<a href="http://www.thegeekstuff.com/2011/07/lazy-sysadmin/">lazy sysadmin</a>” in me had of course automated the process so it only took a minute to satisfy these requests. But the increase in frequency was causing chafing at having to make this change at all. Now comes ChatOps as a solution to this chafing.</p><p>But how to implement ChatOps. My next hour or two of research gave me many possibilities, and lead me down a path of frustration and eventually starting over and going with the simple solution.</p><p>tbc</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ff46ca16c9fa" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>