About configuring an OS deployment plan from a hypervisor cluster profile

You can configure the OS deployment plan either from a server profile template or through a hypervisor cluster profile. If the OS deployment plan and OS deployment settings are already defined in the server profile template, then the same plan is populated in the hypervisor cluster profile and is used for deploying hypervisor OS on the server hardware. The OS deployment settings that are not configured in the server profile template can be configured in the following hypervisor cluster profile locations:
  • OS deployment settings: OS deployment settings that are applicable to all hypervisors in the cluster can be configured in the OS deployment settings section.

  • Hypervisor: OS deployment settings that are unique to each hypervisor can be configured in the hypervisor section.

NOTE:

You cannot configure the NIC type OS deployment setting in the hypervisor cluster profile except for the ManagementNIC. NIC type OS deployment setting can be configured in the associated server profile template.

You can select the OS deployment plan as None in the hypervisor cluster profile to manage the hypervisor OS deployment outside of HPE OneView.

Best practices for configuring OS deployment plan and settings

The following are the best practices that you can follow to configure the OS deployment plans and settings:
  1. Where to configure the OS deployment plan and settings:
    • Configure the OS deployment plan and settings in the server profile template if the hypervisors managed by all the hypervisor cluster profiles using this server profile template are deployed with the same OS deploy configuration.

    • Configure the OS deployment plan and the common OS deployment settings in the server profile template if the hypervisors managed by all the hypervisor cluster profiles using this server profile template are deployed with the same OS deploy image or version. Leave the cluster-specific OS deployment settings blank in the server profile template and configure them in the individual hypervisor cluster profile.

    • Configure the OS deployment plan and settings in the hypervisor cluster profile if the hypervisors managed by the hypervisor cluster profiles using this server profile template are deployed with different OS images or version.

      NOTE:

      If the OS deployment plan has NIC type OS deployment settings for networks, configure the OS deployment plan and settings in the server profile template. You cannot configure the NIC type OS deployment settings for networks in a hypervisor cluster profile.

  2. The OS deployment plan must have the following OS deployment settings for it to be used by the hypervisor cluster profile:
    • ManagementNIC—Used for configuring the NIC for the hypervisor management network. This NIC deployment setting must have a subattribute IP address.

    • Password—Used for configuring the root password on the hypervisor.

    • Hostname and Domain—Used for configuring the hostname on the hypervisor. This setting is required if you plan to add hypervisors to the hypervisor manager using the hostname instead of IPv4 address.

    You do not need to define NIC type OS deployment settings in the OS deployment plan other than ManagementNIC, as networking on the hypervisors are configured based on the network configuration defined in the hypervisor cluster profile.
    NOTE:

    If the OS deployment plan has ManagementNIC with a non-HA configuration, the hypervisor cluster profile will reconfigure this NIC with NIC teaming for HA based on the network configuration defined in the hypervisor cluster profile.

  3. Methods for configuring the hostname on hypervisors:
    • Configure the hostname either in the server profile template or in the OS deployment settings section of the hypervisor cluster profile using tokens or a combination of tokens and text.

      Example 1: Combine the enclosure and enclosure bay tokens and enter a hyphen in between them as follows: {enclosure}-{enclosurebay}. If the enclosure name is Enc1 and the profile is being applied to Bay 2, the resulting hostname would be Enc1-2.

      Example 2: You can specify the hypervisor profile name prefix in the Hypervisor Template section of the hypervisor cluster profile. A sequential number will be appended to this profile name prefix for each profile that is created. If you had specified a profile name prefix of ESXi-Profile-, the profiles would be named ESXi-Profile-1, ESXi-Profile-2, and so on. In the OS deployment settings section, if you specify the hostname and use the {profile} token, the resulting hostnames would be the same as the profile names.

    • Do not specify the hostname in the server profile template or in the OS deployment settings section of the hypervisor cluster profile. When you add the hypervisors, it will prompt you for the hostname of each hypervisor being added. You can then enter any valid hostname. Use this approach only if tokens do not suit your needs.