Skip to content

Commit e8bc6ed

Browse files
authored
Merge pull request #197 from bhgtankita/patch-2
Update how-to-create-attach-compute-cluster.md
2 parents ec061e0 + ea8769c commit e8bc6ed

File tree

1 file changed

+6
-0
lines changed

1 file changed

+6
-0
lines changed

articles/machine-learning/how-to-create-attach-compute-cluster.md

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -57,6 +57,9 @@ Start at [Azure Machine Learning studio](https://ml.azure.com).
5757

5858
---
5959

60+
> [!NOTE]
61+
> When configuring a Virtual Network (VNet) located in a different resource group from your Azure Machine Learning workspace, be aware that resources such as Network Security Groups (NSGs), Public IPs, and Load Balancers will be created in the same resource group as the VNet. This behavior ensures proper network management and isolation.
62+
6063
## What is a compute cluster?
6164

6265
Azure Machine Learning compute cluster is a managed-compute infrastructure that allows you to easily create a single or multi-node compute. The compute cluster is a resource that can be shared with other users in your workspace. The compute scales up automatically when a job is submitted, and can be put in an Azure Virtual Network. Compute cluster supports **no public IP** deployment as well in virtual network. The compute executes in a containerized environment and packages your model dependencies in a [Docker container](https://www.docker.com/why-docker).
@@ -74,6 +77,9 @@ Compute clusters can run jobs securely in either a [managed virtual network](how
7477

7578
* Azure allows you to place *locks* on resources, so that they can't be deleted or are read only. **Do not apply resource locks to the resource group that contains your workspace**. Applying a lock to the resource group that contains your workspace prevents scaling operations for Azure Machine Learning compute clusters. For more information on locking resources, see [Lock resources to prevent unexpected changes](/azure/azure-resource-manager/management/lock-resources).
7679

80+
> [!Caution]
81+
> Applying resource locks, such as "Delete" or "Read-only", to the resource group containing your compute clusters can prevent operations like creation, scaling, or deletion of these clusters. Ensure that resource locks are configured appropriately to avoid unintended disruptions.
82+
7783
## Create
7884

7985
**Time estimate**: Approximately five minutes.

0 commit comments

Comments
 (0)