Components

Eight components make up the whole reference architecture. Seven are somebody’s supported product — OpenShift, OpenShift Virtualization, OpenShift GitOps, OpenShift Pipelines, KEDA, Windows Server, Symphony itself. Exactly one is custom: the Host Factory KubeVirt provider, a five-script plug-in against an interface IBM documents for this purpose. This page is the map; each row below links to the component’s own detail page.

Component view

The one-custom-component thesis

Every row below but one is a vendor-supported product on its own release cadence, with its own vendor to call at 3am. The exception is named, not hidden: the Host Factory KubeVirt provider is a purpose-built implementation of IBM’s documented 5-script Host Factory interface, because no built-in provider targets OpenShift Virtualization. It has prior art doing the identical contract against other substrates (FINOS Open Resource Broker, google/symphony-gcp) but no KubeVirt or Windows-VM code exists anywhere today — this is a real, unbuilt, multi-person-month effort, not a weekend script.

All eight

Component Role Status Detail

Component	Role	Status	Detail
OpenShift Virtualization	HyperConverged Operator (CNV) + CDI + the metal `MachineSet` + CPU Manager static policy every `d1.*` compute VM hard-requires	EXISTS	Detail
Windows golden image pipeline	Two-stage Tekton pipeline (`windows-efi-installer` + an in-repo customize stage) baking WS2019 + virtio + Symphony compute MSIs into one `DataSource`	EXISTS	Detail
Symphony management	RHEL 9 master + candidate VMs running EGO/SOAM as a traditional, non-containerized install	EXISTS	Detail
Windows compute pool	`VirtualMachinePool` cloning the golden image and joining each clone to the grid at sysprep specialize time	EXISTS — join fixed-in-source, not yet independently re-confirmed	Detail
GitOps	OpenShift GitOps (Argo CD) app-of-apps — the sole operating model for cluster state after bootstrap	EXISTS	Detail
KEDA metrics shim	KEDA + a Symphony-REST-polling shim scaling the compute pool’s `/scale` subresource — proves elasticity, demo only	PLANNED (Phase 4)	Detail
Host Factory KubeVirt provider [CUSTOM]	The one custom component — 5-script Host Factory interface, external kubeconfig, sysprep injection, negotiated (lazy) return	PLANNED (Phase 5)	Detail
Interconnect	IPsec VPN (PoC) upgrading to Direct Link (production) between the AWS and IBM Cloud sites, carrying the full Symphony port matrix	PLANNED (Phase 3) — parked pending IBM Cloud API key + VNI-allowlist ticket	Detail

OpenShift Virtualization

HyperConverged Operator (CNV) + CDI + the metal MachineSet + CPU Manager static policy every d1.* compute VM hard-requires

EXISTS

Detail

Windows golden image pipeline

Two-stage Tekton pipeline (windows-efi-installer + an in-repo customize stage) baking WS2019 + virtio + Symphony compute MSIs into one DataSource

EXISTS

Detail

Symphony management

RHEL 9 master + candidate VMs running EGO/SOAM as a traditional, non-containerized install

EXISTS

Detail

Windows compute pool

VirtualMachinePool cloning the golden image and joining each clone to the grid at sysprep specialize time

EXISTS — join fixed-in-source, not yet independently re-confirmed

Detail

GitOps

OpenShift GitOps (Argo CD) app-of-apps — the sole operating model for cluster state after bootstrap

EXISTS

Detail

KEDA metrics shim

KEDA + a Symphony-REST-polling shim scaling the compute pool’s /scale subresource — proves elasticity, demo only

PLANNED (Phase 4)

Detail

Host Factory KubeVirt provider [CUSTOM]

The one custom component — 5-script Host Factory interface, external kubeconfig, sysprep injection, negotiated (lazy) return

PLANNED (Phase 5)

Detail

Interconnect

IPsec VPN (PoC) upgrading to Direct Link (production) between the AWS and IBM Cloud sites, carrying the full Symphony port matrix

PLANNED (Phase 3) — parked pending IBM Cloud API key + VNI-allowlist ticket

Detail

Continue to OpenShift Virtualization, the substrate every other component schedules onto.