Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

General Plan #2

Closed
23 of 24 tasks
arm4b opened this issue Aug 11, 2015 · 2 comments
Closed
23 of 24 tasks

General Plan #2

arm4b opened this issue Aug 11, 2015 · 2 comments

Comments

@arm4b
Copy link
Member

arm4b commented Aug 11, 2015

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 Publish on Ansible galaxy #12
    • Polish, Refactor, Follow best practices
    • Distribution
    • Ansible Galaxy Docs, Examples
  • More distros to support (currently Ubuntu is supported only)
@arm4b arm4b mentioned this issue Aug 11, 2015
12 tasks
@arm4b arm4b modified the milestone: v0.2.0 Aug 19, 2015
@arm4b arm4b changed the title General enhancements General Plan Aug 19, 2015
@cognifloyd
Copy link
Member

This has "Use external/3rd party Ansible Galaxy roles for PostgreSQL/Mongo/RabbitMQ" checked, but those changes have been removed.

@arm4b
Copy link
Member Author

arm4b commented Aug 3, 2017

@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.

@arm4b arm4b closed this as completed Jul 28, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants