Entitlements for bwCloud-SCOPE

⚠️ Please Note: This entitlement model is deprecated and will be outdated with the termination of the bwCloud-OS (Gen2) setup.

Entitlements in bwCloud-OS define who can access the platform, how many resources they may use, and under what conditions. They are issued and managed by the user’s home institution and play a central role in how the platform is used and funded.

Current Entitlement Types

There are currently two types of entitlements:

• bwCloud-Basic Aimed at students and beginner users, offering limited resources. Typical use cases include:
  • Student coursework
  • Short-lived or experimental servers
  • Hosting simple software repositories
• bwCloud-Extended Intended for advanced or long-term users who require more resources. This entitlement is meant for:
  • Research
  • Teaching infrastructure
  • Operational workloads

📌 A user account can have both entitlements — in that case, bwCloud-Extended takes precedence.

Resource Usage and Flavor Access

Entitlements determine which flavor types (resource profiles) a user can launch:

• bwCloud-Basic
  • Only allows launching nano or tiny instances.
• bwCloud-Extended
  • Grants access to all available flavors.
  • Users receive significantly higher quotas.

VM Lifespan and Cleanup Policy

To ensure fair resource distribution and system availability, different rules apply depending on the assigned entitlement:

• bwCloud-Basic
  • VMs may be regularly deleted by the bwCloud team to:
    • Clean up unused instances
    • Free capacity for new users
  • Expect VMs to be potentially removed without notice.
• bwCloud-Extended
  • No such restrictions apply.
  • VMs are persistent and remain active until the user deletes them.