- Print
- DarkLight
Overview
In this document, we will explain the capacity limits of CloudLabs VM Labs and how they relate to the limits and quotas of Azure. We will also provide some tips and FAQs to help you manage your resources effectively.
CloudLabs Limits
CloudLabs does not have limits on the number of labs, students, templates, images, or any other CloudLabs resources as long as an Azure quota is available. You can create and run as many labs as you need and invite as many students as you want without worrying about CloudLabs limits.
However, CloudLabs does depend on Azure for the underlying infrastructure, and Azure has its limits and quotas that apply to CloudLabs VM Labs. Therefore, you need to be aware of these limits and quotas and how to manage them to avoid any issues or errors when using CloudLabs VM Labs.
Azure Limits
Azure limits are the maximum number of resources that you can create or use in a given Azure subscription, region, or resource group. These limits are set by Azure to ensure fair and efficient use of the cloud resources and to prevent abuse or misuse of the service. You may find Azure limits here.
If you run into any Azure service limits, please work with your CloudLabs account manager to obtain additional subscriptions/tenants for your requirements.
Azure Quota
Azure quota is the amount of resources that you are allowed to use or create in a given Azure subscription or region within a certain time period. Azure quota is different from Azure limits because Azure quota can vary depending on the availability and demand of the resources and can change over time.
The Azure quota applies to CloudLabs VM Labs as well, since CloudLabs uses Azure resources to create and run the labs. For example, the Azure quota determines how many VMs of a certain size or type (SKU) you can create or use in a region.
You can view the Azure quota for your subscription and region in the CloudLabs portal. You can also request to increase some of these quotas by contacting CloudLabs Support. If you need more resources for your labs, the CloudLabs team will work with Microsoft to meet your quota needs.
Quota Tracking in the CloudLabs Portal
Quota tracking capabilities are coming soon to the CloudLabs portal. Until then, please work with the support team to track your quota or get a direct report.
Tips and FAQs
If you run into Azure quota issues when creating or running a lab, you can try changing the VM SKU to a different size or type that has more quota available in your region. You can use the CloudLabs portal to check the available quota for different VM SKUs in your region.
If you need more Azure quota for a certain VM SKU or resource, you can request an increase from CloudLabs support. CloudLabs will work with Microsoft on your request. However, this may take some time, and there is no guarantee that your request will be approved. Therefore, you should plan and request the quota increase well before you need it.
If you use GPU-enabled VMs for your labs, you should be aware that the GPU quota may be hard to get by, especially in some regions. GPU quotas are in high demand, and Azure may not have enough capacity to fulfill your request. Therefore, you should plan in advance and request the GPU quota increase well before you need it, or consider using a different region or VM SKU that has more GPU quota available.
If you use your own Azure subscription (BYOS) for CloudLabs VM Labs, you are responsible for managing your Azure quota and limits and requesting any increase from Azure support. CloudLabs support cannot help you with Azure quota or limit issues if you use your subscription.
A quota report will be available in the CloudLabs portal UI soon, which will show you the current and available quota for your subscription and region and help you manage your resources better. Until then, you can use the Azure portal to check your quota.
A quota is by region, which means that you have a separate quota for each Azure region that you use for your labs. You can use different regions to create and run your labs if you have enough quotas in those regions. However, you should also consider the network latency and data transfer costs that may occur when using different regions.