Azure CycleCloud HPC Modernization with Slurm

This case study shows how PTP modernized high-performance computing on Azure by deploying a secure Azure CycleCloud environment with Slurm orchestration, dynamic autoscaling, and cost-optimized cloud infrastructure for compute-intensive workloads. The solution replaced manual cluster management with a fully automated HPC framework, improved scheduling efficiency, strengthened security and governance with private networking and RBAC, and supported up to 80% savings on interruptible queues through Azure Spot VMs.

Illustration of Goat working on servers leading data to the cloud and to a proved treatment

%

automated cluster lifecycle

Savings with Azure Spot VMs

Compute to Reduce Idle Waste

Executive Summary

A customer requiring highly scalable and cost-efficient High-Performance Computing (HPC) infrastructure needed a modern cloud-native solution to support compute-intensive workloads such as scientific simulations, financial modelling, engineering applications, and batch processing. The legacy environments lacked automation, dynamic scalability, and unified management metrics. The engineering strategy involved deploying a secure, resilient Azure CycleCloud platform tightly integrated with a Slurm workload manager orchestration tier. The implementation delivered a fully automated HPC environment capable of dynamically scaling compute layers on-demand while guaranteeing enterprise-grade security and governance controls.

Customer Context & Drivers

  • Industry: Research, Engineering, and Compute-Intensive Batch Workloads.
  • Legacy Environment: Manually managed clusters, static infrastructure allocations, high operational overhead, restricted burst scaling capacity, and significant resource underutilization during idle windows.
  • Primary Business Drivers: Transition to a cloud-native model, enable aggressive autoscaling policies, optimize cloud infrastructure spend, and streamline orchestration overhead via centralized controls.

Target Problem Matrix

  • Infrastructure Challenges: Manual configuration and physical provisioning methods created persistent processing bottlenecks during peak, time-sensitive simulation windows.
  • Operational Bottlenecks: Complex standalone scheduler topologies increased maintenance overhead, making node health validation difficult across disparate jobs.
  • Financial Inefficiencies: Substantial cloud waste incurred due to 'always-on' compute resources remaining provisioned and billing during idle scheduling gaps.
  • Security & Governance: Absence of centralized role-based access security, granular auditing controls, and secure perimeter isolation layers.

System Architecture & Workflow

The modernized architecture separates orchestration, scheduling, and high-performance execution into distinct, isolated layers connected securely within an Azure Virtual Network (VNet) topology.


Architectural Core Elements

  • Azure CycleCloud Server: Acts as the orchestration engine, governing cluster lifecycle policies, dynamic configuration deployments, and scalable cluster templates.
  • Slurm Scheduler Head Node: Hosts active control daemons (slurmctld, slurmd) to manage execution logic, workload queues, and user request routing.
  • Slurm Accounting Database: Utilizes an external Azure Database for MySQL Flexible Server to ensure highly available, durable persistence for historical metrics and accounting logs.
  • Shared Storage Infrastructure: Combines specialized Azure NetApp Files (ANF) instances for low-latency active paths (/home and shared datasets) alongside cost-optimized Azure Blob Storage for cold diagnostic outputs.

End-to-End Operational Workflow

[1. Job Submission via Slurm Tools (sbatch/squeue)]

[2. Slurm Head Node Evaluates Computational Demands]

[3. Azure CycleCloud Orchestrates Target VM Nodes]

[4. Autoscaling Compute Nodes Execute and Access Storage (ANF)]

[5. Idle Nodes Automatically Deallocated to Eliminate Waste]

The cluster operational execution follows five distinct phases: (1) Researchers submit specialized containerized or script jobs using native Slurm CLI mechanisms. (2) The Slurm Scheduler tracks queue capacity requirements and requests scale-out adjustments. (3) Azure CycleCloud translates these demands, spawning instances dynamically. (4) Compute nodes mount Azure NetApp Files pathways, processing live tasks rapidly. (5) On-completion, inactivity timers trigger absolute node termination.

Key Technical Components

1. Orchestration & Scheduling Foundations

  • Azure CycleCloud Architecture: Acts as the centralized provisioning engine, enabling strict compliance enforcement via customized cluster blueprint templates.
  • Slurm Workload Manager: Enforces advanced fair-share job scheduling, multi-queue structures, priority sorting, and structured cluster state monitoring.

2. Infrastructure & Persistent Data Tiers

  • Azure Database for MySQL: Removes accounting overhead from the active master node, tracking jobs across an enterprise-ready MySQL database backend.
  • Storage Tier Segregation: Employs dual-tier capabilities (ANF for high-throughput block execution; Azure Blob for long-term durable archival storage).

3. Networking & Security Perimeter

  • Network Isolation: Ensures all compute instances live inside strict private subnets, routing outbound requests safely through NAT Gateways.
  • Access Governance & RBAC: Restricts operational environments via corporate Azure Active Directory roles and strict SSH-key policies.

TECHNICAL DESIGN NOTE

By leveraging Azure Database for MySQL Flexible Server for Slurm accounting instead of hosting a local flat-file database on the Head Node, the environment achieves complete state separation. This prevents performance degradation on the controller during high-frequency short-job submission bursts.

The Solution: Strategic Implementation Approach

The solution was deployed via a systematic, multi-phased engineering pipeline to guarantee alignment with cloud-native security baselines.

Phase 1: Environment & Guardrails Preparation

  • Isolated resource groups configured across dedicated availability zones.
  • Generated explicit Entra ID Enterprise Application credentials mapped to targeted resource definitions.
  • Assigned strict Contributor role definitions locked exclusively to the CycleCloud principal identity.

Phase 2: Core Database Provisioning

  • Provisioned an Azure Database for MySQL Flexible Server instance.
  • Configured isolated Virtual Network private endpoints, cutting off public internet visibility.
  • Injected hardened administrative credentials and applied custom firewall routing matrices.

Phase 3: Azure CycleCloud Orchestration Setup

  • Deployed the official Azure CycleCloud instance directly from the Azure Marketplace repository.
  • Mapped standard storage path mount points and structured core virtual networks.
  • Integrated explicit Bastion Host proxies to ensure fully encrypted administrative jump-box entry.
  • Defined target SKU sizes for both CPU-heavy and GPU-driven workload partitions.

Phase 4: Slurm Cluster Fine-Tuning & Service Launch

  • Accessed the primary management dashboard UI to bootstrap target configurations.
  • Linked the external Slurm accounting database backend to track active telemetry seamlessly.
  • Initialized essential master scheduling services (slurmctld) on the Head Node cluster.
  • Executed pipeline integration tests validating dynamic scaling policies and node heartbeat health checks.

Project Outcomes & Cost Optimization

Business & Operational Outcomes

  • Infrastructure Velocity: Eliminated manual node administration, delivering a 100% automated cluster lifecycle framework.
  • Performance Enhancements: Reduced scheduling queue delays by matching job parameters to specific VM compute shapes instantly.
  • Operational Visibility: Granted cluster administrators granular visibility into individual user resource consumption metrics.
  • Hardened Governance: Achieved compliance goals through absolute network perimeter isolation and RBAC alignment.
Cost Component Tier Applied Engineering Optimization Strategy
Compute Node Management Dynamic scaling engines scale clusters to zero upon job completion, avoiding idle-capacity billing.
Fault-Tolerant Queues Leveraged low-cost Azure Spot VMs for interruptible queues, yielding up to 80% savings on baseline pricing.
Management & Control Nodes Right-sized master head nodes and CycleCloud instances to match steady-state operation profiles.
Predictable Baselining Applied 1-to-3 year Azure Reserved Instances for continuous, non-autoscaling architectural nodes.

Core Differentiators

  • HPC Specialization: Proven architecture blueprints combining custom Slurm parameters with cloud-native scaling controllers.
  • Financial Precision: Dynamic scale-to-zero capabilities reduce infrastructure waste without operational degradation.
  • Enterprise Readiness: Delivers enterprise security frameworks out of the box, ensuring strict isolation suitable for sensitive datasets.

About the Author: Rajaji Thirumeni – Azure and M365 Solutions Architect at PTP

Graphs Isometric Contained Icon

Ready to Modernize HPC on Azure?

PTP helps organizations build secure, scalable Azure CycleCloud and Slurm environments for compute-intensive workloads. From automated cluster lifecycle management and dynamic autoscaling to stronger governance and cost optimization, we help teams modernize legacy HPC infrastructure for better performance, visibility, and cloud efficiency.

Talk to an Azure HPC Expert

Let PTP help you modernize your infrastructure and reduce downtime. Schedule a free consultation today!

Homepage Contact Us