Types of custom attributes

String

  • Can have any value unless a regular expression constraint is specified in the OS Build Plan.

Constraints for String custom attribute value:
Regular Expression

The specified value must match the regular expression. For example, a regular expression constraint ^[A-Za-z0-9]+$ implies that the custom attribute value must contain only uppercase alphabets, lowercase alphabets and numbers. To match the entire string, always remember to specify ^ as the starting character or $ as the ending character.

If left blank, the custom attribute value is not validated.

Length

Can be up to 254 characters in length.

Password

  • The password value is encrypted for storage and is masked while you enter it.

Constraints for Password custom attribute value:
Regular Expression

The password must match if the regular expression constraint is specified. To match the entire string, always remember to specify ^ as the starting character or $ as the ending character.

Minimum length

Minimum number of characters required.

Maximum length

Maximum number of characters required.

IPv4 address

  • The value must be a valid IPv4 address.

Hostname

  • The value must be a valid hostname.

Constraints for Hostname custom attribute value:
Length

Can be up to 254 characters in length.

Allowed characters

  • Cannot contain period (.).

  • Can contain alphabets, numbers, hyphen (-) and underscore(_).

  • Cannot start with hyphen (-) or underscore(_).

FQDN

  • The value must be a valid Fully Qualified Domain Name.

    .
Constraints for FQDN custom attribute value:
Allowed characters

  • Must contain at least one period (.).

  • Can contain alphabets, numbers, hyphen (-) and underscore(_).

  • Cannot start with hyphen (-) or underscore(_).

Length

Can be up to 254 characters in length.

Number

  • The value can be an integer or decimal.

Constraints for Number custom attributes:
Minimum

Minimum value allowed

Maximum
Maximum value allowed
Increment
Number by which the value is increased or decreased. The increment or decrement options are available on the following screens:

  • Create Deployment Plan

  • Edit Deployment Plan

  • Copy Deployment Plan

  • Create Server Profile

  • Edit Server Profile

Unit

Unit corresponding to the number

Option

  • Restricts the custom attribute values to the user-specified values.

  • A menu appears on the following screens to enable the user to choose the value from the list of options:

    • Create Deployment Plan

    • Edit Deployment Plan

    • Copy Deployment Plan

    • Create Server Profile

    • Edit Server Profile

NIC

  • Plan Scripts can contain Network Interface Controller (NIC) attributes. NIC attributes are complex custom attributes and contain interface configuration parameters.

    If an interface configuration parameter is not used in Plan Scripts, server profile does not prompt for the parameter.

    A NIC attribute follows the format - <attribute>.<parameter>

  • If a custom attribute name contains period (.), the type is automatically set to NIC and cannot be modified thereafter. The part of name before the . is considered as the name of the custom attribute.

  • NIC attributes are grouped in the OS Build Plan and Deployment Plan under a single attribute name and are of type NIC.

  • All the rules for custom attributes in Plan Scripts apply to NIC attributes. A NIC attribute can contain the following interface configuration parameters:

    • ipaddress

    • domain

    • dns1

    • dns2

    • dns3

    • mac

    • netmask

    • gateway

    • vlanid

    • dhcp

    • networkuri

    • ipv4disable

For a particular NIC attribute, IPv4 configuration can be set to Static, DHCP, or Disable Network configuration.
Static

IPv4 configuration details are set from selected connection (automatically or specified by user) during server profile creation.

DHCP

IPv4 configuration details are set from DHCP server.

Disable Network configuration

NIC will not be configured

Constraints for NIC custom attributes:
Default values

NIC attributes cannot have default values. The value can either be automatically populated from the IP pool if auto mode is enabled in the server profile in HPE OneView or specified by the user.