Onboarding compute resources
You must onboard the compute resources that will be used in the cloud. You can onboard virtual clusters and physical servers. When you onboard a virtual cluster, any associated virtual resource pools, virtual hosts, and virtual disk repositories are also onboarded.
When you onboard a resource, it is placed in the pod's default compute pool until that resource is assigned to a specific, administrator-created resource pool. The default pool's name is podName_default_pool. There is one default pool for each pod. An onboarded compute resource cannot be used until it is assigned to an administrator-created compute pool.
This topic describes how to onboard compute resources. It contains the following sections:
Before you begin
- You must have a registered compute provider before you can onboard compute resources.
- On VMware virtual clusters, the Distributed Resource Scheduler (DRS) must be enabled.
- When onboarding a new VMware cluster, it may take up to 30 minutes before the resource is available in the BMC Cloud Lifecycle Management user interface.
- Onboarding a virtual cluster may fail if the target VMware vCenter server contains VMs that do not have IP or DNS entries. It might take up to 2 hours for the VMs to be filtered out before the cluster can be onboarded successfully.
- For physical devices, after offboarding a resource, it may take up to 30 minutes before the resource can be onboarded again. During this time, you may see the error, "Did not find Physical Server to be onboarded," when you attempt to onboard the resource again.
- You can reset a physical device to make it available in BMC Cloud Lifecycle Management. In the BMC Server Automation console, right-click the device under the Devices node in and select Provision Later. It might take up to 30 minutes before the physical resource is available in the BMC Cloud Lifecycle Management user interface.
To onboard compute resources
- From the BMC Cloud Lifecycle Management Administration console, click the vertical Workspaces menu on the left side of the window and select Resources.
- Under Quick Links on the left, click Resources under the Compute section.
- Click the Onboard Resource icon
The Onboard Resource dialog box is displayed. .
- Select the Pod, Provider Name, and Resource Type for the resource you want to onboard.
By selecting a Resource Type, you can onboard resources from a virtual cluster or physical server. When you onboard a virtual cluster, you are also onboarding the virtual hosts, virtual resource pools, and virtual disk repositories (also called datastores) associated with the virtual cluster.
An alphabetical list of resources is displayed in the Available Resources table.
- Find the resources that you want to add.
- You can page through a long list by clicking the Page button .
- You can search for resources by entering a search string in the Search box and clicking the search icon .
- Select one or more resources and click the Add button to move them to the Selected Resources table.
You can also drag and drop resources from the Available Resources table to the Selected Resources table.
- Click Onboard to onboard the selected resources and close the dialog box.
The onboarded resources are placed in the default compute pool.
The onboarded compute resources are now available to be added to resource pools, as described in Creating compute resource pools. Compute resources cannot be used until you add them to a resource pool.
Updating a virtual cluster
Onboarded virtual clusters might be reconfigured outside of BMC Cloud Lifecycle Management. You can update the virtual hosts, virtual resource pools, and virtual disk repositories associated with the virtual cluster by selecting the virtual cluster and clicking the Synchronize Virtual Cluster icon.
If you remove a virtual host from a virtual cluster and then synchronize the cluster with BMC Cloud Lifecycle Management by clicking the Synchronize Virtual Cluster icon, the removed virtual host continues to be displayed in the virtual host list for the cluster. You must manually off board the removed virtual host from BMC Cloud Lifecycle Management.
When background activity is required from a command issued in the user interface, the Pending Activity section opens to display the progress and status of the background activity. You can:
- Remove a completed activity record from the Pending Activity table by selecting the record and clicking the Delete Activity icon .
- Get detailed error information about a failed activity by selecting the record and clicking the Advanced Error Information icon .
- Display the Audit Trail workspace by clicking the Audit Trail icon .
- Click the Refresh icon in the Pending Activity section to refresh the table.
For information on purging, archiving, and managing pending activities, see Managing pending activity records.
After the activity is marked as complete, you can click the Refresh iconin the upper-right corner of the window to refresh the Resources table so that the newly onboarded resources appear in the table.