Rendered folder index
Direct articles in this section
Folders and articles are both available in the left browser. This panel promotes actual notes first.
DC 3.0 requires deterministic, auditable network configuration delivery across a large fabric. Incremental changes are hard to validate end-to-end and allow drift to accumulate ove
adr / supersededADR-003 DC 3.0 validation, state capture, and operational toolingStatus: superseded by adr-018-network-validation-ansible-vendor-cli.
adr / acceptedADR-007 IP Addressing Plan for 1H2026 OpenShift EngagementThe 1H2026 OpenShift implementation needs IP allocations for nodes, pods, services, and supporting networks without colliding with existing RWS routes. The plan must also be compat
adr / acceptedADR-008 Storage Network Segmentation and QoSStorage traffic shares the same fabric as application and management traffic. We need to decide whether storage access should be isolated in a dedicated segment (VLAN/VXLAN) and if
adr / supersededADR-016 Network Topology for 2026 OpenShift EngagementStatus: superseded by adr-019-hybrid-network-rollout-aci-a-ai-only-evpn-b-target.
adr / acceptedADR-018 Network validation and drift baseline with Ansible + vendor CLIsThe network operating model needs a single baseline that is simple to execute in production AAP workflows, while still producing auditable evidence and repeatable drift checks. The
adr / acceptedADR-019 Hybrid network rollout: ACI in Location A (AI-only) and EVPN/VXLAN in Location B (target)The rollout requires fast delivery of an AI cluster in Location A while the multi-tenant, multi-cluster platform is built and validated in Location B. A single network baseline acr
adr / draftADR-020 Backbone service-vs-transport model: L3VPN over SR-MPLSNetwork reviews still mix service policy and transport behavior into one layer. That causes route-policy ambiguity, weak ownership boundaries, and inconsistent change review.
adr / draftADR-021 DC EVPN to backbone L3VPN interconnect patternThe datacenter lane uses EVPN/VXLAN and the backbone uses L3VPN over SR-MPLS. Without a fixed interconnect pattern, teams introduce inconsistent route leaks, uncontrolled L2 extens
adr / draftADR-023 IPv6 numberplan and cluster scale strategyadr-007-ip-addressing-2026 is accepted for 1H2026 RFC1918 delivery, but it does not define the forward IPv6 strategy for government category usage and large-scale cluster growth.
Network ADRs define connectivity, topology, addressing, and operational validation choices for the target architecture.
Start Here
Key Network ADRs
- ADR-019 Hybrid network rollout (accepted)
- ADR-018 Network validation baseline (accepted)
- ADR-020 Backbone service-vs-transport model (draft)
- ADR-021 DC-to-backbone interconnect pattern (draft)
- ADR-007 IP addressing plan (accepted)
- ADR-023 IPv6 numberplan and cluster scale strategy (draft)
- ADR-008 Storage network segmentation and QoS (accepted)
Authority Map
- Working direction (draft): backbone service versus transport policy in adr-020-backbone-service-vs-transport-l3vpn-sr-mpls.
- Working direction (draft): DC-to-backbone interconnect default and L2 exception policy in adr-021-dc-evpn-to-backbone-l3vpn-interconnect.
- Working direction (draft): forward IPv6 numberplan and overlap policy in adr-023-ipv6-numberplan-and-cluster-scale-strategy.
Related Lenses
- Supporting facts: Facts and Taxonomy.
- Delivery impact: Delivery Work Packages.