nyuuzyou/wikis huggingface dataset:
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
Catalyst/Updates/2024-08-22

== 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 continued working on stage 2 of the soft lunch as per our planned timeline. We currently expect this to happen on schedule on 2024-08-26
** team has continued working on hardening the production patchdemo after the initial lunch
** legacy Patchdemo repository has been archived:
*** all open patchdemo issues from GitLab have been migrated to Phabricator: phab:project/view/7367
*** new Patchdemo repository is fully up-to-date with all commits from the legacy repo
** created a proposal for the Patchdemo deployment pipelines. Including the existing production pipeline and a new staging environment
* Any new metrics related to the hypothesis
** no
* Any emerging blockers or risks
** no new blockers or risks
* 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
Catalyst/Updates/2024-08-29

== 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 continued working on stage 2 of the soft lunch
*** deploy to the production patchdemo finally happened on 2024-08-29
*** catalyst backend is now available to all users as an opt-in checkbox
** team has continued working on hardening the production patchdemo
** field "Start with version" is now fully supported by the new system: phab:T371974
* Any new metrics related to the hypothesis
** no
* Any emerging blockers or risks
** no new blockers or risks
* 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
Catalyst/Updates/2024-09-06

== 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
** phab:T373620 added link to documentation about the Catalyst backend
** phab:367784 CI running BDD tests for Catalyst API
** phab:T373913 set up staging environment for Patchdemo and Catalyst API
*** deploying to production is a manual step in Gitlab CI
** phab:T373605 prepared banner for Beta Launch
* Any new metrics related to the hypothesis
** no
* Any emerging blockers or risks
* 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
**** Vaughn is preparing to facilitate a meeting between Abstract Wikipedia and Catalyst to scope and plan the work
* Have there been any new lessons from the hypothesis?
** no new lessons
* Have there been any changes to the hypothesis scope or timeline?
** no
Catalyst/Updates/2024-09-13

== 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
** phab:T373917 fixed up low disk space on kubernetes cluster
*** unfortunately this involved unschedule downtime, see note on 3 hour downtime below
** phab:T373604 MR for enabling most extensions and all skins on the Catalyst backend for Patchdemo
** met with Abstract Wikipedia team to coordinate getting their test environments onto Catalyst
*** next quarter, goal is to spin up per-merge-request test environments for the Function Orchestrator and Function Evaluator
* Any new metrics related to the hypothesis
** no
* Any emerging blockers or risks
** we were slowed down on Tuesday by a roughly 3 hour downtime
*** root cause was that the kubernetes cluster ran out disk space
*** further complications emerged when removing and resizing volumes
**** we removed a volume on Horizon to make room to resize another volume, and recreated a (smaller) volume, and attached it to the VM
**** because /etc/fstab was configured to take a disk UUID, it failed to mount and thus failed to boot
**** CloudVPS had to change our /etc/fstab on the unbootable instance before we could fix the problem
* 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 new lessons
* Have there been any changes to the hypothesis scope or timeline?
** we will begin our engagement with Abstract Wikipedia for per-MR test environments in earnest at the beginning of Q2 (October)
Catalyst/Updates/2024-09-20

== 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
** phab:T373604 support for all extensions and skins on the Catalyst backend for Patchdemo
** phab:T374285 users can delete environments on https://patchdemo-legacy.wmcloud.org/
* Any new metrics related to the hypothesis
** no
* Any emerging blockers or risks
** risk: 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.
*** our current solution is set up a development environment on CloudVPS (which we are aware is not an intended use-case for CloudVPS)
* 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?
** risk: we are down one engineer until mid October
** risk we discovered that Catalyst environments can take up to 4GB of disk space
*** we risk running out of disk space quickly when switching most workloads to the Catalyst backend
*** we have some ideas on how to greatly reduce this phab:T375236
* Have there been any new lessons from the hypothesis?
** no
* Have there been any changes to the hypothesis scope or timeline?
** an initial task has been made to deploy a Wikifunctions environment on Catalyst phab:T374864
*** work to integrate with with Abstract Wikipedia's CI pipelines will begin in earnest at the beginning of Q2 (October)
Catalyst/Updates/2024-09-27

== 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
** phab:T373906 Support design/codex and oojs/ui in catalyst patchdemo environments
** phab:T374285 Legacy Patchdemo (patchdemo-vm) users should be able to delete old environments
* Any new metrics related to the hypothesis
** no
* Any emerging blockers or risks
** risk: 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.
*** phab:T375984 is a potential soltution using Skaffold, an open source project by Google, to define, deploy, and sync development environments
* 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?
** risk: we are down one engineer until mid October
** risk we discovered that Catalyst environments can take up to 4GB of disk space
*** we risk running out of disk space quickly when switching most workloads to the Catalyst backend
*** we have some ideas on how to greatly reduce this phab:T375236
* Have there been any new lessons from the hypothesis?
** no
* Have there been any changes to the hypothesis scope or timeline?
** an initial task has been made to deploy a Wikifunctions environment on Catalyst phab:T374864
*** work to integrate with with Abstract Wikipedia's CI pipelines will begin in earnest at the beginning of Q2 (October)
Catalyst/Updates/2024-10-04

== 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
** Finished phab:T371828 Create plan and documentation for horizontally scaling Catalyst k3s resources
** Finished phab:T373803 Move "Don't see your environment?" message to the "Previously generated wikis" section
** Fixed phab:T375924 creating an environment with no extensions, skins, or modules renders patchdemo in a wedged/non-functional state
** Finished phab:T375236 [Refactor] [ci-charts] environments share and link to a "repository pool" to save space
*** this saves us on up to 4GB of disk space per environment
** Progress phab:T372900 User can see install progress when installing a k8s-environment
*** This has vexed us for a bit because there is/was a timing component to when the Catalyst API would allow you to stream logs (i.e. the pod that to be running). This meant that patchdemo had to divine when it would be safe to stream the results. What was worse is that, except when the pod was ready to stream logs, it's response would not be text/event-stream which would cause the PHP http clients to throw and exception. We're still working on smoothing out this integration.
* Any new metrics related to the hypothesis
** no
* Any emerging blockers or risks
** risk: 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.
*** phab:T375984 is a potential soltution using Skaffold, an open source project by Google, to define, deploy, and sync development environments
*** we've done some experimenting with Skaffold this week, but are deprioritizing the work until we have launched beta
** risk: we are down one engineer until mid October
* 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?
** we are meant to start work on getting Wikifunctions environments up and running on Catalyst
*** but our main priority is to get to beta launch first
* Have there been any new lessons from the hypothesis?
** no
* Have there been any changes to the hypothesis scope or timeline?
** no
Catalyst/Updates/2024-10-22

== 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
** All of the tail end of wiki env creation features have been implemented.
*** This brings us just about to feature complete after phab:T372900
** intial work of onboarding wikifunctions (i.e. deploying the helm chart on catalyst phab:TT374864) has begun this week
* Any new metrics related to the hypothesis
** no
* Any emerging blockers or risks
** risk: 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 been having some success with Skaffold
*** we're planning to prioritze a track of work to make the developer onboarding experiece good for users of both mac and linux
** we are running out of disk space (again?)
*** we are planning on implementing a TTL (time-to-live) (i.e. experation date) for new environments
*** we are requesting more space from CloudVPS in the meantime
**** we are asking for a ~double size increase to tide us over while we figure out if this is normal usage or if there are some low hanging fruits to optimize disk usage
* 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?
* Have there been any new lessons from the hypothesis?
** no
* Have there been any changes to the hypothesis scope or timeline?
** no
Catalyst/Updates/2024-10-25

== 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
* 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
* 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
Stef Dunlap (talk) 22:29, 25 October 2024 (UTC)
Catalyst/Updates/2024-11-01

== 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:
*** this was pushed back a week due to concern of available disk space
*** we plan to send a wikitech-l email and update our wiki page
*** the "use catalyst" checkbox will remain unchecked by default as we collect feedback
** work continued with onboard Abstract Wikipedia onto catalyst
*** we have successfully deployed a wikifunctions environment onto catalyst
*** we chatted with the AW team about some of the lower level risks and consideration (i.e. got into the weeds)
** started work on getting a better handle on our disk space
*** phab:T378374 audit where we are spending disk space
*** phab:T376272 refresh and garbage collect the repo-pool
* Any new metrics related to the hypothesis
** no
* Any emerging blockers or risks
** risk: we are running out of disk space (79% capacity) for our k3s k8s environment
*** we are waiting on CloudVPS to respond to a quota increase request phab:T378231
** risk: we are running low on memory in our k3s k8s environment
*** we have the quota to increase, and it is planned next week phab:T378749
* 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
Stef Dunlap (talk) 21:57, 1 November 2024 (UTC)