Page MenuHomePhabricator

[EPIC] Deploy the mediawiki-services-chromium-render service (Proton)
Closed, ResolvedPublic

Description

This task tracks the deployment of the mediawiki-services-chromium-render service (Proton, herein). Proton's development and deployment is storied but did, at one time, support the FY 2017-18 Q2 goal T181079: [GOAL] Provide an expanded reading experience by improving the ways that users can download articles of interest for later consumption.

Current status

RESTBase is mirroring 100% of all production traffic to Proton and discarding its responses. Services will switchover to Proton and start decommissioning mediawiki-services-electron-render (Electron, herein) when Proton has been handed over to Readers Infrastructure.

Release timeline

  • 18th September 2018: RESTBase mirrors 25% of all production traffic to Proton (T186748#4595101)
  • 18th October 2018: RESTBase mirrors 100% of all production traffic to Proton (T186748#4677976)
  • Handover Proton to Readers Infrastructure (T210652)
  • TBD: RESTBase sends 100% of all production traffic to Proton and serves its responses (T210651)

Past updates

Update 2017/11/21

At the time of writing (Tuesday, 21st November 2017), the mediawiki-services-chromium-render service is currently under active development and soon to have it's initial round of performance testing on non-production hardware.

After lengthy investigation, it was determined that the service must be run under Debian Stretch. This is because the service uses the puppeteer library, which requires an up-to-date version of the Chromium binary to be available and such a binary wasn't immediately available for Debian Jessie. Details of the investigation can be found:

Per T178189#3740805, we (Readers Web) intend to deploy this new PDF rendering service alongside the current service in order to evaluate its performance with production traffic. Once we're all happy, then we can switch out the services and decommission the superseded service.

Related Objects

StatusSubtypeAssignedTask
Resolvedovasileva
ResolvedNone
ResolvedBawolff
Resolvedphuedx
Resolvedphuedx
Resolvedphuedx
Resolvedphuedx
Resolvedphuedx
Resolvedmobrovac
Resolvedmobrovac
Resolvedmobrovac
Resolvedmobrovac
Resolvedakosiaris
Resolvedmobrovac
Resolvedfgiunchedi
Resolved pmiazga
Resolvedfaidon
Resolvedmobrovac
Resolvedmobrovac
Resolved pmiazga
ResolvedJdrewniak
Resolvedmobrovac
Resolvedphuedx
Resolved pmiazga
Resolved pmiazga
ResolvedNiedzielski
Resolvedphuedx
ResolvedJdrewniak
Resolvedphuedx
Resolvedphuedx
Resolvedphuedx
Resolvedphuedx
DeclinedNone
Resolvedbmansurov
Resolvedmobrovac
Resolvedovasileva
InvalidNone
ResolvedJdlrobson
Resolvedphuedx
Resolvedphuedx
Resolvedholger.knust
ResolvedTgr
Resolvedjijiki
ResolvedMSantos
Resolvedmobrovac
Resolvedovasileva
Resolvedphuedx
Declined pmiazga
ResolvedDzahn
Resolved pmiazga
Duplicateholger.knust
ResolvedMSantos
ResolvedTgr
ResolvedJohan

Event Timeline

There are a very large number of changes, so older changes are hidden. Show Older Changes

@mobrovac: Just a heads up that Web have started picking up the Puppet/Scap3-ization tasks for the service and I'll be looking to spend some time with Services to figure out how we get it deployed under Debian Stretch.

ovasileva added a subscriber: ovasileva.

Adding to kanban board for goals tracking

Jdlrobson changed the task status from Stalled to Open.Aug 10 2018, 6:29 PM
Jdlrobson changed the status of subtask T181118: [EPIC] Build a Chromium-based PDF renderer service from Stalled to Open.
Jdlrobson added a subscriber: Jdlrobson.

Due to recent activity.

Niedzielski renamed this task from [EPIC] Deploy the mediawiki-services-chromium-render service to [EPIC] Deploy the mediawiki-services-chromium-render service (Proton).Nov 28 2018, 3:59 PM
MSantos claimed this task.
MSantos updated the task description. (Show Details)
MSantos added a subscriber: MSantos.

Closing this EPIC since there are no children tasks and service are stable for a long time now.