The Edit vApp Templates tab includes options for setting vApp values for lab templates.

Note:

In addition to editing for individual templates, the vApp Template page includes a bulk action drop-down menu that you can use to perform an action on all vApp templates. The drop-down menu includes the Clear Errors option. When a prepop fails to deploy,VMware Learning Platform marks it as an error and shows the count of errors. The Clear Errors option clears all errors for all vApp templates listed and drops the current count of errors to zero.

Procedure

  1. Click the three vertical dots next to the vApp template you want to edit and click Update to open the Edit vApp Template form for the selected vApp template with the Edit vApp Template tab current.
  2. Set values for your vApp.
    Option Description

    Enabled

    Enables or disables the vApp template.

    If not enabled, then the vApp template cannot deploy prepops or an on-demand lab. This text box is useful when you want to disable prepop deployment for a vApp template hosted in a particular cloud. For example, you might have a vApp hosted in a cloud located in the United States and a clone of that vApp hosted in Europe. In such cases, you might want to deploy prepops only in the vApp hosted in the United States but not in Europe.

    Fixed Size

    If the Fixed Size text box is enabled, then the Refill At and Fill Up values do not display. Instead the Pool Size value displays. The Pool Size value, sets Refill At and Fill Up values to the Pool Size value. Most importantly, if Fixed Size is enabled, then the system keeps the number of running vApps equal to the pool size limit value. As a result, the Fixed size text box allows a tenant admin to ensure that the number of running vApps is constant, regardless of the system refilling prepops. Example Scenario: If the tenant admin were to set the vApp template to a pool size of 10, then:

    • System deploys 10 vApps and sets Refill At and Fill Up to 10.

    • If an end user then starts a lab, the system uses one of the 10 vApps and assigns the vApp to the end user’s entitlement.

    • vApp template continues to have 10 running vApps. If additional end users continue to start labs and use all the deployed vApps from the fixed size pool, then upon an 11th entitlement, the system will return an error.

    Refill At

    Sets value for the least number of available prepops. If the number of available prepops goes below the Refill At value, then the system deploys prepops (refills) until the Refill At value is met.

    Fill up

    Sets value to reach (fill up) for the number of prepops to be deployed.

    Prepops

    Sets the current number of prepops available for the vApp template. If you adjust this number, it adds or removes prepops from the vApp template.

    Concurrent Usage Limit

    The maximum number of vApps, for this template, that the system allows to be running. If a user starts a lab while below the concurrent use limit, then the system allows the user to start the lab. However, if a user starts a lab while the concurrent use limit has been reached, then the system will not allow the user to start the lab. The concurrent use limit increases once a student successfully starts a lab but decreases when a student ends/exits a lab.

    Placement Algorithm

    Specifies the placement algorithm for this vApp template and overrides the tenant-wide placement algorithm as set in the page (within General Options). Placement algorithms are described in the discussion about the Name of Default Prepop Placement Algorithm option.

    Time To Live (Hours) (0 Implies No Limit)

    Specifies the amount of time, in hours, that a prepop can exist before the system deletes it. This text box allows you to specify the amount of time a prepop must be left waiting in the cloud until either the system assigns it to an entitlement or deletes it.

    Note:

    When the system successfully deploys a prepop, it adds a time stamp to the database record. By using the time stamp and the value of the template’s Time to Live text box, the system calculates when it must delete the prepop. When the time to delete the prepop arrives, the prepop becomes eligible for recycling. This recycling will not occur until the next time the job that checks prepop statuses runs, meaning prepops can continue to live past their end of life time by several minutes.

    Auto-Deploy Replacements For Expired Prepops

    If enabled, then the system deploys a new prepop each time a prepop has been undeployed because it has reached its Time To Live limit.

    Note:

    For fixed size pools, auto-redeployment will occur whether this field is enabled or not.

    Assignment Algorithm

    Specifies the assignment algorithm for this vApp template and overrides the tenant-wide placement algorithm as set in the Edit Tenant page (within General Options). Assignment algorithms are described in the discussion about the Name of Default Prepop Placement Algorithm option.

    Assignment Prepop Preference

    Specifies the assignment prepop preference for this vApp template and overrides the tenant-wide prepop preference as set in the Edit Tenant page (within General Options). Prepop preferences are described in the discussion about the Name of Default Prepop Placement Algorithm option.

    Prepop Template Name Example

    Displays an example of a prepop name that was generated with the pattern used by the system. By default, the system uses a single, static pattern for the naming.

    Drain Prepops Tab

    Opens a tab that lists all the cloud org vDCs having the template running within them as prepops. This list allows you to select a specific org vDC to be drained as opposed to draining all prepops.

    • Sync Prepops: Sends a start request is sent for all the prepops currently deployed. If a prepop exists, the start request does nothing. It creates a prepop if one does not exist.

    • Drain All Prepops: Undeploys all prepops and drops the number of deployed prepops to zero.

    • Drain Prepops: Opens a tab that lists all the cloud org vDCs having the template running within them as prepops. This list allows you to select a specific org vDC to be drained as opposed to draining all prepops.

    • Clear Errors: When a prepop fails to deploy, VMware Learning Platform marks it as an error and shows the count of errors. Clearing the errors marks the database record for the error as cleared and drops the current count of errors to zero.

    • Fill Up: Sends a fill up equal to the Fill up value (number of prepops that must be deployed).

    • Set to Refill: Value for the least number of available prepops. If the number of available prepops goes below the Refill At value, then the system deploys prepops (refills) until the Refill At value is met.

    • Reset Average Deploy Time Statistics: VMware Learning Platform monitors the average lab deployment time and continuously updates the average as end users continue to start (deploy) labs. This is the estimated deployment time an end user sees when launching a lab. Reset Average Deploy Time Statistics clears the statistics for the selected template to restart the calculation for the average deploy time. You can enable display of the average deploy time statistics on the vApp Template List. Doing so allows you to easily know which are the slowest vApp templates and so which to reset.

      Note:

      You can click Reset all average deployment time statistics on the vApp Template List to reset all the vApp templates at once.

    • More Details: Displays details of the selected vApp template.

  3. Click Update.