Skip to content

Service Offerings

Service offerings are pre-configured resource profiles that define how an Instance consumes OpenCloud infrastructure. They are defined and managed by US Signal and cannot be modified by end users.

  • Compute Offerings: define the vCPU count and RAM allocated to an Instance.
  • Disk Offerings: define the size and type of storage that can be attached to an Instance.
  • Network Offerings: define the services available on a network. See Networking for details.

Viewing Service Offerings

  1. Log in to OpenCloud and click on Service Offerings in the left-hand panel.
  2. The dropdown contains Compute Offerings, Disk Offerings, and Network Offerings.
  3. Click into any offering to see its details including CPU, RAM, and applicable zones.

Compute Offerings

Compute offerings define the vCPU count and RAM for an Instance.

Naming Convention

Offerings follow the format: <Type>-<CPU>-<Cores>-<RAM>

Type Name CPU Processor Architecture
S Standard I Intel x86_64
CD Compute Dense A AMD x86_64
MP Memory Plus I Intel x86_64
MD Memory Dense I Intel x86_64
S Standard R ARM aarch64
CD Compute Dense R ARM aarch64

Zone Availability

Not all offering types are available in every zone. CPU architecture varies by zone — Intel and ARM64 are available in Auburn Hills and Denver, AMD is available in Des Moines and Grand Rapids.

CPU Architecture by Zone

us-mi-abh-01 us-co-eng-01 us-ia-dsm-01 us-mi-kwd-01
Intel (x86_64) ✅ ✅ ❌ ❌
AMD (x86_64) ❌ ❌ ✅ ✅
ARM64 (aarch64) ✅ ✅ ❌ ❌

Offering Types by Zone

us-mi-abh-01 us-co-eng-01 us-ia-dsm-01 us-mi-kwd-01
S ✅ ✅ ✅ ✅
CD ✅ ✅ ✅ ✅
MP ✅ ✅ ❌ ❌
MD ✅ ✅ ❌ ❌

MP and MD offerings are only available in us-mi-abh-01 and us-co-eng-01. ARM64 offerings only include S and CD types.

Changing Between Offering Tiers

S and CD offerings run on different infrastructure than MP and MD offerings. CloudStack cannot move an Instance directly between these tiers. An intermediate step using the Change-Service-Offering offering is required.

Change-Service-Offering is a minimal offering (1 vCPU) that is not tied to any specific infrastructure. It allows the Instance to float between tiers before being scaled to the target offering.

Process:

  1. Stop the Instance.
  2. Scale to Change-Service-Offering.
  3. Scale to the target MP or MD offering.
  4. Start the Instance.

Warning

Change-Service-Offering is not intended to run workloads. Do not start an Instance while it is set to this offering.

ARM 64 (aarch64) Instances

ARM 64 (aarch64) Instances are available in us-mi-abh-01 and us-co-eng-01 only. ARM 64 (aarch64) supports Linux-based Instances only — Windows is not supported or permitted on ARM 64 (aarch64).

ARM 64 (aarch64) Instances have different configuration requirements from standard AMD 64 (x86_64) Instances:

Topic Notes
UEFI Do not set. ARM64 has no legacy BIOS — UEFI is always active. Setting UEFI to LEGACY or SECURE will cause the Instance to fail to boot.
Secure Boot Not supported on ARM64.
video.hardware Set to virtio. Required for console access — without it, the console will show nothing during boot.
rootDiskController Some live Linux installers fail to detect the disk with virtio. If an installer boots but cannot find the disk, set rootDiskController to scsi.
Template / ISO Arch Must be set to ARM 64 bits (aarch64). If not set, the template or ISO will not appear in the ARM64 architecture selector when creating Instances.

See Compute for ARM 64 (aarch64) instance settings.

Network Offerings

Network offerings define the types of networks available and the services each provides. See Networking for details on available network offerings and their behavior.