See also T93213

Change 202689 had a related patch set uploaded (by KartikMistry):
Beta: Add wikis for ContentTranslation

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

I dont think anything is blocked on Releng. The Add a wiki tutorial should covers all steps required and they are doable by anyone able to +2 on operations/mediawiki-config and in the wmf LDAP group to refresh the Jenkins job.

If there is something actually blocking, please be specific :)

@hashar Just https://gerrit.wikimedia.org/r/#/c/202689 and we're good to go! :)

@hashar Ping!

Just added a few more people to that review list (SPOFs are bad ;) ).

Change 202689 merged by jenkins-bot:
Beta: Add wikis for ContentTranslation

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

Change 206389 had a related patch set uploaded (by Hashar):
Beta: Add wikis for ContentTranslation

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

The wiki page https://wikitech.wikimedia.org/wiki/Nova_Resource:Deployment-prep/Add_a_wiki list several steps and the last one (configure Jenkins) hasn't been completed. I have proposed https://gerrit.wikimedia.org/r/#/c/206389/ to do so.

One has to verify that all steps have been completed ie:

• databases created with addWiki.php)
• search setup
• Parsoid configuration
• Jenkins update

@hashar https://wikitech.wikimedia.org/wiki/Nova_Resource:Deployment-prep/Add_a_wiki#Step_2:_update_the_Apache_configuration seems outdated as /a/common doesn't exists :/

@KartikMistry: I'm working on updating the docs on wikitech and hopefully automating the process a bit more.

@mmodell, that would be fantastic! Thank you!!

@KartikMistry it should be correct now, I'm going to try to further automate the process but this is less confusing now. Thanks to @demon, he did most of the documentation cleanup.

So....right now CentralAuth is broken because these wikis haven't been set up yet.

Reverted the all-labs.dblist/wikiversions.json changes in https://gerrit.wikimedia.org/r/#/c/208170/ as it was breaking CentralAuth. The databases need to be created FIRST and then config changes done.

In T90683#1253021, @Legoktm wrote:

The databases need to be created FIRST and then config changes done.

This.

That add a wiki instruction is way outdated (and should be merged into the primary one). You should create the wiki prior to adding to wikiversions. In fact, addWiki does that for you! I think the idea was to use the new wiki's dbname as the --wiki param to addWiki.php but this is incorrect.

The invocation of addWiki.php is incredibly arcane.

mwscript addWiki.php --wiki=aawiki [lang] [site] [dbname] [domain]

The --wiki parameter actually turns out to be important. We need a master DB connection to an existing wiki on the same cluster as the target wiki. An existing wiki. Ideally this shouldn't happen but there's always a chance of a hook doing something dumb prior to getting to the core tables created and us ending up hitting a non-existent table. Also I'm not sure of the behavior on trying to get db config for a non-existing wiki (and even end up on the right cluster--this is untested territory).

Usually this will be s3. So most wikis (including the aawiki example) would be fine here. But if you really want to end up on a different cluster--which should be preconfigured in db-*.php as it is--then aawiki won't cut it.

In T90683#1253146, @demon wrote:

The --wiki parameter actually turns out to be important. We need a master DB connection to an existing wiki on the same cluster as the target wiki. An existing wiki. Ideally this shouldn't happen but there's always a chance of a hook doing something dumb prior to getting to the core tables created and us ending up hitting a non-existent table. Also I'm not sure of the behavior on trying to get db config for a non-existing wiki (and even end up on the right cluster--this is untested territory).

does it really make sense to let hooks run in administration scripts?

In T90683#1255823, @mmodell wrote:

In T90683#1253146, @demon wrote:

The --wiki parameter actually turns out to be important. We need a master DB connection to an existing wiki on the same cluster as the target wiki. An existing wiki. Ideally this shouldn't happen but there's always a chance of a hook doing something dumb prior to getting to the core tables created and us ending up hitting a non-existent table. Also I'm not sure of the behavior on trying to get db config for a non-existing wiki (and even end up on the right cluster--this is untested territory).

does it really make sense to let hooks run in administration scripts?

In most cases yes, you would want hooks to run. For example: if you were running refreshLinks.php on a wiki you would want to make sure all parser-related hooks are there so you end up parsing the links as intended.

For addWiki we could possibly unset $wgHooks prior to execution. I'm still on the fence about it.

The Jenkins job that update the databases can probably read the .dblist T98342

Change 206389 abandoned by Hashar:
Beta: Add wikis for ContentTranslation

Reason:
The Jenkins job has been refactored and now reads the databases directly from all-labs.dblist

T98342 beta-update-databases-eqiad should get list of DB to update from mediawiki-config all-labs.dblist

Code https://gerrit.wikimedia.org/r/#/c/210619/3/jjb/beta.yaml,unified

That has been made simpler following your recent wiki additions :]

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

/poke

what's the status of this?

@mmodell, can you explain parameters of,

mwscript extensions/WikimediaMaintenance/addWiki.php --wiki=aawiki \
    en wikimedia loginwiki login.wikimedia.beta.wmflabs.org

en = ?

--help explains them:

Arguments:
    <language>: Language code of new site, e.g. en
    <site>: Type of site, e.g. wikipedia
    <dbname>: Name of database to create, e.g. enwiki
    <domain>: Domain name of the wiki, e.g. en.wikipedia.org

Unblocked per discussion in SoS. We'll revisit this once the Staging project is un-paused.

@KartikMistry is there anything left to do on this task? Seems all wiki have been created and are functional. If that is the case please close this bug, else poke me anytime so we can pair/sprint/finish it :-]

Do we need any more testing environments? If not, and if I understand the title correctly, this can probably be closed.

Moved to externally blocked on the beta-cluster work-board.

New wiki databases are not on deployment-prep as of right now. If this is no longer a priority for ContentTranslation feel free to close.