akosiaris added a comment.
In T355685#9484621 <https://phabricator.wikimedia.org/T355685#9484621>, @Lucas_Werkmeister_WMDE wrote: > In T355685#9484091 <https://phabricator.wikimedia.org/T355685#9484091>, @akosiaris wrote: > >> My high level suggestion would be to re-evaluate if the `test` helm release actually serves a useful purpose (I know it serves `test.wikidata.org` but it apparently gets updated very infrequently. All termbox releases have been at the same version for 10 months now, so can't we just have `test.wikidata.org` use the main one?). > > IMHO it’s useful to be able to test a new Termbox version on Test Wikidata before deploying it to Wikidata – but as we’ve seen in this task, the current setup doesn’t support that perfectly, because there are too many differences between in the `test` release. Agreed on the last part. On the first part, it depends on what a failure of Termbox would mean for your end users and whether it indeed makes sense to have 1 more safety net (in addition to staging). It's a product decision as you say. If it would help them make that decision, the dashboard for the `/termbox` API endpoint, is at https://grafana-rw.wikimedia.org/d/wJRbI7FGk/termbox?orgId=1&var-dc=thanos&var-site=All&var-service=termbox&var-prometheus=k8s&var-container_name=All&from=now-6M&to=now&viewPanel=12&editPanel=12 A quick reading show over the last 12 months, shows a multimodal distribution. It's split in 2 main sections, 1 that's before Jun 2023 and after mid-November 2023 and the in-between (Northern Summer+Autumn let's call it). The traffic in the latter pattern apparently tripled and then subsided again. I have no idea if this is a seasonal effect or a result of some code changes. In any case, the amount of rps implies a small amount of concurrent users globally, so there's an argument to be made that it might be OK to not have a `testing` ground. > Would it be possible to have just one helm release, but have Test Wikidata use the `staging` cluster while Wikidata uses the `eqiad` and `codfw` clusters? Meaning merging the functionality of `test` in the functionality of the `staging` release ? It certainly is possible, although that would mean overloading the functionality of the `staging` release. We do have an open big question of what the `staging` releases mean to deployers after all and whether they indeed find them useful. I am a bit ambivalent about that approach, but it certainly is possible and if product people deemed it is useful to have a test release, we can go down that path. > Otherwise, I think it wouldn’t be the end of the world if we just lost this ability, and always had to deploy to Test Wikidata and Wikidata together; the impact is that mobile users without JavaScript lose access to terms until the deployer notices the problem and rolls back to the old version, which should be accceptable IMHO. (Though I’d want to check that with Product if we decide to go this way.) Thanks for this input, I appreciate it. TASK DETAIL https://phabricator.wikimedia.org/T355685 EMAIL PREFERENCES https://phabricator.wikimedia.org/settings/panel/emailpreferences/ To: akosiaris Cc: Aklapper, akosiaris, Clement_Goubert, Jdforrester-WMF, Michael, WMDE-leszek, Lucas_Werkmeister_WMDE, Danny_Benjafield_WMDE, Kappakayala, Mohamed-Awnallah, Astuthiodit_1, lbowmaker, Arnoldokoth, BTullis, karapayneWMDE, Invadibot, Ywats0ns, maantietaja, wkandek, JMeybohm, ItamarWMDE, Akuckartz, darthmon_wmde, Nandana, jijiki, Lahi, Gq86, GoranSMilovanovic, QZanden, KimKelting, LawExplorer, _jensen, rosalieper, Scott_WUaS, Wikidata-bugs, aude, Lydia_Pintscher, Mbch331
_______________________________________________ Wikidata-bugs mailing list -- wikidata-bugs@lists.wikimedia.org To unsubscribe send an email to wikidata-bugs-le...@lists.wikimedia.org
