TSC Meeting (14 May 2024)

[winem]

May 2024 @StackStorm/tsc 1 hour meeting:

• Tuesday, 14 May 2024, 9:30 AM US Pacific / 6:30 PM EU CEST
• See StackStorm TSC Meetings #33 for the schedule and how to join
• TLDR; Jitsi link: https://meet.jit.si/StackStormTSC

Attendees

Present

• Jacob Floyd cognifloyd
• Marcel Weinberg winem
• Eugen armab
• Dan Porter
• Scott jk464

Absent

• Amanda McGuinness amanda11
• Carlos nzlosh
• Mark Mercado mamercad

Meeting Agenda

Progress status

• StackStorm v3.9.0 https://github.com/orgs/StackStorm/projects/31
• Support for Python3.10 [WIP] Interoperability updates for py3.8, py3.9 and py3.10 st2#6157
• Support for MongoDB 5, 6, 7
• Eventlet Retirement Eventlet retirement st2#6128
• StackStorm Exchange - Pack compatibility with Python3.9/3.10/3.11
• Pants
• stackstorm.com revamp StackStorm.com: Jamstack Revamp to Increase Visibility, Vitality & Engagement #132
• CI/CD on AWS - st2 upgrade and Ubuntu upgrade required -> could come with cost savings

[winem]

Meeting Minutes

StackStorm 3.9.0

@cognifloyd aligned the requirements of all components so that there is just the absolute minimum of dependencies. He also cherry-picked a lot of the changes @nzlosh did in StackStorm/st2#6157

Support for Python 3.10

The branch used in StackStorm/st2#6157 diverged from main and has a lot of conflicts. @cognifloyd will try to sort them out one by one.

Support for MongoDB 5, 6 & 7

With the latest changes and all the work @cognifloyd put into the alignment of the st2 modules dependencies, the mongodb client libraries are the only ones that are still pinned to specific versions due to version constraints depending on the MongoDB servers version.
@winem will have a look at StackStorm/st2#6079 and see if any help is needed.

Eventlet retirement

There is an ongoing discussion in StackStorm/st2#6128
It looks like we tend to migrate to asyncio. This topic is not directly related for 3.9 and driven by eventlet being retired - not by any dependencies to the new st2 or Python releases. So we'll focus on the topics for 3.9 for now and this topic will probably picked up once st2 3.9 is out.

The eventlet maintainers are discussing and potentially working on solutions to make the migration to asyncio as smooth as possible. We will monitor the status of their efforts on that topic as this will probably save us a lot of work and effort.

StackStorm Exchange - Pack compatibility with Python 3.9/3.10/3.11

Dan Porter is about to complete the work on the GitHub actions. Once the test runners are up and running we want to reflect the status of the tests on the exchange so that the Python versions the pack is compatible to can be seen on the first sight.

We already know that the pagerduty pack has issues with 3.11

The test framework based on the GitHub actions will cover Python versions 3.8 and above. 3.6 is not going to be supported.

Pants

Tremendous work is already done (big shout-out and thanks to @cognifloyd) and it's still ongoing. The next step is to get the tests running with pytest. The currently working nose tests will be the baseline for the tests & test coverage we want to achieve with pytest.

CI/CD on AWS - st2 and OS upgrade required

Beside the fact that both the st2 version as well as the operating systems version is outdated this is one of the last remaining items to be done on our cost reduction efforts: https://github.com/orgs/StackStorm/projects/27

The infrastructure for the E2E tests consist of one EC2 instance running all the time (hosting the st2-cicd infrastructure) and additional instances being started during the tests. It's one instance per operating system version.

@winem will create an issue to discuss the opportunities we have. Ideas that came up during the TSC meeting:

• Can't we use GitHub Actions and work with the AWS API if needed (i.e. to spin up instances)
• Do we still want to execute the E2E-tests? These are a "relict" from the time there was an Enterprise version of StackStorm

stackstorm-k8s

There is no owner yet but @cognifloyd is probably the one who knows the code best.

Scott and Marcel offered there help regarding helm charts while Scott already provided a lot of code and improvements to the project.

Probably one of the biggest issues we have here is the one with containers running as non-root. This breaks the st2 utilities and probably can't be fixed in the k8s project alone. It may require further adaptions in the actual st2 codebase.

Final words

A very good point was mentioned during the discussion on the stackstorm-k8s topic: Let us all take care of people who contribute to the project. Make our appreciation visible and don't hesitate to promote contributors. This also helps to be build a stable community.