Quick start

Prerequisites

Be sure to:

  • Set up a Media Server and load the software that will be used in provisioning servers. For details on using the Media Server setup utility, see the Insight Control server provisioning Installation Guide.

  • Configure DHCP as needed. For details on DHCP, see the Insight Control server provisioning Installation Guide.

  • Add Windows product keys. For information, see Edit product key settings screen details.

Quick start tasks

The following sections demonstrate how to use Insight Control server provisioning to perform some basic tasks such as adding a server, running a Build Plan, and monitoring a job.

Task 1: Discovering a server

  1. From the Main Menu, select Servers as shown in the screen example, to display the Servers Overview screen.


    [NOTE: ]

    NOTE: For information on adding servers, see “Managing and provisioning servers” in the Insight Control server provisioning Administrator Guide.


    Main Menu

    Main Menu
  2. On the Servers Overview screen, select +Add server in the master pane. Alternatively, use the Actions menu to select ActionsAdd server, as shown in the screen example.

    Select Add server

    Select Add server
  3. Enter the iLO IP address and credentials, click OK, and wait for the server to be added.

    See Add a server for complete details.

Task 2: Selecting an OS Build Plan to run on a target server

  1. Select OS Build Plans from the Main Menu to display the OS Build Plans screen as shown in the following figure.

    OS Build Plans screen

    OS Build Plans screen

    Hewlett Packard Enterprise provides Build Plans for use in provisioning and configuring servers. A Build Plan is made up of steps. There are different types of actions; but the majority of steps consist of running scripts, deploying configuration files and installing zip packages.

  2. Be sure you have the OS distribution loaded on the Media Server and ready for use by the Build Plan. Then select an OS Build Plan that meets your requirements from the master pane list of OS Build Plans.

Task 3: Running an “out-of-the-box” OS Build Plan

  1. From the OS Build Plans screen and with the Build Plan selected, select ActionsRun OS Build Plans as shown in the screen example, to display the Run OS Build Plans dialog box.

    Select Run OS Build Plans from the Actions menu

    Select Run OS Build Plans from the Actions menu
  2. The Build Plan you selected is shown in the OS Build Plans section of the Run OS Build Plans dialog box. Select the server you want to run the Build Plan on by clicking Add Server in the Servers section, as shown in the screen example.

    Select Add servers on the Run OS Build Plans screen

    Select Add servers on the Run OS Build Plans screen
  3. Select the target server from the Select Servers for the Job dialog box, as shown in the screen example. To help find the server in the list, enter any part of the server name, model, management IP address, or serial number in the search box. When the target server is selected, click Add.

    Select Servers for the Job dialog box

    Select Servers for the Job dialog box
  4. The Run OS Build Plan dialog box is displayed with the Build Plan and target server listed as shown in the screen example below.

    You can optionally configure the NICs on your target server by selecting Customize in the Network section (for details see Configure Networking). You also have the option to either run the job immediately or schedule the job for a future date and time.

    Run the OS Build Plan

    Run the OS Build Plan
  5. Click OK and Yes, run to run the OS Build Plan to provision the selected server.

Task 4: Monitoring a job

  1. After selecting Yes, run from the Run OS Build Plan dialog box, the Jobs screen is automatically displayed so you can monitor the progress of the job.

    However, at any time you may go to the Jobs screen by selecting Jobs from the Main Menu and then selecting a job of interest from the master pane list of jobs as shown in the screen example. For information about monitoring a job from the Jobs screen, see Jobs screen details.

    Jobs screen

    Jobs screen
  2. To check the log output of the job, select the Logs link in the Jobs screen. For details, see Find log output for a job.


    [NOTE: ]

    NOTE: Log output for a job is not available until the job is complete.


Task 5: Modifying the kickstart file in a Hewlett Packard Enterprise provided Build Plan

The Hewlett Packard Enterprise provided Build Plans are provided as basic templates. You can modify the Hewlett Packard Enterprise provided Build Plans to create custom Build Plans that can be run on your servers. This enables you to create Build Plans that meet your organization's specific needs.

To modify a Hewlett Packard Enterprise provided Build Plan, you must save a copy and then modify the copy because the Hewlett Packard Enterprise provided Build Plans are read-only. Use the following steps to create a customized Build Plan.

  1. From the OS Build Plans screen, select a Build Plan to modify. To customize the installation of Red Hat Linux on a server, select the HP ProLiant OS – RHEL 6.3 x64 Scripted Install Build Plan. Then select ActionsSave as.

    Save the Hewlett Packard Enterprise provided Build plan with a new name so it can be modified

    Save the Hewlett Packard Enterprise provided Build plan with a new name so it can be modified
  2. In the Save as dialog box, rename the Build Plan to be unique, for example MyCopy-HP ProLiant OS – RHEL 6.4 x64 Scripted Install and click OK. You can now make changes to the Build Plan you copied. The following steps demonstrate how to change the kickstart file, which is a typical modification.

    Enter a new name for the Build Plan you want to modify

    Enter a new name for the Build Plan you want to modify
  3. Select the copied Build Plan and in the Steps pane select the Kickstart file (RHEL 6.3 x64 en_us Kickstart) in the list of steps. This is a configuration file.

    Select the OS Build Plan’s Kickstart step to modify

    Select the OS Build Plan’s Kickstart step to modify
  4. When you click on the step name, the Configuration File screen is displayed with the RHEL x64 en_us Kickstart file selected. To modify this configuration file you must first save a copy. Select ActionsSave as.

    Save the configuration file with a new name so it can be modified

    Save the configuration file with a new name so it can be modified
  5. In the Save as dialog box, rename the configuration file to be unique, for example, RHEL 6.3 x64 en_us Kickstart MyCOPY and click OK. You can now make changes to this new configuration file.

    enter a new name for the configuration file

    enter a new name for the configuration file
  6. In the Configuration Files screen, with the new configuration file selected, select Edit in the Configuration File pane.

    Select Edit configuration file

    Select Edit configuration file
  7. In the Edit screen make the necessary changes. For this example, scroll down to the end and add emacs to the list of components. Click OK.

    A message indicates that the configuration file is updating.

    Modify the configuration file copy

    Modify the configuration file copy
  8. Select OS Build Plans from the Main Menu and then select the copy of the Build Plan you created earlier. It should already be selected when you go to the Build Plans screen.

    In the Steps pane select Edit.

    On the OS Build Plans screen select Edit steps

    On the OS Build Plans screen select Edit steps
  9. In the Steps dialog box locate the step RHEL 6.3 x64 en_us Kickstart and select the Edit icon.

    In the Steps dialog box select the edit icon next to the Config file to be replaced

    In the Steps dialog box select the edit icon next to the Config file to be replaced
  10. In the Edit Step dialog box, select the modified Kickstart configuration file RHEL 6.3 x64 en_us Kickstart MyCOPY and click OK.

    Select the modified configuration file to replace the default configuration file in the Build Plan

    Select the modified configuration file to replace the default configuration file in the Build Plan
  11. The Edit OS Build Plan dialog box is displayed. In the list of steps, the default configuration file is replaced with the modified Kickstart file. Click OK. A message indicates the Build plan is updating.

    The modified configuration file replaces the default file in the Build Plan

    The modified configuration file replaces the default file in the Build Plan
  12. On the OS Build Plans screen you will now see the modified Kickstart configuration file listed in the steps.

    You can run this customized Build Plan just as you would a Hewlett Packard Enterprise provided Build Plan.

    OS Build Plan with the modified configuration file in the steps

    OS Build Plan with the modified configuration file in the steps

Task 6: Creating a new Build Plan to perform an operation on a server after OS deployment

Another feature of IC server provisioning is the ability to perform operations on servers after OS installation. You can create scripts to perform a variety of actions on a server after OS installation. You can then create a new Build Plan (rather than copying a Hewlett Packard Enterprise provided Build Plan) that includes the scripts and run the Build Plan against a server after the server has been deployed.

The following example shows how to create a simple script, create a new Build Plan, add a step to the Build Plan to run the script, and save the Build Plan to run on a server after OS deployment.

This is a simple example, but you can create complex build plans to perform nearly any action on a target server.

  1. Go to the Scripts screen and select Create script.

    Select Create a script

    Select Create a script
  2. In the Create scripts dialog box enter the following:

    1. Select script type UNIX.

    2. Give the script a name (in this example whats-my-name).

    3. Enter a description.

    4. Type in the script contents. In this example the script contents is:

      #!/bin/bash
      echo “Hello”
      echo “This is my system name ‘hostname’ ”
      echo
      echo “This was your parameter $*”
      
    5. Click Create.

    Create a new script

    Create a new script
  3. Go to the OS Build Plans screen and select Create OS Build Plan to create a new Build Plan. In the Create OS Build Plan dialog box give the Build Plan a name (in this example Post Install Job) and enter a description.

  4. Select the Build Plan you created and then select Edit in the Steps pane to add a step to the Build Plan that will run the script you created.

    Select Edit steps in the Build Plan

    Select Edit steps in the Build Plan
  5. In the Edit dialog box click Add steps.

    Select Add steps

    Select Add steps
  6. In the Add Step dialog box enter the following:

    1. Select the step type Run script.

    2. Find the name of the script you created and select it.

    3. Enter a parameter for the script (in this example Display me).

    4. Enter a description.

    5. Then click Add.

    Add the script as a step

    Add the script as a step
  7. In the Edit step dialog box you will now see one step listed. Click OK to save the edited Build Plan.

    Add the script as a step

    Add the script as a step
  8. Now you can run this Build Plan on a server that already has an OS running on it. Select Run OS Build Plans and add a server to run it on. It can be run against a production server or one in the service OS.

    Run the Build Plan on a server that already has an OS installed

    Run the Build Plan on a server that already has an OS installed
  9. After the job runs, select the Logs link on the Jobs screen which should indicate that the job succeeded. You can see that the script was run and the parameter is displayed.

    Check the Logs to see that the script ran

    Check the Logs to see that the script ran

Helpful background information