Onboarding Microsoft Hyper-V resources

This topic explains how to onboard Microsoft Hyper-V resources into BMC Cloud Lifecycle Management. It includes the following sections:

Overview of the onboard process

BMC Cloud Lifecycle Management QuickStart and REST API capability lets you identify existing virtual machines (VMs)  in the Microsoft Hyper-V portal 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 Hyper-V VMs. 

For onboarding existing Hyper-V VMs using the Quickstart utility, see Onboarding existing VMs. For details on using the Quickstart utility, see Using Quick Start

You can onboard existing virtual machines (VMs) by using the ServiceOfferingInstance onboard request. For onboarding exisiting Hyper-V VMs using the REST API, see ServiceOfferingInstance onboard request.

Before you onboard an existing VM, you must ensure that the VM complies with the constraints of the onboard request.

Note

You can use Quick Start utility to onboard a single-tier service offering instance. You can use the ServiceOfferingInstance onboard request to onboard a single-tier as well as multi-tier service offering instance.


Before you begin

Review the following topics:

To onboard the Hyper-V System Center VMM server

To onboard the Hyper-V virutal machine manager (VMM) server, complete the following steps:

  1. From the BMC Cloud Lifecycle Management Administration Console, click the vertical Workspaces menu on the left side of the window and select Resources.
  2. Under Quick Links on the left, click Resources under the Compute section.
  3. Click the Onboard Resource icon .
  4. In the Onboard Resource dialog box, select the pod.
  5. Select the Virtual Cluster resource type.

    For Hyper-V, if there are n number of standalone hosts enrolled in the VMM, BMC Cloud Lifecycle Management creates n dummy clusters with the same names as the host names; those clusters will be available for onboard.

  6. Under Provider Name, select BBSA.
  7. From Available Resources, select the Hyper-V resource that you want to onboard.
  8. Click Onboard.

To create the compute resource pools

  1. From the BMC Cloud Lifecycle Management Administration Console, click the vertical Workspaces menu on the left side of the window and select Resources.
  2. Under Quick Links on the left, click Compute Pools under the Compute section.
    The list of current compute resource pools is displayed.
  3. Click the Create Compute Pool icon.
  4. In the Create Compute Pool dialog, type a name for this pool.
  5. Type a useful description.
  6. From the Pod menu, select the network pod to which this pool will belong.
  7. From the Resource Type menu, select the type of resources that this pool will contain.
    For example, select Virtual Host or Virtual Disk Repository if you are creating a datastore.

    The Virtual Clusters type is not supported for Hyper-V as clusters cannot be used as targets to provision a VM. Only hosts can be used as targets.

  8. From the Provider Type menu, select BBSA.
  9. From the Vendor menu, select Microsoft.
  10. From the Hardware Architecture menu, select X86_64.

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:

  2. Click the Servers tab and select the onboarded VM to view the details, as shown in the following figure:

Was this page helpful? Yes No Submitting... Thank you

Comments