Resource Pricing Model¶
Overview¶
Arrhenius PCD uses a usage-based pricing model for compute resources. The cost of resources is calculated based on the allocated resources and the time they are available.
The pricing model applies to:
- Virtual Machines (VMs) running on the OpenStack cloud platform.
- Kubernetes-as-a-Service resources (planned service, not currently available).
The cost is calculated based on three main resource components:
- CPU cores (core-hours)
- Memory (RAM) (GB-hours)
- Storage (GB-hours)
The total cost is calculated as:
Total Cost =
(CPU cores × CPU core-hour price × Running hours)
+ (RAM GB × RAM GB-hour price × Running hours)
+ (Storage GB × Storage GB-hour price × Running hours)
Resource Pricing¶
The current resource prices are:
| Resource | Unit | Price |
|---|---|---|
| CPU | Core-hour | 0.058 |
| RAM | GB-hour | 0.0139 |
| Storage | GB-hour | 0.0065 |
Virtual Machine Pricing Example¶
The following example shows the estimated cost of a Virtual Machine with the following configuration:
| Resource | Amount |
|---|---|
| CPU cores | 8 cores |
| RAM | 8 GB |
| Storage | 100 GB |
Hourly Cost Calculation¶
| Resource | Calculation | Cost per hour |
|---|---|---|
| CPU | 8 cores × 0.058 | 0.464 |
| RAM | 8 GB × 0.0139 | 0.1112 |
| Storage | 100 GB × 0.0065 | 0.650 |
| Total VM cost | 1.2252 / hour |
Estimated VM Running Costs¶
The following table shows the estimated cost if the VM runs continuously.
| Running period | Calculation | Estimated cost |
|---|---|---|
| 1 hour | 1.2252 × 1 | 1.2252 |
| 1 day (24 hours) | 1.2252 × 24 | 29.4048 |
| 1 week (168 hours) | 1.2252 × 168 | 205.8336 |
| 1 month (30 days, 720 hours) | 1.2252 × 720 | 882.144 |
| 1 year (365 days, 8760 hours) | 1.2252 × 8760 | 10732.752 |
Kubernetes-as-a-Service Pricing¶
Kubernetes-as-a-Service will follow the same resource-based pricing model when the service becomes available.
The cost of Kubernetes workloads will be calculated based on the allocated:
- CPU resources
- Memory resources
- Storage resources
Kubernetes-as-a-Service is currently under development and is not available for users yet.
Important Notes¶
- The pricing is based on allocated resources, not actual resource utilization.
- Running resources continue to accumulate costs while they are active.
- Users should stop or remove unused resources to avoid unnecessary costs.
- Storage resources may continue generating costs while they exist, even if a VM is stopped.
- The final billed amount is calculated according to the actual resource usage period and the service billing rules.
Source repository