Page MenuHomePhabricator

Request creation of wise VPS project
Closed, ResolvedPublic

Description

Project Name: wise

Developer account usernames of requestors: @Carandraug, @Gopavasanth

Purpose: semantic search of wikimedia commons with wise

Brief description: I am one of the developers of WISE Search engine (Apache 2 license and all dependencies are FOSS). We have built some demos where it searches some of the wikimedia, see https://meru.robots.ox.ac.uk/motd/ and I'm now exploring getting it running closer to wikimedia commons, namely on how to keep it up to date as new media are added. I've been talking with ebernhardson and dcausse on Wikimedia-Search (IRC) who suggested I applied for a a VPS. If it is possible to have a VM with 64 (or at least 32GB) of memory and 200GB of disk space that would be nice.

How soon you are hoping this can be fulfilled: this is not urgent at all. I guess sometime next month should be fine.

Details

Related Changes in GitLab:
TitleReferenceAuthorSource BranchDest Branch
flavors: add custom flavor for wiserepos/cloud/cloud-vps/tofu-infra!310volansT424068main
Customize query in GitLab

Event Timeline

Hello and thank you for reaching out. Wikimedia Foundation offers and supports a platform for running managed user workloads called Toolforge (https://wikitech.wikimedia.org/wiki/Portal:Toolforge). In practice it means having containers running on k8s, though with less per-containers resources (e.g. 4GB). Would WISE run distributed/partitioned/sharded in multiple containers and thus could run on Toolforge? Running on Toolforge, among other benefits, would mean not having to operate/admin a VM and instead run on a supported platform. Please let us know!

It is possible to shard wise but if each shard would only have 4GB I don't think that's worth it. I didn't measure it but I wouldn't be surprised if there was at least 1GB of overhead for each shard. It is also, currentlyy, a lot more work to run it in a distributed manner so I'd prefer to start with running it in a standalone manner and then investigate running it distributed.

Also, I'll be attending the wikimedia hackathon this coming weekend where I would like to be working on it (so the "this is not urgent at all. I guess sometime next month should be fine" no longer applies). See T424092

@Carandraug could you confirm that we should add also @Gopavasanth as project maintainers?

Or you can add them later. But I need you to link your ldap account into your phabricator profile (see LDAP user in https://phabricator.wikimedia.org/p/Carandraug/ ).

@Carandraug could you confirm that we should add also @Gopavasanth as project maintainers?

Yes, I confirm.

[...] But I need you to link your ldap account into your phabricator profile (see LDAP user in https://phabricator.wikimedia.org/p/Carandraug/ ).

It is done now. Thank you

thanks, +1 from my side, creating the project

Mentioned in SAL (#wikimedia-cloud-feed) [2026-04-30T11:26:34Z] <volans@cloudcumin1001> END (PASS) - Cookbook wmcs.vps.create_project (exit_code=0) for project wise in eqiad1 (T424068)

Project created. @Carandraug, @Gopavasanth please verify that you have access and also make sure to join the cloud-announce mailing list.

With the current quota you can create single VMs up to 32GB of RAM and there is a project limit of 64GB of RAM. To be able to run a 64GB RAM VM a custom VM flavor is needed. It also makes the VM harder to be live-migrated in case of maintenance so if you can make it work with 32GB is probably better also in terms of disruptions. But feel free to ask for the special flavor if really needed.

As discussed at the hackathon with Volans, we're equesting the 64GB instance for now

As discussed at the hackathon with Volans, we're equesting the 64GB instance for now

+1, @Volans is preparing the patch.

As discussed at the hackathon with Volans, we're equesting the 64GB instance for now

Chatted with me (and Francesco). I've explained the limitation of the 64GB RAM VM

New flavor available: g4.cores8.ram64.disk20 you can select this flavor in horizon UI. You can also switch the flavor of an existing instance once it's stopped going to the edit instance page.

Let us know if it works.

ssh -J gopavasanth@primary.bastion.wmflabs.org gopavasanth@wise.wise.eqiad1.wikimedia.cloud
gopavasanth@wise.wise.eqiad1.wikimedia.cloud: Permission denied (publickey).

@Volans, could you please help us here? Unable to SSH to our machine, After the instance resize.

Volans claimed this task.
Volans triaged this task as Medium priority.

Access problem was resolved. Resolving this task as the project is now working.