Assets

  • Additional Disks

    Users can specify opt four additional disks of unto 1 TB each in the System Builder. When the system is launched, these disks will be added to the base image/template, formatted, and mounted. On Linux systems, the default mount point starts at /cons3rt_disk1 and increments with each disk. An ex...
  • App Bundles

    Users can create bundles of software assets called "App Bundles" to install as a group on systems. Just like Systems, App Bundles include reboot and a build order. Creating an App Bundle Create a System or navigate to one that has already been made Click the "Create App Bundle" button Name you...
  • Asset States

    This article includes information about the lifecycle of an Asset, and how to set asset states to reflect that lifecycle. What are the Asset States In Development: Every asset's initial state. Asset editing is allowed. For software assets, install scripts can be edited and media file can be...
  • Assets with Reboot and Reboot Delay

    Assets with Reboot For each asset on your System, that you add to the System Builder (/kb/assets/system-builder), you can check the Reboot system after installation? checkbox. This tells CONS3RT to reboot the host after the asset has completed installation. This is useful when installing an ap...
  • Asset Tags

    Add Tags to my Assets Asset tags are useful when searching for assets of a specific category, and also to help users find assets that you have created. See below for information on a special asset tag called "Disruptive". You can assign up to 3 tags to each of your assets. To add a tag to one...
  • Asset Types

    Generally speaking, Assets are the "things" that make up a CONS3RT system. There are three categories of Assets: Resource, Component and Composite. Resource Assets Elements of a cloud that are registered to be available for use by the CONS3RT. The Cloud Administrator controls which resources t...
  • Cloning Systems/Scenarios/Deployments

    Cloning Overview Cloning creates a Copy of the System, Scenario, or Deployment asset in your builders. Once a clone is created, you can save an identical copy, or modify and tweak it as needed. Cloning is useful when: You need to launch another instance of an existing Deployment Run You need ...
  • Create a Scenario

    Step 1: Add Systems First you need to create a System (/kb/assets/system-builder) From the Main Navigation Menu, click Systems Select the System you would like to add to your Scenario Click the Add to Scenario Builder button If you would like to add another copy of the same System, click the Add...
  • Create a System Design

    Create a System Design by clicking the Add button next to Systems on the main menu. This builder allows you to design a virtual or physical host. Your System design will include: An Operating System (OS), a specific OS template, or a physical device Minimum number of CPUs Minimum Memory (RAM) ...
  • Creating Component Assets

    Component assets are developed by you and other CONS3RT users, and imported into CONS3RT for use in your Systems. The three categories of Component Assets are: Software Assets Source Code Assets Test Case Assets There are 2 options for creating component assets: Use the Software Asset Builder ...
  • Deleting an Asset

    If an asset does not have any dependencies, it can be deleted. To delete an asset: On the asset page, look for the gear-shaped icon on the right side next to "Details". You will see it if you have appropriate permissions (/articles/user-permissions) Click the gear icon, and select Delete this ...
  • Deployment Properties & Environment Variables

    Deployment Properties Each system in a deployment has a set of properties that contains CONS3RT and user defined values for use in the configuration and execution of Systems. These allow for customization in software and test assets. Contents The CONS3RT properties are values generated on eac...
  • Docs and Licenses

    The documentation for an Asset is available in the UI by selecting "Help" tab on the Asset's main page. This section should provide all relevant information and necessary requirements that pertain to your Asset. As the owner of an Asset, you are the only one who can edit its documentation. This c...
  • Exportable Asset Bundles

    CONS3RT provides the capability to export an asset bundle for each host in your deployment runs. These asset bundles can deploy on virtual or physical hosts that are disconnected from CONS3RT (e.g. an offline, disconnected lab). The Asset Bundle Installer feature is available as an add-on featu...
  • Favorites

    The "favorite" feature allows you to tag the Assets you use most frequently. To do so, mouse over the desired Asset and click the star button.
  • HmC Storage Service

    HmC provides a persistent storage service as an add-on feature. Use this for: Storing persistent data Data accessibility across deployment runs Loading large files (> 3 GB) as part of asset Data backup To request the storage service for your team, please enter a support ticket (mailto:suppor...
  • Importing Your Asset Zip File

    One you have created an asset zip file according to this article (/articles/creating-component-assets), you'll want to import it into CONS3RT. To do so: Click the "+" button at the top-right as shown Note: if you do not see the "+" button, you may need permissions added in your project If you...
  • Instance Limits

    An instance limit sets how many concurrent instances of an Asset that can be provisioned. This can be used to manage usage of an Asset that is constrained due to licensing considerations or physical resources. Once a instance limit is reached, the deployment runs will remain in the scheduled st...
  • Platform Enforcement

    If an operating system platform is specified for an asset, CONS3RT will prevent the install of that asset on the wrong platform. For example, the System Builder will not let a user save a Windows Firefox asset on a Linux operating system. This requires the optional field applicationOsFamilyType t...
  • Sharing Assets with Another Project

    Sharing assets is a two step process. First, your Project Owner must add the Project you'd like to share assets with as a Trusted Project using these instructions (/articles/setting-up-a-trusted-project) Edit the sharing on the asset you would like to share, using the following instructions: Na...
  • Snapshots

    Snapshots Bottom Line - CONS3RT offers a better approach! ...to the traditional notion of snapshots. As your team begins transitioning from traditional cloud hosting environments, there will inevitably be a time when when the team wants to "snapshot" a system. When the team refers to snapshots ...
  • Software Asset Builder

    You can create your own software assets using the software asset builder. To get started: From the main menu, click on the Software section Click the "+" button at the top-right as shown. Note: if you do not see the "+" button, you may need permissions (/kb/project-manager/user-permissions) ad...
  • Source Code Assets

    Source Code Assets are used to check out, build and install uncompiled code. Pointers to the external source repositories are contained in each asset. When built, these assets contain the latest updates to source. Scripts are executed on CONS3RT's SourceBuilder service, and then installed on your...
  • Updating Software Assets

    In order to update a Software Component Asset, there are a few criteria that must be satisfied: The Asset State must be In Development (this is the default state) more info on asset states (/kb/assets/asset-states) You must be a member of the Project that owns the asset, and the Project is selec...
  • Using a Custom Template

    A note on using Custom Templates The best way to configure your environment is using automation, instead of custom templates. Using automated configuration will increase the flexibility, repeatability, and maintainability of your systems. CONS3RT provided a suite of tools to enable you to full...
  • Using Physical Machines

    CONS3RT gives you the power to register and provision physical machines into your cloudspace. Registering a Physical Machine Physical machines are registered to a single cloudspace. Thus, only projects that have access to the cloudspace can access and deploy the physical machine. To regis...
  • Using PowerShell

    Windows asset developers can now call PowerShell scripts as the primary install method for assets. Powershell scripts are also editable in the GUI. To use Powershell Set the installScript property in your asset.properties file to your "install-script.ps1" file Add your asset to a System and D...
  • Visibility

    Visibility defines which other users can see and access your Assets in the library. Only the Owner can change its visibility. The four levels of visibility are: "No One Else (sharing disabled)" - Only the original creator can see or use this asset. This is the default setting for any newly impo...