Content translation/Deployments/How-to

From MediaWiki.org
Jump to navigation Jump to search

This document describes deployment procedure for ContentTranslation, cxserver and Apertium.

ContentTranslation[edit]

Content Translation is updated via regular MediaWiki train. In case of manual update needed, follow the steps below.

  1. Update desired branches to desired commit/update using delete and create branches at Gerrit interface, https://gerrit.wikimedia.org/r/#/admin/projects/mediawiki/extensions/ContentTranslation,branches In case of emergency, note down old hash.
  2. Read and follow: https://wikitech.wikimedia.org/wiki/How_to_deploy_code#Updating_the_submodule Make sure you've clean copy of MediaWiki/core for this.
  3. You're ready for actual deployment.

cxserver[edit]

Testing[edit]

Note image tag version from Gerrit patchset to be deploy. For eg: https://gerrit.wikimedia.org/r/#/c/mediawiki/services/cxserver/+/502964/ has 2019-04-11-112002-production tag.

Run it: docker run -p 4000:8080 docker-registry.wikimedia.org/wikimedia/mediawiki-services-cxserver:2019-04-11-112002-production --it --entrypoint /bin/bash -c config.dev.yaml

Where, config.dev.yaml is local cxserver config file.

Endpoints can be tested at: http://localhost:4000/v2 etc

Deployment[edit]

ssh deploy1001
cd /srv/scap-helm/cxserver/

Edit: cxserver-*-values.yaml files with new version or configuration you want to change. In most cases we only need to update TAG.

Upgrade[edit]

CLUSTER=codfw scap-helm cxserver upgrade -f cxserver-codfw-values.yaml production stable/cxserver
CLUSTER=eqiad scap-helm cxserver upgrade -f cxserver-eqiad-values.yaml production stable/cxserver
CLUSTER=staging scap-helm cxserver upgrade -f cxserver-staging-values.yaml staging stable/cxserver

Check status for all of three with status command.

Log to SAL[edit]

This is automatically done with each deployment, but if needed to add any specific task, Log the update at #wikimedia-operations

Example:

!log Updated cxserver to <REV> (T123456, T123457,..)

Status[edit]

Example:

CLUSTER=codfw scap-helm cxserver status production

History[edit]

CLUSTER=codfw scap-helm cxserver history

Rollback[edit]

To rollback to particular revision:

CLUSTER=codfw scap-helm cxserver rollback production <REV>

See also[edit]

Apertium[edit]

Apertium deployment is done via updating apertium packages through Gerrit change and puppet.

Troubleshooting[edit]

  1. Check if package list are up-to-date in Puppet.
  2. Make sure to ask to restart 'apertium-apy' on scb1001 and scb1002 to any Ops member after adding new languages support for Apertium MT.
  3. Check logs at: /srv/logs/apertium/

See also[edit]