Rendered folder index

Direct articles in this section

Folders and articles are both available in the left browser. This panel promotes actual notes first.

index

architecture / draftDC 3.0 Capability Roadmap

This note introduces the architecture roadmap graph for DC 3.0. It defines how service offerings, capabilities, dependency constraints, and target windows are modeled so the vault

architecture / draftPlatform Intent → Automation → Runtime Evidence

The RWS platform uses **one operating model** across domains:

architecture / draftOpenShift AI Cluster Setup (DC-A Transitional Production Lane)

This note defines the **transitional production** architecture for a single OpenShift AI cluster in DC-A (AM1), created to deliver production value quickly by reusing selected IST

architecture / activeOpenShift Platform – Concept Overview

High-level view of the hybrid-cloud OpenShift platform across datacenters, covering cluster roles (management/application/virtualization/AI for DevOps acceleration), storage, netwo

architecture / draftOpenShift Virtualization Architecture

This draft defines the target architecture for the candidate OpenShift Virtualization SBB. It gives the implementation context for the Virtual Machines as a Service (VMaaS) and Wor

architecture / activeQuay Registry Architecture

Red Hat Quay is the selected target registry pattern for the DC 3.0 registry capability. It provides the controlled image and artifact distribution point that lets restricted-netwo

Platform Architecture

Canonical hub for the platform domain: operating model, service delivery, and OpenShift runtime architecture.

Scope

In scope

Platform service delivery and automation: WP-08 Platform Services and Automation
Platform service catalog and onboarding flows across Delivery Work Packages
OpenShift runtime architecture and lifecycle via openshift-concept-overview, openshift-virtualization-architecture, and openshift-ai-cluster-setup
Cluster governance and lifecycle management with ACM/MCE patterns as the accepted production baseline.
Controlled registry and image distribution through quay-registry-architecture and red-hat-quay.

Current baseline direction: OpenShift-centered runtime, GitOps reconciliation, and Location B Datacenter Services controls, while Location A remains an ACI-scoped transitional OpenShift AI lane.

Out of scope

Physical network topology and cabling details (see Network Architecture)

Key Concepts

Cluster and platform operating model: openshift-concept-overview
DC 3.0 capability roadmap and maturity gates: dc30-capability-roadmap
CaaS offering roadmap: clusters-as-a-service-offering
OpenShift AI runtime sub-area (DC-A transitional production lane): openshift-ai-cluster-setup
OpenShift Virtualization target architecture (Location B): openshift-virtualization-architecture
Transitional Location A ACI scope controls for OpenShift AI: topic-network-aci-location-a-ai-fasttrack
Rollout governance and cutover controls: adr-004-single-active-phased-rollout, wp-01-dc3-0-network-and-supporting-services, wp-08-platform-services-automation, wp-16-business-continuity-and-disaster-recovery
Git-based delivery and reconciliation: Automation
Controlled image and artifact registry: quay-registry-architecture via red-hat-quay implementing registry
Platform observability baseline: security-operations-center
Secondary execution lens: Delivery Work Packages
Secondary DC 3.0 building-block lens: DC 3.0 Building Block Lens

ADR-004 Single-active phased datacenter rollout (accepted)
ADR-005 Datacenter Services baseline (accepted)
ADR-006 External load-balancing vendor constraint (accepted)
ADR-010 ACM for cluster deployment (accepted)
ADR-011 Restricted network vs disconnected installation (accepted)
ADR-012 SSO for OpenShift and Hosted Services (draft)
ADR-013 Implementation phasing (accepted)
ADR-015 Keycloak IAM architecture (draft)
ADR-019 Hybrid network rollout (accepted)
ADR-022 Transitional OpenShift AI production exception (draft)

Principles Coverage

Automation First - delivery and reconciliation are Git-driven.
Self-Service Platform - platform capabilities are exposed as reusable services.
Cost Transparency - platform services should expose measurable usage and cost signals.

Supporting Facts

Key Sources

Diagrams

Platform landscape diagram source: OpenShift platform landscape.
Quay registry architecture source: Quay registry architecture.

Mapping Views

DC 3.0 capability-to-solution mapping for this domain: DC 3.0 Building Block Lens.

Next Steps

Capture new platform capability questions in 10-topics/platform/.
Update OpenShift-specific architecture via openshift-concept-overview and openshift-ai-cluster-setup.
Add or update platform/runtime ADRs under 30-decisions/platform/ (see way-of-working).
Add stable platform facts to 40-facts/.
Track DC-A transitional-lane delivery execution in wp-21-openshift-ai-dc-a-transitional-production-lane.