# overlays/vr1-dc1-machines.yaml
#
# Retag the 9-machine block from the vr1-dc0 base to vr1-dc1 for the dc1 deploy.
# ONE Office1 MAAS region sees BOTH DCs' nodes (D-104/D-123 single region), so the
# machines-block constraint must carry the DC-scoping tag or dc1's model could grab a
# dc0 node. The DC tag (openstack-vr1-dc1) selects THIS DC's nodes; the role sub-tag
# (control/compute/storage, applied at Stage 4 per Fork-3) selects the role. The base
# bundle.yaml is the vr1-dc0 source of truth (matches overlays/vr1-dc1-vips.yaml);
# this overlay + the VIP overlay are the two per-DC deltas for dc1.
#
# Applied (with the HA scale-up + VIP overlays):
#   juju deploy ./bundle.yaml \
#     --overlay overlays/vr1-dc1-machines.yaml \
#     --overlay overlays/vr1-dc1-vips.yaml \
#     --overlay overlays/dc-ha-scaleup.yaml -m "${DC1_MODEL}"
#
# VERIFY-LIVE: confirm the machines-block override merges as expected at
# `juju deploy --dry-run` BEFORE deploy (no offline juju merger exists to prove it
# here). If it does not take, the fallback is inlining these dc1 tags into a rendered
# dc1 bundle (cheap) -- see committee-20260724-track2-bundle-render.md, Fork 2.
machines:
  "0":
    constraints: arch=amd64 tags=openstack-vr1-dc1,control
  "1":
    constraints: arch=amd64 tags=openstack-vr1-dc1,control
  "2":
    constraints: arch=amd64 tags=openstack-vr1-dc1,control
  "3":
    constraints: arch=amd64 tags=openstack-vr1-dc1,compute
  "4":
    constraints: arch=amd64 tags=openstack-vr1-dc1,compute
  "5":
    constraints: arch=amd64 tags=openstack-vr1-dc1,storage
  "6":
    constraints: arch=amd64 tags=openstack-vr1-dc1,storage
  "7":
    constraints: arch=amd64 tags=openstack-vr1-dc1,storage
  "8":
    constraints: arch=amd64 tags=openstack-vr1-dc1,storage