Topic: Deployments
Editing Interfaces For Deployment Runs
To edit your network interfaces for your Deployment Run, follow these steps: Under “Configure Resources” choose the Edit option. From here you can edit, add and delete interfaces. The edit button allows you to make an interface Primary or Internal. Primary means it is the default network and Internal means it has no access to internet. You can also add custom MAC addresses under the edit option. First 3 octets will be 00:50:56.
To edit your network interfaces for your Deployment Run, follow these steps: Under “Configure Resources” choose the Edit option. From here you can edit, add and delete interfaces. The edit button allows you to make an interface Primary or Internal. Primary means it is the default network and Internal means it has no access to internet. You can also add custom MAC addresses under the edit option. First 3 octets will be 00:50:56.
Dedicated Hosts
Dedicated Hosts Users can request a dedicated host via a support ticket. The Arcus team will create the dedicated host and make it available. In your support request, please specify: Cloud Type (AWS or Azure) Desired Dedicated Host Family/Type Note: RHEL 7, 8, and 9 are not available When launching deployment runs, users can select the dedicated host: Capabilities Deployment runs can be provisioned on top of dedicated hosts. Deployment runs on dedicated hosts can perform host actions (resize, reboot, shutdown, snapshot, restore).
Dedicated Hosts Users can request a dedicated host via a support ticket. The Arcus team will create the dedicated host and make it available. In your support request, please specify: Cloud Type (AWS or Azure) Desired Dedicated Host Family/Type Note: RHEL 7, 8, and 9 are not available When launching deployment runs, users can select the dedicated host: Capabilities Deployment runs can be provisioned on top of dedicated hosts. Deployment runs on dedicated hosts can perform host actions (resize, reboot, shutdown, snapshot, restore).
Power Scheduling
Power Scheduling is a new capability in Arcus 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 Arcus Teams that have typical working hours and want to save money or resources by powering off non-essential VMs during non-work hours and weekends. Looking for information on Basic Power Management in Arcus?
Power Scheduling is a new capability in Arcus 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 Arcus Teams that have typical working hours and want to save money or resources by powering off non-essential VMs during non-work hours and weekends. Looking for information on Basic Power Management in Arcus?
RAM, CPU, and Boot Disk
Adjusting RAM, CPU, and Boot Disk There may come a time when you need to update the RAM, CPU or Boot Disk on your systems to free up resources, improve system performance, or simply plan for the future. Through Arcus it is very easy to make changes quickly. There are likely three timeframes in which you might want to make these changes: during system design, while launching, and after a deployment run is reserved.
Adjusting RAM, CPU, and Boot Disk There may come a time when you need to update the RAM, CPU or Boot Disk on your systems to free up resources, improve system performance, or simply plan for the future. Through Arcus it is very easy to make changes quickly. There are likely three timeframes in which you might want to make these changes: during system design, while launching, and after a deployment run is reserved.
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 Cloudspace: Cons3rt Net - Used for Remote Access connections and CONS3RT communications Primary Net - Used for connecting to the Internet and for communications with other hosts in your Cloudspace Retrieve my IP Addresses Navigate to the Runs page, and click on your Run For each host in the run, there is a card containing info about the host and Remote Access connections, click on a host to view details At the top of the details page, there is is a list of networks and the IP address on each network.
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 Cloudspace: Cons3rt Net - Used for Remote Access connections and CONS3RT communications Primary Net - Used for connecting to the Internet and for communications with other hosts in your Cloudspace Retrieve my IP Addresses Navigate to the Runs page, and click on your Run For each host in the run, there is a card containing info about the host and Remote Access connections, click on a host to view details At the top of the details page, there is is a list of networks and the IP address on each network.
Deployment Run Credentials
Arcus 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 username, but you can set this to anything you’d like. Password – Please provide a complex password. Please keep in mind that operating system password criteria are not satisfied, your run may fail to provision.
Arcus 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 username, but you can set this to anything you’d like. Password – Please provide a complex password. Please keep in mind that operating system password criteria are not satisfied, your run may fail to provision.
Custom Properties
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 and HP Fortify allow users to customize their scans using Custom Properties. How to Set Custom Properties Custom Properties are defined when you create a Deployment or launch a Run See these instructions for creating a Deployment and defining Custom Properties See these instructions for setting Custom Properties when launching your Run How to Use Custom Properties Custom properties are made available in the deployment properties files which exist on each system deployed by Arcus.
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 and HP Fortify allow users to customize their scans using Custom Properties. How to Set Custom Properties Custom Properties are defined when you create a Deployment or launch a Run See these instructions for creating a Deployment and defining Custom Properties See these instructions for setting Custom Properties when launching your Run How to Use Custom Properties Custom properties are made available in the deployment properties files which exist on each system deployed by Arcus.
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 X button next to the recurring schedule that you would like to remove More Help Review this process with our video tutorials:
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 X button next to the recurring schedule that you would like to remove More Help Review this process with our video tutorials:
Launching a "Quick Build"
Overview 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 follow the Run wizard to launch your Run! Considerations Quick Build is designed for convenience and speed, but has a few catches to keep in mind:
Overview 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 follow the Run wizard to launch your Run! Considerations Quick Build is designed for convenience and speed, but has a few catches to keep in mind:
Launching a Deployment
Once you have created your Deployment, there are 3 sections to the launch wizard that you will need to fill out. Base Settings 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, a description is optional. Credentials: A username and password is required. Please use a good complex password, some Operating Systems will fail if the password provided is too simple.
Once you have created your Deployment, there are 3 sections to the launch wizard that you will need to fill out. Base Settings 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, a description is optional. Credentials: A username and password is required. Please use a good complex password, some Operating Systems will fail if the password provided is too simple.
Creating a Deployment
A DEPLOYMENT consists of: Scenario (optional) Elastic Test Asset (optional) Custom Properties 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 need permissions in your project Step 1: Add a Scenario (Optional) A scenario contains an ordered list of systems to deploy into one of your cloudspaces.
A DEPLOYMENT consists of: Scenario (optional) Elastic Test Asset (optional) Custom Properties 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 need permissions in your project Step 1: Add a Scenario (Optional) A scenario contains an ordered list of systems to deploy into one of your cloudspaces.
Power Management
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 click Runs, then under My Runs or Browse, select your Deployment Run. You are at the Deployment Run page. To access the power buttons, click on the card for the host you’d like to manage.
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 click Runs, then under My Runs or Browse, select your Deployment Run. You are at the Deployment Run page. To access the power buttons, click on the card for the host you’d like to manage.
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 Nightly builds Weekly weekend performance tests Monthly redeployments Create a Recurring Schedule From the main navigation menu, select Deployments Click on the Deployment that you would like to schedule, or type the ID in the search box at the top right Click the Launch button Select a Cloudspace, and fill out the deployment run options as usual Click the Set Recurring Schedule button next to Repeats In the pop up windows, select Hourly, Daily, Weekly, or Monthly Set the details, including the end date, or number of occurences Click Save Click Next and follow the steps to launch your deployment as usual View a 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, where existing and expired recurring schedules are listed Remove a Recurring Schedule Follow these instructions to remove a recurring schedule More Help Review this process with our video tutorials:
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 Nightly builds Weekly weekend performance tests Monthly redeployments Create a Recurring Schedule From the main navigation menu, select Deployments Click on the Deployment that you would like to schedule, or type the ID in the search box at the top right Click the Launch button Select a Cloudspace, and fill out the deployment run options as usual Click the Set Recurring Schedule button next to Repeats In the pop up windows, select Hourly, Daily, Weekly, or Monthly Set the details, including the end date, or number of occurences Click Save Click Next and follow the steps to launch your deployment as usual View a 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, where existing and expired recurring schedules are listed Remove a Recurring Schedule Follow these instructions to remove a recurring schedule More Help Review this process with our video tutorials:
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 Cloudspace at the top-left Click on My Runs at the top-left Click on the Deployment Run you would like to cancel On the Deployment Run page, click the Cancel button at the top-right Release a Run Releasing a Run that is “Available” or in an “Error” state will:
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 Cloudspace at the top-left Click on My Runs at the top-left Click on the Deployment Run you would like to cancel On the Deployment Run page, click the Cancel button at the top-right Release a Run Releasing a Run that is “Available” or in an “Error” state will: