Epic: Two Workspace Classes on SaaS

[svenefftinge]

Summary

Provide users with the ability to select between two different workspace classes for all their workspaces. On SaaS, the options are:

• Standard (up to 4 cores, up to 8GB RAM, 30GB storage)
• XL Large (up to 8 cores, up to 16GB RAM, 50GB storage)

⚠️ Note that because of the storage size differences, a XL workspace can't be restarted as Standard, and neither can a Standard workspace be started from an XL prebuild.

Context

Different projects require different resources. To allow developers to fully leverage the power and scalability of the cloud, we want to allow for different workspace classes.

Internal Signal

Value

Users will have access to better performance, that supports heavier workloads.

Acceptance Criteria

• SaaS users that don't have a "legacy" monthly subscription must be able to choose between the two options (Standard and XL) in the Account Settings.
• SaaS users that have "legacy" monthly subscriptions should continue to use standard or XL according to the excludeFromMoreResources as they do today.
• SaaS users must be billed according to the workspace class they are using.
• Workspaces must not fail to start because the backup is larger than the storage available in the chosen class.
• Users should be able to determine what is the class of a given workspace, and what was the class used to run a prebuild

Measurement

• % of workspaces that were XL.

Growth Area

Expansion.

Persona(s)

Users that have heavier workloads.

Out of Scope

• Self-hosted use case.
• Having different workspace classes share the same node pool, and similar optimizations.
• Per project or per workspace class.

See #10805 to check what will follow.

Tasks

• Register workspace classes that are supported by the workspace cluster #10842
• Support pvc workspace classes #11357
• Customers should be able to select their preferred workspace class #10843
• Allow specification of workspace class in project settings #10963
• Make ws-daemon workspace class aware #10981
• Update settings page with the latest design #11358
• Dashboard source workspace class names dynamically from server #11583
• Configure workspace classes for SaaS
• Remove fixed resources feature #11839
• Ensure workspace gets appropriate workspace class if created from a prebuild #11972
• Show workspace class in admin view #12048

Front conversations

[ajhalili2006]

What about the storage for /workspace? Is it limited to 5 GB (like in Google Cloud Shell for /home/<your-gmail-username-over-here-probably>)?

[rohan-patra]

How would this affect users with unleashed/unlimited plans?

[rohan-patra]

What about the storage for /workspace? Is it limited to 5 GB (like in Google Cloud Shell for /home/<your-gmail-username-over-here-probably>)?

I believe they allow 30 gb to persist in that directory and the allowed space in a running workspace might be higher but will be deleted when the workspace stops.

[csweichel]

We should generalise a tad and move to "workspace classes"

[shaal]

@csweichel that last link is not accessible to the public