Page MenuHomePhabricator

Request creation of checkuser-beta-wiki VPS project
Closed, ResolvedPublic

Description

Project Name: checkuser-beta-wiki

Wikitech Usernames of requestors: Dreamy Jazz (@Ladsgroup suggested this to me)

Purpose:
To run a single wiki instance of mediawiki, with the CheckUser extension installed, to test database changes as CheckUser is not enabled on the beta cluster.

Brief description:
The beta wiki cluster cannot have the CheckUser extension enabled for privacy concerns (T214820). I'm currently working on changes that include database changes, and the process for altering a table usually requires having the change applied to the beta cluster. As such, alters to the database structure are harder to achieve especially if this requires removal or modification. Having a wiki where update.php can be run and CheckUser is also enabled allows testing database changes.

This, unlike a local testing wiki, could be accessed by others for testing purposes which makes it possible for the DBAs to verify that the alter to the database would not have unintended side effects and issues. The wiki is unlikely to need much in way of resources, but it would be good to have a replication and primary database. Access will only be needed for testing, so this wiki will not need to be open.

Ladsgroup suggested using a Cloud VPS instance in T321391. Because the data that CheckUser collects is private it was suggested to use Cloud VPS over Toolforge. I already have access to CheckUser data on the English Wikipedia, and would intend to keep access limited to only those with access to this kind of data on WMF wikis (and thus have signed the relevant NDAs).

How soon you are hoping this can be fulfilled: Removal of columns is coming to the cu_changes table in the short to medium term (as part of the follow up to T324907) and being able to test this using something like this setup is almost certainly required.

Event Timeline

+1.

The cloud vps web proxy by default doesn't forward IP addresses to the backend. It's possible to enable IP forwarding on a per-proxy basis, would you need that?

The cloud vps web proxy by default doesn't forward IP addresses to the backend. It's possible to enable IP forwarding on a per-proxy basis, would you need that?

I presume by IP forwarding you are meaning having the IP of the client connecting through the proxy instead of the proxy IP.

If so, I don't think there would be the need to have different IP addresses appear for testing purposes at the moment. In the future I think this may be a useful thing as there are likely to be database changes where IP and XFF columns are modified to normalise them (and for XFF to allow searching by more than just the first XFF IP in the chain).

Mentioned in SAL (#wikimedia-cloud-feed) [2023-01-12T14:12:53Z] <wm-bot2> Created project checkuser-beta-wiki with default quotas. (T326740) - cookbook ran by arturo@nostromo

Mentioned in SAL (#wikimedia-cloud-feed) [2023-01-12T15:56:14Z] <wm-bot2> Added user dreamyjazz to the project as projectadmin (T326740) - cookbook ran by arturo@nostromo

aborrero claimed this task.

Mentioned in SAL (#wikimedia-cloud-feed) [2023-01-13T14:49:48Z] <wm-bot2> added user dreamyjazz to the project as user (T326740) - cookbook ran by arturo@nostromo