Segal AI Training
Run container-based training jobs on supported CPU or GPU configurations, with explicit data attachments and job state.
The supported upstream service is AI Training. Segal supplies the branded application and support boundary; activation depends on the approved customer configuration and applicable provider terms.
Request and resource flow
- Select a regional AI Training configuration.
- Submit the versioned training container and data attachments.
- Track the job and preserve its outputs in object storage.
Configuration responsibilities
- A job has a container image, resources and an execution command.
- Data synchronization and training execution are separate stages.
- Logs and provider-reported job state drive operations.
Supported scope
Container-based training jobs. Accelerator types, GPU bundles and quotas follow the selected AI region.
- GPU types, counts and quotas are specific to each AI region.
- A stopped job and a persistent data container have separate lifecycles.
- Container dependencies, model licenses and training code remain customer responsibilities.
Read your organization’s inventory
Open the AI Training workspace after signing in. The server resolves your active organization and its allowed OVHcloud resources. It does not accept a provider project ID from the browser.
The authenticated endpoint is GET /api/infrastructure/training. Supply an allowed region where needed, and a zero-based page for inventory pagination. Each response reports the requested region and the next page when one exists. Project-wide inventories may contain resources from more than one region; an unreported resource region is not inferred from a seed catalog.
The endpoint uses the Segal browser session. Demonstration sk_segal_ keys do not grant production access. Provider credentials stay server-side. A missing connection returns an explicit error rather than sample resources.
Ordering and changes
New orders and configuration changes for this service are engineering-assisted. The workspace reads authorized provider inventory; it does not imply an automated purchase or provisioning workflow. Request a configuration review before committing to a plan.
Activation and service evidence
Follow provider setup before enabling live access. Demo resources, website imagery and documentation examples do not verify capacity, certification, latency or delivery. Confirm regional availability, contract scope, recovery ownership and final customer pricing before production use.
Read the product architecture. Upstream technical reference: AI Training (reviewed 24 October 2026).