Creating a Runbook

The runbook is the inventory file we'll use to catalog a group of VMs and define the parameters of our runbook automation task. 

1. Navigate to the Velostrata Manager page at https://VELO_APPLIANCE_IP.

2. Click the Runbook Automation icon.

3. Log in as apiuser

A. Your password will be your Velostrata subscription ID or your GCP billing ID.

4. Once you're successfully logged in, click the Create New Runbook button.

5. When the menu appears, you'll select your Source which will either be vSphere or AWS

Continue along by expanding the appropriate section below:

On-Prem as Source

1. [Mandatory] For Source Datacenter, select the on-premises VMware datacenter whose inventory you'd like to export. This list of options is automatically populated from the vCenter you registered this Velostrata appliance with. 

2. [Optional] For Target Cloud Extension, select your cloud destination (where VMs will be migrated to). You can populate this later if you'd like. 

3. [Optional] For Target Network, based on your target cloud extension selection, you can also choose the  Populate with Cloud Extension Defaults option. You can populate these fields later, too, if desired. 

Note: This pre-populates the target subnet and GCP network tags with CE defaults for workloads.

4. Click Create

AWS as Source

1. Select the required Source Cloud Details, which is where VMs will be migrated from.

2. [Mandatory] Enter one or more Filter by Source Tags by entering Name and Value pairs. This is how we'll pull the VM information out of AWS. Therefore, you must have this tag pair in AWS as well for any VM you wish to inventory. For example, you would need a tag named "WORKLOAD" with value "CRM" in AWS, and then you would define that here in this menu, too. You can also use operators, such that tag name equals "WORKLOAD" and the value you specify in Velostrata is the * operator, which would inventory any VM with the WORKLOAD tag from this AWS environment. 

3. [Optional] For Target Network, based on your target cloud extension selection, you can also choose the  Populate with Cloud Extension Defaults option. You can populate these fields later, too, if desired. 

Note: This pre-populates the target subnet and GCP network tags with CE defaults for workloads.

5. Click Create.  

After configuring your options and clicking complete, the runbook inventory file (.csv) is created and you will be prompted to save it locally. 

It will look like this when you open it via your spreadsheet editor: