Using the Discovery Manager

The Cloud Discovery wizard begins with the account selection and testing phase. Specify your cloud provider and select the service account to discover. Discovery allows you to include one or all available sub-accounts (AWS only) on the schedule. Provide the credentials for the cloud service account and test the connection.

1. In the Basic Info pane of the Discovery Manager, select the name of your cloud provider, such as AWS.
2. In the Schedule Name field, enter a unique and descriptive name for this schedule.
   The wizard displays the count of the validated and available MID Servers.
3. If no MID Servers have the Cloud Management capability, click Configure MID Servers and configure a MID Server appropriately.
   1. Navigate to MID Servers > Capabilities.
   2. Select the Cloud Management capability.
      You can also select the ALL capability, which includes Cloud Management by default.
   3. Click Edit in the MID Servers related list, and then add your MID Servers to the capability.
   4. Click Save.
      Your MID Servers are ready to communicate with your cloud service accounts.

      

4. In the Service Accounts pane, select the existing account for the newly named schedule.
   If you select an existing account, the system auto-completes the form with the available information. If you add an account, you must provide the account ID, credentials, and URL, if applicable. For VMware, the URL is mandatory.
   • The AWS account ID is the 12-digit account number.
   • The Azure account ID is the Subscription ID.
   • The IBM account ID is also called the Account ID.
   • The GCP account ID is the Project ID.
   • The VMware account ID is the virtual machine instance UUID.

   Note: VMware discovery can run without a service account. To discover VMware resources, configure the schedule to run on the IP address of the vCenter server.
5. Select the credentials for this cloud service account or add new credentials.
   1. To add a credential, click the plus icon (+).
   2. Select the appropriate cloud credential type from the list.
   3. Complete the form and click Save.
      Note: AWS users can configure AWS to generate temporary credentials for service accounts. This capability eliminates the need to define some credentials on the instance and can be used to increase security on your sub-accounts. For details, see Assume an AWS role for temporary cloud Discovery credentials.

   

6. Click Test Account to validate the account with the details provided.
   Messages in the header bar notify you of the validation results. If you specified a master account and the connection test was successful, the wizard displays a selection screen for any sub-accounts associated with the master account. By default, all current sub-accounts are selected for the schedule and cannot be moved to the Available list.

   Note: If the validation process does not return any sub-accounts or sub-accounts that you added recently, click Refresh Members or re-run the validation process. If validation times-out repeatedly, increase the timeout interval in the cdu.record.watcher.timeout MID Server property.

   

7. To select specific sub-accounts for the schedule, deactivate the auto-select feature.
   By default, all sub-accounts are selected. To disable the feature and to permit the selection of specific datacenters to discover, slide the toggle switch to the left.

   

8. Drag and drop the sub-accounts you want to exclude from the schedule from the Selected list to the Available list.

Discovery displays the list of available datacenters when you validate the service account. Specify which datacenters you want to discover with this schedule.

1. To select the datacenters to discover, click the Select Datacenters phase in the Discovery Manager tab bar.
   By default, all datacenters associated with your service account are selected for the schedule.

   Note: If no datacenters appear, click Refresh Datacenters or re-run the account validation. If validation times-out repeatedly, increase the timeout interval in the cdu.record.watcher.timeout MID Server property.

   

2. To select specific datacenters for the schedule, deactivate the auto-select feature by moving the toggle switch to the left.
3. Drag and drop the datacenters you want to discover from the Available list to the Selected list.
4. Click the next phase in the tab bar.
   Optionally, you can configure IP ranges to discover virtual machines (VM), or move to the schedule phase and complete Cloud Discovery setup.

Virtual machine (VM) Discovery is an optional configuration that performs a deep discovery of the virtual machines identified by the cloud schedule, using the IP addresses of the VMs. VM Discovery is enabled by default in the Discovery Manager wizard.

1. To discover the VMs that are part of the current schedule, click the Discover Virtual Machines (optional) phase in the Discovery Manager tab bar.
   By default, VM discovery is active.
2. Select the MD Server to use.
   The available MID Server selection types are:

   • Auto-Select MID Server: Discovery selects an appropriate MID Server automatically.
   • Specific MID Cluster: Discovery uses the named MID Server cluster.
   • Specific MID Server: Discovery uses the named MID Server.

   

3. To prevent VM Discovery from running, toggle the activation switch to the left.
   The MID Selection Type field disappears.
4. When you have completed this configuration, click the Create Schedule phase in the tab bar.

The final phase in the Discovery Manager wizard creates the schedule that triggers Cloud Discovery.

1. To configure the Cloud Discovery schedule, click Create Schedule in the Discovery Manager tab bar.
   By default, the schedule is active.
2. Configure when and how often the schedule should run and define a timeout threshold if you want to restrict Cloud Discovery to a specific duration.

   

3. To deactivate the schedule, toggle the switch to the left.
   This prevents Cloud Discovery from running.
4. Complete the Cloud Discovery configuration process by selecting one of these options:
   • Finish and Run: Runs Discovery immediately, using the current configuration. All subsequent cloud discoveries run on the schedule you provided.
   • Finish: Exits the wizard and runs Cloud Discovery on the schedule you provided.
5. Open the Discovery Home page and view the results of your cloud Discovery.