Catalyst/Updates/2024-10-25
< Catalyst
Introduction
Project Catalyst is a team working on a kubernetes cluster as a service explicitly for CI and and exploratory testing. Our current effort is upgrading Patch Demo, to use kubernetes to provision and host wikis with custom extensions and skins. The Catalyst API wraps a small kubernetes cluster. A new instance of PatchDemo will consume this API. Our next effort will be to open the Catalyst API for more general workloads include wikis which rely on (micro)services.
Update
- Status: On Track
- Progress update on the hypothesis for the week
- we are likely to announce public beta next week, this will involve:
- publicising the availability of the Catalyst backend and encouraging people to use intial
- changing some copy on the patchdemo home page
- the "use catalyst" checkbox will remain unchecked by default as we collect feedback
- long tail of outstanding features for new wiki configuration has been completed and merged in
- streaming logs in patchdemo is at a state where we are comfortable enough to go to beta phab:T372900
- wikifunctions has been successfully deployed on catalyst phab:T374864
- this is the first step in onboarding Abstract Wikipedia onto catalyst
- we are likely to announce public beta next week, this will involve:
- Any new metrics related to the hypothesis
- no
- Any emerging blockers or risks
- risk: we are running out of disk space (81% capacity) for our k3s k8s environment
- we are scoping the work for TTL for environments at our next planning meeting
- we are requesting more space from CloudVPS in the meantime phab:T378231
- and resizing our volumes accordingly phab:T378234
- risk: new engineers using Apple silicon (e.g. M1, et. al.) rolling on the team are having a difficult time being able to become effective quickly because their device can't run container images created for x64 and cannot run a full-featured kubernetes locally.
- we've scheduled time as a team to discuss what is difficient in the current state and what we'd like to have
- risk: we are running out of disk space (81% capacity) for our k3s k8s environment
- Any unresolved dependencies - do you depend on another team that hasn’t already given you what you need? Are you on the hook to give another team something you aren’t able to give right now?
- no
- Have there been any new lessons from the hypothesis?
- no
- Have there been any changes to the hypothesis scope or timeline?
- no