Page MenuHomePhabricator

Update CX to use the new Restbase provided public API instead of CXServer
Open, HighPublic

Description

Once T162576 and https://github.com/wikimedia/restbase/pull/796 are done (and other related patches too), update CX config to use new Restbase provided public API instead of CXServer.

Timeline:

  • Add configuration patch for CX and update documentation.
  • Update CX Labs instances.
  • Deploy in Beta.
  • Deploy in Production.
  • Deprecate: cxserver.wikimedia.org URL

Issues:

  • Deploy: CXServer's /list/{tool}{/from}{/to} should work when only {from} is provided

Event Timeline

Restricted Application added a subscriber: Aklapper. · View Herald TranscriptApr 18 2017, 1:33 PM
Nikerabbit updated the task description. (Show Details)Apr 18 2017, 3:55 PM
Amire80 triaged this task as Low priority.Apr 19 2017, 6:46 AM

Translate also need to update while doing this.

Translate also need to update while doing this.

It's not enabled by default in Translate, but the configs for translatewiki.net and Wikimedia need to be updated. And someone should check beforehand that the new URL scheme actually works with the current Translate code.

KartikMistry raised the priority of this task from Low to Medium.May 31 2017, 12:27 PM

Any update on this task? Once we haven completed the cxserver migration, we will finally be able to complete T133001 as well, which Traffic has been pushing for for a while.

What is the new non-project specific location of cxserver's MT api (for Translate) when cxserver.wikimedia.org goes away? Will the internal cxserver location stay, or is that going to be removed too?

What is the new non-project specific location of cxserver's MT api (for Translate) when cxserver.wikimedia.org goes away?

Most of the API is hosted on the [global wikimedia.org domain](https://wikimedia.org/api/rest_v1/#/Transform); the exception being the GET /page/segments/ end point which is part of project-specific domain APIs.

Will the internal cxserver location stay, or is that going to be removed too?

All access to CX APIs should from now on go though the public REST API interface without distinction between internal/external requests.

https://phabricator.wikimedia.org/T173038 is currently blocking deploying of /translate end point.

KartikMistry raised the priority of this task from Medium to High.Apr 23 2018, 12:15 PM

I'm making list of impact of this change and update here soon. It mostly few instances, Beta and then Production. Also, we need to update documentation and various places (Extension and setup pages) along with it.

KartikMistry updated the task description. (Show Details)May 3 2018, 3:51 AM

Change 431526 had a related patch set uploaded (by KartikMistry; owner: KartikMistry):
[operations/mediawiki-config@master] WIP: Beta: Use Restbase provided public API instead of CXServer

https://gerrit.wikimedia.org/r/431526

Added: https://github.com/wikimedia/restbase/pull/993 to add missing end point /list/{tool}/{from}/{to}

Mentioned in SAL (#wikimedia-operations) [2018-05-14T14:15:54Z] <mobrovac@tin> Started deploy [restbase/deploy@75dc661]: API: Add /transform/list/tool/{tool}{/from}{/to} - T163203

Mentioned in SAL (#wikimedia-operations) [2018-05-14T14:39:29Z] <mobrovac@tin> Finished deploy [restbase/deploy@75dc661]: API: Add /transform/list/tool/{tool}{/from}{/to} - T163203 (duration: 23m 35s)

KartikMistry updated the task description. (Show Details)May 21 2018, 2:47 AM
KartikMistry updated the task description. (Show Details)Jun 5 2018, 7:19 AM
KartikMistry updated the task description. (Show Details)Jun 6 2018, 4:51 AM
Restricted Application edited projects, added ContentTranslation; removed CX-deployments. · View Herald TranscriptJun 13 2018, 6:32 PM

Change 431526 abandoned by KartikMistry:
WIP: Beta: Use Restbase provided public API instead of CXServer

Reason:
Working on better patch.

https://gerrit.wikimedia.org/r/431526

Aklapper removed KartikMistry as the assignee of this task.Jun 19 2020, 4:17 PM

This task has been assigned to the same task owner for more than two years. Resetting task assignee due to inactivity, to decrease task cookie-licking and to get a slightly more realistic overview of plans. Please feel free to assign this task to yourself again if you still realistically work or plan to work on this task - it would be welcome!

For tips how to manage individual work in Phabricator (noisy notifications, lists of task, etc.), see https://phabricator.wikimedia.org/T228575#6237124 for available options.
(For the records, two emails were sent to assignee addresses before resetting assignees. See T228575 for more info and for potential feedback. Thanks!)