Terraform provider reference / data sources / server_type_pricing

fiberax_server_type_pricing (Data Source)

Prices and limits of one server type.

Rates are per hour; the monthly figure is the same rate over 720 hours, and it is there for comparison, not to work out your bill.

Example Usage

# Prices and limits of a server type.
#
# Rates are hourly; the monthly figure is the same rate over 720 hours, meant for
# comparison rather than for working out a bill.
data "fiberax_server_type_pricing" "cluster" {
  server_type_id = data.fiberax_server_type.cluster.id
}

output "hourly_rates" {
  value = { for k, v in data.fiberax_server_type_pricing.cluster.metered : k => v.hourly }
}

output "slider_limits" { value = data.fiberax_server_type_pricing.cluster.limits }

Schema

Required

• server_type_id (Number) The server type to read prices for.

Read-Only

• gpu_models (Attributes List) Card models you can combine on this type. Filled on types where you pick the cards, empty everywhere else.

Take key and pass it as model inside the server's gpus. (see below for nested schema)

• gpu_packages (Attributes List) GPU packages this type sells. Filled on types sold as packages, empty everywhere else.

Take key and pass it as the server's gpu_package; the package defines the card, the cores, the memory and the system disk, so the size fields are refused with it. (see below for nested schema)

• limits (Attributes) Upper bounds for slider types. Null where the type is not sized by sliders. (see below for nested schema)
• metered (Attributes Map) Rate per billed item. Keys depend on the type: resource rates on slider types, plan rates on plan types. (see below for nested schema)
• plans (Attributes List) Ready-made plans. Empty on types that are not sold as plans.

Take the ID of the plan you want from here and pass it as the server's plan_id. (see below for nested schema)

• pricing_mode (String) How a server of this type is sized:

• sliders - you choose cores, memory_mb and disk_gb, all three; on a type with graphics cards you also pick the cards in gpus and, optionally, the storage class in disk_type;

• plans - you choose a ready-made plan by plan_id, and the slider fields are refused;

• fixed - a GPU package defines the whole machine: name it in gpu_package, and the size fields are refused.

Read the pricing of the type to see what it offers: plans, gpu_packages or gpu_models.

Nested Schema for gpu_models

Read-Only:

• key (String) Identifier of the model, for example l40s.
• memory_gb (Number) Memory on the card itself.
• name (String)
• price (Number) Price per month per card. Zero means the card is included in the price of the type.

Nested Schema for gpu_packages

Read-Only:

• backup_price (Number) Price per month for automatic backups of such a server - a flat figure per server, not per gigabyte.
• cores (Number)
• disk_gb (Number)
• gpu_count (Number) Cards in the package. One: the host and its card are not shared between servers.
• gpu_model (String) Card model in the package, for example L4.
• key (String) Identifier of the package, for example gpu-l4-24.
• memory_gb (Number)
• name (String)
• price (Number) Price per month.

Nested Schema for limits

Read-Only:

• cores (Number)
• disk_gb_ceph (Number) Disk limit on shared storage.
• disk_gb_local (Number) Disk limit on local storage.
• gpus (Number) Most graphics cards one server of this type may hold. Null on types where the client does not pick the cards.
• memory_gb (Number)

Nested Schema for metered

Read-Only:

• hourly (Number)
• monthly (Number)

Nested Schema for plans

Read-Only:

• cores (Number)
• disk_gb (Number)
• id (Number)
• memory_gb (Number)
• name (String)
• price (Number) Price per month.

Generated from the provider schema for version 0.3.0. How to install the provider: Terraform provider.