Go to main content

Automatically Installing Oracle® Solaris 11.4 Systems

Exit Print View

Updated: July 2019
 
 

How to Include a Non-Global Zone in an Automatic Installation

In this procedure, steps performed on the AI server are specifically indicated.

Before You Begin

The non-global zone must already be created and properly configured on a separate working system.

Ensure that your role has the appropriate rights profiles to perform this procedure. See Using Rights Profiles to Install Oracle Solaris.

  1. On the system where your current non-global zone exists, create its configuration file.
    1. (Optional) Display the non-global zone's live configuration.
      $ zonecfg -z zone-name -r info
    2. Export the live configuration.

      Use the following command syntax to create zone configuration files.

      $ zonecfg -a zone-name export -f filename.cfg
    3. Store the configuration file at a location that is network accessible.

      You can also store the configuration file directly on the AI server itself.

  2. On the non-global zone manifest, define installation instructions.

    Use a copy of the template /usr/share/auto_install/manifest/zone_default.xml.

  3. Associate the non-global zone manifest with the install service of the global zone.

    Suppose that your non-global zone manifest file is /tmp/zmanifest.xml, the manifest instance name is zmanifest, and the install service is solaris11_4-sparc. To use the manifest to install zone1 and zone2, you would issue the following command:

    aiserver$ installadm create-manifest -n solaris11_4-sparc -f /tmp/zmanifest.xml \
       -m zmanifest -c zonename="zone1 zone2"
  4. (Optional) Prepare the configuration profile for the zone.
    1. Create the XML file that contains the zone's configuration profile.

      See Non-Global Zone System Configuration Profiles and Chapter 3, Working With System Configuration Profiles in Customizing Automated Installations With Manifests and Profiles.

    2. Associate the profiles with the install service of the global zone.

      Suppose that you created two profiles for the install service solaris11_4-sparc:

      • /tmp/z1profile.xml with instance name z1profile to be used for zone1 and zone2

      • /tmp/z2profile.xml with instance name z2profile to be used further for zone2

      You would issue the following commands:

      aiserver$ installadm create-profile -n solaris11_4-sparc -f /tmp/z1profile.xml \
         -p z1profile -c zonename="zone1 zone2"
      
      aiserver$ installadm create-profile -n solaris11_4-sparc -f /tmp/z2profile.xml \
         -p z2profile -c zonename="zone2"
  5. Configure the global zone manifest to install the non-global zones.

    Assume that the global zone manifest is line1-netra2000.xml. Configure that file's configuration element by choosing from one of the following methods, depending on what zone files you are using:

    • If you are using zone configuration files (*.cfg)

      Specify the zone configuration files on the configuration element. Suppose that the zone configuration file is zconfig.cfg in system1. The file is used to install both zone1 and zone2. You would add the following lines to the bottom of the file:

      ...
        <configuration type="zone" name="zone1"
          source="http://system1/tmp/zconfig.cfg"/>
        <configuration type="zone" name="zone2"
          source="http://system1/tmp/zconfig.cfg"/>
      
        </ai_instance>
      </auto_install>
    • If you are using a zone archive file

      Specify the zone archive on the configuration element. Suppose that the archive file zsystem.uar contains the zone configuration of orig-zone. You want to apply the archived configuration to both zone1 and zone2. You would add the following lines to the bottom of the file:

      ...
        <configuration type="zone" name="zone1"
          source="archive:orig-zone" archive="http://system1/archives/zsystem.uar"/>
        <configuration type="zone" name="zone2"
          source="archive:orig-zone" archive="http://system1/archives/zsystem.uar"/>
      
        </ai_instance>
      </auto_install>
  6. (Optional) Display the manifests and configuration profiles associated with the service.

    The install service name is solaris11_4-sparc.

    aiserver$ installadm list -n solaris11_4-sparc -m -p
    
    Service Name      Manifest Name   Type    Status  Criteria
    ------------      -------------   ----    ------  --------
    solaris11_4-sparc line1-netra2000 xml     active  mac = 00:14:4F:2D:7A:DC
                      zmanifest       xml     active  zonename = zone1,zone2
                      orig_default    derived default none  
    
    Service Name      Profile Name Environment Criteria
    ------------      ------------ ----------- --------
    solaris11_4-sparc z1profile    system      zonename = zone1,zone2
                      z2profile    system      zonename = zone2
  7. Start the installation by booting the client from the network.

    See Running AI on Clients by Using an AI Server.

  8. (Optional) Trace the progress of a non-global zone installation.

    You can either monitor the system/zones-install service or check the output of the zoneadm list -cv command.