Parent folderOpen Confluence

RWS Architecture article

Worker Virtualization

Worker Virtualization is the product-neutral architecture building block for virtualization substrate for worker nodes and VM-capable platform services. It states what DC 3.0 needs

  1. Typeabb
  2. Statuscandidate
  3. Domainplatform
On this page
  1. ABB Worker Virtualization
  2. Summary
  3. Capabilities
  4. Constraints
  5. Service Description
  6. Roadmaps
  7. Landing Zones
  8. Interfaces
  9. Dependencies
  10. EIRA Alignment
  11. Available SBB's

ABB Worker Virtualization

Summary

Worker Virtualization is the product-neutral architecture building block for virtualization substrate for worker nodes and VM-capable platform services. It states what DC 3.0 needs from this capability before a concrete SBB, product, or operating model is selected.

Capabilities

  • Provides virtualization substrate for worker nodes and VM-capable platform services.
  • Defines the functional, technical, security, and quality expectations that SBBs must satisfy.
  • Keeps service ownership, interfaces, and consumption boundaries visible before product selection.
  • Enables traceability from architecture intent to implementation, operational evidence, and consuming services.

Constraints

  • The resulting SBB must fit the datacenters ownership model and document the support, lifecycle, and service-management boundary.
  • Security, privacy, logging, evidence, and compliance controls must be explicit enough to assess BIO2-aligned implementation where applicable.
  • Virtualization hosts must have defined capacity, availability, patching, and hardware lifecycle requirements.
  • SBBs must make workload placement and failure-domain behavior explicit.

Service Description

This ABB offers a worker-virtualization service that provides the compute virtualization layer required by VM-oriented or hybrid platform workloads. It is consumed by solution architects, platform teams, and service owners as the capability contract for selecting and shaping SBBs.

The service description remains implementation-neutral: product selection, hosting pattern, detailed runbooks, and service levels belong in the mapped SBB and related ADRs.

Roadmaps

  • Baseline: confirm scope, service ownership, constraints, and acceptance criteria for Worker Virtualization.
  • MVP: validate the mapped SBB implementation and record the selected support and lifecycle model.
  • Next: add measurable service levels, evidence requirements, and roadmap dependencies once the SBB is selected.

Landing Zones

  • Private cloud and central DC 3.0 landing zone for core infrastructure and platform services.
  • Government cloud or external cloud landing zones only when the SBB documents the required control set, connectivity model, and data classification fit.

Interfaces

  • Hypervisor, host management, and VM lifecycle APIs.
  • Storage, network, firmware, and monitoring integrations.
  • Automation and inventory interfaces.

Dependencies

  • Depends on dc-network-structure for a supporting capability or integration boundary.
  • Depends on block-file-s3-storage for a supporting capability or integration boundary.
  • Depends on firmware for a supporting capability or integration boundary.
  • Implemented by openshift-virtualization as currently mapped SBB traceability.
  • Consuming ABB and SBB dependencies must be recorded as links when solution design identifies concrete upstream or downstream use.

EIRA Alignment

Available SBB's

  • openshift-virtualization - OpenShift Virtualization is a candidate solution building block for the translated DC 3.0 ABB model. It remains candidate until the responsible architects confirm service ownership, support model, and acceptance criteria.