Some discussion on how to approach this is happening. Jason will update here.

Note that @Ladsgroup advised that deploying the topic model would be messy/complicated with the current recentchanges design; so we should avoid that one in particular for now. But, we can deploy ores with the revert risk models on all but the busiest wikis.
I created a list of wikis that we can deploy the language agnostic revert risk model here:

I'll do the same for the multilingual revert risk model

On the side of table catalog. I suggest creating a dblist for ores tables so we can catalog the tables without needing to hand code all of these. Also do you really want to deploy it to nostalgia.wikipedia.org? :P

In T391103#10713983, @Ladsgroup wrote:

On the side of table catalog. I suggest creating a dblist for ores tables so we can catalog the tables without needing to hand code all of these. Also do you really want to deploy it to nostalgia.wikipedia.org? :P

I think we're good on that one :-D! just defining the technical limitations in P74609

ah okay

and here's the list of wikis on which we can deploy the multilingual revert risk model:

@JWheeler-WMF we'll need to decide which wikis from the deployable lists (P74609, P74610) we're going to enable ores for; that's what we'll ask DBA for help with.

Change #1143638 had a related patch set uploaded (by Jsn.sherman; author: Jsn.sherman):

[operations/mediawiki-config@master] Create dblist for ores extension

https://gerrit.wikimedia.org/r/1143638

In T391103#10713983, @Ladsgroup wrote:

On the side of table catalog. I suggest creating a dblist for ores tables so we can catalog the tables without needing to hand code all of these. [...]

I gave it a shot here:

In T391103#10805610, @gerritbot wrote:

Change #1143638 had a related patch set uploaded (by Jsn.sherman; author: Jsn.sherman):

[operations/mediawiki-config@master] Create dblist for ores extension

https://gerrit.wikimedia.org/r/1143638

I just started with the wikis that look like they already have the ores extension setup. I assume we would then add new entries to the dblist as part of our deployment process and then run the table creation script against the list as mentioned here?
https://wikitech.wikimedia.org/wiki/Creating_new_tables#Deployment
Is it idempotent, meaning we can run it against a list that includes wikis that already have the table?

I made a comment on the patch.

For deploying to new wikis. You must first create the table in the wiki. You have two options and they are outlined in https://wikitech.wikimedia.org/wiki/Creating_new_tables (either add to createExtensionTables.php or directly invoke the sql file) and then you can enable ores on the wiki via adding it to the dblist.

In T391103#10806815, @Ladsgroup wrote:

I made a comment on the patch.

I'll get that patch updated.

For deploying to new wikis. You must first create the table in the wiki. You have two options and they are outlined in https://wikitech.wikimedia.org/wiki/Creating_new_tables (either add to createExtensionTables.php or directly invoke the sql file) and then you can enable ores on the wiki via adding it to the dblist.

Makes sense! I got a little tripped up by a this passage in https://wikitech.wikimedia.org/wiki/Creating_new_tables#Deployment:

You can run the script on all wikis in a dblist using foreachwikiindblist name-of-dblist.dblist extensions/WikimediaMaintenance/createExtensionTables.php extensionname

but I can see that would probably only make sense if you were adding the tables for a new list that didn't already have some tables deployed already.

In T391103#10806815, @Ladsgroup wrote:

I made a comment on the patch.

For deploying to new wikis. You must first create the table in the wiki. You have two options and they are outlined in https://wikitech.wikimedia.org/wiki/Creating_new_tables (either add to createExtensionTables.php or directly invoke the sql file) and then you can enable ores on the wiki via adding it to the dblist.

Hello, @Ladsgroup I had a question about this.
In looking at the createExtensionTables.php I see that ORES is already added to the file. Since that is the case, do we still need to do step 6?

As you mention ores is already in the createExtensionTables.php file.
My understanding is that we would run the following command to create tables for idwiki:

mwscript-k8s --comment="T382171" -- extensions/WikimediaMaintenance/createExtensionTables.php --wiki=idwiki ores

IIUC if we wanted to do it in a batch we would have to run the following command (after we had updated the dblist with new entries):

foreachwikiindblist ores.dblist extensions/WikimediaMaintenance/createExtensionTables.php ores

My understanding is that this would cause an error since the tables for all the other wikis already exist. So to Jason's question I understand that this is not idempotent and it would throw errors since the CREATE TABLE statements do not have a IF NOT EXISTS clause in https://github.com/wikimedia/mediawiki-extensions-ORES/blob/master/sql/mysql/tables-generated.sql
I would be happy if I'm just wrong and this works so then we can just run it in a batch. Not saying that running it one by one is gonna be an issue ofc

In T391103#10830006, @Kgraessle wrote:

In T391103#10806815, @Ladsgroup wrote:

I made a comment on the patch.

For deploying to new wikis. You must first create the table in the wiki. You have two options and they are outlined in https://wikitech.wikimedia.org/wiki/Creating_new_tables (either add to createExtensionTables.php or directly invoke the sql file) and then you can enable ores on the wiki via adding it to the dblist.

Hello, @Ladsgroup I had a question about this.
In looking at the createExtensionTables.php I see that ORES is already added to the file. Since that is the case, do we still need to do step 6?

What @isarantopoulos said. I have nothing else to add!

In T391103#10830212, @Ladsgroup wrote:

In T391103#10830006, @Kgraessle wrote:

In T391103#10806815, @Ladsgroup wrote:

I made a comment on the patch.

For deploying to new wikis. You must first create the table in the wiki. You have two options and they are outlined in https://wikitech.wikimedia.org/wiki/Creating_new_tables (either add to createExtensionTables.php or directly invoke the sql file) and then you can enable ores on the wiki via adding it to the dblist.

Hello, @Ladsgroup I had a question about this.
In looking at the createExtensionTables.php I see that ORES is already added to the file. Since that is the case, do we still need to do step 6?

What @isarantopoulos said. I have nothing else to add!

Perfect, thanks!

Change #1147104 had a related patch set uploaded (by Ilias Sarantopoulos; author: Ilias Sarantopoulos):

[operations/puppet@production] mariadb: Add ores extension tables to the table catalog

https://gerrit.wikimedia.org/r/1147104

Change #1143638 merged by jenkins-bot:

[operations/mediawiki-config@master] Create dblist for ores extension

https://gerrit.wikimedia.org/r/1143638

Mentioned in SAL (#wikimedia-operations) [2025-05-19T11:52:47Z] <isaranto@deploy1003> Started scap sync-world: Backport for [[gerrit:rGERRIT114363824469|Create dblist for ores extension (T391103)]]

Mentioned in SAL (#wikimedia-operations) [2025-05-19T11:56:54Z] <isaranto@deploy1003> isaranto, jsn: Backport for [[gerrit:rGERRIT114363824469|Create dblist for ores extension (T391103)]] synced to the testservers (see https://wikitech.wikimedia.org/wiki/Mwdebug). Changes can now be verified there.

Mentioned in SAL (#wikimedia-operations) [2025-05-19T12:05:15Z] <isaranto@deploy1003> Finished scap sync-world: Backport for [[gerrit:rGERRIT114363824469|Create dblist for ores extension (T391103)]] (duration: 12m 27s)

Change #1147104 merged by Ladsgroup:

[operations/puppet@production] mariadb: Add ores extension tables to the table catalog

https://gerrit.wikimedia.org/r/1147104

From the above initial list the extension is already enabled in the following wikis:

simplewiki
trwiki

And we have also enabled it in idwiki.
I have created the tables for the remaining list of wikis (ores_classification and ores_model tables).
This is the list of the remaining wikis, as this step precedes the extension installation:

cywiki
bewiki
kkwiki
nnwiki
mkwiki
lawiki
afwiki
tewiki
mrwiki
swwiki
mlwiki
iswiki
pawiki
hawiki
tlwiki
bnwiki
azwiki

Could someone run the maintain-views script for the above? Thank youu 🙏
cc: @Ladsgroup @taavi

Could someone run the maintain-views script for the above? Thank youu 🙏

First the tables must be created in production, if they are not created the maintain-views will be noop. Let me know once you created the tables and I can run it (also I think you can just directly create the tables without needing to enable the extension or deploy anything, it'll be sitting there empty but that's fine)

In T391103#10851929, @Ladsgroup wrote:

Could someone run the maintain-views script for the above? Thank youu 🙏

First the tables must be created in production, if they are not created the maintain-views will be noop. Let me know once you created the tables and I can run it (also I think you can just directly create the tables without needing to enable the extension or deploy anything, it'll be sitting there empty but that's fine)

nvm, I'm illiterate. You already created them.

Cookbook cookbooks.sre.wikireplicas.update-views run by ladsgroup: Started updating wiki replica views

Cookbook cookbooks.sre.wikireplicas.update-views started by ladsgroup completed:

• an-redacteddb1001.eqiad.wmnet (PASS)
  • Ran Puppet agent
  • Ran 'maintain-views --replace-all --auto-depool --databases lawiki'

• clouddb1017.eqiad.wmnet (PASS)
  • Ran Puppet agent
  • Ran 'maintain-views --replace-all --auto-depool --databases lawiki'

• clouddb1018.eqiad.wmnet (PASS)
  • Ran Puppet agent
  • Ran 'maintain-views --replace-all --auto-depool --databases lawiki'

• clouddb1019.eqiad.wmnet (PASS)
  • Ran Puppet agent
  • Ran 'maintain-views --replace-all --auto-depool --databases lawiki'

• clouddb1020.eqiad.wmnet (PASS)
  • Ran Puppet agent
  • Ran 'maintain-views --replace-all --auto-depool --databases lawiki'

• clouddb1013.eqiad.wmnet (PASS)
  • Ran Puppet agent
  • Ran 'maintain-views --replace-all --auto-depool --databases lawiki'

• clouddb1014.eqiad.wmnet (PASS)
  • Ran Puppet agent
  • Ran 'maintain-views --replace-all --auto-depool --databases lawiki'

• clouddb1015.eqiad.wmnet (PASS)
  • Ran Puppet agent
  • Ran 'maintain-views --replace-all --auto-depool --databases lawiki'

• clouddb1016.eqiad.wmnet (PASS)
  • Ran Puppet agent
  • Ran 'maintain-views --replace-all --auto-depool --databases lawiki'

I ran it with multiple db options and only lawiki was run. So the cookbook must be either run one by one (or xargs) or the old fashioned way. I leave that to WMCS to handle.

I split that to T395122 since this task is going to get very confusing otherwise.

Yes that makes sense. Once again thank you both!