Skip to main content
Version: FCP 25.11

Billing

tip
  1. This feature is available only in FCP-Suite and only after Hybrid Cloud is enabled. It is disabled by default.
  2. The Fsched cluster HA feature itself is not charged regardless of whether Hybrid Cloud is enabled (the feature is free, but underlying resources are billed normally).

Overview​

  • What it does: The Billing module provides cost query, analysis, and alerting capabilities so you can understand resource consumption on the FCP platform.
  • Important notes:
    1. Data shown in the platform is pre-billing data based on resource usage, for day-to-day tracking and estimation.
    2. At the beginning of each month, Fastone performs a final reconciliation based on last month's actual consumption and sends the official bill by email. The emailed bill is the official settlement basis.
    3. The platform's pre-billing data does not represent a specific settlement or payment model. Billing cycles, payment methods, and processes follow the commercial contract you signed with Fastone.
    4. Because architectures, service requirements, and commercial terms differ by customer, the final monthly bill composition follows commercial agreements.

View and analyze bills​

1. Billing overview​

  • Description: Shows cost trends for recent months in a bar chart.
  • Actions:
    • Filter: Use the User drop-down (top-left) and the Billing period selector (top-right) to view data for a specific user or time range.

2. Monthly detailed bill​

  • Description: View a detailed cost breakdown for a selected month.
  • Layout: Displayed below the billing overview.
  • Contents:
    • Amount due: Total cost for the month (tax inclusion depends on the UI display).
    • Cost breakdown:
      • Resource cost: Listed by resource type (compute, storage, file system, etc.).
      • Support cost: Listed separately if included in the contract.
  • Actions:
    • Select month: Choose the month to view in the top-right selector.
    • Export bill: Click Export bill (top-right) to export a PDF for the month.

Charge items explained​

1. Compute resources​

  • Billing types:
    • Pay-as-you-go: Calculated based on actual usage duration within the last hour.
    • Monthly/yearly: Commit to a duration. Cost is booked into the current billing period after purchase.
  • Rules for prepaid nodes:
    • Commitment:
      • Monthly: 1 to 11 months (if > 10 months, yearly is recommended).
      • Yearly: 1 year.
    • Manual renewal duration: Same options as commitment.
    • Lifecycle rules:
      • Within commitment: Cannot be released and cannot be converted to pay-as-you-go.
      • At expiration: Can be set to "convert to pay-as-you-go", "auto release", or "auto renew".
      • Spec change: Up/down sizing is not supported.
      • Renewal:
        • Auto renew: Renews monthly or yearly based on the last effective order.
        • Manual renewal: Supported.
      • Release: Manual release is supported, but fees for the current effective order are not refundable.

2. File systems​

Costs have two parts:

  • A. File system base fee
    • Billing types:
      • Pay-as-you-go: Based on usage duration within the last hour.
      • Monthly: Commit for 1 month; cost is booked into the current billing period.
    • Monthly rules:
      • Commitment and renewal: 1 month.
      • Lifecycle: Cannot be released or converted to pay-as-you-go within commitment; auto renews by default at expiration; spec changes are not supported.
  • B. File system storage fee
    • Billing: Pay-as-you-go.
    • Update cycle: Usage and cost are updated hourly (for reference only).

3. Storage​

Aggregates storage-related costs generated by all users.

  • Cloud disks:
    • Billing: Pay-as-you-go.
    • Update cycle: Hourly (for reference only).
  • Image/backup storage:
    • Billing: Pay-as-you-go.
    • Update cycle: Daily (for reference only).
  • Object storage:
    • Billing: Pay-as-you-go.
    • Update cycle: Daily (for reference only).

4. Traffic​

  • Scope: Outbound traffic costs generated when users download data via the DM client or Web pages.
  • Billing: Pay-as-you-go.
  • Update cycle: Daily (for reference only).

5. Fsched head node HA​

  • Charge condition: If a cluster has 2 or more running head nodes, HA mode is considered enabled and charging starts.
  • Billing: Pay-as-you-go.
  • Update cycle: Usage and cost are updated hourly.

Billing alerts​

1. Permissions​

  • Only super administrators can configure billing alerts. Administrators and regular users do not have permission.

2. Alert configuration​

  • Configurable items:
    • Billing amount thresholds: Up to 10 thresholds.
    • Notification frequency: Trigger-only, daily, or weekly.
    • Notification method: Email; up to 50 email addresses.
  • Edit effect: After modifying threshold/frequency/recipients, email alerts will be re-triggered.

3. Alert status indicators​

  • Not configured: Gray.
  • No alert: Blue (configured but threshold not reached).
  • Triggered: Red (threshold reached or exceeded).

4. Notifications​

  • In-app notifications:
    • Recipients: All administrators.
    • Triggers:
      1. Notifications pop up when thresholds change (about every 15 minutes).
      2. If a user clicks Do not remind again, the notification will not pop up again.
      3. After clearing browser cache, all in-app notifications (including those marked as "Do not remind again") will pop up again.
  • Email notifications: When spending reaches a configured threshold, alert emails are sent to the configured recipients.
  • Known limitation: Due to cost calculation delay, email alerts are for reference only.