Skip to content

Deployment Settings

Deployment Settings in HyLabs determines the deployment pattern for the reservations.

Supported deployment settings:

  1. On Demand: Refers to configurations where deployment of reservation will occur before a predefined time reservation start.

  2. Specific Window: The deployment for reservation will happen in the predefined reservation window.

On Demand Deployment

Configuring deployment settings as On Demand provides following configurable options to reservation administrator:

  • Deployment Type: To be set as On Demand

  • Keep VM: Configuration to decide if VMs being deployed should be kept as powered on or powered off post deployment.

  • Preparation Time: Time in minutes. Deployed DVMs will be prepared (Powered-On) as per configured preparation time. E.g., 5 mins preparation times will start the DVMs 5 minutes before the reservation start. In case if the VMs are not yet deployed, even the deployment of reservation will start with preparation time. Maximum value allowed in 180 mins.

  • Self-study Preparation Time: Specific to self-study reservations. Self-study reservations will be prepared in given time. Being volatile in nature, Self-study Preparation Time should be kept high enough to allow Cloning, Sysprep and Power Operation. Maximum value allowed in 180 mins.

  • Deployment Time: Time in minutes. HyLabs will start deploying (cloning) VMs as per the configured Deployment Time. E.g., if deployment time is configured as 60 mins, controller will start the deployment 60 mins before the reservation start time. If multiple reservations/ reservations with higher number of units to be deployed, the configuration should be kept high enough to support the cloning and Sysprep time for the reservations. Maximum value allowed in 540 minutes.

  • Preparation Fail Retry Count: Number of times, for which Controller should attempt to deploy a failed reservation. E.g., 3 retry count, enables controller to attempt for 3 times to deploy a reservation.

Specific Window

Deployment in specific window refers to process where all the deployments will be scheduled for a specific time slot.

  • Deployment Type: To be set as Specific Window

  • Keep VM: Configuration to decide if VMs being deployed should be kept as powered on or powered off post deployment.

  • Preparation Time: Time in minutes. Deployed DVMs will be prepared (Powered-On) as per configured preparation time. E.g., 5 mins preparation times will start the DVMs 5 minutes before the reservation start. In any case if the VMs are not yet deployed, even the deployment of reservation will start with preparation time. Maximum value allowed in 180 mins.

  • Self-study Preparation Time: Specific to self-study reservations. Self-study reservations will be prepared in given time. Being volatile in nature, Self-study Preparation Time should be kept high enough to allow (Cloning, Sysprep and Power Operation). Maximum value allowed in 180 mins.

  • Deployment Start Time: Specific time to start the DVMs deployment.

  • Deployment End Time: End time to stop provisioning. Please note all the started deployments will be completed, once started.

  • Next Deployment Start Time: Next scheduled deployment start time.

  • Next Deployment End Time: Next scheduled deployment end time.

  • Specific Days: Option to specify days on which deployment should be scheduled.

  • Number of Concurrent Deployments: Number of parallel replicas cloning tasks to be executed on configured provider. This should be considering as per the available resources.

  • Preparation Fail Retry Count: Number of times, for which Controller should attempt to deploy a failed reservation. E.g., 3 retry count, enables controller to attempt for 3 times to deploy a reservation.

Important for Specific Window Deployment

  1. Self-study deployments will always be deployed as per Self-study preparation time and will not follow specific window defined.

  2. Course Self-study deployments for volatile course reservations will be deployed as per preparation time instead of specific time window.

  3. There is no priority of reservation deployments, HyLabs will randomly pick and deploy the VMs out of the scheduled reservations.

  4. If a reservation is not deployed within specified time window, then it will be deployed in next time window if there are not schedules until next deployment cycle.

    1. If there is a schedule before next deployment cycle, then it will get deployed as per the preparation time.