Skip to content

Commit be3c64a

Browse files
authored
Merge pull request #217686 from RoseHJM/als-v1-to-v2
Migrate from v1 to v2
2 parents 5281095 + d6c40e2 commit be3c64a

File tree

3 files changed

+139
-2
lines changed

3 files changed

+139
-2
lines changed

articles/lab-services/TOC.yml

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -125,10 +125,12 @@
125125
href: lab-plan-setup-guide.md
126126
- name: Lab creation guide
127127
href: setup-guide.md
128+
- name: Transition to August 2022 Update
129+
href: migrate-to-2022-update.md
128130
- name: Create & configure lab plans (admin)
129131
items:
130132
- name: Request core limit increase
131-
href: how-to-request-capacity-increase.md
133+
href: how-to-request-capacity-increase.md?tabs=Labplans
132134
- name: Determine Usage and Quota
133135
href: how-to-determine-your-quota-usage.md
134136
- name: Create and manage lab plans

articles/lab-services/lab-services-whats-new.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ ms.custom: devdivchpfy22
88

99
# What's new in Azure Lab Services August 2022 Update
1010

11-
We've made fundamental improvements for the service to boost performance, reliability, and scalability. In this article, we'll describe all the great changes and new features that are available in this preview!
11+
We've made fundamental improvements for the service to boost performance, reliability, and scalability. In this article, we'll describe all the great changes and new features that are available in this update!
1212

1313
## Overview
1414

@@ -116,6 +116,7 @@ Let's cover each step to get started with the August 2022 Update in more detail.
116116

117117
## Next steps
118118

119+
- As an admin, [Migrate to August 2022 Update](migrate-to-2022-update.md)
119120
- As an admin, [create a lab plan](tutorial-setup-lab-plan.md).
120121
- As an admin, [manage your lab plan](how-to-manage-lab-plans.md).
121122
- As an educator, [create a lab](tutorial-setup-lab.md).
Lines changed: 134 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,134 @@
1+
---
2+
title: Moving from lab accounts to lab plans
3+
titleSuffix: Azure Lab Services
4+
description: 'Learn how to transition from Azure Lab Services to Azure Lab Services August 2022 Update.'
5+
ms.topic: how-to
6+
ms.author: rosemalcolm
7+
author: RoseHJM
8+
ms.date: 11/30/2022
9+
---
10+
11+
# Transition from lab accounts to the improved Azure Lab Services August 2022 Update
12+
13+
This article applies to users of Azure Lab Services with labs created with a lab account. If you are a brand new user to Azure Lab Services, start with [create a lab plan](tutorial-setup-lab-plan.md).
14+
15+
In this article, you'll learn the sequence to getting started using the features and resources made available beginning in the August 2022 update. The important update to Azure Lab Services August 2022 includes enhancements that boost performance, reliability, and scalability. It also gives you more flexibility in the way you manage labs, use capacity, and track costs.
16+
17+
>[!Important]
18+
> While you don't have to migrate to the August 2022 update of Azure Lab Services yet, we do recommend you begin using the update for all new labs.
19+
20+
A big part of the August 2022 update is centered around the fact that the concept *lab plans* replaces *lab accounts* in the August 2022 Update. Although similar in functionality, there are some fundamental differences between the two concepts. The lab plan serves as a collection of configurations and settings that apply to the labs created from it. Also since the August 2022 update, a lab is an Azure resource in its own right and a sibling resource to lab plans. You can read more about the differences between lab plans and lab accounts in [What's new in Lab Services?](./lab-services-whats-new.md#lab-plans-replace-lab-accounts).
21+
22+
If you're moving from the current version of Azure Lab Services to the August 2022 Update, there's likely to be a time when you're using both your existing lab accounts and using the newer lab plans. And that's ok as both are still supported, can coexist in your Azure subscription, and can even share the same external resources.
23+
24+
## Transition path at-a-glace
25+
26+
There is a bit of a mental shift to transitioning to the Azure Lab Services Update from August 2022.
27+
28+
This checklist highlights the sequence at a high-level:
29+
30+
> [!div class="checklist"]
31+
> - Create a lab plan
32+
> - Request capacity for your lab plans
33+
> - Configure shared resources
34+
> - Create additional lab plans
35+
> - Validate images
36+
> - Create and publish labs
37+
> - Update cost management reports
38+
39+
40+
## 1. Create a lab plan
41+
42+
To begin using the update, you'll need to create a lab plan.
43+
44+
If you don't already have a lab plan, you can create a temporary lab plan for requesting capacity, and delete the plan afterwards. Because capacity is assigned to your subscription, it's not affected when you create or delete lab plans. The first time you create a lab plan, a special Microsoft-managed Azure subscription is automatically created. This subscription isn’t visible to you and is used internally to assign your [dedicated capacity](/azure/lab-services/capacity-limits#per-customer-assigned-capacity).
45+
46+
- [Create a lab plan](/azure/lab-services/tutorial-setup-lab-plan).
47+
- This lab plan can be deleted once capacity is requested.
48+
- You don't need to enable advanced networking or images; or assign permissions.
49+
- You can select any region.
50+
51+
In practice, more than one lab plan might be needed depending on your scenario. For example, the math department may only require one lab plan in one resource group. The computer science department might require multiple lab plans. One lab plan can enable advanced networking and a few custom images. Another lab plan can use basic networking and not enable custom images. Multiple lab plans can be kept in the same resource group.
52+
53+
And, since lab accounts and lab plans cannot share capacity, you'll need to request new capacity for lab plans even if you have existing capacity for lab accounts. Before you request capacity, you must have at least one lab plan in your subscription.
54+
55+
## 2. Request capacity
56+
57+
As a customer, you're now assigned your own [dedicated VM cores quota](/azure/lab-services/capacity-limits#per-customer-assigned-capacity). This quota is assigned per-subscription. The initial number of VM cores assigned to your subscription is limited, so you'll need to request a core limit increase. Even if you're already using lab accounts in the current version of Azure Lab Services, you'll still need to request a core limit increase; existing cores in a lab account won't be available when you create a lab plan.
58+
59+
1. Verify the capacity available in your subscription by [determining the current usage and quota](./how-to-determine-your-quota-usage.md).
60+
1. [Request a core limit increase](/azure/lab-services/how-to-request-capacity-increase?tabs=Labplans).
61+
1. If you created a temporary lab plan, you can delete it at this point. Deleting lab plans has no impact on your subscription or the capacity you have available. Capacity is assigned to your subscription.
62+
63+
#### Tips for requesting capacity
64+
65+
The time that it takes to assign capacity varies depending on the VM size, region, and number of cores requested. To ensure you have the resources you require when you need them, you should:
66+
67+
- Request capacity as far in advance as possible.
68+
- Make incremental requests for VM cores rather than making large, bulk requests. Breaking requests for large numbers of cores into smaller requests gives extra flexibility in how those requests are fulfilled.
69+
- For example, when you move from lab accounts to lab plans, you should first request sufficient capacity to set up a few representative labs that serve as a proof-of-concept. Later, you can make additional capacity requests based on your upcoming lab needs.
70+
- If possible, be flexible on the region where you're requesting capacity.
71+
- Capacity remains assigned for the lifetime of a subscription. You only need to request extra capacity if you need more than is already assigned to your subscription.
72+
73+
## 3. Configure shared resources
74+
75+
You can reuse the same Azure Compute Gallery and licensing servers that you use with your lab accounts. Optionally, you can also [configure more licensing servers](/azure/lab-services/how-to-create-a-lab-with-shared-resource) and galleries based on your needs. For VMs that require access to a licensing server, you'll create lab plans with [advanced networking](/azure/lab-services/how-to-connect-vnet-injection#connect-the-virtual-network-during-lab-plan-creation) enabled as shown in the next step.
76+
77+
## 4. Create additional lab plans
78+
79+
While you're waiting for capacity to be assigned, you can continue creating lab plans that will be used for setting up your labs.
80+
81+
1. [Create and configure lab plans](/azure/lab-services/tutorial-setup-lab-plan).
82+
- If you plan to use a license server, don't forget to enable [advanced networking](/azure/lab-services/how-to-connect-vnet-injection#connect-the-virtual-network-during-lab-plan-creation) when creating your lab plans.
83+
- The lab plan’s resource group name is significant because educators will select the resource group to [create a lab](/azure/lab-services/tutorial-setup-lab#create-a-lab).
84+
- Likewise, the lab plan name is important. If more than one lab plan is in the resource group, educators will see a dropdown to choose a lab plan when they create a lab.
85+
1. [Assign permissions](/azure/lab-services/tutorial-setup-lab-plan#add-a-user-to-the-lab-creator-role) to educators that will create labs.
86+
1. Enable [Azure Marketplace images](/azure/lab-services/specify-marketplace-images).
87+
1. [Configure regions for labs](/azure/lab-services/create-and-configure-labs-admin). You should enable your lab plans to use the regions that you specified in your capacity request.
88+
1. Optionally, [attach an Azure Compute Gallery](/azure/lab-services/how-to-attach-detach-shared-image-gallery).
89+
1. Optionally, configure [integration with Canvas](/azure/lab-services/lab-services-within-canvas-overview) including [adding the app and linking lab plans](/azure/lab-services/how-to-get-started-create-lab-within-canvas). Alternately, configure [integration with Teams](/azure/lab-services/lab-services-within-teams-overview) by [adding the app to Teams groups](/azure/lab-services/how-to-get-started-create-lab-within-teams).
90+
91+
If you're moving from lab accounts, the following table provides guidance on how to map your lab accounts to lab plans:
92+
93+
|Lab account configuration|Lab plan configuration|
94+
|---|---|
95+
|[Virtual network peering](/azure/lab-services/how-to-connect-peer-virtual-network#configure-at-the-time-of-lab-account-creation)|Lab plans can reuse the same virtual network as lab accounts. </br> - [Setup advanced networking](/azure/lab-services/how-to-connect-vnet-injection#connect-the-virtual-network-during-lab-plan-creation) when you create the lab plan.|
96+
|[Role assignments](/azure/lab-services/administrator-guide-1#manage-identity) </br> - Lab account owner\contributor. </br> - Lab creator\owner\contributor.|Lab plans include new specialized roles. </br>1. [Review roles](/azure/lab-services/administrator-guide#rbac-roles). </br>2. [Assign permissions](/azure/lab-services/tutorial-setup-lab-plan#add-a-user-to-the-lab-creator-role).|
97+
|Enabled Marketplace images. </br> - Lab accounts only support Gen1 images from the Marketplace.|Lab plans include settings to enable [Azure Marketplace images](/azure/lab-services/specify-marketplace-images). </br> - Lab plans support Gen1 and Gen2 Marketplace images, so the list of images will be different than what you would see if using lab accounts.|
98+
|[Location](/azure/lab-services/how-to-manage-lab-accounts#create-a-lab-account) </br> - Labs are automatically created within the same geolocation as the lab account. </br> - You can't specify the exact region where a lab is created. |Lab plans enable specific control over which regions labs are created. </br> - [Configure regions for labs](/azure/lab-services/create-and-configure-labs-admin).|
99+
|[Attached Azure Compute Gallery (Shared Image Gallery)](/azure/lab-services/how-to-attach-detach-shared-image-gallery-1)|Lab plans can be attached to the same gallery used by lab accounts. </br>1. [Attach an Azure Compute Gallery](/azure/lab-services/how-to-attach-detach-shared-image-gallery). </br>2. Ensure that you [enable images for the lab plan](/azure/lab-services/how-to-attach-detach-shared-image-gallery#enable-and-disable-images).|
100+
|Teams integration|Configure lab plans with [Teams integration](/azure/lab-services/lab-services-within-teams-overview) by [adding the app to Teams groups](/azure/lab-services/how-to-get-started-create-lab-within-teams).|
101+
|[Firewall settings](/azure/lab-services/how-to-configure-firewall-settings-1) </br> - Create inbound and outbound rules for the lab's public IP address and the port range 49152 - 65535.|[Firewall settings](/azure/lab-services/how-to-configure-firewall-settings) </br> - Create inbound and outbound rules for the lab's public IP address and the port ranges 4980-4989, 5000-6999, and 7000-8999.|
102+
103+
## 5. Validate images
104+
105+
Each of the VM sizes has been remapped to use a newer [Azure VM Compute SKU](/azure/lab-services/administrator-guide#vm-sizing). If you're using an [attached compute gallery](/azure/lab-services/how-to-attach-detach-shared-image-gallery), validate each of your customized images with the new VM Compute SKU by publishing a lab with the image and testing common student workloads. Before creating labs, verify that each image in the compute gallery is replicated to the same regions enabled in your lab plans.
106+
107+
## 6. Create and publish labs
108+
109+
Once you have capacity assigned to your subscription, you can [create and publish](/azure/lab-services/tutorial-setup-lab) representative labs to validate the educator and student experience. Creating representative labs is an optional but highly recommended step, which enables you to validate performance based on common student workloads.
110+
111+
### Lab strategies
112+
113+
You cannot migrate existing labs to the August 2022 Update. Instead, you must create new labs. Along with all the new enhancements, the requirement to create new labs provides a good opportunity to revisit your overall lab structure and plan changes where necessary.
114+
115+
- **Delete and recreate labs**
116+
117+
Most schools delete their labs and recreate them each semester (or class session). You can schedule the move to the August 2022 Update during one of these transitions.
118+
119+
- **Reuse existing labs**
120+
121+
Some schools reuse the same labs each class session and change the student roster. With this approach, you must plan the creation of new labs to transition to, typically at the start of a new session.
122+
123+
> [!NOTE]
124+
> Although you cannot migrate existing labs, you can still reuse other assets such as Compute Galleries and images, and any licensing servers.
125+
126+
## 7. Update cost management reports
127+
128+
Update reports to include the new cost entry type, `Microsoft.LabServices/labs`, for labs created using the August 2022 Update. [Built-in and custom tags](/azure/lab-services/cost-management-guide#understand-the-entries) allow for [grouping](/azure/cost-management-billing/costs/quick-acm-cost-analysis) in cost analysis. For more information about tracking costs, see [Cost management for Azure Lab Services](/azure/lab-services/cost-management-guide).
129+
130+
## Next steps
131+
132+
- As an admin, [create a lab plan](tutorial-setup-lab-plan.md).
133+
- As an admin, [manage your lab plan](how-to-manage-lab-plans.md).
134+
- As an educator, [configure and control usage of a lab](how-to-configure-student-usage.md).

0 commit comments

Comments
 (0)