stackstorm / ansible-st2 Goto Github PK

Use external 3rd party Ansible Galaxy role for Mongo.
Mark it as dependency for st2 role.

According to https://docs.stackstorm.com/install/upgrades.html

Mistral DB upgrading may be required after every st2mistral package update:

# Stop related services
service mistral-api stop
service mistral stop

# Upgrade database
/opt/stackstorm/mistral/bin/mistral-db-manage --config-file /etc/mistral/mistral.conf upgrade head
/opt/stackstorm/mistral/bin/mistral-db-manage --config-file /etc/mistral/mistral.conf populate

# Restart related services
service mistral start
service mistral-api start

TODO

• Implement migration logic in st2mistral role
• Verify if service start/stop is a required step

• Put together all changes that were done as part of v0.6.0 release
• Document in Release CHANGELOG
• Release v0.6.0

We started adding EL support in #65 and #65 as part of #5.
Working without CI is bad for quality, testing and reviewing.

There is a need to add CentOS6 integration Testing in Travis as we already do for Ubuntu Trusty and Ubuntu Xenial. The framework is already setup.

It's possible to make CentOS6 build non-voting to skip the failure for entire build (see travis.yml example for st2 repo) until we re-write all roles to support new platforms.

See:

• https://travis-ci.org/StackStorm/ansible-st2
• https://github.com/StackStorm/ansible-st2/blob/master/.travis.yml
• https://github.com/StackStorm/ansible-st2/blob/master/.kitchen.yml

cc @humblearner

In testing EL7, I encountered this issue when running the Ansible playbook:

TASK [mongodb : yum | Install mongodb dependencies] ****************************
failed: [10.0.0.96] (item=[u'python-urllib3', u'pyOpenSSL', u'python-pyasn1', u'python-ndg_httpsclient']) => {"failed": true, "item": ["python-urllib3", "pyOpenSSL", "python-pyasn1", "python-ndg_httpsclient"], "msg": "Failure talking to yum: failure: repodata/repomd.xml from stackstorm: [Errno 256] No more mirrors to try.\nhttps://packagecloud.io/StackStorm/stable/el/7Server/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 404 - Not Found"}
	to retry, use: --limit @/Users/oswaltm/Code/ansible-st2/stackstorm.retry

This is because the $releasever variable in the yum configuration evaluates to 7Server when on EL7 (whereas it equals simply 7 on CentOS7).

[ec2-user@ip-10-0-0-96 ~]$ cat /etc/yum.repos.d/st2.repo
[stackstorm]
baseurl = https://packagecloud.io/StackStorm/stable/el/$releasever/$basearch
name = Stackstorm Repo
[ec2-user@ip-10-0-0-96 ~]$ python -c 'import yum, pprint; yb = yum.YumBase(); pprint.pprint(yb.conf.yumvar, width=1)'
(...truncated...)
{'arch': 'ia32e',
 'basearch': 'x86_64',
 'releasever': '7Server',
 'uuid': '8b7c566e-243b-4985-a077-8e6dbeed7e16'}

This is expected behavior.

The question is, how should this get answered? Should we deal with this on the Ansible side, rewriting this config to include the actual hard-coded version like 7, instead of 7Server, or should we make a change on the packagecloud side that includes the expected path?

External dependency ANXS.postgresql doesn't support EL platform family.
We need to write custom role to install PostgreSQL for Mistral.

• Tag all tasks in role
• Meta
• Get best practices from ANXS.postgresql code
• Ensure service is listening on 127.0.0.1 by default (configurable), see: #75
• EL support
  • CentOS6
  • RHEL6
  • CentOS7
  • RHEL7
• Idempotence check
• Update README

cc @humblearner based on your feedback

Similar to Pack Install #74 we'll need an abstraction for st2 key/value store.

For example define a list of K/V pairs in yaml which will be added in st2 datastore during Ansible provisioning.

See: https://docs.stackstorm.com/datastore.html

At a low level it could be implemented via Ansible plugins/modules (lookup/set):

• https://www.ansible.com/blog/how-to-extend-ansible-through-plugins
• http://docs.ansible.com/ansible/playbooks_lookups.html

Existing MySQL role fails on some Ubuntu installations.

       TASK: [mysql | Change MySQL password] ***************************************** 
       <localhost> REMOTE_MODULE mysql_user login_password=VALUE_HIDDEN name=root password=VALUE_HIDDEN login_user=root
       <localhost> EXEC ['/bin/sh', '-c', 'mkdir -p $HOME/.ansible/tmp/ansible-tmp-1440013362.89-221545053412569 && echo $HOME/.ansible/tmp/ansible-tmp-1440013362.89-221545053412569']
       <localhost> PUT /tmp/tmp4WsWvG TO /home/kitchen/.ansible/tmp/ansible-tmp-1440013362.89-221545053412569/mysql_user
       <localhost> EXEC ['/bin/sh', '-c', u'LANG=en_US.UTF-8 LC_CTYPE=en_US.UTF-8 /usr/bin/python /home/kitchen/.ansible/tmp/ansible-tmp-1440013362.89-221545053412569/mysql_user; rm -rf /home/kitchen/.ansible/tmp/ansible-tmp-1440013362.89-221545053412569/ >/dev/null 2>&1']
       failed: [localhost] => {"failed": true}
       msg: unable to connect to database, check login_user and login_password are correct or ~/.my.cnf has the credentials

       FATAL: all hosts have already failed -- aborting


       localhost                  : ok=11   changed=9    unreachable=0    failed=1  

Most probably using 3rd party Ansible Galaxy role for MySQL #8 will fix it.

As reported in: StackStorm/st2contrib#421

Ansible-lint (#52) works well.

In addition to existing ansible-lint rules there is another repo with set of pretty good checks, see:
https://github.com/tsukinowasha/ansible-lint-rules

Add them to existing checks.

Good "sign of quality" objective is to publish StackStorm roles on Ansible galaxy to get some more attention from the community.
At that point it should be tested/stable enough.

• Register Ansible Galaxy account
• Polish, Refactor, Follow best practices
• Integration Tests #15
• Ansible Galaxy Docs, Examples
• Decide: ship it as stackstorm.st2 role or st2, st2web, st2mistral, st2chatops roles
• Use Ansible Galaxy 3rd-party dependencies for postgresql, rabbitmq, mongo (We use our own roles now, but should leave an option for users to choose alternate external roles)

Adjust st2web role to allow optionally specifying custom cert, instead of generating self-signed one every time.

Add tasks to install StackStorm WebUI.

Options:

• st2_deploy.sh approach. Install by default, but add variable to opt-out: st2_install_webui.
• Use st2-puppet approach. Install webui in any case without option to opt-out.

Resources:

• https://github.com/StackStorm/puppet-st2/blob/master/manifests/profile/web.pp
• https://github.com/StackStorm/st2/blob/dffb8c5a2ad5180be9aece1c9d6954ea63c3ebea/tools/st2_deploy.sh#L605

TravisCI is red for forked PRs, starting from st2chatops and bwc role implementations.

This is caused by private env variables defined in our Travis settings: HUBOT_SLACK_TOKEN and BWC_LICENSE which are not available to forked builds.

https://docs.travis-ci.com/user/environment-variables/#Defining-Variables-in-Repository-Settings

Similarly, we do not provide these values to untrusted builds, triggered by pull requests from another repository.

Find the way how to proceed this the right way in future, - because we can't turn down CI for contribution PRs.

Draft a StackStorm blog for ansible-st2 v0.7.0 release, highlight breaking changes, new features with usage examples and new roles like @lakshmi-kannan's bwc and @humblearner's st2chatops.

Currently only ubuntu 14/16 installation story is covered as minimum viable example for contributions.

Add support for the following flavors (we build packages for each):

• Ubuntu Trusty
• Ubuntu Xenial
• RHEL/CentOS 7
• RHEL/CentOS 6
• Debian Wheezy
• Debian Jessie

We should add provision logic and integration tests for some of these platform, starting from ubuntu 14.

See notes #15 how we going to test them (Docker + Serverspec way as we do in st2-packages).

Add option to install additional StackStorm packs within Ansible installer.

Good feature, as seen at puppet-st2. Low priority, after v0.3.0.

The "Lookup literal version" task is failing silently with "sort: unrecognized option `--version-sort'"
Leaving _st2_version set to "" and breaking following tasks

https://github.com/willthames/ansible-lint

ansible-lint checks playbooks for practices and behaviour that could potentially be improved

From the:

• StackStorm/st2-packages#405
• StackStorm/st2docs#363

At the moment we don't even configure any username/passwords for external services like Mongo, RabbitMQ with st2 Ansible installation. Additionally, we're not sure whether those services are listening on 127.0.0.1 or are open to public net.

All of that needs better control and improvement.

• Ensure we can configure host for dependent services
• Services should run on 127.0.0.1 (PostgreSQL, Mongo, RabbitMQ) by default
• Configure/Set username/password for PostgreSQL, Mongo, RabbitMQ
• If not explicitly set, passwords for PostgreSQL, Mongo, RabbitMQ should be generated randomly and placed in st2.conf

This happens on EL6 (reproducible in CentOS6 Vagrant).
st2api, st2stream, st2auth got duplicated:

$ sudo st2ctl status
##### st2 components status #####
st2actionrunner PID: 699
st2actionrunner PID: 720
st2actionrunner PID: 740
st2actionrunner PID: 763
st2actionrunner PID: 789
st2actionrunner PID: 814
st2actionrunner PID: 841
st2actionrunner PID: 868
st2actionrunner PID: 896
st2actionrunner PID: 936
st2api PID: 29766
st2api PID: 29778
st2stream PID: 1034
st2stream PID: 1057
st2auth PID: 1085
st2auth PID: 1096
st2garbagecollector PID: 1133
st2notifier PID: 1167
st2resultstracker PID: 1202
st2rulesengine PID: 1241
st2sensorcontainer PID: 1277
st2chatops is not running.
mistral-server is not running.
mistral-api is not running.

This is dangerous behavior what could cause future problems like race conditions and zombie services.

Probably requires debugging and fixing st2-packages init files for rpm, see:

• https://github.com/StackStorm/st2-packages/blob/master/packages/st2/rpm/st2api.init
• https://github.com/StackStorm/st2-packages/blob/master/packages/st2/rpm/st2auth.init
• https://github.com/StackStorm/st2-packages/blob/master/packages/st2/rpm/st2stream.init

• Tag all tasks in role
• Update meta file
• EL support
  • CentOS6
  • RHEL6
  • CentOS7
  • RHEL7
• Idempotence check
• New parameters to pass to st2web like hostname
  • Update README.md

When numeric st2_version is used, st2_revision is pinned to default val 1, which is not desired beavior.

Instead, when st2_revision is not set: is empty or latest, - let playbook install latest package revision number for respective version.

After an ansible install from https://docs.stackstorm.com/install/ansible.html on a fresh ubuntu 14.04 vm none of the st2 services were started. This is because /var/log/st2 was owned by root:root, and needed to be owned by stanley:stanley ({{ st2_system_user }}).

• Rename mistral to st2mistral
• Tag all tasks in role
• Update meta file
• EL support
  • CentOS6
  • RHEL6
  • CentOS7
  • RHEL7
• Idempotence check

Depends on PostgreSQL Role [EL] #76

We started adding EL support in #65 and #65 as part of #5.
Working without CI is bad for quality, testing and reviewing.

There is a need to add CentOS7 integration Testing in Travis as we already do for Ubuntu Trusty and Ubuntu Xenial. The framework is already setup.

It's possible to make CentOS7 build non-voting to skip the failure for entire build (see travis.yml example for st2 repo) until we re-write all roles to support new platforms.

See:

• https://travis-ci.org/StackStorm/ansible-st2
• https://github.com/StackStorm/ansible-st2/blob/master/.travis.yml
• https://github.com/StackStorm/ansible-st2/blob/master/.kitchen.yml

cc @Mierdin

Allow user to install and configure StackStorm when 3rd party services like Mongo, RabbitMQ, MySQL already existing or remote HA clusters.

Think how to make it better.
Should be more clear after solving related #8 #9 #10.

For simplicity reasons, at the moment we keep all the required roles (12) to install/configure StackStorm in one single repository ansible-st2, available under StackStorm.stackstorm Ansible Galaxy, see meta/main.yml workaround.

Alternative is to add more flexibility, distribute everything as different Ansible Galaxy roles (?)

Some arguments:

• StackStorm can be used in High Availability Deployment
• Could be installed/distributed across many hosts
• Can use external RabbitMQ, PostgreSQL, Mongo, ChatOps server
• Not all packages are needed for everyone

Disadvantages:

• Significant breaking change
• Increased complexity & support (we don't need that yet ?)
• Different repos, harder to maintain (?)
• Hard to test "all in one st2" because of components decoupling (CI, PRs)
• Less visibility (give me everything in one place) https://galaxy.ansible.com/StackStorm/stackstorm/

Second stackstorm.yml playbook re-run should end with the following: changed=0.*failed=0, meaning 0 resources changed.

Include Idempotence check in CI, see:
https://github.com/StackStorm/ansible-st2/blob/master/.kitchen.yml#L17-L18

Reported in Slack community by @withrocks

Include st2chatops package installation

Add new features/changed vars from the v0.7.0 in
https://github.com/StackStorm/st2docs/blob/master/docs/source/install/ansible.rst docs.

[DEPRECATION WARNING]: Instead of sudo/sudo_user, use become/become_user and make sure become_method is 'sudo' (default). This feature will be removed in a future release.

Deprecation warnings can be disabled by setting deprecation_warnings=False in ansible.cfg.

[DEPRECATION WARNING]: Using bare variables is deprecated. Update your playbooks so that the environment value uses the full variable syntax ('{{postgresql_env}}'). This feature
will be removed in a future release. Deprecation warnings can be disabled by setting deprecation_warnings=False in ansible.cfg.

we'll probably have to pin to a specific version of stackstorm, but the revision is less important for us.

It'd be good to be able to set st2_version=2.2.1 st2_revision=latest to pin at whatever the latest 2.2.1 release is without having to know the exact revisions that've been released in advance

Use external 3rd party Ansible Galaxy role for RabbitMQ (or create own).
Mark it as dependency for st2 role.

Since StackStorm v1.6 MongoDB 3.2 is the default version,
see: https://docs.stackstorm.com/install/deb.html#install-dependencies for installation instructions.

Reflect the change in st2 Configuration Management repos.

Implement a convenient ansible-friendly way (as Ansible module) to install st2 packs, as well as provide configurations/settings for them.

Decide:

• define config settings in yaml plays inline
• use /opt/stackstorm/configs/<pack>.yaml

https://docs.stackstorm.com/pack_configs.html

Alternative example from puppet-st2: https://github.com/stackstorm/puppet-st2#installing-and-configuring-packs

In short, it should work like similar pip or gem Ansible module, but for installing st2 packs.

Fix the builds (since: https://circleci.com/gh/StackStorm/ansible-st2/31), check what's new in recent Ansible 2.0 version which broke the build, verify/test entire playbook story, check the backward compatibility.

Before publishing on Ansible Galaxy, add some Integration/Smoke tests, increase infrastructure coverage.

Infrastructure Testing Frameworks

• Evaluate ServerSpec / InSpec - ruby-based. Famous, big community, nice looking and best in his class. But the team prefers Python (st2 main lang).
• Evaluate BATS - Bash Automated Testing System, which is a bit easier.
• Evaluate TestInfra - Python-based infra testing framework. Still pretty young, very small community. Intro.

Automation

• Molecule project - automation for testing Ansible roles
• TestKitchen - automation to spin up Vagrant or Docker or even AWS instance and test Ansible roles with Serverspec/BATS against just spinned up machines.

More info: http://stackoverflow.com/a/37006819/4533625
Continue work started in #7

Installation of staging-unstable breaks on Ubuntu with the following exception:

Exception: Versioning for this project requires either an sdist tarball, or access to an upstream git repository. Are you sure that git is installed?

Yes, git IS installed on the box.

After it happens, re-running the playbook skips the Register mistral actions step.

TASK [st2mistral : Register mistral actions] ***********************************
skipping: [st2]

Playbook:

---
- name: Install StackStorm
  hosts: st2
  strategy: debug
  vars:
    st2_pkg_repo: staging-unstable

  roles:
    - mongodb
    - rabbitmq
    - postgresql
    - st2repos
    - st2
    - st2mistral
    - nginx
    - st2web
    - st2smoketests

TASK [st2mistral : Register mistral actions] ***********************************
fatal: [st2]: FAILED! => {"changed": true, "cmd": "/opt/stackstorm/mistral/bin/mistral-db-manage --config-file /etc/mistral/mistral.conf populate && touch /etc/mistral/mistral-db-manage.populate.ansible.has.run", "delta": "0:00:02.174987", "end": "2017-01-28 00:50:31.550711", "failed": true, "rc": 1, "start": "2017-01-28 00:50:29.375724", "stderr": "Traceback (most recent call last):\n  File \"/opt/stackstorm/mistral/bin/mistral-db-manage\", line 11, in <module>\n    sys.exit(main())\n  File \"/opt/stackstorm/mistral/local/lib/python2.7/site-packages/mistral/db/sqlalchemy/migration/cli.py\", line 130, in main\n    CONF.command.func(config, CONF.command.name)\n  File \"/opt/stackstorm/mistral/local/lib/python2.7/site-packages/mistral/db/sqlalchemy/migration/cli.py\", line 71, in do_populate\n    action_manager.sync_db()\n  File \"/opt/stackstorm/mistral/local/lib/python2.7/site-packages/mistral/services/action_manager.py\", line 82, in sync_db\n    register_action_classes()\n  File \"/opt/stackstorm/mistral/local/lib/python2.7/site-packages/mistral/services/action_manager.py\", line 128, in register_action_classes\n    _register_dynamic_action_classes()\n  File \"/opt/stackstorm/mistral/local/lib/python2.7/site-packages/mistral/services/action_manager.py\", line 87, in _register_dynamic_action_classes\n    for generator in generator_factory.all_generators():\n  File \"/opt/stackstorm/mistral/local/lib/python2.7/site-packages/mistral/actions/generator_factory.py\", line 32, in all_generators\n    mod_action_cls = importutils.import_class(mod_cls_name)\n  File \"/opt/stackstorm/mistral/local/lib/python2.7/site-packages/oslo_utils/importutils.py\", line 30, in import_class\n    __import__(mod_str)\n  File \"/opt/stackstorm/mistral/local/lib/python2.7/site-packages/mistral/actions/openstack/actions.py\", line 37, in <module>\n    muranoclient = importutils.try_import('muranoclient.v1.client')\n  File \"/opt/stackstorm/mistral/local/lib/python2.7/site-packages/oslo_utils/importutils.py\", line 103, in try_import\n    return import_module(import_str)\n  File \"/opt/stackstorm/mistral/local/lib/python2.7/site-packages/oslo_utils/importutils.py\", line 73, in import_module\n    __import__(import_str)\n  File \"/opt/stackstorm/mistral/local/lib/python2.7/site-packages/muranoclient/v1/client.py\", line 17, in <module>\n    from muranoclient.v1 import artifact_packages\n  File \"/opt/stackstorm/mistral/local/lib/python2.7/site-packages/muranoclient/v1/artifact_packages.py\", line 22, in <module>\n    from muranoclient.common import utils\n  File \"/opt/stackstorm/mistral/local/lib/python2.7/site-packages/muranoclient/common/utils.py\", line 20, in <module>\n    from muranopkgcheck import manager as check_manager\n  File \"/opt/stackstorm/mistral/local/lib/python2.7/site-packages/muranopkgcheck/__init__.py\", line 19, in <module>\n    'muranopkgcheck').version_string()\n  File \"/opt/stackstorm/mistral/local/lib/python2.7/site-packages/pbr/version.py\", line 457, in version_string\n    return self.semantic_version().brief_string()\n  File \"/opt/stackstorm/mistral/local/lib/python2.7/site-packages/pbr/version.py\", line 452, in semantic_version\n    self._semantic = self._get_version_from_pkg_resources()\n  File \"/opt/stackstorm/mistral/local/lib/python2.7/site-packages/pbr/version.py\", line 439, in _get_version_from_pkg_resources\n    result_string = packaging.get_version(self.package)\n  File \"/opt/stackstorm/mistral/local/lib/python2.7/site-packages/pbr/packaging.py\", line 671, in get_version\n    raise Exception(\"Versioning for this project requires either an sdist\"\nException: Versioning for this project requires either an sdist tarball, or access to an upstream git repository. Are you sure that git is installed?", "stdout": "", "stdout_lines": [], "warnings": []}

Use external 3rd party Ansible Galaxy role to install PostgreSQL.
Mark it as dependency for st2 role.

Initial Minimum Viable implementation for installation of new packages was done in #42.

Real production use requires much more settings to configure.

• Ability to use unstable repo (?)
• Improve version/revision installation logic
• Ability to adjust st2.conf parameters #121
• nginx-related stuff (st2web)
  • Specify custom certificate #133
• MongoDB
  • Allow adjusting st2 config [database] group settings via Ansible variables #121
  • MongoDB role setting changes should inject into st2 config.
  • Add ability to use external MongoDB server. #17
• Much more to add [...]

Since we started adding support for more platforms as part of #5 in #65 and #66 We'll need a way to bootstrap Vagrant for:

• Ubuntu14
• Ubuntu16
• CentOS6
• CentOS7

Example syntax:

vagrant up ubuntu14
vagrant up ubuntu16
vagrant up centos6
vagrant up centos7

Implementation examples:

• 1. Via Vagrant multi-machine https://www.vagrantup.com/docs/multi-machine/
     https://github.com/StackStorm/showcase-ansible-chatops/blob/master/Vagrantfile#L8-L21
     and
     https://github.com/StackStorm/showcase-ansible-chatops/blob/master/Vagrantfile#L51
• 2. https://github.com/StackStorm/st2puppet/blob/production/Vagrantfile#L40-L45

cc @Mierdin and @humblearner

Follow st2 mistral changes:

• StackStorm/st2#1860
• StackStorm/puppet-st2#46

Generate passwords for root and mistral PostgreSQL users

For better maintainability add automated tests.

• Test-kitchen
• CircleCI
  • Configuration
  • Parallelism
  • Badge
• Test Playbook run
• Write first minimal Rspec tests as proof of work (add more test coverage much later)

Create a set of common rules, recommendations and conventions for development flow when contributing to ansible-st2.

This is a much-needed project for us. I want to build StackStorm in production environment with this.

The current tasks in the RabbitMQ role just only install package and start service.
But the RabbitMQ servers that I expect are set up a cluster configuration.

I want some tasks to set up cluster configuration in the RabbitMQ role.

Thank you.

Since we have own postgresql role, - let it handle DB creation for st2mistral.

Use native Ansible modules postgresql_user and postgresql_db instead of init_mistral_db SQL template file.

So after all postgresql + st2mistral usage should look as following:

- name: Install st2mistral on a single node
  hosts: all
  roles:
    - name: Install PostgreSQL and configure databases
      role: postgresql
      vars:
        postgresql_databases:
          - name: "{{ st2mistral_db }}"
        postgresql_users:
          - name: "{{ st2mistral_db_username }}"
            pass: "{{ st2mistral_db_password }}"
            encrypted: yes

    - name: Install and configure StackStorm Mistral
      role: st2mistral
      vars:
        st2mistral_database_connection: postgresql://{{ st2mistral_db_username }}:{{ st2mistral_db_password }}@localhost/{{ st2mistral_db }}

Use best practices from https://github.com/ANXS/postgresql

Additionally, this will allow us to manage multi-node deployments #17 better in future.

Ansible deployment repo definitely needs some polishing/testing/improvements for mass-use.

The big point is to polish & publish it on Ansible galaxy (public hub) to get some visibility in the community. Another good thing are real CI Integration tests, for better maintainability.

TODO:

Part 1

• Check for minimum requirements like memory (disk space for Mongo?)
• Version check before install (check if 13.5.99 version is available)
• stable, unstable support (besides of numeric 0.12.1 version)
• Vagrantfile
• Refactor all variables, add st2_ prefix (best practice for Ansible Galaxy)
• Upgrade to higher st2 version as well as downgrade should work
• Fix Upstart
• Upstart N action-runners
• Initial Docs

• Support New packages
• Add WebUI installation
• Use external/3rd party Ansible Galaxy roles for PostgreSQL/Mongo/RabbitMQ
• Tag all tasks, split into logical groups
• Idempotence (playbook re-run shouldn't change anything unless new st2 version is available)
• CI tests for better maintainability (Test-kitchen?, CircleCI?)
• Extend list of variables/options to configure
• Ability to configure with existing/remote installations of Mongo, RabbitMQ, PostgreSQL
• Publish on Ansible galaxy #12
  • Polish, Refactor, Follow best practices
  • Distribution
    • Ship it as single stackstorm.stackstorm https://galaxy.ansible.com/StackStorm/stackstorm/
    • Split into: st2, st2mistral, st2web, st2chatops independent roles (v1.0 ??)
  • Ansible Galaxy Docs, Examples
• More distros to support (currently Ubuntu is supported only)