BSFG Environment Deployment Map

Purpose

This document defines the environment-specific realization of a BSFG estate containing:

• Enterprise
• IDMZ
• Plant A
• Plant B

It answers:

• what zones exist
• how each zone is realized
• which hosts and VIPs belong to each zone
• which identities belong to each zone
• which team owns each zone

It does not define the cross-zone authorization and federation policy in detail.
That belongs in the companion:

• Federation Relationship Matrix: Enterprise + IDMZ + 2 Plants

Relationship to Other Documents

This document instantiates:

• Reference Deployment Pattern: Triad-HA with Keepalived Failover

It assumes cross-zone behavior will be governed by:

• Reference Interaction Pattern: Cross-Zone BSFG Federation

Environment Summary

Zone Realization Rule

Each zone in this environment is realized as a Triad-HA instance:

• Alpha
• Beta
• Gamma
• Keepalived VIP
• local JetStream quorum
• active/passive BSFG controller
• zone-local artifact storage where applicable

This means the full estate contains:

• 4 zones
• 4 Triad-HA instances
• 12 hosts total

Zone Inventory

Host Role Matrix

Zone Endpoint Map

Zone Identity Map

Identity validation is based on configured certificate identity policy, typically using subject or SAN.

Zone Storage Posture

Ownership Matrix

Deployment Instance Notes

Enterprise

• primary aggregation and supervisory integration zone
• expected to expose enterprise-facing streams and retained artifacts
• does not require direct connectivity to plant zones in the canonical mediated model

IDMZ

• real durable zone, not transparent network fabric
• mediates Enterprise ↔ Plant A and Enterprise ↔ Plant B relationships
• does not host “boundary middleware”; it hosts a zone-owned BSFG deployment

Plant A

• autonomous production zone
• remains locally operational when Enterprise or IDMZ is unavailable
• participates only in explicitly configured federation relationships

Plant B

• same realization model as Plant A
• independent of Plant A at substrate level
• no direct plant-to-plant federation in the default estate

Canonical Estate Diagram

flowchart TD
  subgraph ENT["ENTERPRISE"]
    EA["enterprise-alpha"]
    EB["enterprise-beta"]
    EG["enterprise-gamma"]
    EVIP["VIP: 10.0.1.10"]
  end

  subgraph IDMZ["IDMZ"]
    IA["idmz-alpha"]
    IB["idmz-beta"]
    IG["idmz-gamma"]
    IVIP["VIP: 10.1.1.10"]
  end

  subgraph PA["PLANT A"]
    PAA["plant-a-alpha"]
    PAB["plant-a-beta"]
    PAG["plant-a-gamma"]
    PAVIP["VIP: 10.2.1.10"]
  end

  subgraph PB["PLANT B"]
    PBA["plant-b-alpha"]
    PBB["plant-b-beta"]
    PBG["plant-b-gamma"]
    PBVIP["VIP: 10.3.1.10"]
  end

Constraints Preserved by This Realization

• each zone is autonomous at the substrate level
• each zone owns its own durable state
• no cross-zone shared JetStream
• no cross-zone shared object store
• no direct plant-to-plant relationship in the default estate
• no direct enterprise-to-plant relationship in the default estate
• IDMZ remains a durable zone, not a durable boundary transport fabric

What This Document Does Not Define

This document does not define:

• per-peer exported streams
• artifact authorization per relationship
• cursor initialization modes per stream
• federation directionality policy
• forbidden vs allowed peer relationships beyond the default estate assumption
• commissioning procedure
• validation procedure

Those belong in:

• Federation Relationship Matrix: Enterprise + IDMZ + 2 Plants
• runbooks
• validation checklists

Related Documentation

• Reference Deployment Pattern
• Reference Interaction Pattern
• Federation Relationship Matrix: Enterprise + IDMZ + 2 Plants
• Runbook: Triad-HA Zone Deployment
• Checklist: Triad-HA Commissioning