StackStorm Integration with Device42
Device42 Integration with StackStorm
StackStorm is a powerful if-this-then-that type tool that helps you automate your workflows and changes to your infrastructure based on predefined “trigger” criteria taking place anywhere across your environment. Device42 is an ideal companion for this type of tool because you need a single source of truth to correctly and reliably orchestrate these automated workflows.
Push, Pull, And Trigger
Push data to Device42, Pull data from or kick off a job with Webhooks.
Stackstorm allows you to both utilize the always up-to-date information in your Device42 CMDB instance as both a source of data and at the same time, a source of triggers to drive automation via Device42’s powerful webhook functionality.
Webhooks allow you to easily kick off jobs across your organization in response to any change in Device42 that creates an audit log entry. That can be anything from one or more device, network, software, or application additions, changes, or deletions. With Stackstorm + Device42, orchestrating complex automation has never been simpler.
Next Level “If-This-Then-That”
Turn nightmare scenarios into a good night’s sleep.
Imagine a network switch fails at 3AM. The stuff of nightmares… Or so it once was. With Device42 & Stackstorm, you could immediately reroute traffic in response to an event occurring on a device, such as the absence of expected service.
Taking it a step further, you can awake to an automatically created trouble ticket in your ITSM system that records work to be done, or if an escalation chain is configured, a certain set of events can trigger a page or text message to support staff.
The possibilities at hand when Device42’s Webhooks are utilized with StackStorm Actions are only limited by your imagination, making any automation task from routine to Goldberg-like more easily realizable.
Custom Actions Against Any Number of Devices
Find your exact targets with any combination of CI attributes.
Need a list of all devices running the FreeBSD operating system? Powerful filters featuring everything from a room name, room_id, service levels, device tags, device types (physical, virtual, blade, etc), and more are available out of the box.
This makes it simple to automatically deploy updates to all servers running Windows Server 2012 or to push a new software package to hundreds or thousands of servers running CentOS.
With optional filter parameters, filtering for specific devices is a breeze. If you tag devices according to function, getting a list of all ‘web’ servers and pushing out a new configuration file is as simple as querying for ‘web’.
Automatically Assign and Reserve the Next IP
Get the IP and Mark it as used – Automatically.
With the device42.suggest_next_ip call, a subnet can be specified by name, VLAN, by the actual subnet in slash notation (192.168.1.0/24). Do you use VRF Groups? No problem – Request by vrf_group or vrf_group_id.
In addition, if this isn’t a test run, pass the reserved_ip=yes flag, and the IP suggestion becomes a reservation.