Large Instances Meeting Notes 2024-10-29

On the call today: Representatives from eduNEXT and OpenCraft.

Updates

eduNEXT:

@Jhony Avella We’re working on a few PRs:

  1. One for bumping the versions of the various sub-charts that are used in Harmony. We’ve been testing some of the version bumps on our clusters, but some haven’t been tested yet.
    chore(bump): upgrade helm chart global dependencies by Ian2012 · Pull Request #86 · openedx/openedx-k8s-harmony

  2. Integration testing - to validate the major components are working as expected.
    https://github.com/openedx/openedx-k8s-harmony/pull/80

  3. PR from Henry to add example of deploying to Amazon / EKS .
    https://github.com/openedx/openedx-k8s-harmony/pull/87

Also, we need to start planning to update Harmony to support the new Sumac release. @Jhony Avella will create an issue for that.

Also, we started migrating our clusters to the latest Kubernetes release (1.31). We’ll report back if we encounter any issues.

@Cristhian Garcia Mentioned the work eduNEXT has been doing on optimizing celery - chore: add gevent as bundle dependency by Ian2012 · Pull Request #35591 · openedx/edx-platform , feat: add a filter to define celery workers command by Ian2012 · Pull Request #1134 · overhangio/tutor .

@Felipe Montoya mentioned that eduNEXT hasn’t had any support in getting a scheduler like celery beat included in the core platform. Using scheduled Kubernetes Tasks is a workaround for now, but not as useful because a lot of code written for edx-platform like scheduled email sending etc, depends on celery beat.

[Discussion about the need for more flexible celery configuration for large instances, and tutor’s current lack of support.]

OpenCraft:

@Gábor Boros Not a lot of updates to share this week. Would like to push forward the discussion around Terraform scripts for setting up a cluster. [Discussion around that, seems like support for moving ahead. @Gábor Boros will compare the PR with eduNEXT’s AWS terraform to OpenCraft’s terraform and see what there is in common.]

Meeting logistics

@Felipe Montoya will follow up on moving the recurring call to Hangouts like all the other working groups are doing.