Skip to main content

Discovery Data Consolidation

Runbook Azure

DOCUMENT CATEGORY: Runbook SCOPE: Discovery output consolidation PURPOSE: Generate master configuration documents MASTER REFERENCE: Variable Registry Process

Status: Active


After completing all discovery sessions and workload assessments, consolidate the findings into the master infrastructure.yml (schema 5). Every Azure Local tool reads this one file, so the discovery answers go straight into its keys. Names follow the naming standards.

The master file​

The excerpt below shows where the main discovery answers go. The values are the toolkit's example customer (IIC) and documentation address ranges. The full example, with every section, is config/variables/examples/infrastructure.example.yml in azurelocal-toolkit.

_metadata:
schema_version: "5.6.0"

scenario:
identity: active_directory # active_directory | local_identity
storage_architecture: s2d # s2d | san | hybrid
storage_connectivity: switched # switched | switchless

site:
code: "IIC"
customer: "Infinite Improbability Corp"

azure:
tenant_id: "00000000-0000-0000-0000-000000000000"
subscription_id: "00000000-0000-0000-0000-000000000000"
location: "eastus"
resource_group: "rg-iic-azl-01"
custom_location: "cl-iic-azl-01"

key_vaults:
- name: "kv-iic-mgmt-01"
subscription_id: "00000000-0000-0000-0000-000000000000"
resource_group: "rg-iic-mgmt-01"
purpose: "management"

cluster:
name: "iic-azl-01"
witness:
type: cloud
storage_account: "stiicazl01wit"

nodes:
- name: "iic-azl-n01"
management:
ip_address: "192.0.2.11"
mac_address: "00:00:5E:00:53:11"
serial_number: "SERIAL01"
bmc:
ip_address: "198.51.100.11"
type: idrac
- name: "iic-azl-n02"
management:
ip_address: "192.0.2.12"
mac_address: "00:00:5E:00:53:12"
serial_number: "SERIAL02"
bmc:
ip_address: "198.51.100.12"
type: idrac

hardware:
vendor: "Dell"
model: "AX-760"

networking:
management:
subnet: "192.0.2.0/24"
gateway: "192.0.2.1"
vlan_id: 0 # 0 means untagged
dns_servers: ["192.0.2.4", "192.0.2.5"]
oob:
subnet: "198.51.100.0/24"
gateway: "198.51.100.1"
intents:
- name: "management"
traffic: [management]
adapters: ["Port1", "Port2"]
- name: "compute_storage"
traffic: [compute, storage]
adapters: ["Port3", "Port4"]
storage:
networks:
- { name: "StorageNetwork1", adapter: "Port3", vlan_id: 711 }
- { name: "StorageNetwork2", adapter: "Port4", vlan_id: 712 }
vlans:
- { name: "workloads", id: 2204, subnet: "203.0.113.0/24" }

identity:
local_admin:
username: "azl-admin"
password: "keyvault://kv-iic-mgmt-01/local-admin-password"
active_directory:
domain_fqdn: "improbability.cloud"
ou_path: "OU=iic-azl-01,OU=AzureLocal,DC=improbability,DC=cloud"
lcm_user:
username: "lcm-iic-azl-01"
password: "keyvault://kv-iic-mgmt-01/lcm-password"

Secrets are never values in the file: each one is a keyvault://<vault>/<secret> reference to a vault listed in key_vaults. Check the file with ./scripts/common/infrastructure/Test-InfrastructureFile.ps1 -Path ./infrastructure.yml. It lists every problem at once.

Implementation Readiness Checklist​

Pre-Implementation Validation​

  • Naming Standards:

  • All naming patterns documented and approved

  • DNS namespace design validated

  • No conflicts with existing infrastructure

  • Network Design:

  • VLAN IDs allocated and documented

  • IP ranges reserved in IPAM

  • Firewall rules defined

  • Switch configurations prepared

  • Azure Resources:

  • Subscription access verified

  • Resource providers registered

  • Naming standards comply with Azure requirements

  • Cost estimates approved

  • Documentation:

  • Configuration summary reviewed by stakeholders

  • Network diagram approved

  • Migration plan accepted

  • Sign-off obtained