Setup Profile

Viewing Settings

You can use the Profile List CLI command to view your current profile, including bucket and pool defaults.

$ osmo profile list
user:
  name: John Doe
  email: jdoe@nvidia.com
notifications:
  email: False
  slack: True
bucket:
  default: my-bucket
pool:
  default: my-pool
  accessible:
  - my-pool
  - team-pool
roles:
- osmo-user
- osmo-ml-team

Token Expiration

When using an access token, osmo profile list shows its expiration date, never for a Secret-backed credential with no scheduled expiration, or unknown when expiration metadata is unavailable (including older servers). A credential shown as never can still be rotated or removed. The short-lived JWT issued at login has its own expiration and is refreshed independently. The default temporary admin bootstrap token has a scheduled expiration; its issued JWT expiration is capped at the credential deadline. Gateway validation allows an additional 60 seconds of clock skew for already-issued sessions.

API clients can request GET /api/profile/settings?include_token_expiration=true to receive token.expiration_status as scheduled, never, or unknown. expires_at remains a timestamp or null; clients that omit this option retain the existing response shape.

Default Pool

What is a Pool?

A Pool is a shared group of managed compute resources (machines) used to run workflows.

Key benefits:

• 👥 Team sharing - access-controlled resources shared across your organization

• 🎯 Hardware targeting - platforms let you specify GPU types and configurations

• ⚖️ Smart scheduling - maximize resource usage with intelligent workload placement

See Pools for complete details.

To choose a default pool, use the Profile List CLI command to view available pools and Resource List CLI command to see what resources are in each pool.

Set the default pool using the profile CLI.

$ osmo profile set pool my_pool