Host Factory Supported APIs¶
This document lists AWS API combinations first, followed by OCICompute support and its current validation scope.
Supported API Combinations¶
Current Implementation Status¶
| Provider API | Fleet Type | Price Type | Status | Description |
|---|---|---|---|---|
| RunInstances | - | ondemand | IMPLEMENTED | |
| RunInstances | - | spot | NOT-SUPPORT | Intentionally not supported to maintain backward compatibility |
| SpotFleet | request | ondemand | IMPLEMENTED | |
| SpotFleet | request | spot | IMPLEMENTED | |
| EC2Fleet | instant | ondemand | IMPLEMENTED | |
| EC2Fleet | instant | spot | IMPLEMENTED | |
| EC2Fleet | request | ondemand | IMPLEMENTED | |
| EC2Fleet | request | spot | IMPLEMENTED | |
| EC2Fleet | maintain | ondemand | NOT-IMPLEMENTED | |
| EC2Fleet | maintain | spot | NOT-IMPLEMENTED | |
| ASG | - | ondemand | IMPLEMENTED | |
| ASG | - | spot | NOT-IMPLEMENTED |
Legend¶
- IMPLEMENTED: Code implemented and tested.
- NOT-IMPLEMENTED: Not yet implemented.
- NOT-SUPPORT: Intentionally not supported.
OCICompute¶
OCI uses the OCICompute provider API for individual VM and bare metal workers.
Capacity selection uses OCI's capacity_type: ondemand|preemptible, rather than
the AWS price/fleet combinations above. See the
OCICompute provider reference for supported fields
and lifecycle behaviour, and the deployment guide
for initialization with --scheduler hostfactory.
HostFactory template mapping, persistence, generation, and dry-run CLI workflows are covered by automated tests. Configure and validate Symphony worker registration and workload execution for the target deployment.