Run an OS Build Plan

Use the following links to display topics of interest.


[NOTE: ]

NOTE: When a set of jobs is run together a ‘control’ job is created in addition to the individual jobs in the set of jobs. The control job is the driving component that kicks off the next OS Build Plan as the previous one completes and controls the failure response.


To run an OS Build Plan

  1. Before beginning, verify the target servers have met the prerequisites as described in Make sure a target server is ready for an OS Build Plan.

  2. From any OS Build Plan, Servers, Device Groups or Jobs screen, select ActionsRun OS Build Plan. The Run OS Build Plans screen will be displayed. If coming from the OS Build Plans screen then the OS Build Plan you selected will be listed on the Run OS Build Plans screen. If coming from the Servers screen then the servers you selected will be listed.

  3. You can select OS Build Plans to run by selecting Add in the OS Build Plans section. And you can remove OS Build Plans from the list by selecting X in the Build Plan row. In the Select OS Build Plans pop-up window type directly in the field or select to search through the list of available Build Plans. And select Add or Add+ to select one or more Build Plans to run on the servers you select.

  4. You can select servers to run the OS Build Plans on by selecting Add in the Servers section. And you may remove target servers by selecting X on the server row. In the Select servers pop-up window select a listed server to be provisioned with the Build Plans or use the browse box to find available servers. And select Add or Add+ to select one or more servers to run Build Plans on.

  5. If running a set of OS Build Plans, then under Job Information you can specify a name for the set of Build Plans.

  6. Also under Job Information you can select a Schedule option to either run the job or set of jobs now or in the future.

  7. You may opt to configure the target server networking at this point by checking the Configure check box under Static Network. See Configure static networking information and change host name for details.

  8. If you are running several OS Build Plans then select what type of failure response you want if there are any failures in running the OS Build Plans.

  9. Select OK to launch the job or select Cancel to return to the previous screen. You will be asked to verify launching the job if you select OK.

  10. Once the job has been launched, you will be taken to the Jobs screen with the newly created job highlighted. You may monitor the job from there or continue working.


[NOTE: ]

NOTE: To get your Build Plan to work on servers with B120i and B320i controllers, create a custom attribute named kernel_arguments and set the value toblacklist=ahci for RHEL installations or brokenmodules=ahci for SLES installations.


Run OS Build Plans screen details

Screen component Description
OS Build Plans

Description:

This is the list of one or more OS Build Plans that will be run on the servers you select.

You can add OS Build Plans to the list by selecting Add. In the pop-up window, type directly in the field or select to search through the list of available Build Plans. Then, in the pop-up window select Add or Add+ to select one or more OS Build Plans to run on the servers you select.

The Build Plans will be listed in priority order (Run Order). You can change the run order by using the arrow buttons to move Build Plans up or down in the list.

You can remove OS Build Plans from the list by selecting X in the Build Plan row.

The OS Build Plan description is read only in this context. To change the description you must edit the Build Plan as described in Edit OS Build Plans.


[NOTE: ]

NOTE: When you select more than one OS Build Plan a separate job is created for each Build Plan. And an additional job is created to manage start and stop times, the sequence to run in and the failure response. For example, if you selected two OS Build Plans to run, when you go to the Jobs page you will see three jobs, one for each OS Build Plan and one control job.


Default value:

None

Required:

Yes, you must select at least one OS Build Plan

Examples:

  • ProLiant OS - RHEL6.6 x64 Scripted Install

  • ProLiant SW - Offline Firmware Update

Servers

Description:

This is a list of one or more servers selected for the OS Build Plans. When OK is selected, provisioning of the listed Build Plan or set of Build Plans will begin on these servers.

You can add servers to the list by selecting Add. In the pop-up window, select a listed server to be provisioned with the Build Plans or use the browse box to find available servers. Then, in the pop-up window select Add or Add+ to select one or more servers to be provisioned.

You can remove servers from the list by selecting X in the server row.

The server description is read only in this context. The server description includes the following:

  • Status

  • Display Name

  • Model

  • Deployment Interface

  • Location

  • Serial Number

Default value:

None

Required:

Yes, you must select at least one server.

Job Information

Job name

Description:

If you select a set of jobs to run together, a ‘control’ job is created in addition to the individual jobs in the set of jobs. The control job is the driving component that kicks off the next OS Build Plan as the previous one completes. When running a set of jobs you can specify a job name to be used to identify the control job as shown on the Jobs screen. Job Name can contain the following: alphanumeric characters, dash, underscore and spaces.

If you are running a single Build Plan you will not see the Job name field.

Default value:

Run OS Build Plans

Required:

No.

Run job

Description:

You can select to run the OS Build Plan Immediately or select a future run time.

To select a future time and date, check Select run time. A pop-up window is displayed that allows you to select a date from the calendar and a time using the Hour and Minute slider bars. Select Done when you’ve selected the date and time. If you decide you want to run the job now, exit the pop-up window and select the option to run the job Immediately.

Default value:

Immediately

Required:

No.

Static Network

Description:

Checking the Configure box allows you to personalize the networking for the target servers. Additional fields will be displayed on the screen when this box is checked that allow you to enter specific networking information for the target servers. See Configure static networking information and change host name for details.

Required:

No.

Failure Response

Description:

If you have selected more than one OS Build Plan to run then you will see a list of failure responses to select from. The failure response you select determines what happens when there is a failure.

The options are:

  • Run next Build Plan only on successful servers

    — This means for the server the OS Build Plan failed on, don’t run any more Build Plans, but do run the next Build Plan on the rest of the servers where there is no failure.

  • Run next Build Plan on all servers (successful or failed) — This means go to the next Build Plan and run it on all servers, even the failed server.

  • Do not run any more Build Plans — This means after any failure run no more Build Plans.

Default value:

Run next Build Plan only on successful servers.

Required:

If you have selected to run more than one OS Build Plan then a failure response selection is required. Otherwise no failure response is needed.

Run OS Build Plans screen buttons
OK

Select OK to begin provisioning the selected servers with the selected OS Build Plans. A dialog box will be displayed to verify you want to proceed. If you proceed, you will be taken to the Jobs screen with the job selected. You can monitor its progress from that screen if you like or you can continue working.

Cancel

Select Cancel to go back to the screen previous to the Run OS Build Plans screen.