Ensure that the policies appropriate to the VM technology are configured. For more information, see Section 4.0, Orchestration Provisioning Adapter Information.
For vSphere, the default number of slots is 4. We recommend that you increase this number to 10, depending on the hardware and available computing resources (RAM/CPU) of the server where the agent is running (this is also the server associated with the vsphere_client policy). Each joblet slot causes a separate Java instance on this resource. Each Java instance uses 50-60 MB of RAM and is quite CPU-intensive.
For Xen, we recommend that you accept the default slot number of 1. No more than one provision operation should happen concurrently on the Xen host, particularly any operation that is disk-related.
For more information on the policies, see Section 4.0, Orchestration Provisioning Adapter Information.
Ensure that you have set the correct number of joblet slots for the VM hosts in the policies appropriate to the VM technology. For more information, see Joblet Slots in the NetIQ Cloud Manager 2.1.5 Orchestration Console Reference.
In the Orchestration Console, click> .
The Discover VM Hosts and Repositories dialog box is displayed.
Select your provisioning adapter from the drop-down list.
Clickto view the section in the Orchestration Console and verify that the job has started.
After your VM host machines are discovered, you can refresh your tree view or wait for the automatic tree refresh to see the VM host machine listed under the provisioning adapter, although no VMs are listed.
This also discovers:
Local repositories for all types of hypervisors.
SAN and NAS repositories for Xen and vSphere.
To view the discovered repositories, click, then click or .
For a list of the VM technologies and supported host and guest operating systems, see NetIQ Cloud Manager 2.1.5 Installation Planning Guide.