Onboarding existing VMs

Quick Start lets you identify existing virtual machines (VMs) and import them into BMC Cloud Lifecycle Management so they each become a service offering instance (SOI). During this process, you identify a tenant and user who function as the owner of the SOIs, and you provide information about the service you want to associate with the VMs.

If the VMs you are onboarding are not already enrolled in TrueSight Server Automation (formerly called BMC Server Automation), the onboarding process automatically enrolls the VMs.

This topic includes the following sections:

• Before you begin
• To onboard existing VMs
• To validate onboarded VMs

See the following BMC Communities video (6:08) for an overview about how to onboard virtual machines through the UI and through the API.

https://youtu.be/ROJTyDJEj_E

Before you begin

There are many preconditions you should check before onboarding an existing VM using Quick Start:

_{Back to top}

To onboard existing VMs

1. On the Quick Start welcome page, click Onboard Existing Virtual Machines.
   The VM Onboard page opens. 
   
   
   
   

2. Provide information about the owner to be associated with the VM when it is onboarded.

   Option	Description
   Select Service Type	Type of service that should be associated with the VMs to be onboarded (VMWare, Hyper-V, AWS, or Azure).
   Select Tenant	Tenant organization that should own the SOI.
   Select User	User belonging to the tenant organization that should own the SOI.

    

3. Provide the following service information that is associated with the VM when it is onboarded.

   Option	Description
   Service Offering	A previously defined service offering in the service catalog.

4. Click Next.
   The Search Servers page opens.

5. Provide information to search for VMs to be onboarded.

   Click here for information related to VMware, Hyper-V, or AWS VM onboarding.

   1. Provide information to search for VMs to be onboarded. The information you enter depends on whether you selected VMware or AWS on the previous page.

      Previously Selected Service Type	Option	Description
      VMware	Network Container	The network container that includes the existing VM.
      	Virtual Entity Manager	The vCenter server used to define the VM template for the existing VM.
      Hyper-V	Network Container	The network container that includes the existing VM. Note: The Network Container list contains all the tenants irrespective of the provider type.
      	Virtual Entity Manager	The Hyper-V server used to define the VM template for the existing VM.
      AWS	AWS Account	The AWS account used to create the VM.
      	AWS Environment	The AWS environment used to create the VM.

   2. (Applicable for 4.6.07.003 and later) For VMware, if you want to include the latest servers from TrueSight Server Automation, select Get the latest data from TSSA and then click OK. By default, the option is not selected. When you select this option, the list of servers is refreshed.

      Note: Getting the latest list of servers from TrueSight Server Automation

      When you select the Get the latest data from TSSA option, refreshing the server list might take some time depending on your environment.

   3. Under Available Servers, select the server to onboard. Select a server by clicking  or by clicking in the check boxes to the left of the servers and then clicking .If necessary, you can narrow the list of possible servers by searching. Enter a text string in the Search Servers box and click Search. 
   4. To remove a selected server, click  or click the check box to the left of a selected server and then click .

   5. Click Onboard.
      A page displays the results of the VMs you have selected to onboard. If a VM fails to onboard, the page shows the error messages generated.

      

   Click here for information related to Azure VM onboarding.

   1. In the Search Servers page (as shown in the figure below), provide the following information to search for Azure VMs to be onboarded:

      Option	Description
      AZURE Account	The Azure account used to create the VM.
      AZURE Environment	The Azure environment refers to the Azure Virtual Network used to create the VM.

      

      A list of available Azure servers appears. 

   2. Under Available Servers, select the VMs to onboard. Select a server by clicking  or by clicking in the check boxes to the left of the servers and then clicking .
      
      
      
      If necessary, you can narrow the list of possible servers by searching. Enter a text string in the Search Servers box and click Search.

      Note

      Only the VMs that are not onboarded are displayed in the search results. 

      To remove a selected server, click  or click the check box to the left of a selected server and then click .

   3. Click Onboard.
      A page displays the results of the VMs you have selected to onboard. If a VM fails to onboard, the page shows the error messages generated.
      
      
6. Click Close.

_{Back to top}

To validate onboarded VMs

1. Navigate to the My Services Console and click the Services tab to view the resource details of the cloud service for the onboarded VM, as shown in the following figure:
   
   
   
   Once you onboard the VMs, the status is displayed as Onboarding.
   
   
2. Click the Servers tab and select the onboarded VM to view the details, as shown in the following figure:
   
   
   Once all the VMs are onboarded, the status is displayed as Running.

_{Back to top}