Skip to main content
Version: FCP 25.11

Cluster List

Field descriptions​

  • ID: Auto-generated globally unique ID.
  • Name: Cluster name.
  • Status: Cluster status.
  • Created at: Cluster creation time.
  • Updated at: Last change time.
  • Username: Cluster creator.

Note: If a billing indicator appears before the cluster ID, it means the cluster contains machines that are still billed while powered off.

Cluster operations​

  • Release (single/batch): Two behaviors:
    • Release: Releases all dynamic nodes in the cluster by default, including their system volumes. Released dynamic nodes stop billing and cannot be recovered. You can optionally release static pay-as-you-go nodes.
    • Remove: Removes all static nodes from the cluster. The cluster clears node configuration. Removed nodes can be configured into a new cluster later.
  • Power on (single/batch): Powers on all nodes in the cluster.
  • Power off (single/batch): Powers off all nodes in the cluster. Nodes that are billed while powered off continue billing; nodes that are not billed while powered off stop billing. System volumes continue to be billed.
  • Delete (single/batch): Deletes the cluster record. A cluster can be deleted only when it is in Released or Error status.
  • Scheduled power on/off
    • Configure schedule
      • When powering off, choose immediate power-off or scheduled power-off; set the scheduled time.
      • When powering on, optionally set a shutdown time (default: not set).
    • Cancel schedule: can be canceled in the cluster details.
  • View historical error messages: Cluster error messages are shown in status. New errors may overwrite previous messages. This feature allows you to view historical error messages. Fields:
    • Time: Time when the error was triggered. If the same error repeats, the count increases and time updates to the latest.
    • Object: Target object of the error (cluster/node ID/file system/desktop).
    • Count: Number of occurrences for the same error.
    • Reason: Detailed error information.
  • Remote control: Supports connecting/disconnecting via SSH and VNC. If multiple login nodes exist, you can choose a specific login node to create a connection.

Example (SSH): Click the SSH icon and the browser opens a new window to connect to the cluster. The first connection typically needs 1 to 2 seconds to start the session; after it starts, the SSH icon changes from gray to blue. For later connections, hover over SSH to see Connect and Disconnect. Click Connect to open a new window; click Disconnect to disconnect and the icon becomes gray. VNC works similarly.

Note: Remote control is shown when the cluster has login nodes. If there are no login nodes, you can use compute nodes for remote control.