addressing PR review feedback

Author: tomvcassidy

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

@@ -5,11 +5,11 @@ author: tomvcassidy
 ms.author: tomcassidy
 ms.date: 08/30/2024
 ms.topic: how-to
-ms.service: 
-services: 
+ms.service: azure-virtual-machines
+ms.subservice: hpc
 ---
 
-# End-to-end HPC lift and shift architecture
+# End-to-end HPC lift and shift architecture overview
 
 "Lift and shift" in the context of High-Performance Computing (HPC) mostly refers to the process of migrating an on-premises environment and workload to the cloud. Ideally, modifications are kept to a minimum (for example, applications, job schedulers, and their configurations should remain mostly the same). Adjustments on storage and hardware are natural to happen because resources are different from on-premises to cloud platforms. With the lift and shift approach, organizations can start benefiting from the cloud more quickly.
 
@@ -28,44 +28,44 @@ This document therefore:
 Before jumping into the architecture description, it's relevant to understand
 the different personas in this context, their needs, and expectations.
 
-## Personas and User Experience
+## Personas and user experience
 
 There are different people who need to access the HPC environment. Their activities and how they interact with the environment vary quite a bit.
 
 ### End-user (engineer / scientist / researcher)
 
 This persona represents the subject matter expert (for example, biologist, physicist, engineer, etc.) who wants to run experiments (that is, submit jobs) and analyze results. End-users interact with system administrators to fine-tune the computing environment whenever needed. They may have some experience using CLI-based tools, but some of them may rely only on web portals or graphical user interfaces via VDI to submit their jobs and interact with the generated results.
 
-**New Responsibilities in Cloud HPC Environment:**
+**New responsibilities in cloud HPC environment:**
 
 - End-user shouldn't have any new responsibilities based on the work from both the HPC Administrator and Cloud Administrator. Depending on the on-premises environment, end-users have access to a larger capacity and variety of computing resources to become more productive.
 
-### HPC Administrator
+### HPC administrator
 
 This persona represents the one who has HPC expertise and is responsible for deploying the initial computing infrastructure and adapting it according to business and end-user needs. This persona is also responsible for verifying the health of the system and performing troubleshooting. HPC administrators are comfortable accessing the architecture and its components via CLI, SDKs, and web portals. They're also the first point of contact when end-users face any challenge with the computing environment.
 
-**New Responsibilities in Cloud HPC Environment:**
+**New responsibilities in cloud HPC environment:**
 
 - Managing cloud resources and services (for example, virtual machines, storage, networking) via cloud management platforms.
 - Implementing and managing clusters and resources via new resource orchestration tools (for example, CycleCloud).
 - Optimizing application deployment by understanding infrastructure details (that is, VM types, storage, and network options).
 - Optimizing resource utilization and costs by using cloud-specific features such as autoscaling and spot instances.
 
-### Cloud Administrator
+### Cloud administrator
 
 This persona works with the HPC administrator to help deploy and maintain the computing infrastructure. This persona isn't (necessarily) an HPC expert, but a Cloud expert with deep knowledge of the overall company IT infrastructure, including network configurations/policies, user access rights, and user devices. Depending on the case, the HPC administrator and Cloud administrator may be the same person.
 
-**New Responsibilities in Cloud HPC Environment:**
+**New responsibilities in cloud HPC environment:**
 
 - Collaborating with HPC administrators to ensure seamless integration of HPC workloads with cloud infrastructure.
 - Monitoring and managing cloud infrastructure performance, security, and compliance.
 - Helping with the configuration of cloud-based networking and storage solutions to support HPC workloads.
 
-### Business Manager / Owner
+### Business manager / owner
 
 This persona represents the one who is responsible for the business, which includes taking care of budget and projects to meet organizational goals. For this persona, the accounting component of the architecture is relevant to understand costs for each project. This persona works with HPC admins and end-users to understand platform needs, including storage, network, computing resources. They also plan for future workloads.
 
-**New Responsibilities in Cloud HPC Environment:**
+**New responsibilities in cloud HPC environment:**
 
 - Analyzing detailed cost reports and usage metrics provided by cloud service providers to manage budgets and forecast expenses.
 - Making strategic decisions based on cloud resource usage and cost optimization opportunities.
@@ -81,8 +81,8 @@ There are also extensions that could be in place, such as sign-in nodes, data mo
 
 This production-level environment may have various components to be set up. Therefore, environment deployers and managers become key to automate its initial deployment and upgrade it along the way, respectively. More advanced installations can also have environment templates (or specifications) with software versions and configurations that are more optimal and tested properly. Once the environment is in production with all the required components in place, over time, adjustments may be required to meet user demands, including changes in VM types or storage options/capabilities.
 
-## Instantiating the lift and shift HPC Cloud architecture
+## Instantiating the lift and shift HPC cloud architecture
 
 Here we provide more details for each architecture component, including pointers to official Azure products, tech blogs with some best practices, git repositories, and links to non-product solutions.
 
-**Quick start.** For a quick start solution to create an HPC environment in the cloud with basic building blocks, we recommend using [Azure CycleCloud Slurm workspace](https://techcommunity.microsoft.com/t5/azure-high-performance-computing/introducing-azure-cyclecloud-slurm-workspace-preview/ba-p/4158433).
+**Quick start.** For a quick start solution to create an HPC environment in the cloud with basic building blocks, we recommend using [Azure CycleCloud Slurm workspace](https://techcommunity.microsoft.com/t5/azure-high-performance-computing/introducing-azure-cyclecloud-slurm-workspace-preview/ba-p/4158433).

articles/high-performance-computing/lift-and-shift-production-level-overview.md

@@ -5,8 +5,8 @@ author: tomvcassidy
 ms.author: tomcassidy
 ms.date: 08/30/2024
 ms.topic: how-to
-ms.service: 
-services: 
+ms.service: azure-virtual-machines
+ms.subservice: hpc
 ---
 
 # Production-level environment migration guide overview
@@ -20,7 +20,7 @@ In this article and the following articles, we guide you through a product-level
 
 You need an Azure subscription to provision cloud resources.
 
-## Migrating from on-premises to the cloud: Production level
+## Migrating from on-premises to the cloud: production level
 
 After the proof-of-concept phase, planning is required to get ready for creating a production-level HPC environment. This new environment can represent part of the on-premises infrastructure (for example, an HPC cluster from a group of clusters or queue/partition from an existing cluster), or the entire computing capability.
 
@@ -34,7 +34,6 @@ Due to component dependencies, the deployment of this HPC cloud environment is b
 1. Compute nodes' specifications;
 1. End user entry point.
 
-In the following articles, we cover each deployment step and the components involved. In the descriptions of the components, we highlight their relevant dependencies in more detail. It is also worth noting that the component deployment steps can be executed in several ways. We provide a few tips to help get started with the deployment components via the Azure portal. But at a production level, we recommend the creation of an environment deployer that leverages Infrastructure-as-code (e.g. via bicep, Terraform, or Azure CLI). By doing so, one can create an environment in an automated and replicable fashion.
+In the following articles, we cover each deployment step and the components involved. In the descriptions of the components, we highlight their relevant dependencies in more detail. It's also worth noting that the component deployment steps can be executed in several ways. We provide a few tips to help get started with the deployment components via the Azure portal. But at a production level, we recommend the creation of an environment deployer that leverages infrastructure-as-code (for example, via bicep, Terraform, or Azure CLI). By doing so, one can create an environment in an automated and replicable fashion.
 
 For each step, certain topics need to be assessed before starting the migration process.
-

articles/high-performance-computing/lift-and-shift-proof-of-concept.md

@@ -5,8 +5,8 @@ author: tomvcassidy
 ms.author: tomcassidy
 ms.date: 08/30/2024
 ms.topic: how-to
-ms.service: 
-services: 
+ms.service: azure-virtual-machines
+ms.subservice: hpc
 ---
 
 # Proof-of-concept migration overview
@@ -20,8 +20,8 @@ In this article, we guide you through a proof-of-concept migration.
 
 You need an Azure subscription to provision cloud resources.
 
-## Migrating from on-premises to the cloud: Proof-of-concept (PoC)
+## Migrating from on-premises to the cloud: proof-of-concept (PoC)
 
 We recommend starting with a proof-of-concept (PoC) by provisioning a simple cluster in Azure, using Azure CycleCloud as a resource orchestrator, with one well-known scheduler, such as Slurm, PBS, or LSF. This approach allows one to start understanding Azure technology, assess the functionality of user applications, and investigate performance/costs trade-offs in comparison to the on-premises environment.
 
-If one is flexible with the job scheduler, or already uses Slurm scheduler, we recommend using Azure CycleCloud Slurm workspace, which is an offering that helps create a CycleCloud based cluster, with Slurm scheduler, and the basic setup for networking and storage options available. Some details on this process are available in the Resource Orchestrator section from this document.
+If one is flexible with the job scheduler, or already uses Slurm scheduler, we recommend using Azure CycleCloud Slurm workspace, which is an offering that helps create a CycleCloud based cluster, with Slurm scheduler, and the basic setup for networking and storage options available. Some details on this process are available in the Resource Orchestrator section from this document.

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

@@ -1,15 +1,15 @@
 ---
-title: "Deployment step 1: Landing zone - Network access component"
+title: "Deployment step 1: basic infrastructure - network access component"
 description: Learn about the configuration of network access during migration deployment step one.
 author: tomvcassidy
 ms.author: tomcassidy
 ms.date: 08/30/2024
 ms.topic: how-to
-ms.service: 
-services: 
+ms.service: azure-virtual-machines
+ms.subservice: hpc
 ---
 
-# Deployment step 1: Landing zone - Network access component
+# Deployment step 1: basic infrastructure - network access component
 
 Mechanism to allow users access cloud environment in a secure way. It's a common practice in production environments to have resources with private IP addresses, and with rules to define how resources should be accessed.
 
@@ -18,31 +18,31 @@ This component should:
 - Allow users to access private network hosting the high performance computing (HPC) environment;
 - Refine network security rules such as source and target ports and IP addresses that can access resources.
 
-## Define Network Needs
+## Define network needs
 
-1. **Estimate cluster size for proper network setup:**
+* **Estimate cluster size for proper network setup:**
    - Different subnets have different ranges of IP addresses.
 
-2. **Security rules:**
+* **Security rules:**
    - Understand how users access the HPC environment and security rules to be in places (for example, ports and IPs open/closed).
 
-### Tools and Services
+## Tools and Services
 
-1. **Private network access:**
+* **Private network access:**
    - In Azure, the two major components to help access private network are Azure Bastion and Azure VPN Gateway.
 
-2. **Network rules:**
+* **Network rules:**
    - Another key component for network setup is Azure Network security groups, which is used to filter network traffic between Azure resources in an Azure virtual network.
 
-3. **DNS:**
+* **DNS:**
    - Azure DNS Private Resolver allows query Azure DNS private zones from an on-premises environment and vice versa without deploying VM based DNS servers.
 
-### Best Practices for Network in HPC Lift and Shift Architecture
+## Best practices for network in HPC lift and shift architecture
 
-1. **Have good understanding on cluster sizes and services to be used:**
+* **Have good understanding on cluster sizes and services to be used:**
    - Different cluster sizes require different IP ranges, and proper planning helps avoid major changes in parts of the infrastructure. Also, some services may need exclusive subnets, and having clarity on those subnets is essential.
 
-### Example Steps for Setup and Deployment
+## Example steps for setup and deployment
 
 Networking is a vast topic itself. In a production level environment, it's good practice to not use public IP addresses. So one could start by testing such functionality by provisioning a VM and using Bastion.
 
@@ -59,7 +59,7 @@ For instance
    - Select option "Deploy Bastion"
    - Once the bastion is provisioned, the VM can be access through it.
 
-#### Resources
+## Resources
 
 - VPN Gateway documentation: [product website](/azure/vpn-gateway/)
 - Azure Bastion documentation: [product website](/azure/bastion/)

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

@@ -1,15 +1,15 @@
 ---
-title: "Deployment step 1: Basic infrastructure - Overview"
+title: "Deployment step 1: basic infrastructure - overview"
 description: Learn about production-level environment migration deployment step one.
 author: tomvcassidy
 ms.author: tomcassidy
 ms.date: 08/30/2024
 ms.topic: how-to
-ms.service: 
-services: 
+ms.service: azure-virtual-machines
+ms.subservice: hpc
 ---
 
-# Deployment step 1: Basic infrastructure - Overview
+# Deployment step 1: basic infrastructure - overview
 
 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.
 
@@ -25,7 +25,7 @@ When provisioning resources in the cloud, it's important to have an understandin
 
 ## Storage
 
-In any Azure subscription, setting up basic storage is essential for managing data, applications, and resources effectively. While more advanced and HPC-specific storage configurations will be addressed separately, a solid foundation of basic storage is crucial for general resource management and initial deployment needs.
+In any Azure subscription, setting up basic storage is essential for managing data, applications, and resources effectively. While more advanced and HPC-specific storage configurations are addressed separately, a solid foundation of basic storage is crucial for general resource management and initial deployment needs.
 
 For details check the description of the following component:
 
@@ -41,4 +41,4 @@ Here we describe each component. Each section includes:
 - Best practices for the component in the context of HPC lift & shift
 - An example of a quick start setup
 
-The goal of the quick start is to have a sense on how to start using the component. As the HPC cloud deployment matures, one is expected to automate the usage of the component, by using, for instance, Infrastructure as Software tools such as Terraform or Bicep.
+The goal of the quick start is to have a sense on how to start using the component. As the HPC cloud deployment matures, one is expected to automate the usage of the component, by using, for instance, Infrastructure as Software tools such as Terraform or Bicep.

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

@@ -1,58 +1,58 @@
 ---
-title: "Deployment step 1: Basic infrastructure - Resource group component"
+title: "Deployment step 1: basic infrastructure - resource group component"
 description: Learn about the configuration of resource groups during migration deployment step one.
 author: tomvcassidy
 ms.author: tomcassidy
 ms.date: 08/30/2024
 ms.topic: how-to
-ms.service: 
-services: 
+ms.service: azure-virtual-machines
+ms.subservice: hpc
 ---
 
-# Deployment step 1: Basic infrastructure - Resource group component
+# Deployment step 1: basic infrastructure - resource group component
 
 Resource groups in Azure serve as containers that hold related resources for an Azure solution. In an HPC environment, organizing resources into appropriate resource groups is essential for effective management, access control, and cost tracking.
 
-## Define Resource Group needs
+## Define resource group needs
 
-1. **Project-Based Grouping:**
+* **Project-based grouping:**
    - Organize resources by project or workload to simplify management and cost tracking.
 
-2. **Environment-Based Grouping:**
+* **Environment-based grouping:**
    - Separate resources into different groups based on environments (for example, development, testing, production) to apply different policies and controls.
 
 ### This component should
 
-- **Organize Resources:**
+* **Organize resources:**
   - Group related HPC resources (for example, VMs, storage accounts, and network components) into resource groups based on project, department, or environment (for example, development, testing, production).
 
-- **Simplify Management:**
+* **Simplify management:**
   - Use resource groups to apply access controls, manage resource lifecycles, and monitor costs efficiently.
 
-### Best Practices for Resource Groups in HPC Lift and Shift Architecture
+## Best practices for resource groups in HPC lift and shift architecture
 
-1. **Consistency in Naming Conventions:**
+* **Consistency in naming conventions:**
    - Establish and follow consistent naming conventions for resource groups to facilitate easy identification and management.
 
-2. **Resource Group Policies:**
+* **Resource group policies:**
    - Apply Azure Policy to resource groups to enforce organizational standards and compliance requirements.
 
-### Example Steps for Resource Group Setup
+## Example steps for resource group setup
 
-1. **Create a Resource Group:**
+1. **Create a resource group:**
 
    - Navigate to the Azure portal.
    - Select "Resource groups" and select "Create."
    - Provide a name for the resource group and select a subscription and region.
    - Select "Review + create" and then "Create."
 
-2. **Add Resources to the Resource Group:**
+2. **Add resources to the resource group:**
 
    - When creating resources (for example, VMs, storage accounts), assign them to the appropriate resource group.
    - Use tags to further organize resources within the group for better cost management and reporting.
 
-### Resources
+## Resources
 
 - Resource Groups Documentation: [product website](/azure/azure-resource-manager/management/manage-resource-groups-portal)
 - Azure Policy Documentation: [product website](/azure/governance/policy/overview)
-- Azure Tags Documentation: [product website](/azure/azure-resource-manager/management/tag-resources)
+- Azure Tags Documentation: [product website](/azure/azure-resource-manager/management/tag-resources)