Create a Scenario

Step 1: Add Systems

  • First you need to create a System
  • 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 to Scenario Builder as many times as needed
  • To add another System to your Scenario, follow the same process

Step 2: Scenario Builder

  • Click on the Scenario Builder in the top left of the page (it is the server stack icon)
  • (Optional) set the build order by using the after previous and with previous buttons
  • (Optional) Set the master scenario host by clicking the designate as master checkbox (details below)
  • Click Next
  • Give your Scenario a Name, and optionally a Description, and click Next
  • (Optional) Add Scenario Configuration and Teardown scripts as desired (details below)
  • Click Next
  • Click Create Scenario

Next you should add your Scenario to a Deployment.

What are Scenario Configuration and Teardown scripts?

  • Optional scripts that can be added to each of the systems your scenario
  • Scenario configuration scripts execute during provisioning time, after all asset installs have completed
  • Scenario teardown scripts execute on each system before the deployment run releases (i.e. when you click the "Release" or "Rerun" button)
  • For Linux systems, this is executed as a shell script, so please specify the shebang accordingly (e.g. #!/bin/bash)
  • For Windows systems, this is executed as a Powershell script

Example Scenario Configuration Scripts

  • Additional configuration not contained in an asset
  • Send email, Slack, or other notifications that a system has completed building
  • Notification to other systems in the scenario when a system has completed

Example Scenario Teardown Scripts

  • Cleanup of resources, for example AWS elastic IP addresses
  • Send email, Slack, or other notifications that a system is about to releasing
  • ReST calls to HmC to kick off something when a system releases

What does the Master system do?

  • One system in each scenario is designated as the Master
  • Can run additional Master scenario configuration and teardown scripts
  • Master scenario configuration scripts run after all other scenario configuration scripts have completed
  • Master scenario teardown scripts run after all other scenario teardown scripts have completed
  • For Linux systems, this is executed as a shell script, so please specify the shebang accordingly (e.g. #!/bin/bash)
  • For Windows systems, this is executed as a Powershell script

Example Master Scenario Configuration Scripts

  • Orchestration of tasks across systems in the scenario, after all the systems are built
  • Send email, Slack, or other notifications
  • ReST calls to HmC to update assets, launch additional deployments, etc.

Example Master Scenario Teardown Scripts

  • Cleanup of scenario-wide resources, for example AWS elastic IP addresses
  • Send email, Slack, or other notifications that a system is about to releasing
  • ReST calls to HmC to kick off something when the deployment run releases