Skip to main content
Version: FCP 25.11

Usage Guide

Overview​

tip
  1. You can register up to 1000 nodes in a single operation.
  2. Pay-as-you-go nodes and subscription nodes (referred to as cloud nodes in this document) are available only when Hybrid Cloud is enabled in FCP-Suite.

Manage all compute resources in the admin portal. Compute resources are categorized by billing type, node type, and power-on method. For definitions, see Glossary.

Permissions​

For details, see Permissions.

Host Management​

Host list​

Field descriptions:

  • Node ID: Globally unique ID.
  • Host Name: Hostname of the node.
  • Node Type: Base node / Static node / Dynamic node.
  • Configuration: Instance type, CPU cores, memory size, GPU count, system volume size.
  • Operating System: OS of the node.
  • IP Address: Private IP address.
  • Subnet Name: Subnet where the node resides.
  • Billing Type: Pay-as-you-go / Subscription / Subscription (prepaid). Some fields are displayed only for certain billing types, such as:
    • Instance type (not shown for subscription nodes)
    • Expiration time, expiration policy, and remaining days (shown only for subscription nodes; remaining days are highlighted when <= 7 days)
  • Days Remaining: Remaining days before expiration.
  • Host Group: Host group this node belongs to.
  • Attached Resource: Desktop(s) or cluster(s) using this node.
  • Image Name: Image used by the node.
  • Image Size: Image size.
  • Image Type: Base image (provided by Fastone) or custom image (built by customer based on a Fastone base image).
  • Usage Status: Usage state of the node.
  • Node Status: Health/runtime state of the node.
  • Created At: Creation time.
  • Updated At: Last modified time.
  • Released At: Release time.
  • Username: Creator of the node.

Note: If a billing indicator appears before the node ID, it means the node is still being billed even while powered off.

Operations: If an operation is not supported for a node, follow the UI prompts.

Supported operations for subscription nodes:

  • Test: Test a single node or multiple nodes (subscription nodes only).
  • Change password/key: Change password or SSH key for a single node (subscription nodes only).

Supported operations for cloud nodes (hybrid cloud enabled):

  • Convert to prepaid: Convert one or multiple nodes to subscription (prepaid).
  • Change expiration policy: Change the expiration policy for prepaid nodes (prepaid nodes only).
  • Manual renewal: Manually renew prepaid nodes (prepaid nodes only).
  • Power on/off: Power on/off one or multiple nodes (pay-as-you-go and prepaid only).
  • Expand: Expand the system disk of a single node.

Supported operations for all nodes:

  • Upgrade: Only static nodes support single/batch upgrades, whether in use or not. Upgrade is needed when the node component version is inconsistent with the core node component version. Upgrade is triggered manually in the UI.
  • Show unavailable nodes: Nodes in Error/Released states are hidden by default. Enable this to show them.
  • Export: Export all nodes based on selected columns and filters.
  • Configure sessions: Default is 99 sessions; supports single/batch session configuration.
  • Release: Release one or multiple nodes.
    • Subscription nodes can be released only when not in use.
    • Pay-as-you-go and prepaid nodes can be released only when not in use. For prepaid nodes, active orders are not refundable; only non-effective orders are refundable. Releasing a pay-as-you-go node stops billing immediately.

Create host​

You can create subscription nodes, pay-as-you-go nodes, and prepaid nodes. Nodes created from this page are static nodes.

Create subscription nodes​

Fields:

  • Host spec:
    • You can add a specific IP:port, for example 192.168.2.2:22.
    • You can also add an IP range, for example 192.168.1.[1-10]:22.
    • Enter one IP or range per line. Separate lines with newlines and press Enter to confirm.
  • Credentials: You can authenticate using a password or an SSH key.
    • Host username: Required. Default is root and can be modified. If using a non-root user, the user must be able to escalate to root without password (passwordless sudo).
  • Host password: Either password or key is required. Password is hidden by default and can be toggled visible.
  • Host key: Either password or key is required.

Validation for subscription nodes:

  • Pre-check:
    • IP duplication check. Duplicate IPs cannot be added.
  • Post-check:
    • Validate whether username/password is correct. If incorrect, the node cannot be added.
    • Validate whether required service components are installed. If missing, the node cannot be added.
    • Test all hosts. In the host list, hosts can be expanded and the platform retrieves hostname, vCPU, memory, OS, etc.

Create pay-as-you-go nodes​

Fields:

  • Host name prefix: Optional. Hostnames are generated as <prefix>-1, <prefix>-2, and so on.
  • Image: Determines whether to create a Linux or Windows instance.
  • Subnet: Subnet for the node.
  • System volume: System disk size. Must not be smaller than the selected image size.
  • Node count: Number of nodes to create. Default: 1.
  • Cost: Real-time estimated cost for the nodes based on instance type and count. This estimate excludes system volume and network traffic.

Create prepaid nodes​

Fields:

  • Host name prefix: Optional. Hostnames are generated as <prefix>-1, <prefix>-2, and so on.
  • Image: Determines whether to create a Linux or Windows instance.
  • Subnet: Subnet for the node.
  • System volume: System disk size. Must not be smaller than the selected image size.
  • Node count: Number of nodes to create. Default: 1.
  • Purchase duration:
    • Selecting 1 month or multiple months purchases monthly subscription.
    • Selecting 1 year purchases yearly subscription.
    • Monthly: if quota = 0, you cannot purchase monthly.
    • Yearly: if quota = 0, you cannot purchase yearly.
  • Cost: Real-time estimated cost based on instance type and count. This estimate excludes system volume and network traffic.
  • Notifications for prepaid nodes:
    • Purchase notification: After purchasing prepaid nodes (monthly/yearly), both the user and Fastone staff receive purchase email notifications.
    • Expiration notification: Email reminders are sent at 7 days, 3 days, and 1 day before expiration to both the user and Fastone staff.

Convert to prepaid​

Convert-to-prepaid converts pay-as-you-go nodes to prepaid (monthly/yearly subscription).

Supported nodes: In static nodes, pay-as-you-go nodes can be converted to prepaid. In dynamic nodes, nodes with manual power-on can be converted to pay-as-you-go.

Fields:

  • Duration: Monthly or yearly. Monthly can be 1 month or multiple months; yearly can only be 1 year.
  • Total cost: The cost for this conversion.
  • Node ID: Select the node ID to convert.
  • Instance type: Instance type of the node being converted.
  • Host name: Hostname.
  • New expiration time: Changes based on selected duration.
  • Cost booked this month: After submission, the displayed amount is booked into the billing for the current month.

Manual renewal​

Manual renewal is supported only for nodes that are already prepaid. Renewal duration options are the same as purchase: 1 month, multiple months, or 1 year.

Fields:

  • Duration: Monthly or yearly. Monthly can be 1 month or multiple months; yearly can only be 1 year.
  • Total cost: Sum of renewal costs for selected nodes in a batch.
  • Node ID: Select the node ID(s) to renew.
  • Instance type: Instance type of the prepaid node.
  • Host name: Hostname.
  • Expiration time: Current expiration time before renewal.
  • New expiration time: Expiration time after renewal.
  • Cost booked this month: After submission, the displayed amount is booked into the billing for the current month.

Change expiration policy​

Note: For base nodes, you cannot change the expiration policy to Auto release on expiration. If a node is used by a cluster as a head node, its expiration policy cannot be changed to auto release either.

Expiration policies:

  • Convert to pay-as-you-go on expiration
  • Auto release on expiration
  • Auto renew on expiration
    • If the last order duration is 1 to 11 months, auto renews for 1 month.
    • If the last order duration is 1 year, auto renews for 1 year.

Static node upgrade​

Fastone platform versions map one-to-one to the base component version on static nodes. After a platform upgrade, an older base component version might become incompatible with the new platform version.

After upgrading the platform, you can upgrade old-version static nodes from Host Management.

Static nodes can be upgraded when they are Not Used or Running and their components are an older version.

When a static node is in Upgrading state, it cannot be selected when creating a cluster, creating a host, or creating a desktop.

Pricing​

For product pricing, see: https://fastonetech.com/fcc-e/pricing