Skip to content

Commit e9eeae5

Browse files
committed
intro paragraphs for each overview
1 parent 8e20738 commit e9eeae5

File tree

5 files changed

+22
-2
lines changed

5 files changed

+22
-2
lines changed

articles/high-performance-computing/lift-and-shift-step-1-overview.md

Lines changed: 6 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
---
2-
title: "Deployment step 1: Landing zone - Overview"
2+
title: "Deployment step 1: Basic infrastructure - Overview"
33
description: Learn about production-level environment migration deployment step one.
44
author: tomvcassidy
55
ms.author: tomcassidy
@@ -9,7 +9,11 @@ ms.service:
99
services:
1010
---
1111

12-
# Deployment step 1: Landing zone - Overview
12+
# Deployment step 1: Basic infrastructure - Overview
13+
14+
The critical foundational components required to establish a landing zone in the cloud for an HPC environment are outlined here. The focus is on setting up resource groups, networking, and basic storage, which serve as the backbone of a successful HPC lift-and-shift deployment.
15+
16+
This section provides a clear understanding of the purpose and requirements of these components, along with available tools and best practices tailored to HPC workloads. A quick start guide is also included to help users efficiently deploy and manage these core components, with the expectation that more advanced automation will be implemented as the HPC environment evolves.
1317

1418
## Resource group
1519

articles/high-performance-computing/lift-and-shift-step-2-overview.md

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -11,6 +11,10 @@ services:
1111

1212
# Deployment step 2: Base services - Overview
1313

14+
One of the key component's users interact with in an on-premises environment is the job scheduler (for example, Slurm, PBS, and LSF). During a lift-and-shift process, users should retain the same level of interaction with these schedulers. However, the difference is that resources are no longer static; they're provisioned on-demand.
15+
16+
This section covers the core components related to the job scheduler, including the resource orchestrator for provisioning and setting up resources, identity management for user authentication, monitoring (including node health checks), and accounting to better understand the status and usage of resources. Each component plays a crucial role in ensuring the performance, scalability, and security of the HPC environment. By utilizing familiar on-premises technologies like Active Directory and established application runtimes, organizations can transition to the cloud more smoothly while maintaining continuity. A comprehensive overview of tools, best practices, and quick-start setups is provided, with the goal of progressively automating these services as the cloud environment evolves.
17+
1418
## User identity
1519

1620
Using technologies such as Active Directory Services and LDAP, user accounts and properties in use on-premises could be reused in the cloud environment. We recommend you apply the existing on-premises user identity technologies as much as possible.

articles/high-performance-computing/lift-and-shift-step-3-overview.md

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -11,6 +11,10 @@ services:
1111

1212
# Deployment step 3: Storage - Overview
1313

14+
With the cloud offering a broader range of storage solutions compared to on-premises systems, it's essential to define where different types of data—such as user home directories, project data, and scratch disks—should be stored. The section also discusses data migration strategies, whether it involves a one-time transfer or continuous synchronization between on-premises systems and the cloud. Organizations can optimize costs and performance by carefully selecting storage options and utilizing tools for efficient data movement.
15+
16+
This section highlights the critical considerations for managing storage in an HPC cloud environment, focusing on the variety of cloud storage options and the processes for migrating data. Also, it offers practical guidance for setting up storage and managing data migration, with an emphasis on scalability and automation as the HPC environment evolves.
17+
1418
## Storage options in the cloud
1519

1620
Compared to on-premises environment, the variety and capacity for storage options in the cloud increase. A good practice is to define the major places to put data, such as user home directories, project data, scratch disks, and long term storage. As one of the key benefits of cloud is to obtain resources on demand, it's more important at the beginning to define the storage options. As environment evolves, the amount of data required for storage options becomes clearer.

articles/high-performance-computing/lift-and-shift-step-4-overview.md

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -11,6 +11,10 @@ services:
1111

1212
# Deployment step 4: Compute nodes - Overview
1313

14+
Managing compute nodes in an HPC cloud environment involves careful consideration of virtual machine (VM) types, images, and quota limits. Testing key on-premises workloads in the cloud helps assess the cost-benefit of different VM SKUs, allowing for more informed hardware decisions over time. Azure provides preconfigured HPC images for Ubuntu and Alma Linux, which include necessary drivers and libraries, simplifying the deployment process. Custom images can also be created using available resources from the Azure HPC image repository. Additionally, it’s important to plan resource usage carefully and consult with Azure to avoid quota limitations, especially when scaling across multiple regions.
15+
16+
This section provides guidance on selecting and managing compute resources efficiently for HPC workloads in the cloud.
17+
1418
## Virtual machine (VM) types (SKUs)
1519

1620
We recommend you test a few key on-premises workloads in the cloud to develop an understanding of cost-benefit for different SKUS. In the cloud, the hardware options allow decisions to be refined over time.

articles/high-performance-computing/lift-and-shift-step-5-overview.md

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -11,6 +11,10 @@ services:
1111

1212
# Deployment step 5: End-user entry point - Overview
1313

14+
Providing a consistent end-user entry point is crucial for ensuring a smooth transition from on-premises to the cloud in an HPC environment. Whether users access resources through an SSH sign-in node or a web portal, maintaining a familiar experience helps minimize disruptions.
15+
16+
This section explores the options for user interaction, emphasizing the importance of addressing potential latency issues that may arise when moving to the cloud. It also provides guidance on tools, services, and best practices to optimize the user entry point for HPC lift-and-shift deployments. A quick start setup is included to help establish this component efficiently, with the goal of automating it as the cloud infrastructure matures.
17+
1418
## Options for user interaction
1519

1620
End-users may benefit from having similar experience accessing resources on-premises and in the cloud. Whether users go to a sign-in node via ssh or a web portal to submit jobs, we recommend you keep the same user experience and access if there are any latency issues that users may face compared to on-premises environment.

0 commit comments

Comments
 (0)