Large Instances Meeting Notes 2024-11-12

On the call today: Representatives from eduNEXT and OpenCraft.

Updates

eduNEXT:

@Moisés González : We have been focused on upgrading to Kubernetes 1.31 and testing our tools for the Sumac release, which has changes like the new forum and using Meilisearch by default.

@Felipe Montoya Asked about whether or not the new forum will be default in Sumac. Apparently the PR has not yet merged to master. A big concern is the upgrade path and the migration of data from MongoDB into MySQL (which is encouraged but not required as the new forum can use either MongoDB or MySQL).

eduNEXT is interested in helping to test the forum v2 and the upgrade pathway.

@Jhony Avella Is the new forum v2 using Meilisearch or Elasticsearch? A: seems both

@Felipe Montoya Mentions that based on recent project requirements, he has put forward Lightweight catalog implementation via extensions and is looking for feedback. Hoping to build something that works for these two projects and the broader community, and may be able to build it before the end of the year. Hoping to collaborate with anyone who is interested, though due to deadlines, will need to build something like this either way.

@Jhony Avella We merged the PR to update the Helm chart dependencies, though a couple like OpenFAAS and Velero still need to be updated. Also renovate opened quite a few version update PRs. Open Question: Is it possible to change renovate to open a single PR with all the version bumps?

Question: What is our policy on merging these PRs? @Jhony Avella suggests we need to get the integration tests in place first.

OpenCraft:

@Gábor Boros has been working on porting the Terraform scripts that we have into Harmony. Also, approved the version bump PRs. Will be opening a PR soon to bump OpenFAAS and Velero.

Discussion around Sumac requirements and how to run Meilisearch for large instances. Should there be one Meilisearch instance per index, per Open edX instance, or per Harmony cluster?

Discussion

@Braden MacDonald Brought up the Sumac release and testing process, asking if there’s a way to get more developers involved in fixing bugs. @Felipe Montoya mentioned that eduNEXT is re-organizing some internal teams but soon one of them will be heavily involved in the testing and bugfixing process.

eduNEXT mention they’re using an annual upgrade strategy, where most customers will be on Redwood, skip Sumac, and then upgrade to Teak next year. But eduNEXT will still be participating in the Sumac bug testing process.

 

 

Meeting Artifacts

recording:https://drive.google.com/file/d/1WcdTu_lg-tLyQPmhWPdifRe3l33u8pfV/view
transcript: https://docs.google.com/document/d/1ABhgFEIca_BSHhyq6DHgpIudUxzqx_iFsk0s-GjPANE/edit?tab=t.0
chat: https://drive.google.com/file/d/1EF6tiK9SM3v4Y5po9nu2aphm8TZRfMg2/view