Skip to main content

Part 7: Validation & Handover

Implementation Azure

DOCUMENT CATEGORY: Implementation Runbook
SCOPE: A deployed Azure Local cluster, after the tests of Part 6
PURPOSE: Collect the evidence that the cluster is healthy, write the documentation package and transfer access to the customer
MASTER REFERENCE: Azure Local deployment validation

Status: Active

Part 6 is the acceptance test of the cluster (health, storage performance with VMFleet, RDMA, failover, security). Part 7 is the evidence run that goes with the handover: four read-only checks that read the cluster name from infrastructure.yml and can be run again at any time (they are also the checks to repeat after an update, Part 8), then the two handover tasks. Every task has a script under scripts/deploy/07-validation-handover, a page here and a test.

Tasks​

TaskWhat it doesScript folderAzure CLI script
Task 01: Cluster HealthCluster service, nodes, Storage Spaces Direct, networks, quorum, Arc agentscripts/deploy/07-validation-handover/task-01-cluster-health-validationno
Task 02: Arc ConnectivityFrom each node: the Arc agent, its extensions and the Arc endpointsscripts/deploy/07-validation-handover/task-02-arc-connectivity-validationno (the Azure side is Phase 04, Task 04)
Task 03: Network ConfigurationAdapters, virtual switches, Network ATC intents, RDMA, cluster networks, DNS, endpointsscripts/deploy/07-validation-handover/task-03-network-configuration-validationno
Task 04: Storage PerformancePools, virtual disks, physical disks, volumes, and an optional I/O latency testscripts/deploy/07-validation-handover/task-04-storage-performance-validationno
Task 05: Deployment DocumentationWrites the documentation package of the instancescripts/deploy/07-validation-handover/task-05-deployment-documentationno
Task 06: Customer TransferGives the customer administrator access to the Azure resources and writes the transfer recordscripts/deploy/07-validation-handover/task-06-customer-transferyes

Tasks 01 to 04 also run in one pipeline, validation, on GitHub Actions, GitLab CI and Azure DevOps. The storage load test runs there as a separate job behind an approval. See Run the Validation in a Pipeline.

How the scripts behave​

  • Each reads infrastructure.yml (-InfrastructureFile, required) and nothing else; cluster.name is the cluster, azure.location the region where an endpoint list is needed.
  • None asks a question. They connect as the account that runs them, or as -Credential where that is offered.
  • Exit codes: 0 nothing failed (warnings are listed), 1 a check failed or the cluster could not be read, 2 a value in the file is missing or not usable (nothing is sent).
PreviousUpNext
Part 6: Testing & ValidationImplementation GuideTask 01: Cluster Health

Document maintained by Azure Local Cloud Team. Part of the Azure Local Implementation Guide.