Users Guide

ii. To start the job immediately, select Run Deployment Job Now.
To go to the job queue after the deployment job starts, select Go to the Job Queue after the job is submitted.
11. Click Finish.
After the deployment wizard tasks are complete, you can manage deployment jobs by using Job Queue. .
Managing deployment jobs using Job Queue
1. In the OpenManage Integration for VMware vCenter, on the Monitor > Job Queue tab, click Deployment Jobs.
The following details about deployment jobs are displayed in the upper grid:
• Name
• Description
• Scheduled Time
• Status
• Collection Size
• Progress Summary
2. To update Deployment Jobs Details, click the Refresh icon.
3. To display deployment job details, which contains detailed information about the servers included in the deployment job, select a
deployment job in the upper grid.
The following details are displayed in the lower grid:
• Service tag
• iDRAC IP address
• Job status
• Deployment job details (more information available on mouse hover)
• Start and End time
You can view entire information about a deployment job as a text pop-up by selecting the job and hovering your cursor on the Details
column for the deployment job.
4. To abort the deployment job, click the
icon.
5. When the message is displayed, click Abort Job to abort, or to cancel, click Do Not Abort Job.
6. To display the Purge Deployment Job Queue window, click . Select the Older than date and job Status, and click Apply.
The selected jobs are then cleared from the queue.
Deployment job timing
The provisioning and deploying bare-metal servers can take between 30 minutes to several hours to complete, depending on several
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 following table provides the approximate time a deployment job can take. The 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
available resources.
Table 37. Approximate deployment time
Deployment type Approximate time per deployment
Hypervisor only Between 30 minutes to 130 minutes
Hypervisor and hardware profiles 1 to 4 hours
Server states within deployment sequence
When an inventory job is run, the auto/maually discovered bare-metal systems are classified in different states to help determine if the
server is new to the data center or has a pending deployment job scheduled. The administrators can use these states to determine if a
server should be included in a deployment job. The following are the states:
102
Deploying hypervisor