Skip to main content
Version: FCP 25.11

Quota Center

tip

Available only when Hybrid Cloud is enabled in FCP-Suite.

Quota management includes platform quotas and user quotas. Resources started on the platform are constrained by both.

  • Platform quota: Limits the maximum resources the platform can use. To change platform quotas, contact Fastone sales.

  • User quota: Configured by platform administrators. You can define user quota policies for users on the platform.

  • Relationship: Platform quotas and user quotas are configured independently. During actual usage, both apply and the effective limit is the minimum of the two.

How quota limits are evaluated

  • Platform and user quotas: Resources can be started only if both are satisfied. When either quota reaches its limit first, the corresponding quota error is reported.
  • When creating nodes with multiple instance types selected: the platform evaluates quota using the instance type with the largest vCPU among the selected types.
  • Autoscaling: quota limits are not validated at form submission time. Example: pay-as-you-go node quota limit is 20, but you create a cluster with autoscaling min=30 and max=99. The cluster can be created and begins creating nodes; when it reaches the 21st node, it fails with a quota limit error shown in cluster status.
  • Editing nodes: quota limits are not validated at form submission time. If the new instance type hits a quota limit, the cluster status shows a quota limit error.
  • Quota limit errors are shown in cluster status, but note that newer cluster errors may overwrite this message.

Platform quota​

Limits the maximum resources the platform can use (note this is not simply the number of running machines).

  • Default quotas by region

    If the quota below is insufficient, contact Fastone sales to increase it.

    RegionAliasQuota
    North Region 1north1Compute (PAYG): 500 instances / 10000 vCPU
    Compute (Monthly): 0 instances / 0 vCPU
    Compute (Yearly): 20 instances / 320 vCPU
    File system (Base, monthly): 5
    File system (Performance, monthly): 1
    Cloud disk (PAYG): 100.00 TiB
    APAC Region 1ap1Same as above
    APAC Region 4ap4Same as above
    APAC Region 5ap5Same as above
    Europe Region 2eu2Same as above
    Europe Region 3eu3Same as above
    US East Region 1us-east1Same as above
    US West Region 1us-west1Same as above
    US West Region 2us-west2Same as above
    Canada Region 1can1Same as above
    Europe Region 4eu4Compute (PAYG): 500 instances / 10000 vCPU
    Compute (Monthly): 20 instances / 320 vCPU
    Compute (Yearly): 20 instances / 320 vCPU
    File system (Base, monthly): 5
    File system (Performance, monthly): 1
    Cloud disk (PAYG): 100.00 TiB
    North Region 2north2Same as above
    North Region 5north5Same as above
    South Region 1south1Same as above
    East Region 2east1Same as above

  • Platform quota limits

    • Compute resources:

      • Monthly: limited by monthly instance count, vCPU, and cloud disk quotas.

      • Yearly: limited by yearly instance count, vCPU, and cloud disk quotas.

      • Pay-as-you-go: limited by pay-as-you-go instance count, vCPU, and cloud disk quotas.

    • File systems:

      • Create Base edition file systems: limited by Base monthly file system count and cloud disk quotas.
      • Create Performance edition file systems: limited by Performance monthly file system count and cloud disk quotas.
      • File system expansion: limited by cloud disk quota.

User quota​

User quotas let you define per-user quota policies and set maximum allowable vCPU and GPU usage to prevent resource waste due to mistakes.

  • User quota notes

    • Disabled by default; administrators can enable and configure it.
    • Applies to: regular users and administrators.
    • Scope: all CPU/GPU-related resources except file systems, including autoscaling and pay-as-you-go, and creating clusters/tasks/desktops with prepaid resources (only admins can create prepaid instances).
    • Impact: does not affect running machines. Quota is validated only when creating new machines.
    • Deduction logic: same as platform quota logic (see "How quota limits are evaluated" above).

  • Enable user quotas

    • Turn on the feature switch. After enabling, users without an associated policy default to quota 0 (cannot start new machines).
    • Create a user quota policy and associate users:
      • For each quota limit, you can set unlimited or a specific limit:
        • Total vCPU quota per user
        • Total GPU quota per user

  • View quota policy details

    • After creating a policy, click the policy name to open the details page.

    • In the policy details, you can view usage for associated users.

      • When a user's available quota is <= 0, usage is highlighted in red.

Note:

If a user exceeds a quota policy: the user may have started resources before being bound to the policy. In this case, available quota can become < 0. Existing machines are not affected, but the user cannot start new resources.

  • Edit/delete user quota policies

    • In the user quota policy list, you can edit or delete policies.
    • Toggling the global user quota switch does not change policy configuration; it only controls whether the feature takes effect.