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

TSC Meeting (03 May 2022): self-check in GH Actions, AWS cost reduction follow-up, v3.7.0 release #100

Closed
3 of 7 tasks
winem opened this issue Apr 27, 2022 · 2 comments
Closed
3 of 7 tasks
Assignees
Labels
TSC:meeting StackStorm Technical Steering Committee Meetings related topics

Comments

@winem
Copy link

winem commented Apr 27, 2022

May 2022 @StackStorm/tsc 1 hour planned meeting: Tuesday, 03 May 2022, 09:30 AM US Pacific.

See #33 for more info on how to join.
(TLDR; Zoom link: https://us02web.zoom.us/j/81082101702?pwd=N1V4TWdYRVQ4SXBsaFh1TFYvVDA0UT09)

Meeting host: @winem

Meeting Agenda

StackStorm AWS cost-reduction project ~(5min)

Migrating AWS parent org to Encore ~(10m)

Drop Python 3.6 / OS support matrix ~(10m)

  • Python 3.8 is not available in CentOS 7 without building/distributing our own.
  • Is there a way to divorce our requirements from OS platforms and focus more on supporting various python versions? (3.9, 3.10)

StackStorm v3.7.0 release preparation ~(5min)

TSC Meeting host rotation ~(5min)

ST2 Security/Maintenance Project ~(10min)

@arm4b arm4b added the TSC:meeting StackStorm Technical Steering Committee Meetings related topics label Apr 28, 2022
@winem
Copy link
Author

winem commented May 2, 2022

Following topics were moved to the next TSC meeting in June:

Demo: migration to Scalyr monitoring for internal st2cicd infra by @Kami ~(10min)

Run st2-self-check in GH Actions ~(5min)

  • current state of the PR CI should run st2-self-check for every PR st2#5496
  • how to handle tests with HTTP actions - the only ones that still fail
  • agree on the MVP to start with the self-check in GH Actions (older Python versions seem to be a problem, I'll provide details during the meeting)

@winem
Copy link
Author

winem commented May 5, 2022

Meeting notes:

Attendees:
@armab @amanda11 @cognifloyd @rush-skills @winem @nzlosh

Migrating AWS parent org to Encore ~(10m)

  • We'll coordinate this async to the TSC meetings
    • The credit card on the root account needs to be changed before the account will be transfered to Encore
  • Given that the AWS credits expire in a few months it was discussed whether AWS is the right cloud provider for us
    • there are multiple maintainers with AWS knowledge, so there is no risk due to a lack of knowledge
    • other cloud providers like GCP and Azure were briefly evaluated in the past and we'll probably have similar challenges regarding the OSS credits

Drop Python 3.6 / OS support matrix ~(10m)

  • CentOS 7 will be EOL June 2024; Py3.8 will not be available on CentOS7
  • The participants agreed that we do not want to provide any kind of home grown Python-environment or solution to run a higher Python version on CentOS7
  • It was also discussed to provide st2 just as Docker containers and have that as the only supported installation method
    • Pros:
      • This would save us some of the bundling, packaging and distribution pain
    • Cons:
      • This will break installations for deployments out there (i.e., bare metal deployments)
      • Such a change can only be done with a major version change and will not be possible in the short term
  • conda as alternative to pip which also manages the Python environment was also discussed to distribute the st2 Python packages, but we want to avoid that
  • The high number of Python version we may have to support in the future raised some concerns:
    • Python3.6 would be required for CentOS7 support
    • Python3.7 would allow us to support Ubuntu 18.04
    • Python3.8 would at least be required for Ubuntu 20 and CentOS8
    • Python3.9 would be needed to support Debian 11
    • Python3.10 would be needed to run st2 on Ubuntu 22

Draft for the next TSC meeting agenda:

StackStorm AWS cost-reduction project ~(5min)

Demo: migration to Scalyr monitoring for internal st2cicd infra by @Kami ~(10min)

Run st2-self-check in GH Actions ~(5min)

  • current state of the PR CI should run st2-self-check for every PR st2#5496
  • how to handle tests with HTTP actions - the only ones that still fail
  • agree on the MVP to start with the self-check in GH Actions (older Python versions seem to be a problem, I'll provide details during the meeting)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
TSC:meeting StackStorm Technical Steering Committee Meetings related topics
Projects
None yet
Development

No branches or pull requests

3 participants