Hello,
I am one of the test engineers on the QTE team.
There is a plan to migrate the MediaWiki software on production to Kubernetes.
In preparation for this, we will be migrating test2wiki to Kubernetes first so that QTE can test it and catch any bugs before the wider roll-out.
I am trying to identify areas of our software for which the migration to Kubernetes might pose a risk.
I wonder if this might be true of any of the software you are responsible for. In particular, I am thinking about where MediaWiki is interacting with different services in our ecosystem. I don't know enough about this area to make an informed judgement.
Any ideas about what might be risky and in need of testing, and how one might go about testing it on test2wiki (https://test2.wikipedia.org/wiki/Main_Page) would be of great help to me.
Let me know if you have any questions.
Thank you,
Dom
Hm, I don't think the analytics systems interact too directly with MediaWiki. They do use the EventStreamConfig extension's https://www.mediawiki.org/wiki/Extension:EventStreamConfig API from meta.wikimedia.org. The EventLogging extension https://www.mediawiki.org/wiki/Extension:EventLogging is used to send instrumentation data, and is still used to host legacy EventLogging schemas http://meta.wikimedia.org/w/index.php?title=Special%3AAllPages&from=&to=&namespace=470 .
I think for the most part, as long as those APIs keep working (mostly with meta.wikimedia.org), our stuff will work. I'll let other folks chime in too. You can follow up with us in IRC at #wikimedia-analytics, or in WMF Slack #data-engineering.
On Tue, Jun 21, 2022 at 4:25 AM Dominic Walden dwalden@wikimedia.org wrote:
Hello,
I am one of the test engineers on the QTE team.
There is a plan to migrate the MediaWiki software on production to Kubernetes.
In preparation for this, we will be migrating test2wiki to Kubernetes first so that QTE can test it and catch any bugs before the wider roll-out.
I am trying to identify areas of our software for which the migration to Kubernetes might pose a risk.
I wonder if this might be true of any of the software you are responsible for. In particular, I am thinking about where MediaWiki is interacting with different services in our ecosystem. I don't know enough about this area to make an informed judgement.
Any ideas about what might be risky and in need of testing, and how one might go about testing it on test2wiki (https://test2.wikipedia.org/wiki/Main_Page) would be of great help to me.
Let me know if you have any questions.
Thank you,
Dom _______________________________________________ Analytics mailing list -- analytics@lists.wikimedia.org To unsubscribe send an email to analytics-leave@lists.wikimedia.org
Thanks for the response Andrew. I asked some questions on IRC but I think they got missed.
Do you know if EventStreamConfig can be tested on test2wiki (so I can check the API is working)?
I also notice that EventBus has some API tests already. Can those be run against test2wiki?
Thanks,
Dom
Andrew Otto otto@wikimedia.org writes:
Hm, I don't think the analytics systems interact too directly with MediaWiki. They do use the EventStreamConfig extension's API from meta.wikimedia.org. The EventLogging extension is used to send instrumentation data, and is still used to host legacy EventLogging schemas.
I think for the most part, as long as those APIs keep working (mostly with meta.wikimedia.org), our stuff will work. I'll let other folks chime in too. You can follow up with us in IRC at #wikimedia-analytics, or in WMF Slack #data-engineering.
On Tue, Jun 21, 2022 at 4:25 AM Dominic Walden dwalden@wikimedia.org wrote:
Hello,
I am one of the test engineers on the QTE team.
There is a plan to migrate the MediaWiki software on production to Kubernetes.
In preparation for this, we will be migrating test2wiki to Kubernetes first so that QTE can test it and catch any bugs before the wider roll-out.
I am trying to identify areas of our software for which the migration to Kubernetes might pose a risk.
I wonder if this might be true of any of the software you are responsible for. In particular, I am thinking about where MediaWiki is interacting with different services in our ecosystem. I don't know enough about this area to make an informed judgement.
Any ideas about what might be risky and in need of testing, and how one might go about testing it on test2wiki (https://test2.wikipedia.org/wiki/Main_Page) would be of great help to me.
Let me know if you have any questions.
Thank you,
Dom _______________________________________________ Analytics mailing list -- analytics@lists.wikimedia.org To unsubscribe send an email to analytics-leave@lists.wikimedia.org
Analytics mailing list -- analytics@lists.wikimedia.org To unsubscribe send an email to analytics-leave@lists.wikimedia.org
Do you know if EventStreamConfig can be tested on test2wiki (so I can
Looks like it! curl ' https://test2.wikipedia.org/w/api.php?action=streamconfigs&all_settings=...'
I also notice that EventBus has some API tests already. Can those be run
against test2wiki? I'm not actually familiar with how this works. It looks like that API test is about something with job queue / change prop? Perhaps ask the Platform Engineering team about this one? Some links:
https://www.mediawiki.org/wiki/Change_propagation https://wikitech.wikimedia.org/wiki/Changeprop
On Tue, Jul 5, 2022 at 9:39 AM Dominic Walden dwalden@wikimedia.org wrote:
Thanks for the response Andrew. I asked some questions on IRC but I think they got missed.
Do you know if EventStreamConfig can be tested on test2wiki (so I can check the API is working)?
I also notice that EventBus has some API tests already. Can those be run against test2wiki?
Thanks,
Dom
Andrew Otto otto@wikimedia.org writes:
Hm, I don't think the analytics systems interact too directly with
MediaWiki. They do use the EventStreamConfig extension's API from meta.wikimedia.org. The EventLogging extension is used to send instrumentation data, and is still used to host
legacy EventLogging schemas.
I think for the most part, as long as those APIs keep working (mostly
with meta.wikimedia.org), our stuff will work. I'll let other folks chime in too. You can follow up with us in IRC at #wikimedia-analytics, or in WMF Slack #data-engineering.
On Tue, Jun 21, 2022 at 4:25 AM Dominic Walden dwalden@wikimedia.org
wrote:
Hello,
I am one of the test engineers on the QTE team.
There is a plan to migrate the MediaWiki software on production to Kubernetes.
In preparation for this, we will be migrating test2wiki to Kubernetes first so that QTE can test it and catch any bugs before the wider roll-out.
I am trying to identify areas of our software for which the migration to Kubernetes might pose a risk.
I wonder if this might be true of any of the software you are responsible for. In particular, I am thinking about where MediaWiki is interacting with different services in our ecosystem. I don't know enough about this area to make an informed judgement.
Any ideas about what might be risky and in need of testing, and how one might go about testing it on test2wiki (https://test2.wikipedia.org/wiki/Main_Page) would be of great help to me.
Let me know if you have any questions.
Thank you,
Dom _______________________________________________ Analytics mailing list -- analytics@lists.wikimedia.org To unsubscribe send an email to analytics-leave@lists.wikimedia.org
Analytics mailing list -- analytics@lists.wikimedia.org To unsubscribe send an email to analytics-leave@lists.wikimedia.org
Analytics mailing list -- analytics@lists.wikimedia.org To unsubscribe send an email to analytics-leave@lists.wikimedia.org
Andrew Otto otto@wikimedia.org writes:
Do you know if EventStreamConfig can be tested on test2wiki (so I can
Looks like it! curl 'https://test2.wikipedia.org/w/api.php?action=streamconfigs&all_settings=...'
Great, thanks!
I also notice that EventBus has some API tests already. Can those be run against test2wiki?
I'm not actually familiar with how this works. It looks like that API test is about something with job queue / change prop? Perhaps ask the Platform Engineering team about this one? Some links:
Will do, thanks for the information.
Dan Andreescu dandreescu@wikimedia.org writes:
Some dashboards rely on the Dashiki extension. As far as I know this is only enabled on meta.wikimedia.org, but it would be good to know if it'll still work going forward or if we have to work around it failing. Other than that I don't really know of anything that we need mediawiki for directly.
OK. Something to keep in mind when we deploy Kubernetes to more wikis.
Thanks,
Dom
Some dashboards rely on the Dashiki extension https://www.mediawiki.org/wiki/Extension:Dashiki. As far as I know this is only enabled https://meta.wikimedia.org/wiki/Special:Version on meta.wikimedia.org, but it would be good to know if it'll still work going forward or if we have to work around it failing. Other than that I don't really know of anything that we need mediawiki for directly.
On Tue, Jun 21, 2022 at 4:25 AM Dominic Walden dwalden@wikimedia.org wrote:
Hello,
I am one of the test engineers on the QTE team.
There is a plan to migrate the MediaWiki software on production to Kubernetes.
In preparation for this, we will be migrating test2wiki to Kubernetes first so that QTE can test it and catch any bugs before the wider roll-out.
I am trying to identify areas of our software for which the migration to Kubernetes might pose a risk.
I wonder if this might be true of any of the software you are responsible for. In particular, I am thinking about where MediaWiki is interacting with different services in our ecosystem. I don't know enough about this area to make an informed judgement.
Any ideas about what might be risky and in need of testing, and how one might go about testing it on test2wiki (https://test2.wikipedia.org/wiki/Main_Page) would be of great help to me.
Let me know if you have any questions.
Thank you,
Dom _______________________________________________ Analytics mailing list -- analytics@lists.wikimedia.org To unsubscribe send an email to analytics-leave@lists.wikimedia.org