Provisioning

Owner: automation-guild · Reviewed: current

Auto-drafted from ansible-provisioning-* when roles change.

When to use

Provisioning a new VM / resource into a target region via the Ansible automation.

Preconditions

• Target subscription / tenant confirmed
• Change ticket (if required): CHG____
• Inventory / target group prepared
• Credentials available via Key Vault (never inline)

Procedure

EMEA / Brazil (global Azure)China (21Vianet)On-prem (vCenter)

ansible-playbook provision.yml \
  -i inventories/emea \
  --limit ring1 \
  -e "region=westeurope data_residency=eu"

# Runs from the in-region runner; uses China-specific endpoints.
ansible-playbook provision.yml \
  -i inventories/china \
  --limit ring1 \
  -e "region=chinanorth3 data_residency=cn cloud=china"

ansible-playbook provision.yml \
  -i inventories/onprem \
  --limit dc1

Validation

• Resource healthy and registered in CMDB
• Monitoring picks up the node
• Tags present: costcenter, env, owner, data_residency

Rollback

• Re-run with -e state=absent on the same limit, or the decommission playbook for a full teardown.

Related

• Decommission · Regions & residency