| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | SDunlap | T346341 Toolforge Integration Exploration | |||
| Declined | None | T346342 EXPLORE how can toolforge tools be created with an API | |||
| Declined | None | T346343 EXPLORE how we can query a subset of tools (e.g. by name or metadata) for a user with a toolforge API | |||
| Declined | None | T346344 EXPLORE how the kubernetes quota limits for tools might impact catalyst created test environments | |||
| Declined | None | T346346 EXPLORE how Catalyst could run k8s/helm commands for a user's environment/tool | |||
| Declined | None | T346658 EXPLORE how Toolforge tools can be destroyed with an API | |||
| Declined | None | T346691 EXPLORE how "teams" might work between Catalyst and Toolforge |
Event Timeline
Comment Actions
After talking with the the Cloud Services team, it looks like using Toolforge to prototype is not a good fit because the Cloud Services team does not see Toolforge as a k8s as a service offering and some of the abstractions do not overlap.
We will likely use Magnum in a Cloud VPS project instead.