Users Guide

• About Managing Hardware Profiles
• Creating A New Hypervisor Profile
• Managing Hypervisor Profiles
• Building A New Deployment Template
• Running The Deployment Wizard
Provisioning Overview
Once a physical inventory of the datacenter is complete, all auto-discovered bare-metal systems are available to the
OpenManage Integration for VMware vCenter for zero touch hardware provisioning and hypervisor deployment. To prepare
for provisioning and deployment, you must:
Create a
Hardware Profile
Contains the hardware settings gathered from a reference server that is used to deploy new servers. See
Creating A New Hardware Profile.
Create a
Hypervisor
Profile
Contains the hypervisor installation information needed for ESXi deployment. See Creating A New
Hypervisor Profile.
Create a
Deployment
Template
Optionally contains a hardware profile, a hypervisor profile, or both. You can save and reuse these profiles
as needed for all available datacenter servers. See Building Deployment Templates.
Once the deployment template is created, use the Deployment Wizard to gather the information necessary to create a
scheduled job that provisions server hardware and deploys new hosts in vCenter. For information about running the Deployment
Wizard, see Running The Deployment Wizard . Lastly, use the Job Queue to view job status and make changes to pending
deployment jobs.
NOTE:
No more than two deployment jobs should be scheduled to run consecutively. Multiple jobs should use the
scheduling feature to stagger deployment execution.
Understanding Deployment Job Times
Provisioning and deploying bare-metal servers can take between 30 minutes to several hours to complete, depending on certain
factors. When starting a deployment job, it is recommended that you plan your deployment time according to the guidelines
provided. The amount of time it takes to complete provisioning and deployment varies with deployment type, complexity, and
number of deployment jobs running simultaneously. The table below gives guidelines of the approximate time a deployment job
may take. Deployment jobs are run in batches of up to five concurrent servers, to improve time for the overall deployment job.
The exact number of concurrent jobs depends on resources available.
Table 3. Approximate Deployment Time Scenarios
Deployment Type Approximate Time Per Deployment
Hypervisor only Between 30 minutes to 130 minutes
Hardware only Up to 2 hours depending on the complexity and the RAID,
BIOS, and boot options to configure
Hypervisor and Hardware profiles 1 to 4 hours
Server States Within The Deployment Sequence
When an inventory job is run, auto-discovered bare-metal systems are classified in different states to help determine if the
server is new to the datacenter or has a pending deployment job scheduled. Administrators can use these states to determine if
a server should be included in a deployment job. The states are:
Unconfigured
The server has contacted the OpenManage Integration for VMware vCenter and is waiting to be
configured. See Understanding Deployment Job Times.
Configured The server is configured with all hardware information required for a successful hypervisor deployment.
48 Hardware Management