Skip to content
Go to file

Latest commit


Failed to load latest commit information.
Latest commit message
Commit time

Ansible & ChatOps with Slack, Hubot and StackStorm - Vagrant demo

Part of tutorial: Ansible and ChatOps. Get started 🚀


This is quick demonstration of the StackStorm event-driven automation platform running with Ansible configuration management tool and Hubot ChatOps engine. The objective is to operate servers with Ansible directly from Slack chat.

Ansible and ChatOps with Slack and Hubot

It will get you up and running with chatops control VM with all St2 components prepared as well as Ansible and Hubot configured. Additionally, it installs 2 Ubuntu VMs: web server with nginx and db server with mysql.

As a result you should get 100% ready environment allowing you to execute Ansible ad-hoc commands and run Ansible playbooks against VMs directly from your Slack chat. In this showcase we already crafted some simple, but useful real world ChatOps commands.

Getting started

1. Prepare Slack

  • Create account if you don't have it yet.
  • Navigate Configure Integrations -> Filter -> Hubot and generate Slack & Hubot API Token.

2. Vagrant up

Edit Vagrantfile and add the just generated API token under HUBOT_SLACK_TOKEN constant, or just export it:

export HUBOT_SLACK_TOKEN=xoxb-1234-5678-91011-00e4dd

To provision the environment run:

vagrant up

Installation takes some time (st2 engine comes with Python, RabbitMQ, PostgreSQL, MongoDB, OpenStack Mistral).

3. Try ChatOps

You should see your bot online in Slack and now you're ready to type some chat commands. Don't forget to invite your bot into the Slack channel: /invite @stanley. Your first ChatOps command is:


Ansible ChatOps with StackStorm, Hubot and Slack. List of ChatOps commands Full list of available commands from st2_chatops_aliases pack:

Additionally check the results of performed commands in StackStorm control panel:
https://www.chatops/ username: demo password: demo

4. Don't stop!

Try it, explore the internals. For configuration see:, which are usual Vagrant shell provisioner scripts. Integrate your custom workflows and deployment mechanisms, you'll see how your work becomes more efficient during time.

Feel the power of control center and may the force will be with you!

Need Help? Want to talk?

Join our community Slack IRC

We're always ready to help, feel free to:

  • Ask questions on our public Slack or IRC
  • Report bug, provide feature request or just give us a ✮ star at GitHub st2
  • Tell us how you use st2, share your StackStorm story. We love stories!
You can’t perform that action at this time.