Instance Types

CONS3RT now allows users to select a specific Instance Type when launching a Deployment in CONS3RT using AWS Commercial, AWS GovCloud, Azure Commercial, or Azure Gov.

For more information on launching a Deployment or launching from Clouds other than AWS or Azure, please see this article.

Setting an Instance Type in Azure

Base Settings
  1. Click the Launch or Finish and Launch button on the Deployment that needs to be launched. This will bring up the launch wizard
  2. Select a Cloudspace: This needs to be an Azure Cloudspace that you have access to, and one that has sufficient resources for your Deployment.
  3. Enter a Name/Description: A name is required, but a description is optional.
  4. Credentials: A username and a password are required. Please use a strong, complex password as some Operating Systems will fail if the password provided is too simple. Click here for more details.
  5. Scheduling: You can schedule your Run to launch now or at a later date/time. You can also specify a Recurring Schedule.
  6. Other Options:
  • Check the Automatically release deployment resources checkbox if you'd like CONS3RT to destroy your VMs after the Deployment and Tests have completed. Doing so is useful if you only need Test Results, or if you don't need your VM once the Assets have completed.
  • Check the Retain the deployment on error checkbox (recommended) to leave your VMs available for troubleshooting if a problem occurs with your Run.
  • Turn on Deployment Run Lockif you'd like to prevent other users in your Project from releasing your Run. See this article for details about how to release or cancel a "locked" Run.
Resources

Several factors determine which Instance Types are made available. Certain instance types will be available based on the OS type chosen at the System level. The minimum “hardware” requirements specified at the System level will also limit the instance types made visible in this section. For example, if a user selects 4 CPUs and 8GBs of RAM as the minimum specification at the System level, the instance type selections will be limited to 4 CPU/8GB RAM or above and will not let the user select an instance smaller than the minimum specification.

  1. Select a specific Azure Instance Type Family on the left drop down (If this field is left blank, the CONS3RT UI will default to Best Matches) Azure Instance Type Selection 1
  2. Select a specific Azure Instance Type on the right drop down (this field is modified by the Instance Type Family as described in the previous step) Azure Instance Type Selection 2
  3. Additional Options:
  • Check the Requires vGPUs checkbox if you'd like CONS3RT to attach a virtual GPU to enhance the performance of graphics-intensive applications on virtualized Systems.
  • Check the Requires nested virtualization checkbox if your Run needs virtual systems that run virtualization hypervisor software – such as VMWare ESXi, Xen, KVM, etc.
Custom Properties

The Custom Properties field will be pre-populated with the data you set at Deployment creation time (or the previous Run of this Deployment). You may edit properties at this time. Click here for more information about Custom Properties.

Note: If you need to delete a custom property, leave the property name with an empty value like this: PROPERTY=

Submit your Run!

When you are satisfied with your Run options, click the Submit button! Doing so will initiate your Deployment Run. CONS3RT will launch your Run in accordance with your System, Scenario, and Deployment specifications, as well as the Run options you have selected (as described in this article). To access your Run, select Runs from the main navigation menu, and this will be the most recent Run shown on your My Runs page.

Setting an Instance Type in AWS

Base Settings
  1. Click the Launch or Finish and Launch button on the Deployment that needs to be launched. Doing so will bring up the launch wizard
  2. Select a Cloudspace: This needs to be an AWS Cloudspace that you have access to, and one that has sufficient resources for your Deployment.
  3. Enter a Name/Description: A name is required, but a description is optional.
  4. Credentials: A username and a password are required. Please use a strong, complex password as some Operating Systems will fail if the password provided is too simple. Click here for more details.
  5. Scheduling: You can schedule your Run to launch nowor at a later date/time. You can also specify a Recurring Schedule.
  6. Other Options:
  • Check the Automatically release deployment resources checkbox if you'd like CONS3RT to destroy your VMs after the Deployment and Tests have completed. This is useful if you only need Test Results, or don't need your VM once the assets have completed.
  • Check the Retain the deployment on error checkbox (recommended), this will leave your VMs available for troubleshooting if a problem occurs with your Run.
  • Turn on Deployment Run Lock: if you'd like to prevent other users in your Project from releasing your Run. See this article for details about how to release or cancel a "locked" Run.
Resources

Several factors determine which Instance Types are made available. Certain instance types will be available based on the OS type chosen at the System level. The minimum “hardware” requirements specified at the system level will also limit the instance types made visible in this section. e.g. If a user selects 4 CPUs and 8GBs of RAM as the minimum specification at the System level, the instance type selections will be limited to 4 CPU/8GB RAM or above and will not let the user select an instance smaller than the minimum specification.

  1. Select a specific AWS Instance Type Family on the left drop down (If this field is left blank the CONS3RT UI will default to Best Matches) AWS Instance Type Selection 1
  2. Select a specific AWS Instance Type on the right drop down (this field is modified by the Instance Type Family as described in the previous step) AWS Instance Type Selection 2
  3. Additional Options:
  • Check the Requires vGPUs checkbox if you'd like CONS3RT to attach a virtual GPU to enhance the performance of graphics-intensive applications on virtualized systems.
  • Check the Requires nested virtualization checkbox if your Run needs virtual systems that run virtualization hypervisor software – such as VMWare ESXi, Xen, KVM, etc.
Custom Properties

The Custom Properties field will be pre-populated with the data you set at Deployment creation time (or the previous Run of this Deployment). You may edit properties at this time. Click here for more information about Custom Properties.

Note: If you need to delete a custom property, leave the property name with an empty value like this: PROPERTY=

Submit your Run!

When you are satisfied with your Run options, click the Submit button! This will initiate your Deployment Run. CONS3RT will launch your Run in accordance with your System, Scenario, and Deployment specifications, and use the Run options you selected as described in this article. To access your Run, select Runs from the main navigation menu, and this will be the most recent Run shown on your My Runs page.

More Help

Learn more about Remote Access in CONS3RT with our YouTube tutorials: