Ansible-st2-secure FORK

This fork is focused on providing security out-of-the-box for StackStorm. Original README follows. Note that the original stackstorm role is include via git submodule, so make sure to use one of these:

WARNING: This branch is a development branch for the security features of ansible-st2. Whenever upstream StackStorm/ansible-st2 is ready to accept PRs, various files will be copied from this branch. Force pushing is valid during development to re-trigger Travis or to rebase/consolidate commits into a more logical timeline.

git clone --recurse-submodules https://github.com/theatro/ansible-st2-secure.git

or

git clone https://github.com/theatro/ansible-st2-secure.git
cd ansible-st2-secure
git submodule init
git submodule update

Ansible-st2

Ansible playbooks to deploy StackStorm.

StackStorm is event-driven automation platform written in Python. With over 50+ integrations like GitHub, Docker, Nagios, NewRelic, AWS, Ansible it allows you to wire together your existing infrastructure into complex Workflows with auto-remediation and many more. Aka IFTTT orchestration for Ops.

Supported platforms

• Ubuntu Trusty (14.04)
• Ubuntu Xenial (16.04)
• RHEL6 / CentOS6
• RHEL7 / CentOS7

If you're using the provided Vagrantfile, note that it uses Xenial by default.

Requirements

At least 2GB of memory and 3.5GB of disk space is required, since StackStorm is shipped with RabbitMQ, PostgreSQL, Mongo, nginx and OpenStack Mistral.

Installation

# stackstorm
ansible-playbook stackstorm.yml

Variables

Below is the list of variables you can redefine in your playbook to customize st2 deployment:

Examples

Install latest stable StackStorm with all its components on local machine:

ansible-playbook stackstorm.yml -i 'localhost,' --connection=local

Note that keeping latest version is useful to update StackStorm by re-running playbook, since it will reinstall st2 if there is new version available. This is default behavior. If you don't want updates - consider pinning version-revision numbers.

Install specific numeric version of st2 with pinned revision number as well:

ansible-playbook stackstorm.yml --extra-vars='st2_version=2.2.0 st2_revision=8'

Installing behind a proxy.

If you are installing from behind a proxy, you can use environment variables http_proxy, https_proxy, and no_proxy in the playbook. For the st2smoketests, you will need to disable proxy for localhost.

  environment:
    http_proxy: http://proxy.example.net:3128
    https_proxy: http://proxy.example.net:3128
    no_proxy: 127.0.0.1,localhost

Developing

There are a few requirements when developing on ansible-st2.

These are the platforms we must support (must pass end-to-end testing):

• Xenial
• Trusty
• CentOS6
• CentOS7
• RHEL6 (via AWS)
• RHEL7 (via AWS)

Must also support Ansible Idempotence (Eg. Ansible-playbook re-run should end with the following results: changed=0.*failed=0)

For development purposes there is Vagrantfile available. The following command will setup ubuntu16 box (ubuntu/xenial64) by default:

vagrant up

Other distros:

vagrant up ubuntu14
vagrant up centos6
vagrant up centos7

Other Installers

You might be interested in other methods to deploy StackStorm engine:

• Configuration Management

  • Chef Cookbook
  • Puppet Module

• Manual Instructions

  • Ubuntu 14.04/16.04
  • RHEL7/CentOS7
  • RHEL6/CentOS6

Help

If you're in stuck, our community always ready to help, feel free to:

• Ask questions in our public Slack channel
• Report bug, provide feature request or just give us a ✮ star

Your contribution is more than welcome!