Guidelines for lab templates in VMware Lab Platform

As a best practice, use the following guidelines when you set up lab templates for VMware Lab Platform.

Right size the workload

To maximize the cost efficiency while still providing seamless experience to lab users, size the virtual machines efficiently.

To function optimally, use as few virtual CPUs as possible for the application.
Avoid configuring virtual machines with more than 4 virtual CPUs.
Note:
Virtual machine with more than 8 virtual CPUs is not supported.
Do not under provision memory as it leads to paging or swapping within the virtual machine and impacts the performance, but also do not over provision memory, which results in excessive waste of the resources.

To conserve lab resources after a lab template is added to a catalog, delete or power off the working copy. Unlike VMware vSphere, when a lab template is added to a catalog in a virtual cloud director, a copy is made.
For a successful lab deployment, ensure that the source lab template virtual machine is gracefully shut down (lab template stop command) before you add it to the catalog as a template.

To import a lab template in VMware Lab Platform, use the process described in Upload a VM or an ISO file in VMware Lab Platform . VMware Lab Platform provides a reliable mechanism to import a virtual machine or lab template exports (OVF/OVA), and ISOs files.
If the lab template was created and exported from the same vCloud Director environment, it might require some clean-up after the import is finished. Review and reconfigure the network configuration after the import is finished.
Importing individual virtual machines results in the creation of a single virtual machine lab template. You must then copy or move the virtual machine lab template as required.

The following ports and protocols are supported for lab templates: