Skip to content

Commit fa9c6e9

Browse files
Merge pull request #279535 from Padmalathas/Batch-updates
Fixes to the code and TOC
2 parents 19816f5 + 45deb56 commit fa9c6e9

File tree

5 files changed

+11
-49
lines changed

5 files changed

+11
-49
lines changed

articles/batch/batch-aad-auth.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
title: Authenticate Azure Batch services with Microsoft Entra ID
33
description: Learn how to authenticate Azure Batch service applications with Microsoft Entra ID by using integrated authentication or a service principal.
44
ms.topic: how-to
5-
ms.date: 06/25/2024
5+
ms.date: 06/27/2024
66
ms.custom: has-adal-ref, subject-rbac-steps
77
---
88

@@ -327,7 +327,7 @@ To authenticate with a service principal from Batch .NET:
327327
1. Call this method by using the following code. The `.default` scope ensures that the application has permission to access all the scopes for the resource.
328328

329329
```csharp
330-
var token = await GetAccessToken(new string[] { "BatchResourceId/.default" });
330+
var token = await GetAccessToken(new string[] { $"{BatchResourceUri}/.default" });
331331
```
332332

333333
1. Construct a **BatchTokenCredentials** object that takes the delegate as a parameter. Use those credentials to open a **BatchClient** object. Then use the **BatchClient** object for subsequent operations against the Batch service:

articles/batch/batch-apis-tools.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
title: APIs and tools for developers
33
description: Learn about the APIs and tools available for developing solutions with the Azure Batch service.
44
ms.topic: conceptual
5-
ms.date: 06/26/2024
5+
ms.date: 06/27/2024
66
---
77

88

@@ -40,7 +40,7 @@ Your applications and services can issue direct REST API calls or use one or mor
4040
| --- | --- | --- | --- | --- | --- |
4141
| **Batch REST** |[Azure REST API - Docs](/rest/api/batchservice/) |N/A |- |- | [Supported versions](/rest/api/batchservice/batch-service-rest-api-versioning) |
4242
| **Batch .NET** |[Azure SDK for .NET - Docs](/dotnet/api/overview/azure/batch) |[NuGet](https://www.nuget.org/packages/Microsoft.Azure.Batch/) |[Tutorial](tutorial-parallel-dotnet.md) |[GitHub](https://github.com/Azure-Samples/azure-batch-samples/tree/master/CSharp) | [Release notes](https://aka.ms/batch-net-dataplane-changelog) |
43-
| **Batch Python** |[Azure SDK for Python - Docs](/python/api/overview/azure/mgmt-datafactory-readme?view=azure-python&preserve-view=true) |[PyPI](https://pypi.org/project/azure-batch/) |[Tutorial](tutorial-parallel-python.md)|[GitHub](https://github.com/Azure-Samples/azure-batch-samples/tree/master/Python/Batch) | [Readme](https://github.com/Azure/azure-sdk-for-python/blob/master/sdk/batch/azure-batch/README.md) |
43+
| **Batch Python** |[Azure SDK for Python - Docs](/python/api/overview/azure/batch) |[PyPI](https://pypi.org/project/azure-batch/) |[Tutorial](tutorial-parallel-python.md)|[GitHub](https://github.com/Azure-Samples/azure-batch-samples/tree/master/Python/Batch) | [Readme](https://github.com/Azure/azure-sdk-for-python/blob/master/sdk/batch/azure-batch/README.md) |
4444
| **Batch JavaScript** |[Azure SDK for JavaScript - Docs](/javascript/api/overview/azure/batch) |[npm](https://www.npmjs.com/package/@azure/batch) |[Tutorial](batch-js-get-started.md) |- | [Readme](https://github.com/Azure/azure-sdk-for-js/tree/main/sdk/batch/batch) |
4545
| **Batch Java** |[Azure SDK for Java - Docs](/java/api/overview/azure/batch) |[Maven](https://search.maven.org/search?q=a:azure-batch) |- |[GitHub](https://github.com/Azure-Samples/azure-batch-samples/tree/master/Java) | [Readme](https://github.com/Azure/azure-batch-sdk-for-java)|
4646

articles/batch/batch-pool-node-error-checking.md

Lines changed: 5 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: Pool and node errors
33
description: Learn about background operations, errors to check for, and how to avoid errors when you create Azure Batch pools and nodes.
4-
ms.date: 06/10/2024
4+
ms.date: 06/27/2024
55
ms.topic: how-to
66
---
77

@@ -142,7 +142,10 @@ After you make sure to retrieve any data you need from the node or upload it to
142142

143143
You can delete old completed jobs or tasks whose task data is still on the nodes. Look in the `recentTasks` collection in the [taskInformation](/rest/api/batchservice/computenode/get#taskinformation) on the node, or use the [File - List From Compute Node](/rest/api/batchservice/file/listfromcomputenode) API. Deleting a job deletes all the tasks in the job. Deleting the tasks in the job triggers deletion of data in the task directories on the nodes, and frees up space. Once you've freed up enough space, reboot the node. The node should move out of `unusable` state and into `idle` again.
144144

145-
To recover an unusable node in [VirtualMachineConfiguration](/rest/api/batchservice/pool/add#virtualmachineconfiguration) pools, you can remove the node from the pool by using the [Pool - Remove Nodes](/rest/api/batchservice/pool/removenodes) API. Then you can grow the pool again to replace the bad node with a fresh one. For [CloudServiceConfiguration](/rest/api/batchservice/pool/add#cloudserviceconfiguration) pools, you can reimage the node by using the [Compute Node - Reimage](/rest/api/batchservice/computenode/reimage) API to clean the entire disk. Reimage isn't currently supported for [VirtualMachineConfiguration](/rest/api/batchservice/pool/add#virtualmachineconfiguration) pools.
145+
To recover an unusable node in [VirtualMachineConfiguration](/rest/api/batchservice/pool/add#virtualmachineconfiguration) pools, you can remove the node from the pool by using the [Pool - Remove Nodes](/rest/api/batchservice/pool/removenodes) API. Then you can grow the pool again to replace the bad node with a fresh one.
146+
147+
> [!Important]
148+
> Reimage isn't currently supported for [VirtualMachineConfiguration](/rest/api/batchservice/pool/add#virtualmachineconfiguration) pools.
146149
147150
## Next steps
148151

articles/batch/batch-virtual-network.md

Lines changed: 1 addition & 40 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
title: Provision a pool in a virtual network
33
description: Learn how to create a Batch pool in an Azure virtual network so that compute nodes can communicate securely with other VMs in the network, such as a file server.
44
ms.topic: how-to
5-
ms.date: 12/06/2023
5+
ms.date: 06/27/2024
66
---
77

88
# Create an Azure Batch pool in a virtual network
@@ -37,10 +37,6 @@ To allow compute nodes to communicate securely with other virtual machines, or w
3737

3838
* Multiple pools can be created in the same virtual network or in the same subnet (as long as it has sufficient address space). A single pool can't exist across multiple virtual networks or subnets.
3939

40-
Other virtual network requirements differ, depending on whether the Batch pool is in the `VirtualMachineConfiguration`
41-
or `CloudServiceConfiguration`. `VirtualMachineConfiguration` for Batch pools is recommended, because `CloudServiceConfiguration`
42-
pools are [deprecated](https://azure.microsoft.com/updates/azure-batch-cloudserviceconfiguration-pools-will-be-retired-on-29-february-2024/).
43-
4440
> [!IMPORTANT]
4541
> Batch pools can be configured in one of two node communication modes. Classic node communication mode is
4642
> where the Batch service initiates communication to the compute nodes.
@@ -110,41 +106,6 @@ You can also disable default remote access on these ports through configuring [p
110106

111107
Outbound to BatchNodeManagement.*region* service tag is required in `classic` pool communication mode if you're using Job Manager tasks or if your tasks must communicate back to the Batch service. For outbound to BatchNodeManagement.*region* in `simplified` pool communication mode, the Batch service currently only uses TCP protocol, but UDP might be required for future compatibility. For [pools without public IP addresses](simplified-node-communication-pool-no-public-ip.md) using `simplified` communication mode and with a node management private endpoint, an NSG isn't needed. For more information about outbound security rules for the BatchNodeManagement.*region* service tag, see [Use simplified compute node communication](simplified-compute-node-communication.md).
112108

113-
## Pools in the Cloud Services Configuration
114-
115-
> [!WARNING]
116-
> Cloud Services Configuration pools are [deprecated](https://azure.microsoft.com/updates/azure-batch-cloudserviceconfiguration-pools-will-be-retired-on-29-february-2024/). Use Virtual Machine Configuration pools instead.
117-
118-
Requirements:
119-
120-
- Supported Virtual Networks: Classic Virtual Networks only.
121-
- Subnet ID: when specifying the subnet using the Batch APIs, use the *resource identifier* of the subnet. The subnet identifier is of the form:
122-
123-
`/subscriptions/{subscription}/resourceGroups/{group}/providers/Microsoft.ClassicNetwork/virtualNetworks/{network}/subnets/{subnet}`
124-
125-
- Permissions: the `Microsoft Azure Batch` service principal must have the `Classic Virtual Machine Contributor` Azure role for the specified Virtual Network.
126-
127-
### Network security groups for Cloud Services Configuration pools
128-
129-
The subnet must allow inbound communication from the Batch service to be able to schedule tasks on the compute nodes, and it must allow outbound communication to communicate with Azure Storage or other resources.
130-
131-
You don't need to specify an NSG, because Batch configures inbound communication only from Batch IP addresses to the pool nodes. However, If the specified subnet has associated NSGs and/or a firewall, configure the inbound and outbound security rules as shown in the following tables. If communication to the compute nodes in the specified subnet is denied by an NSG, the Batch service sets the state of the compute nodes to **unusable**.
132-
133-
Configure inbound traffic on port 3389 for Windows if you need to permit RDP access to the pool nodes. This rule isn't required for the pool nodes to be usable.
134-
135-
**Inbound security rules**
136-
137-
| Source IP addresses | Source ports | Destination | Destination ports | Protocol | Action |
138-
| --- | --- | --- | --- | --- | --- |
139-
| Any <br /><br />Although this rule effectively requires *allow all*, the Batch service applies an ACL rule at the level of each node that filters out all non-Batch service IP addresses. | * | Any | 10100, 20100, 30100 | TCP | Allow |
140-
| Optional, to allow RDP access to compute nodes. | * | Any | 3389 | TCP | Allow |
141-
142-
**Outbound security rules**
143-
144-
| Source | Source ports | Destination | Destination ports | Protocol | Action |
145-
| --- | --- | --- | --- | --- | --- |
146-
| Any | * | Any | 443 | Any | Allow |
147-
148109
## Create a pool with a Virtual Network in the Azure portal
149110

150111
After you've created your Virtual Network and assigned a subnet to it, you can create a Batch pool with that Virtual Network. Follow these steps to create a pool from the Azure portal: 

articles/batch/credential-access-key-vault.md

Lines changed: 1 addition & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -2,16 +2,14 @@
22
title: Use certificates and securely access Azure Key Vault with Batch
33
description: Learn how to programmatically access your credentials from Key Vault using Azure Batch.
44
ms.topic: how-to
5-
ms.date: 06/13/2024
5+
ms.date: 06/27/2024
66
ms.custom: devx-track-azurepowershell
77
---
88

99
# Use certificates to securely access Azure Key Vault with Batch
1010

1111
> [!WARNING]
1212
> Batch account certificates as detailed in this article are [deprecated](batch-certificate-migration-guide.md). To securely access Azure Key Vault, simply use [Pool managed identities](managed-identity-pools.md) with the appropriate access permissions configured for the user-assigned managed identity to access your Key Vault. If you need to provision certificates on Batch nodes, please utilize the available Azure Key Vault VM extension in conjunction with pool Managed Identity to install and manage certificates on your Batch pool. For more information on deploying certificates from Azure Key Vault with Managed Identity on Batch pools, see [Enable automatic certificate rotation in a Batch pool](automatic-certificate-rotation.md).
13-
>
14-
> `CloudServiceConfiguration` pools do not provide the ability to specify either Managed Identity or the Azure Key Vault VM extension, and these pools are [deprecated](https://azure.microsoft.com/updates/azure-batch-cloudserviceconfiguration-pools-will-be-retired-on-29-february-2024/). You should migrate to `VirtualMachineConfiguration` pools which provide the aforementioned alternatives.
1513
1614
In this article, you'll learn how to set up Batch nodes with certificates to securely access credentials stored in [Azure Key Vault](../key-vault/general/overview.md).
1715

0 commit comments

Comments
 (0)