Catalyst/Updates/2024-08-15

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 Patch Demo 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
  • team has finished all tasks blocking the go-live phab:T370076
  • we decided on a standard nomencalture for refering to patchdemo instances and and their environments
    • Patchdemo Instance:
      • k8s-patchdemo - the patchdemo the Catalyst team is running out of k3s
      • vm-patchdemo - the "legacy" VM of patchdemo that can only deploy virtual host environments
    • Environment Type:
      • vhost-env - an environment created and hosted as an apache virtual host (aka a legacy environment)
      • k8s-env - an environment created as a kubernetes deployment by patchdemo
    • Combining:
      • [patchdemo instance]-[environment-type]
      • e.g.:
        • k8s-patchdemo vhost-env is a "legacy" environment created by the Catalyst k8s patchdemo environment
        • k8s-patchdemo-k8s-env is an environment deployed on kubernetes through the Catatlyst kubernetes patchdemo instance
        • vm-patchdemo-vhost-env is an environment created on the legacy patchdemo instance
        • vm-patchdemo-k8s-env is a thing that does not exists because the vm-patchdemo cannot deploy a k8s-env
  • team came to consensus on tactic to preserve old patchdemo links phab:T372291
    • we made a job that queries/scraps existing patchdemo-vm-vhost-envs and adds them to the patchdemo-k8s apache config to redirect to patchdemo-legacy.wmcloud.org
• Any new metrics related to the hypothesis
  • no
• Any emerging blockers or risks
  • the team-lead, Stef, will be on vacation for 1.5 weeks starting next week starting Wednesday
    • the Go-Live is scheduled for Monday 2024-08-19 before she leaves
    • if the Go-Live gets delayed again, steps to deploy have been laid out in phab:T370076#10068123 and Jeena Huneidi will be the deployer
• 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 new unresolved dependencies
    • meta:Abstract Wikipedia is still waiting for us to open up the Catalyst API for general consumption
      • this work is considered blocked behind our go-live
• Have there been any new lessons from the hypothesis?
  • no new lessons
• Have there been any changes to the hypothesis scope or timeline?
  • no