Content translation/Deployments/Deployment Plan/Archive1

CX Deployment Plan for Beta Feature July 2014Edit

Deployment date: July 1-15 2014

Project: Content Translation Framework

Initial Release: Beta Feature release July 2014

What is targeted for Beta Feature release July 2014

Minimum Viable Product (MVP) for v1.0:

Long-term project roadmap:

Language Pair to be supported for MVP: Spanish - Catalan

Release as: Beta Feature

Overall PlanEdit

We plan to have deploy the CX framework for only Spanish and Catalan language wikis to support article content translation for Spanish to Catalan where there are red links for parallel articles in Catalan.

System ArchitectureEdit


Caching ArchitectureEdit

The following diagram includes the caching requirements for the CX framework.

Components to be provisioned for productionEdit

CX server installation and configuration:

See Setup: for detailed information about component, installation and configuation and instructions.

  • Node.js
  • Apertium
  • Extension dependencies:
    • BetaFeatures
    • CLDR
    • EventLogging
  • Backend Services


  • External APIs called by CX
    • Wikidata
    • Parsoid API
  • Configuration Scripts

Upstart and Systemd scripts are at:

Provisioning PlanEdit

a. Storage Requirements To be determined from discussion with ops

b. Hardware Requirements To be determined from discussion with ops

c. Bandwidth Requirements To be determined from discussion with ops

d. Performance expectations

  • MT TPS (Transactions per second)
  • User responsiveness
  • MT Round trip
  • General guidelines

Monitoring and metricsEdit

  • EventLogging activity for CX
  • Number of users enabling the feature
  • Performance of S:CX, backend calls?
  • Check for node and varnish? Who to page?
  • Graph showing requests or timings for the WikiData API(s) we are calling
  • Graph showing requests or timings for the Parsoid API(s) we are calling

External Signoffs RequiredEdit

  • Faidon - Ops
  • Gabriel - Infrastructure architecture
  • Ori - Performance
  • Chris Steipp - Security
  • Greg G - Release engineering
  • Mark - Ops
  • Tim - Platform

LE Team responsibilitiesEdit

  • Kartik - Deployment, Engineer
  • Niklas - Engineer, Code Reviewer
  • Santhosh - Engineer, Code Reviewer
  • David - Engineer, Code Reviewer
  • Runa - Team Scrum-Ninja / testing and communications
  • Pau - Feature UX reviewer, designer
  • Amir - Feature signoff
  • Alolita - Engineering coordination, Eng Manager