OCI Compute to STACKIT Compute Engine

A Flex instance, assessed

A small OCI estate written for this page and assessed by StackToIT on 4 November 2026. Left: the input. Right: the decision StackToIT recorded for it, exactly as it stands in assessment.json.

resource "oci_core_instance" "app" {
  compartment_id      = var.compartment_id
  availability_domain = var.availability_domain
  display_name        = "app-01"
  shape               = "VM.Standard.E5.Flex"

  shape_config {
    ocpus         = 2
    memory_in_gbs = 16
  }

  source_details {
    source_type = "image"
    source_id   = var.image_id
  }

  create_vnic_details {
    subnet_id        = oci_core_subnet.app.id
    nsg_ids          = [oci_core_network_security_group.app.id]
    assign_public_ip = false
  }
}

{
  "id": "oci_core_instance.app",
  "class": "RECONFIGURE",
  "confidence": "MEDIUM",
  "target": {
    "service": "STACKIT Compute Engine"
  },
  "reason": "A compute instance becomes a STACKIT server. The shape becomes a STACKIT flavor, the image is rebuilt or imported, and the attached volumes and network interfaces move with it."
}

• The shape becomes a flavor

  VM.Standard.E5.Flex with 2 OCPUs and 16 GB is matched to a STACKIT flavor. The assessment names this step, together with the image, which is rebuilt or imported.

• Volumes and interfaces move with it

  The instance is assessed with what it carries: its attached volumes and its network interfaces go to STACKIT together with the server.

• Offered where you land

  Compute Engine is offered in eu01 and eu02, as the STACKIT catalogue snapshot of the run shows.

• Every setting named

  The architect report lists all 11 settings the instance block sets, from the availability domain to the network security groups of its VNIC, so your architect carries each one over on purpose.

A block volume with its own performance setting

The same run, for the data volume of the instance.

resource "oci_core_volume" "data" {
  compartment_id      = var.compartment_id
  availability_domain = var.availability_domain
  display_name        = "app-data"
  size_in_gbs         = 200
  vpus_per_gb         = 20
}

{
  "id": "oci_core_volume.data",
  "class": "RECONFIGURE",
  "confidence": "MEDIUM",
  "target": {
    "service": "STACKIT Block Storage"
  },
  "reason": "A block volume becomes a STACKIT volume. The performance setting does not carry over; choose a STACKIT performance class, and move the data at the host or from a backup."
}

• Performance chosen on STACKIT

  vpus_per_gb = 20 is an OCI performance level. On STACKIT you pick a performance class for the volume instead, and the assessment says so.

• Data movement in the plan

  The volume is listed as a stateful unit in the data movement plan. Your team chooses how the data on its 200 GB is copied, by data size, tolerated downtime and the consistency the application needs.

How the compute estate maps

Classes and targets as the run decided them, each at medium confidence.

The order of the move

The run puts the units in waves from their dependencies: a unit moves after everything it depends on, and units in the same wave can move in parallel.

1. 01

   Wave 1

   The VCN and the block volume, which depend on nothing else.

2. 02

   Wave 2

   The subnet and the network security group, which sit inside the VCN.

3. 03

   Wave 3

   The instance and the load balancer, once their network is in place.

Questions infrastructure teams ask

Sources

• Oracle Docs: Compute overview
• STACKIT Docs: Server (Compute Engine)
• STACKIT Docs: Block Storage