Skip to main content
Teams are the core organizational unit in Chamber. They represent teams, projects, or business units that consume GPU resources.

​
What is a Team?

A team is a named entity that:
  • Belongs to an organization
  • Can have parent and child teams (forming a hierarchy)
  • Receives capacity reservations from pools
  • Contains workloads
Think of teams as your org chart mapped to GPU resource allocation.

​
Hierarchy

Teams form a tree structure that mirrors your organization:

​
Why Hierarchies Matter

Capacity Inheritance

Child teams (aka Projects) can use parent capacity when their own is exhausted

Visibility

Managers see aggregate utilization for their entire subtree

Delegation

Team leads manage their subtree without org-wide access

Flexibility

Restructure teams without recreating reservations

​
Capacity and Workloads

​
Reservations

Each team can have reservations in one or more capacity pools:

​
Workloads

Workloads are associated with exactly one team via labels: 
metadata:
  labels:
    chamber.io/team: computer-vision
Workloads without a team label will be rejected by the Chamber scheduler.

​
Best Practices

Begin with a flat structure (one team per major team). Add hierarchy only when you need finer-grained capacity control.
Slugs appear in workload labels and CLI commands. Use short, descriptive slugs like cv-team instead of computer-vision-research-team-2024.
Structure teams to match how you want to see utilization reports. If you report by project, make projects teams.

Reservations

How capacity is allocated to teams

Workload Classes

Reserved vs elastic workloads