Skip to content

Commit 7a95b9e

Browse files
Court72Court72
authored
Merge pull request #228737 from alfpark/revert-228722-revert-228384-Padmalathas-patch-1
Revert "Revert "EndofFeature-MigrationGuide""
2 parents 5270001 + 493d2ac commit 7a95b9e

4 files changed

+158
-10
lines changed

‎.openpublishing.redirection.json

Lines changed: 0 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -6313,16 +6313,6 @@
63136313
"redirect_url": "/azure/architecture/service-fabric/migrate-from-cloud-services",
63146314
"redirect_document_id": false
63156315
},
6316-
{
6317-
"source_path_from_root": "/articles/batch/batch-custom-image-pools-to-azure-compute-gallery-migration-guide.md",
6318-
"redirect_url": "/azure/batch",
6319-
"redirect_document_id": false
6320-
},
6321-
{
6322-
"source_path_from_root": "/articles/batch/batch-pools-to-simplified-compute-node-communication-model-migration-guide.md",
6323-
"redirect_url": "/azure/batch",
6324-
"redirect_document_id": false
6325-
},
63266316
{
63276317
"source_path_from_root": "/articles/batch/big-compute-resources.md",
63286318
"redirect_url": "/azure/architecture/topics/high-performance-computing/",

‎articles/batch/TOC.yml

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -105,12 +105,18 @@
105105
href: batch-compute-node-environment-variables.md
106106
- name: Feature retirements
107107
items:
108+
- name: Active change, retirement, and end of life notices
109+
href: https://github.com/Azure/Batch/labels/notice
108110
- name: Cloud Service Configuration Pools
109111
href: batch-pool-cloud-service-to-virtual-machine-configuration.md
110112
- name: Batch certificates
111113
href: batch-certificate-migration-guide.md
112114
- name: Pools without public IP addresses (classic)
113115
href: batch-pools-without-public-IP-addresses-classic-retirement-migration-guide.md
116+
- name: Classic compute node communication model
117+
href: batch-pools-to-simplified-compute-node-communication-model-migration-guide.md
118+
- name: VHD and Managed Images
119+
href: batch-custom-image-pools-to-azure-compute-gallery-migration-guide.md
114120
- name: TLS 1.0 and TLS 1.1
115121
href: batch-tls-101-migration-guide.md
116122
- name: Job and pool lifetime statistics

‎articles/batch/batch-custom-image-pools-to-azure-compute-gallery-migration-guide.md

Lines changed: 73 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,73 @@
1+
---
2+
title: Migrate Azure Batch custom image pools to Azure Compute Gallery
3+
description: Learn how to migrate Azure Batch custom image pools to Azure compute gallery and plan for feature end of support.
4+
ms.service: batch
5+
ms.topic: how-to
6+
ms.date: 03/07/2023
7+
---
8+
9+
# Migrate Azure Batch custom image pools to Azure Compute Gallery
10+
11+
To improve reliability, scale, and align with modern Azure offerings, Azure Batch will retire custom image Batch pools specified
12+
from virtual hard disk (VHD) blobs in Azure Storage and Azure Managed Images on *March 31, 2026*. Learn how to migrate your Azure
13+
Batch custom image pools using Azure Compute Gallery.
14+
15+
## Feature end of support
16+
17+
When you create an Azure Batch pool using the Virtual Machine Configuration, you specify an image reference that provides the
18+
operating system for each compute node in the pool. You can create a pool of virtual machines either with a supported Azure
19+
Marketplace image or with a custom image. Custom images from VHD blobs and managed Images are either legacy offerings or
20+
non-scalable solutions for Azure Batch. To ensure reliable infrastructure provisioning at scale, all custom image sources other
21+
than Azure Compute Gallery will be retired on *March 31, 2026*.
22+
23+
## Alternative: Use Azure Compute Gallery references for Batch custom image pools
24+
25+
When you use the Azure Compute Gallery (formerly known as Shared Image Gallery) for your custom image, you have control over
26+
the operating system type and configuration, and the type of data disks. Your shared image can include applications and reference
27+
data that become available on all the Batch pool nodes as soon as they're provisioned. You can also have multiple versions of an
28+
image as needed for your environment. When you use an image version to create a VM, the image version is used to create new
29+
disks for the VM.
30+
31+
Using a shared image saves time in preparing your pool's compute nodes to run your Batch workload. It's possible to use an
32+
Azure Marketplace image and install software on each compute node after allocation. However, using a shared image can lead
33+
to more efficiencies in faster compute node to ready state and reproducible workloads. Additionally, you can specify multiple
34+
replicas for the shared image so when you create pools with many compute nodes, provisioning latencies can be lower.
35+
36+
## Migrate your eligible pools
37+
38+
To migrate your Batch custom image pools from managed image to shared image, review the Azure Batch guide on using
39+
[Azure Compute Gallery to create a custom image pool](batch-sig-images.md).
40+
41+
If you have either a VHD blob or a managed image, you can convert them directly to a Compute Gallery image that can be used
42+
with Azure Batch custom image pools. When you're creating a VM image definition for a Compute Gallery, on the Version tab,
43+
you can select a source option to migrate from, including types being retired for Batch custom image pools:
44+
45+
| Source | Other fields |
46+
|---|---|
47+
| Managed image | Select the **Source image** from the drop-down. The managed image must be in the same region that you chose in **Instance details.** |
48+
| VHD in a storage account | Select **Browse** to choose the storage account for the VHD. |
49+
50+
For more information about this process, see
51+
[creating an image definition and version for Compute Gallery](../virtual-machines/image-version.md#create-an-image).
52+
53+
## FAQs
54+
55+
- How can I create an Azure Compute Gallery?
56+
57+
See the [guide](../virtual-machines/create-gallery.md#create-a-private-gallery) for Compute Gallery creation.
58+
59+
- How do I create a Pool with a Compute Gallery image?
60+
61+
See the [guide](batch-sig-images.md) for creating a Pool with a Compute Gallery image.
62+
63+
- What considerations are there for Compute Gallery image based Pools?
64+
65+
See the [considerations for large pools](batch-sig-images.md#considerations-for-large-pools).
66+
67+
- Can I use Azure Compute Gallery images in different subscriptions or in different Azure AD tenants?
68+
69+
If the Shared Image isn't in the same subscription as the Batch account, you must register the `Microsoft.Batch` resource provider for that subscription. The two subscriptions must be in the same Azure AD tenant. The image can be in a different region as long as it has replicas in the same region as your Batch account.
70+
71+
## Next steps
72+
73+
For more information, see [Azure Compute Gallery](../virtual-machines/azure-compute-gallery.md).

‎articles/batch/batch-pools-to-simplified-compute-node-communication-model-migration-guide.md

Lines changed: 79 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,79 @@
1+
---
2+
title: Migrate Azure Batch pools to the simplified compute node communication model
3+
description: Learn how to migrate Azure Batch pools to the simplified compute node communication model and plan for feature end of support.
4+
ms.service: batch
5+
ms.topic: how-to
6+
ms.date: 03/07/2023
7+
---
8+
9+
# Migrate Azure Batch pools to the simplified compute node communication model
10+
11+
To improve security, simplify the user experience, and enable key future improvements, Azure Batch will retire the classic
12+
compute node communication model on *March 31, 2026*. Learn how to migrate your Batch pools to using the simplified compute
13+
node communication model.
14+
15+
## About the feature
16+
17+
An Azure Batch pool contains one or more compute nodes, which execute user-specified workloads in the form of Batch tasks.
18+
To enable Batch functionality and Batch pool infrastructure management, compute nodes must communicate with the Azure Batch
19+
service. In the classic compute node communication model, the Batch service initiates communication to the compute nodes and
20+
compute nodes must be able to communicate with Azure Storage for baseline operations. In the Simplified compute node
21+
communication model, Batch pools only require outbound access to the Batch service for baseline operations.
22+
23+
## Feature end of support
24+
25+
The simplified compute node communication model will replace the classic compute node communication model after *March 31, 2026*.
26+
The change is introduced in two phases:
27+
28+
- From now until *September 30, 2024*, the default node communication mode for newly created
29+
[Batch pools with virtual networks](./batch-virtual-network.md) will remain as classic.
30+
- After *September 30, 2024*, the default node communication mode for newly created Batch pools with virtual networks will
31+
switch to the simplified.
32+
33+
After *March 31, 2026*, the option to use classic compute node communication mode will no longer be honored. Batch pools
34+
without user-specified virtual networks are generally unaffected by this change and the Batch service controls the default
35+
communication mode.
36+
37+
## Alternative: Use simplified compute node communication model
38+
39+
The simplified compute node communication mode streamlines the way Batch pool infrastructure is managed on behalf of users.
40+
This communication mode reduces the complexity and scope of inbound and outbound networking connections required in the
41+
baseline operations.
42+
43+
The simplified model also provides more fine-grained data exfiltration control, since outbound communication to
44+
*Storage.region* is no longer required. You can explicitly lock down outbound communication to Azure Storage if necessary for
45+
your workflow. For example, autostorage accounts for AppPackages and other storage accounts for resource files or output files
46+
can be scoped appropriately.
47+
48+
## Migrate your eligible pools
49+
50+
To migrate your Batch pools from classic to the simplified compute node communication model, follow this document
51+
from the section entitled
52+
[potential impact between classic and simplified communication modes](simplified-compute-node-communication.md#potential-impact-between-classic-and-simplified-communication-modes).
53+
You can either create new pools or update existing pools with simplified compute node communication.
54+
55+
## FAQs
56+
57+
- Are public IP addresses still required for my pools?
58+
59+
By default, a public IP address is still needed to initiate the outbound connection to the Azure Batch service from compute nodes. If you want to eliminate the need for public IP addresses from compute nodes entirely, see the guide to [create a simplified node communication pool without public IP addresses](./simplified-node-communication-pool-no-public-ip.md)
60+
61+
- How can I connect to my nodes for diagnostic purposes?
62+
63+
RDP or SSH connectivity to the node is unaffected – load balancer(s) are still created which can route those requests through to the node when provisioned with a public IP address.
64+
65+
- Are there any differences in billing?
66+
67+
There should be no cost or billing implications for the new model.
68+
69+
- Are there any changes to Azure Batch agents on the compute node?
70+
71+
An extra agent on compute nodes is invoked in simplified compute node communication mode for both Linux and Windows, `Microsoft.BatchClusters.Agent` and `Microsoft.BatchClusters.Agent.exe`, respectively.
72+
73+
- Are there any changes to how my linked resources from Azure Storage in Batch pools and tasks are downloaded?
74+
75+
This behavior is unaffected – all user-specified resources that require Azure Storage such as resource files, output files, or application packages are made from the compute node directly to Azure Storage. You need to ensure your networking configuration allows these flows.
76+
77+
## Next steps
78+
79+
For more information, see [Simplified compute node communication](./simplified-compute-node-communication.md).

0 commit comments

Comments
 (0)