UCSProvisioning - createUCSProvisionJob

UCSProvisioning - createUCSProvisionJob

Description :

This command creates a UCS Provision Job, which you can use to provision a UCS blade using the BLCLI.

This command returns a handle to the newly created UCS Provision Job, but it does not execute the job. To execute the job, use one of the commands in the Job namespace, for example Job : execute .

Here is the general procedure for provisioning a UCS blade using the BLCLI:

1. Create a UCS template that contains certain characteristics of the system that you are about to provision. These characteristics include the selected blade, VNICs, boot order, policies, and so on. You can create this template by using the UCSTemplate:createTemplate command.

2. If you are creating the UCS template for the first time, the UCSTemplate:createTemplate command returns the DBKey of the template. However, if the template was created earlier, you may need to get its DBKey. You can get the DBKey of the template by using the DepotObject : getDBKeyByTypeStringGroupAndName command.

3. Create a "regular" Provision Job by by using the ProvisionJob : createProvisionJob command. You don't run this job, you just create it as a means to store system package overrides and various other settings. When you create the UCS Provision Job, you use the provisionJobDbkey argument to pass in a DBKey to the regular Provision Job you created via ProvisionJob:createProvisionJob.

4. If you are creating the Provision Job for the first time, the ProvisionJob:createProvisionJob command returns thhe DBKey of the Provision Job. However, if the job was created earlier, you may need to get its DBKey. You can get the DBKey of the Provision Job by using the ProvisionJob : getDBKeyByGroupAndName command.

5. Create the UCS template override inputFile. This file includes the following settings.

• 
  
  • 
    
    • Profile and Org setting for the UCS template: ***

UCSTemplate.ProfileName=[valid profile name] (Required)

UCSTemplate.ProfileOrg=[valid org] (Required)

• 
  
  • 
    
    • Action to be taken if target blade is already associated. Valid values are : [0- Job fails, 1-Disassocoate the existing profile, 2-Delete the existing profile] ***

Blade.ExistingProfileAction=[Valid value between 0 to 2] (This setting is optional, but if you do not set this property, the action defaults to 0 - job fails.)

• 
  
  • 
    
    • Network settings: ***

Device.IpAddress=[valid IP] Device.SubNetMask=[valid mask] Device.DefaultGateway=[valid gateway]

Device.IsDhcpEnabled=[Valid values are 0 and 1. 0 means Dynamic IP. 1 means Static IP]

These network settings work in conjunction with the following network setting in the Provision Job's input file:

Network.DHCPEnabled=[true or false]

Here are the various scenarios:

Scenario 1:

In the Provision Job's input file, Network.DHCPEnabled=false (Static IP) AND

in this command's input file Device.IsDhcpEnabled=1 (Static IP).

In this case, you can either use the network settings from the Provision Job (omit Device.IpAddress, Device.SubNetMask,and Device.DefaultGateway here) OR you can override the network settings from the Provision Job by specifying different network settings here, for example:

Device.IpAddress=10.20.38.30 Device.SubNetMask=255.255.255.0 Device.DefaultGateway=10.20.38.1

Scenario 2:

In the Provision Job's input file, Network.DHCPEnabled=false (Static IP) AND

In this command's input file Device.IsDhcpEnabled=0 (Dynamic IP).

Dynamic IP configurations apply. Network setttings are not required. (You should omit Device.IpAddress, Device.SubNetMask,and Device.DefaultGateway here.)

Scenario 3:

In the Provision Job's input file, Network.DHCPEnabled=true (Dynamic IP) AND

in this command's input file Device.IsDhcpEnabled=1 (Static IP).

Network settings are required. You must include a line such as:

Device.IpAddress=10.20.38.30 Device.SubNetMask=255.255.255.0 Device.DefaultGateway=10.20.38.1

Scenario 4:

In the Provision Job's input file, Network.DHCPEnabled=true (Dynamic IP) AND

in this command's input file Device.IsDhcpEnabled=0 (Dynamic IP).

Dynamic IP configurations apply. Network setttings are not required. (You should omit Device.IpAddress, Device.SubNetMask,and Device.DefaultGateway here.)

• 
  
  • 
    
    • Name settings: ***

Device.ComputerName=[computer name] (Optional. If you do not specify a computer name, the name specified in the Provision Job applies.)

Device.OmServerName=[name as it will appear within the BMC Server Automation system] (Optional. If you do not specify a name, the name specified in the Provision Job applies.)

Sample input file: c:/UCSProvJobInput.txt

UCSTemplate.ProfileName=ucs_template_foo

UCSTemplate.ProfileOrg=org-root

Blade.ExistingProfileAction=0 or 1

Device.IsDhcpEnabled=1

Device.ComputerName=comp-foo

Device.OmServerName=comp-foo

Device.IpAddress=10.20.38.30 Device.SubNetMask=255.255.255.0 Device.DefaultGateway=10.20.38.1 This command returns a handle to the UCS Provision Job (a DBKey).

Return type : DBKey

Command Input :

Example

The following example creates a UCS Provision Job.

Script