October Pack Updates

November 1, 2017
by Lindsay Hill

More packs, more updates, more goodness. Here’s October’s roundup of new & changed packs. Zabbix, Keycloak, Foreman, Solarwinds and more. Plus a couple of proposals for pack changes to Kubernetes and AWS, and a warning about upcoming Python action changes.

New Packs!

  • Napalm Logs: You’ve probably already heard of the Napalm network automation project – this is a sister project that aims to normalise network device syslog messages. This sensor lets you turn those logs into ST2 triggers.

  • Keycloak: Actions for working with Keycloak, an Open Source Identity and Access Management system.

  • Zabbix: You have always been able to submit webhooks from Zabbix to ST2. But now we have an integration pack, and a well-documented story on how to raise triggers in ST2 when things happen in Zabbix.

Noteworthy Updates

Here’s a few of the more interesting pack changes in October:

  • Solarwinds Orion: Added multiple new actions for querying agent information, deleting nodes, and allow setting nodes to be unmanaged for a specific time in future.

  • Foreman: Actions are now auto-generated from the Foreman API. Be warned: This is a breaking change. Read the README. We think the change is worth it.

  • Rabbitmq Fixed a long-standing bug where the sensor always returned the last queue name. This was a bit annoying if you were trying to monitor multiple queues.

RFC #1: AWS Pack Changes

We have been having discussions about the future of the AWS Pack. One approach is to have a separate pack per AWS service. Andy Moore has generated a whole bunch of example PRs to show what this looks like. Got some feedback on this approach? Please weigh in.

RFC #2: Kubernetes Pack

The Kubernetes API can change between versions. AndyMoore proposes that we align our pack versions with the Kubernetes version. So if you are running Kubernetes v1.4, you would install the v1.4 version of the ST2 pack with st2 pack install kubernetes=1.4. This seems sensible to me. Agree? Disagree? Let us know via that GitHub issue.

Technical Note: Changed Action Import Path

If you are writing Python actions, pay attention to this change. We have changed the Action import path. Previously most Python actions would have this line:

from st2actions.runners.pythonrunner import Action

This should now be:

from st2common.runners.base_action import Action

Right now both styles will work, but we will remove the older option in StackStorm 2.7. We are in the process of updating all packs on the Exchange.

Want to add your own pack?

No problem – just submit a PR against exchange-incubator. We’ll help you through the rest. It’s pretty easy, and we promise not to bite.