Before starting work, we want to have a high level understanding of what needs to happen, identify potential problematic points and dependencies on other teams (if they exist).
AC
- List of phab task for the main pieces of the migration
- License inquiry on Elasticsearch 8
- Brief on discussion with LTR plugin maintainers
- SPIKE on vector embeddings of OpenSearch
- Community Resources communication plan, including for as many parts of the Wikimedia software ecosystem as possible (including addition to Asana calendar(s))
- Cloud Elastic - check logs for usage
- Cloud Elastic - communicate timing
- Cloud Elastic - migrate
- Cloud Elastic - add vector based search support (may require standalone instances)
- Dev developer environments (MediaWiki-Docker with Cindy, maybe another environment such as Catalyst if it's stable; probably not MW QuickStart based on discussions)
- Product Analytics consultation
- Search metrics
- Intervention analysis of upgrades along the way to verify no issues (e.g., HTTP headers that make their way into refined tables)
- Cindy the browser bot built for replacement
- Review, report of any analysis chain changes
- Analysis chain change fixes
- Confirm Toolhub compatibility
- Review breaking changes
- Migrate plugins
- Migrate Relforge
- Deprecation logging
- Deprecation and breaking changes fixes
- Migration guide (or tooling, or both; TBD) for third party CirrusSearch installations
- Update Extension:Translate
- apifeatureusage
- Translatewiki.net - align schedule for TWN (probably with Federico)
- deployment-prep / beta
- Alternate cluster - migrate
- Main cluster - migrate