You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
@cognifloyd Updated, thanks.
In fact, we used some external galaxy roles before. That was a long time ago when we supported just Trusty in ansible-st2.
With all the 4(6) distros we have now: Trusty, Xenial, CentOS/RHEL 6, CentOS/RHEL 7 in our roles it doesn't make sense anymore to use external galaxy roles, since it's hard to find the role that will work for all the distros in the way we want.
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
memory
(disk
space for Mongo?)13.5.99
version is available)stable
,unstable
support (besides of numeric0.12.1
version)st2_
prefix (best practice for Ansible Galaxy)N
action-runnersUse external/3rd party Ansible Galaxy roles for PostgreSQL/Mongo/RabbitMQstackstorm.stackstorm
https://galaxy.ansible.com/StackStorm/stackstorm/st2
,st2mistral
,st2web
,st2chatops
independent roles (v1.0
??)The text was updated successfully, but these errors were encountered: