As per https://www.mediawiki.org/wiki/Content_translation/Setup#Backend_Services, Varnish will help to make Content Translation fast using caching mechanism. Varnish for cxserver is not yet configure and it would be nice to have for Production. We need to configure Varnish on Beta, so that exercise for Production will be easy.
Description
Description
Details
Details
| Subject | Repo | Branch | Lines +/- | |
|---|---|---|---|---|
| Reuse parsoid varnish for cxserver | operations/puppet | production | +31 -5 | |
| Introduce cxserver.eqiad.wikimedia.org | operations/dns | master | +2 -0 |
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | Arrbee | T76185 Preparation for CX Deployment in production | |||
| Resolved | KartikMistry | T76187 Groundwork for ContentTranslation in Production | |||
| Resolved | akosiaris | T76200 Setup Varnish on Beta (and Production) for cxserver |
Event Timeline
Comment Actions
Change 181613 had a related patch set uploaded (by Alexandros Kosiaris):
WIP: Reuse parsoid varnish for cxserver in beta
Comment Actions
Change 183888 had a related patch set uploaded (by Alexandros Kosiaris):
Introduce cxserver.eqiad.wikimedia.org
Comment Actions
So, a temporary solution while we discuss and setup the "services" varnish cluster has been implemented via the parsoid varnish cluster. Requests with to the "cxserver.eqiad.wikimedia.org" hostname and with the "cxserver.eqiad.wikimedia.org" Host: HTTP header will be routed to the cxserver backends via the varnish cluster. For now, in the interest of not polluting the parsoid varnish caches, no caching is done at the varnish level. This is mean to change when we move the the dedicated "services" varnish infrastructure