Cancel or Release a Deployment Run
Cancel a Building Run
Cancelling a Run that is building will:
Stop the Deployment process
Destroy VMs included in the Run
Release CPU, RAM, and storage resources
Delete history of the Deployment Run
To cancel a Run:
First ensure the correct Project is selected on the top-right.
Select the Clou...
Create a Recurring Schedule
You can create a recurring schedule to launch your Deployment automatically at defined intervals. Here are some example uses for recurring scheduled deployments:
Hourly continuous integration runs
Weekly weekend performance tests
Create a Recurring Schedule
Creating a Deployment
A DEPLOYMENT consists of:
Elastic Test Asset (optional)
To create a Deployment:
On the main menu, click the Add button next to Deployments, this will open the Deployment Builder
Note: If you don't see the "Add" button, notify your project owner(s) that you ...
Custom Properties are used to provide properties to your asset install scripts that can be used for a variety of use cases:
Dynamically pass a git branch to an asset that clones source code
Set log level for an application
Provide credential information
Some Elastic Test Tools (ETTs) like Nessus...
Deployment Run Credentials
CONS3RT requires that users provide username and password credentials before submitting a Deployment Run.
How to Set Credentials
After clicking the Launch button, there is a section on the Base Settings page to provide credentials.
Username -- This will be pre-populated with your account use...
IP Addresses in your Run
After launching your Deployment, your VMs will deploy with IP addresses assigned to networks within your Cloudspace. See this article for more information about Cloudspace IP address ranges and the use of static IP addresses. Typically, each VM will have a network interface on 2 networks in your ...
Launching a Deployment
Once you have created your Deployment, there are 3 sections to the launch wizard that you will need to fill out.
Select Cloudspace: It needs to be a cloudspace that you have access to and one that has sufficient resources for your deployment.
Name/Description: The name is required...
Launching a "Quick Build"
You have the option to launch your Run directly from a System or Scenario without building a Deployment. The preferred method is to build out a Deployment, and Launch your Run from the Deployment.
To launch a "Quick Build", navigate to your System or Scenario, click the "Launch" button, and fol...
Power management functions are available to the owner of the run or any project member with the "Can manage project trusts and resources" permission set.
You can access power buttons for individual hosts in "Available" Deployment Runs. To access the power buttons:
From the main navigation menu...
Power Scheduling is a new capability in HmC that allows project leaders to set a default schedule used to automatically power off and power on deployed virtual systems for cost and energy savings. Typical use cases generally include HmC Teams that have typical working hours and want to save money...
RAM and CPU
Adjusting RAM and CPU
There may come a time when you need to update the RAM and CPU on your systems to free up resources, improve system performs better, or just planning for the future. Through CONS3RT it is very easy to quickly make these changes. There are likely three timeframes in which you...
Remove a Recurring Schedule
To remove an existing or expired recurring schedule:
From the main navigation menu, select Deployments
Click on the Deployment, or type the ID in the search box at the top right
Click on the Settings tab
Under Recurring Schedules you can see the existing or expired recurring schedules
Click the ...