Core Platform Team/Initiatives/REST JobExecutor
Appearance
(Redirected from Core Platform Team/Initiative/REST JobExecutor)
This page is obsolete. It is being retained for archival purposes. It may document extensions or features that are obsolete and/or no longer supported. Do not rely on the information here being up-to-date. The Core Platform Team and its initiatives do not exist anymore. See MediaWiki Engineering Group instead since 2023. |
REST JobExecutor
|
Initiative Vision
This page is obsolete. It is being retained for archival purposes. It may document extensions or features that are obsolete and/or no longer supported. Do not rely on the information here being up-to-date. The Core Platform Team and its initiatives do not exist anymore. See MediaWiki Engineering Group instead since 2023. |
Vision:
| ||||
Stakeholder(s):
|
Problem:
|
Solution:
|
Aligned Goals:
|
Initiative Description
This page is obsolete. It is being retained for archival purposes. It may document extensions or features that are obsolete and/or no longer supported. Do not rely on the information here being up-to-date. The Core Platform Team and its initiatives do not exist anymore. See MediaWiki Engineering Group instead since 2023. |
- Summary
Replace calls to mediawiki-config/rpc hierarchy with a REST API call for job execution
- Significance and Motivation
Tech debt cleanup
- Outcomes
rpc endpoints removed from mediawiki-config
- Baseline Metrics
100% of job executions go via rpc
- Target Metrics
0% of job executions go via rpc
- Stakeholders
Platform Engineering Team
- Known Dependencies/Blockers
SRE support
Epics, User Stories, and Requirements
This page is obsolete. It is being retained for archival purposes. It may document extensions or features that are obsolete and/or no longer supported. Do not rely on the information here being up-to-date. The Core Platform Team and its initiatives do not exist anymore. See MediaWiki Engineering Group instead since 2023. |
- Epic: task T175146
Time and Resource Estimates
This page is obsolete. It is being retained for archival purposes. It may document extensions or features that are obsolete and/or no longer supported. Do not rely on the information here being up-to-date. The Core Platform Team and its initiatives do not exist anymore. See MediaWiki Engineering Group instead since 2023. |
- Estimated Start Date
None given
- Actual Start Date
None given
- Estimated Completion Date
None given
- Actual Completion Date
None given
- Resource Estimates
1 eng, 1 sre, 1 sprint
- Collaborators
SRE
Subpages
50% done
Poll
Team members are invited to voice support or opposition, and give their reasoning. Please use the polling templates, for example:
* {{support}} I like this example! ~~~~
* {{oppose}} This is not a great example example... ~~~~
- Strong support This work is vital for reducing complexity in advance of k8s migration work. A few attempts have been made at unifying this config and there are WIPs that we can leverage to make this happen more easily. --HNowlan (WMF) (talk) 13:32, 4 September 2020 (UTC)
- Support This doesn't only "just make sense", we also already started it. So we should go ahead and finish it. -- DKinzler (WMF) (talk) 14:35, 4 September 2020 (UTC)
- Support This would reduce tech debt and since ~50% of it is already done we should finish it. CAndrew (WMF) (talk) 14:51, 4 September 2020 (UTC)
- Support Its ~50% done and it would make MW on K8's easier AMooney (WMF) (talk), 9 September 2020
- Support If it will clear the path for moving k8s forward and its already half done i think it will be difficult to find a counter argument to this work :) NNikkhoui (WMF)
- Support Support for reasons above. WDoran (WMF)
- Support Important benefit for MW on k8s and should be completed NNzali (WMF)
- Support Supported for all the reasons already mentioned. BPirkle (WMF)
- Support Support for reasons above. CCicalese (WMF) (talk) 19:34, 10 September 2020 (UTC)