Skip to main content
Resources is Siverse’s entry point for managing compute and storage. Development environments, training jobs, and inference services consume the instance and storage resources managed here during runtime. Before starting a task, confirm that sufficient compute capacity, storage volumes, resource pools, and quotas are available. If resources are insufficient, the task may fail to be created, be queued, or be rejected during quota validation.

​
Feature Entry

After you access Resources, the commonly used entry points are as follows: When comparing resource, quota, or usage data, use the same filter criteria, such as Region, Cluster, Resource Type, Resource Pool, and time range.

​
Resource Objects

​
Resource Pool Type

Instance resources are organized by resource pool. Different resource pools are suitable for different isolation, cost, and management requirements.

​
Resource Quotas and Scheduling Boundaries

  • Resources are organized by region and cluster. Before creating a task, ensure that the resources, storage volumes, images, datasets, and models are in regions and clusters that you can access.
  • Instance resources and storage resources are purchased and consumed as quotas. After purchasing instance resources, ensure that the quota has been added to the available resource pool. After purchasing storage resources, you must also create Volumes within the storage quota.
  • A resource pool can be configured with user-level policies, such as authorized users, individual quotas, priorities, and resource guarantees. It can also restrict the workload types that can be submitted. If the current user or task type is not allowed, the submission will be rejected by quota validation.
  • Dedicated resource pools require whole-machine validation. GPU Instances must be allocated in increments of a full 8-GPU machine, while CPU Instances must be allocated in increments of a full 120-CU machine.
  • After an order expires, the associated quotas become invalid. Before expiration, confirm whether renewal is required.

​
Resource Usage Dir

Resources are typically prepared and used as follows:
  1. Purchase instance resources or storage resources to generate resource orders. When purchasing instance resources, if the target dedicated or exclusive resource pool already exists, you can directly Specify the quota destination. If no destination is specified, the quota is allocated to the shared resource pool.
  2. Based on usage scope and isolation requirements, create or adjust dedicated and exclusive resource pools, and adjust the resource pool allocation of existing instance quotas as needed.
  3. Create or adjust storage volumes and authorize the users who need to use them.
  4. In Develop, Training, or Inference, select the resource pool, instance specification, and storage volume.
  5. In Resource Dashboard, view resource usage, scheduling rate, and user usage; in Task Dashboard, view task resource consumption.
  6. Before an order expires, renew it in Order to prevent quota expiration from affecting task execution.