Using System Configuration Profile Templates

Profiles can contain variables to retrieve configuration parameters from the install server environment or from criteria specified in the create-profile subcommand. In this way, a single profile file can set different configuration parameters on different clients. See Table 6–1 for a list of variables you can use.

In the following example profile, named hostIPnet.xml, AI_HOSTNAME is a placeholder for the client system's host name, AI_IPV4 is a placeholder for the client system's IP address, and AI_NETWORK is a placeholder for the client system's IP version 4 network number.

<?xml version='1.0'?>
<!DOCTYPE service_bundle SYSTEM "/usr/share/lib/xml/dtd/service_bundle.dtd.1">
<service_bundle type="profile" name="sysconfig">
  <service name="system/identity" version="1" type="service">
    <instance name="node" enabled="true">
      <property_group name="config" type="application">
        <propval name="nodename" value="{{AI_HOSTNAME}}"/>
      </property_group>
      <property_group name="install_ipv4_interface" type="application">
        <propval name="name" value="net0/v4"/>
        <propval name="address_type" value="static"/>
        <propval name="static_address" type="net_address_v4" value="{{AI_IPV4}}/8"/>
        <propval name="default_route" type="net_address_v4" value="{{AI_NETWORK}}"/>
      </property_group>
    </instance>
  </service>
</service_bundle>

The following commands create customized system configuration profiles in the install service without changing the input hostandIP.xml file.

# installadm create-profile -n svc1 -f /export/hostIPnet.xml \
-p server1 -c hostname="server1" -c ipv4="10.0.0.1" -c network="10.0.0.0"
# installadm create-profile -n svc1 -f /export/hostIPnet.xml \
-p server2 -c hostname="server2" -c ipv4="10.0.0.2" -c network="10.0.0.0"
$ installadm list -n svc1 -p
Profile  Criteria
-------  --------
server1  hostname = server1
         ipv4 = 10.0.0.1
         network = 10.0.0.0
server2  hostname = server2
         ipv4 = 10.0.0.2
         network = 10.0.0.0

While the hostandIP.xml file remains unchanged, the server1 and server2 profiles that are internal to the svc1 install service are customized. For example, the server1 profile has the following content:

# installadm export -n svc1 -p server1
<?xml version='1.0'?>
<!DOCTYPE service_bundle SYSTEM "/usr/share/lib/xml/dtd/service_bundle.dtd.1">
<service_bundle type="profile" name="sysconfig">
  <service name="system/identity" version="1" type="service">
    <instance name="node" enabled="true">
      <property_group name="config" type="application">
        <propval name="nodename" value="server1"/>
      </property_group>
      <property_group name="install_ipv4_interface" type="application">
        <propval name="name" value="net0/v4"/>
        <propval name="address_type" value="static"/>
        <propval name="static_address" type="net_address_v4" value="10.0.0.1/8"/>
        <propval name="default_route" type="net_address_v4" value="10.0.0.0"/>
      </property_group>
    </instance>
  </service>
</service_bundle>

This same result can be achieved by setting environment variables. You need to specify one -c option that identifies this client uniquely, such as MAC address or host name, so that these configuration values are applied only to that client.

# export AI_HOSTNAME=server1;export AI_IPV4=10.0.0.1;export AI_NETWORK=10.0.0.0
# installadm create-profile -n svc1 -f /export/hostIPnet.xml \
-p server1 -c mac="aa:bb:cc:dd:ee:ff"

The following table shows the variables that can be used as placeholders in template profiles. These variables can also be specified as environment variables.

Table 11-9 Variables for System Configuration Template Profiles

arch

cpu

hostname

ipv4

mac

mem

network

zonename