Enable Release Engineering test use case for Magnum (spin up a k8s cluster, deploy helm charts, do end to end testing, teardown). Magnum itself as a feature is blocked by T321220: Openstack Magnum network setup, however, this specific use case shouldn't be.
Description
Description
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | rook | T280792 Investigate Openstack Magnum | |||
| Declined | None | T324156 Explore Openstack Magnum release engineering use case |
Event Timeline
Comment Actions
I've been thinking on a plan:
- add the missing magnum bits to eqiad1 (like: images, coe templates, ssh keys, etc) to make it usable in a similar fashion to codfw1dev
- create a new project, a PoC tenant, something like magnum-poc that release engineering can use.
- enable magnum for this project, figure out quotas, create a bastion server and give release engineering folks access to the project
- create some docs on wikitech (perhaps https://wikitech.wikimedia.org/wiki/Portal:Cloud_VPS/Admin/notes/Magnum_POC_for_release_engineering) so folks in Release Engineering know how to operate and interact with magnum:
- since we don't have the horizon plugin installed, to spin up a new cluster they will need to use the API directly, either on cloudcontrols, using remote API access via auth token (didn't we just enable this), using terraform or whatever
- how to retrieve the kubeconfig, manage ssh keys, etc. There is potentially work here to figure out API endpoints ACL for users etc.
Comment Actions
That sounds fine to me. The Magnum API is currently firewalled but I don't mind opening it up as soon as there's a reason to do so.
Comment Actions
According to release engineering, no work is planned on this in the near future. Unassigning for now.
Comment Actions
I'm going to go a step further than @nskaggs and close. Please re-open should this project be revived.