|
2 | 2 | title: Labs concepts - Azure Lab Services | Microsoft Docs
|
3 | 3 | description: Learn the basic concepts of Lab Services, and how it can make it easy to create and manage labs.
|
4 | 4 | ms.topic: how-to
|
5 |
| -ms.date: 11/19/2021 |
| 5 | +ms.date: 01/21/2022 |
6 | 6 | ---
|
7 | 7 |
|
8 | 8 | # Labs concepts
|
9 | 9 |
|
10 |
| -This article describes key Lab Services concepts and definitions. |
| 10 | +This article describes key Azure Lab Services concepts and definitions. |
11 | 11 |
|
| 12 | +## Schedules |
| 13 | + |
| 14 | +Schedules are the time slots that an educator creates so the student lab VMs are available for class time. Schedules can be one-time or recurring. Any scheduled time doesn't count against extra time students may be given to complete homework. For more information about providing time for students to do their homework, see [Quota](#quota). A lab can use quota time, scheduled time, or a combination of both. |
| 15 | + |
| 16 | +Scheduled time is commonly used when students are following the professor's directions during class hours. For instructions to add scheduled time to a lab, see [Create and manage schedules for labs in Azure Lab Services](how-to-create-schedules.md). All the student VMs are started with schedules. VMs are started even if a student doesn't log in to a VM. See [Configure automatic shutdown of VMs for a lab](how-to-enable-shutdown-disconnect.md) to help reduce likelihood of accruing costs when a VM isn't being used. Unclaimed VMs aren't started when schedules run. |
| 17 | + |
| 18 | +There are two types of schedules: Standard and Stop only. |
| 19 | + |
| 20 | +- **Standard**. This schedule will start all student VMs at the specified start time and shut down all student VMs at the specified stop time. |
| 21 | +- **Stop only**. This schedule will stop all student VMs at the specified time, even if the VM was manually started by an instructor or student. |
| 22 | + |
12 | 23 | ## Quota
|
13 | 24 |
|
14 |
| -Quota is the time limit (in hours) that an educator can set for a student to use a lab VM. It can be set to 0, or a specific number of hours. If the quota is set to 0, a student can only use the virtual machine when a schedule is running or when an educator manually turns on the virtual machine for the student. |
| 25 | +Quota is the limited of time (in hours) an educator can allow a student to use their VM outside of scheduled time. For example, quota can be used to allow students time to complete homework using a lab VM. If the quota is set to 0, a student can only use the virtual machine when a schedule is running or when an educator manually turns on the virtual machine for the student. |
15 | 26 |
|
16 | 27 | Quota hours are counted when the student starts the lab VM themselves. If an educator manually starts the lab VM for a student, quota hours aren't used for that student.
|
17 | 28 |
|
18 |
| -## Schedules |
| 29 | +A lab can use either quota time, scheduled time, or a combination of both. |
19 | 30 |
|
20 |
| -Schedules are the time slots that an educator can create for the class so the student VMs are available for class time. Schedules can be one-time or recurring. Quota hours aren't used when a schedule is running. A lab can use either quota time or scheduled time, or a combination of both. |
| 31 | +### Automatic shut-down |
21 | 32 |
|
22 |
| -Scheduled time is commonly used when all the students have their own VMs and are following the professor's directions at a set time during the day (like class hours). See [Create and manage schedules for labs in Azure Lab Services](how-to-create-schedules.md) for instructions to add scheduled time to a lab. The downside is that all the student VMs are started and are accruing costs, even if a student doesn't log in to a VM. See [Configure automatic shutdown of VMs for a lab](how-to-enable-shutdown-disconnect.md) to help reduce likelihood of accruing costs when a VM isn't being used. |
| 33 | +Anytime a machine is **Running**, costs are being incurred, even if no one is connected to the VM. You can enable several auto-shutdown cost control features to avoid extra costs when the VMs aren't being used. The are three auto-shutdown policies available in Azure Lab Services. |
23 | 34 |
|
24 |
| -There are three types of schedules: Standard, Start only and Stop only. |
| 35 | +- Disconnect idle virtual machines. |
| 36 | +- Shutdown virtual machines when students disconnect from the virtual machine. |
| 37 | +- Shutdown virtual machines when students don't connect a recently started virtual machine. |
25 | 38 |
|
26 |
| -- **Standard**. This schedule will start all student VMs at the specified start time and shutdown all student VMs at the specified stop time. |
27 |
| -- **Start only**. This schedule will start all student VMs at the specified time. Student VMs won't be stop until a student stops the their VM through the Azure Lab Services portal or a stop only schedule occurs. |
28 |
| -- **Stop only**. This schedule will stop all student VMs at the specified time. |
| 39 | +For more information, see [Configure automatic shutdown of VMs for a lab plan](how-to-configure-auto-shutdown-lab-plans.md). |
29 | 40 |
|
30 | 41 | ## Template virtual machine
|
31 | 42 |
|
32 |
| -A template virtual machine in a lab is a base virtual machine image from which all users’ virtual machines are created. Trainers/lab creators set up the template virtual machine and configure it with the software that they want to provide to training attendees to do labs. When you publish a template VM, Azure Lab Services creates or updates lab VMs based on the template VM. |
| 43 | +A template VM in a lab is a base image from which all users’ VMs are created. Instructors can configure the template VM with the software that they want to provide to lab users. When you publish a template VM, Azure Lab Services creates or updates lab VMs based on the template VM. |
33 | 44 |
|
34 | 45 | With the [January 2022 Update (preview)](lab-services-whats-new.md), labs can now be created from a pre-defined virtual machine image without the need for a template machine.
|
35 | 46 |
|
36 | 47 | ## User profiles
|
37 | 48 |
|
38 |
| -This article describes different user profiles in Azure Lab Services. |
| 49 | +This section describes different user profiles in Azure Lab Services. |
39 | 50 |
|
40 | 51 | ### Lab plan owner
|
41 | 52 |
|
42 |
| -The lab plan owner, typically an IT administrator of organization's cloud resources, is the one who owns the Azure subscription and does the following tasks: |
| 53 | +The lab plan owner is typically an IT administrator of organization's cloud resources. The lab plan owner is the one who owns the Azure subscription and does the following tasks: |
43 | 54 |
|
44 | 55 | - Creates and organizes resource groups to contain lab plans and labs.
|
45 |
| -- Sets up a lab plan(s) for your organization. |
| 56 | +- Creates lab plan(s) for your organization. |
46 | 57 | - Manages and configures policies across all labs.
|
47 | 58 | - Gives permissions to people in the organization to create a lab under the lab plan.
|
48 | 59 |
|
49 | 60 | ### Educator
|
50 | 61 |
|
51 |
| -Typically, users such as a teacher or an online trainer, create labs using a pre-created lab plan. An educator does the following tasks: |
| 62 | +Typically, a teacher or an online trainer, create labs using a pre-created lab plan. An educator does the following tasks: |
52 | 63 |
|
53 | 64 | - Creates a lab.
|
54 | 65 | - Creates virtual machines in the lab.
|
|
0 commit comments