Jun 2, 2021
Diamond Beach - StackStorm [J-イビザ]
seen from Singapore
seen from Indonesia
seen from Switzerland
seen from China
seen from Japan
seen from Germany
seen from China
seen from China
seen from Germany
seen from United States
seen from Switzerland
seen from China
seen from Singapore
seen from China
seen from Malaysia
seen from Russia
seen from China
seen from Yemen
seen from United States
seen from United States
Diamond Beach - StackStorm [J-イビザ]
ジュリアナ東方 - StackStorm [TO-HO Hi-SPEED CLUB MUSiC ESSENTiAL]
Building and Contributing a Zendesk Integration Pack for StackStorm (DevOps/ChatOps)
By Casey
Recently, we've been doing work with some DevOps tools and decided to contribute to a powerful open-source project called StackStorm. StackStorm is (according to their website):
"...a powerful open-source automation platform that wires together all of your apps, services and workflows. It's extendable, flexible, and built with love for DevOps and ChatOps."
StackStorm enables enterprises and service providers to orchestrate event-based automation (IFTTT) between different common tools and services, including integrations with things like Chef, Puppet, GitHub, Docker, VMware, Jenkins, Slack, Twitter, Splunk, Twilio, Cassandra, and many more. And with the recent acquisition of StackStorm (the company) by Brocade, StackStorm now has the capability to tie its automation framework into networking and systems enterprise hardware, including Brocade.
After we realized there really weren’t any StackStorm integrations for any customer service ticketing software platforms, we decided to create one for Zendesk, which our team uses currently.
The first step I took when architecting a solution for integrating Zendesk into StackStorm's integration system is figuring out how I'd communicate with Zendesk's API. Since StackStorm is written in Python, I searched online for Zendesk Python API wrappers. It turns out that Zendesk has a great list of these wrappers on their developer site. After looking at examples of both of the top two libraries I decided to go with Zenpy. Zenpy is a great library that is very pythonic and implements every essential feature of the Zendesk API. You can see a few examples of how to use Zenpy at the project's GitHub page.
Once I had decided to use Zenpy, I tested it out by making a few manual calls to a test Zendesk environment I had setup. This helped me to get a feel for how it handles creating tickets and manipulating API objects. Zenpy has a very straightforward API that makes these kinds of calls very easy. The next steps were to begin actually creating my integration pack. I'm going to boil it down to the main points of how I setup my dev environment for creating an integration pack:
Create a fork on GitHub of the st2contrib repo (StackStorm/st2contrib)
Create a branch to work on in my forked repo
Create the base pack structure (guide here)
Start up a VM with StackStorm pre-installed by using Vagrant (guide here)
Once the Vagrant VM is up and running, clone the forked repo into the vagrant folder so that you can work locally and test on the VM
Then setup a hubot instance so that it can properly test chatops aliases (guide here)
Once all those steps were out of the way, it became easy to test out my integration as I was working. The main features of Zendesk that I was aiming to support were: creating tickets, updating tickets, changing ticket statuses, and searching tickets. In addition, I wanted all of those features to be useable through StackStorm's chatops feature. Creating the aliases for StackStorms actions can be a little confusing, but they also have great resources available on their online documentation for action aliases, or by looking through the other packs available in their st2contrib repo.
If you'd like to see more on the Zendesk StackStorm integration pack, you can view the pack here.
Integrate DripStat with PagerDuty through StackStorm
StackStorm is like an If This Then That for your operating environment.
We are today announcing deep integration of DripStat with StackStorm so you can take advantage of the full breadth of integrations that StackStorm offers and use it with DripStat.
Read our blog post on the StackStorm blog that shows how you can get PagerDuty working with DripStat through StackStorm.
Catching up with Cloud Online Meetups
There are three upcoming Cloud Online Meetups you may be interested in:
* April 24: High Availability and Scalability in the Cloud w/ ActiveState and Piston Cloud. (9am PST)
* May 7: How StackStorm builds and Operates StackStorm Software Itself (9am PST)
* May 14: Microservices 101 w/ ActiveState (9am PST)
New Post has been published on SDNCentral by Craig Matsumoto http://nfv.io/1mxogra
New Post on http://www.sdncentral.com/news/stackstorm-takes-modernized-shot-devops/2014/05/
StackStorm Takes a Modernized Shot at DevOps
Data-center automation is a real market with real demand. Opalis, acquired by Microsoft, showed us that. Now Opalis’ chief architect and Nexenta’s former CEO are back to update the vision for automating Puppet and Chef configurations.
