Deploy Infrastructure

Table of Contents

1. Overview
2. Step 1: Create Resource Groups
3. Step 2: Deploy VMs (Idempotent)
4. Step 3: Deploy Storage Accounts
5. Step 4: Verify Deployment
6. Cloud-Init Configuration
7. Checking VM Readiness
   1. What It Checks
   2. Example Output
   3. When to Run
   4. Prerequisites
8. Troubleshooting

---

Overview

This module deploys all Azure resources across 14 APAC regions:

• 14 Resource Groups
• 14 VMs (Standard_B2s) with ws-echo + nginx
• 14 Storage Accounts with static websites
• NSG rules for ports 80 and 8080

Step 1: Create Resource Groups

cd deploy
bash create-resource-groups.sh

This creates rg-latency-{region} for each of the 14 regions.

Step 2: Deploy VMs (Idempotent)

The recommended approach uses the idempotent script:

bash ensure-vms-ready.sh

This script:

1. Checks each VM’s power state
2. If running → skips
3. If stopped/deallocated → starts it
4. If not found → creates it with cloud-init
5. Ensures NSG rules for ports 80 and 8080
6. Waits for all VMs to be running
7. Prints a summary of public IPs

VMs are created with --no-wait for parallel deployment. The script waits at the end.

Step 3: Deploy Storage Accounts

bash create-storage-accounts.sh
bash upload-blob-payload.sh
bash configure-blob-cors.sh

Step 4: Verify Deployment

bash check-vm-status.sh
bash check-blob-status.sh

All VMs should show VM running and all blob endpoints should return HTTP 200.

Cloud-Init Configuration

Each VM is provisioned with:

# Installs: nginx, nodejs, npm
# Deploys: ws-echo.js on port 8080
# Configures: nginx /ping endpoint on port 80
# Enables: systemd services for auto-restart

Checking VM Readiness

Use ensure-vms-ready.sh as your single command to verify and fix the entire infrastructure:

bash deploy/ensure-vms-ready.sh

What It Checks

Check	Action if Failed
Resource group exists	Creates it
VM power state	Starts if stopped/deallocated, creates if missing
NSG rules (ports 80, 8080)	Creates inbound Allow rules
Frontend VM (vm-latency-frontend)	Starts if stopped, warns if missing
Frontend NSG (port 80)	Creates inbound Allow rule
Storage account public access	Enables public network access

Example Output

=== Ensuring all 14 VMs are running ===

[australiacentral]
  ✓ Already running
  Ensuring NSG inbound rules...
  ✓ NSG rules OK (80, 8080)

[southeastasia]
  Starting VM (was VM deallocated)...
  ✓ Start initiated
  Ensuring NSG inbound rules...
  ✓ NSG rules OK (80, 8080)

=== All VMs ready. Public IPs: ===

REGION               IP
------               --
australiacentral     20.53.x.x
southeastasia        20.198.x.x
...

=== Ensuring Frontend VM is running ===
  ✓ Frontend VM already running
  ✓ Frontend NSG rule OK (80)
  Frontend IP: 4.194.41.14

=== Ensuring Storage Account network rules allow public access ===
  salatencyauce: ✓ OK
  salatencysea: ✓ OK
  ...

When to Run

• Before a workshop — ensures all VMs are warmed up and accessible
• After cost-saving deallocations — restarts all VMs in one command
• After NSG changes — re-applies required inbound rules
• Diagnosing connectivity issues — validates the full stack

Prerequisites

The script sources deploy/config.sh which defines:

• REGIONS array (14 APAC regions)
• Naming functions: rg_name, vm_name, nsg_name, pip_name, storage_name
• VM_IMAGE and ADMIN_USER

Ensure you are logged into Azure CLI (az login) before running.

Troubleshooting

Issue	Solution
VM stuck in “Creating”	Wait 5 min, then az vm start
Port 8080 not reachable	Run ensure-vms-ready.sh to fix NSG
Storage 404	Re-run upload-blob-payload.sh
VM OOM during build	Add swap: fallocate -l 2G /swapfile && mkswap /swapfile && swapon /swapfile
Node.js version mismatch	Angular 19 requires Node >= 20. Upgrade via NodeSource
run-command lock	Deallocate and restart the VM to clear extension locks

---

← Architecture Next: Run Tests →