Part 4: Create Batch
A Batch is the third and final level in the Stream → Subject → Batch hierarchy. It represents a group of students who will access lab environments during a specific time period (for example: Morning Slot, Data Analytics – Section A, or Friday 3–5 PM Lab).
Batches play a critical role in AI Labs because they:
- Control how students are grouped for lab sessions.
- Enforce resource policies using Batch Quota and Per User Quota.
- Ensure resource availability by applying start/stop schedules.
- Map students to the correct SKU subscription, ensuring each batch uses only assigned capacity.
- Isolate workloads so students only see the resources and notebooks belonging to their batch.
In the hierarchy:
- A Stream defines the academic specialization.
- A Subject defines the course taught within that specialization.
- A Batch defines the actual student group that will receive notebooks and run workloads.
This makes the Batch the point where actual lab provisioning happens, connecting students to GPU notebooks and enforcing quotas, schedules, and SKU allocations.
What Lab Admins See After Login
- The Lab Admin is automatically placed in the subject project (for example,
subject-data-analytics). - The navigation is limited to the modules relevant to managing student lab activities.
- Under Developer Hub → Administrator → New Notebook, select AI Lab Batch profile available for batch creation.
This profile is used to define batches, associate them with appropriate SKUs, and configure lab schedules for students.
AI Lab Batch – Detailed Parameter Reference¶
Basic Details¶
| Parameter | Description | Example Value |
|---|---|---|
| Name | Specifies the unique name for the batch. This name identifies the batch within the subject. | data-analytics-batch-1 |
| Description | Optional field used to record additional information about the batch. | Morning lab slot (10–12 PM) |
| Workspace | The workspace associated with the subject project. This is auto-populated. | Auto-populated (default-workspace-subject-data-analytics) |
Profiles¶
| Parameter | Description | Example Value |
|---|---|---|
| SKUs | Lists SKUs previously procured through AI Lab Subscription. Determines the notebook type available to students in this batch. | AI Lab-H100-80GB SKU selected from dropdown |
Quota¶
| Parameter | Description | Example Value |
|---|---|---|
| Batch Quota | Total number of notebook instances allowed under this batch. Controls overall capacity. | 10 (10 students × 1 notebook each) |
| Per User Quota | Maximum notebooks each student can create. | 1 (each student gets 1 notebook) |
Schedule – Start Time¶
| Parameter | Description | Example Value |
|---|---|---|
| Day of Month | The specific calendar date on which the batch’s resources should start. If set, the start action triggers only on that date each month. | 10 |
| Hour | The hour of the day (0–23) when the batch should activate and students can begin using lab resources. | 10 |
| Minute | The minute within the hour when the activation should begin. | 20 |
| Month | The month of the year when the start schedule should run. Useful when labs are tied to semester or term-based cycles. | 2 (February) |
| Day of Week | The specific day(s) of the week when the batch should start. Used when labs repeat weekly (e.g., every Monday). | MON |
Schedule – Stop Time¶
| Parameter | Description | Example Value |
|---|---|---|
| Day of Month | The calendar date on which batch resources should stop. When set, the deactivation happens only on that date each month. | 30 |
| Hour | The hour of the day (0–23) when the batch should stop and lab resources should no longer be accessible to students. | 23 |
| Minute | The minute within the hour when the stop action should happen. | 20 |
| Month | The month of the year when the stop schedule should run. Useful for end-of-term shutdowns or defined training windows. | 10 (October) |
| Day of Week | The specific weekday(s) on which the batch should stop. Helps enforce weekly shutdown cycles (e.g., every Thursday). | THU |
Schedule Timezone¶
| Parameter | Description | Example Value |
|---|---|---|
| Timezone | Timezone used for start/stop schedules — ensures labs activate at the correct local time. | Asia/Kolkata |
User Management¶
| Parameter | Description | Example Value |
|---|---|---|
| Batch Admins | Email IDs of users who manage the batch. Must be existing users. Comma-separated values or CSV supported. | assistant.prof@smluniv.edu |
| Batch Students | Students belonging to this batch. If they don’t exist, accounts are created automatically during provisioning. | student1@univ.edu, student2@univ.edu, … (or upload CSV for 10 students) |
Others¶
| Parameter | Description | Example Value |
|---|---|---|
| groupssousers | Defines whether IDP-authenticated users should be auto-promoted as batch admins. Typically preconfigured based on university’s identity setup. | false |
Batch Deployment¶
After the Lab Admin submits the batch configu ration, the deployment status and output are displayed. This confirms whether the batch has been created successfully under the subject project.
Once the batch is deployed, students assigned to the batch can log in to the console with restricted access.
What Students See After Login
- Students land directly in the Developer Hub.
- Only the workspace for the assigned batch is visible to them.
- Navigation is limited to the modules relevant for lab activities (for example, Notebook).
The scoped access ensures that students can:
- View their assigned batch
- Access the lab resources associated with the selected SKU
- Begin provisioning lab environments within the permitted quotas and schedule