Toolhub.wikimedia.org

toolhub.wikimedia.org is a catalog of tools used by the members of the Wikimedia movement. See the Toolhub project page on meta for additional details about the application's features.

Production deployment

Toolhub runs in the "eqiad" Kubernetes cluster. The service is current not active-active in the "codfw" cluster (T288685).

The helm chart and helmfile configuration for the service configure connectivity to its dependencies:

• "m5" MariaDB cluster
• search-chi-{codfw,eqiad} Elasticsearch clusters
• mcrouter managed access to "eqiad-servers" memcached pool
• url-downloader.{codfw,eqiad}.wikimedia.org outbound HTTP proxy
• text-lb.{codfw,eqiad}.wikimedia.org for MediaWiki API access without envoy proxy + custom Host headers

Monitoring

• Grafana dashboard of Prometheus metrics
• OpenSearch dashboard of log events

How to deploy

See also: Kubernetes/Deployments

1. Create a patch to update main_app.version in helmfile.d/services/toolhub/values.yaml to the desired tag of the wikimedia/wikimedia-toolhub container. (example)
2. CR+2 the helmfile.d patch in gerrit to start the merge process.
3. Ssh to the currently active deployment server (deployment.eqiad.wmnet).
4. cd /srv/deployment-charts/helmfile.d/services/toolhub
5. Verify that your changes from step 1 are checked out. The git clone is updated once a minute by a timer, so if your changes are not present yet double check that zuul has merged the change and then wait patiently for the update to be fetched.
6. Deploy the chart to the staging cluster: helmfile -e staging -i apply
7. Deploy the chart to the codfw cluster: helmfile -e codfw -i apply
8. Deploy the chart to the eqiad cluster: helmfile -e eqiad -i apply

If your deployment includes database or elasticsearch schema changes, you will need to apply them manually.

• If you happen to have root rights on the deployment server you can use kube_env admin eqiad to get credentials that will allow you to use kubectl exec -n toolhub -it <pod name> toolhub-main -- /bin/bash to attach to a running container.
• If you are not a root you will need to invent your own environment for performing these post-deploy tasks until T290357: Maintenance environment needed for running one-off commands is resolved. See T290357#7578866 for the script that bd808 uses to run a container on his laptop connected to the production database and elasticsearch instance via ssh tunnels.

Typical migration commands:

• DB_USER=toolhub_admin DB_PASSWORD=<toolhub_admin's password> poetry run ./manage.py showmigrations
• DB_USER=toolhub_admin DB_PASSWORD=<toolhub_admin's password> poetry run ./manage.py migrate
• poetry run ./manage.py search_index --rebuild

Testing deployment

https://toolhub-demo.wmcloud.org in the Toolhub Cloud VPS project hosts a testing deployment that is used for beta testing and demonstrations. It is deployed using docker-compose. See contrib/demo-server/README.md in the project's git repo for more information.

Updating the demo build

$ ssh toolhub-demo01.toolhub.eqiad1.wikimedia.cloud
$ cd /srv/toolhub/demo/
$ make pull restart tail
  watch things happen until the search indices are rebuilt
  ^c
$ make web-shell
$ poetry run ./manage.py crawl --quiet
$ exit
$ exit

Local development

Local development is done with docker-compose. See docs/CONTRIBUTING.rst in the project's git repo for more information.

Visualizations related to Tools and Account creation

• 

  Current understanding of how different parts, systems, and audiences related to one another for the upcoming tools catalog.

• 

  The workflow for creating a new tool on Cloud VPS, with three different entry points. This diagram assumes that the user does not already have an LDAP account.

• 

  The workflow for creating a new tool on Cloud VPS, with three different entry points. This diagram assumes that the user already has an account from using Toolforge and so they don't need to go through the registration process all over again.

• 

  The workflow for creating a tool on Toolforge, including four different entry points.