test

Sun N1 Service Provisioning System User's Guide and Release Notes for the OS Provisioning Plug-In 2.0

Creating Solaris Images and Profiles

To provide basic JumpStart functionality, an image of the appropriate Solaris OS media must be installed on the JET server. That image must then be attached to a profile that explains how the image is to be installed.

ProcedureHow to Import a Solaris Image

To provide basic JumpStart functionality, an image of the appropriate Solaris OS media must be installed on the JET server. The version or versions of Solaris to be imported onto the JET server depend on those required by the target servers. You can install multiple versions of the Solaris media on the same JET server at the same time.

Note –

While it is recommended that you copy the media to disk on the JET server, it is not strictly required. You can share the physical media appropriately to allow the target servers to boot from it. However, using the physical media severely restricts the performance of the target server build and minimizes your ability to support multiple versions of Solaris.

Steps

  1. Mount the Solaris DVD on the JET server, either through a local drive, or by using a shared drive on the network.

  2. In the Common Tasks section of the N1 SPS browser interface, select OS Provisioning.

  3. On the OS Provisioning Common Tasks page, click Import in the Solaris Images section.

  4. On the Plans Details page, click Run.

  5. Choose variables to use for this plan.

    • To use an existing variables set, select a name from the drop-down menu in the SolarisImage component row of the Plan Parameters table.

    • To create a new variables set, click Select from List in the SolarisImage component row of the Plan Parameters table.

      1. Click Create Set.

      2. Type a name for the variables set.

      3. Type the Solaris main version number into the version variable.

      4. Type the Solaris minor version number into the release variable.

      5. Verify the remaining variables and change them, if needed.

        The following table describes the additional variables and their default values.

        Variable Name 

        Description 

        Default Value 

        architecture

        Architecture of the physical system, for example, SPARC or x86.  

        sparc

        installPath

        Unique name for the imported Solaris image. 

        Solaris:[version]_:[release]_:[architecture]

        For example: Solaris9_u7_sparc

        image_path

        Path to where imported image will be stored. 

        /export/osp_image/:[installPath]

        image_subnet_addr

        Subnet address of the image server. 

        :[target(/):sys.ipAddress]

        image_subnet_mask

        Subnet mask of the image server 

        255.255.255.0

        media_src

        Path to the image files. By default, the software assumes the files are on a DVD disc. 

        /cdrom/cdrom0/s0

      6. Save the variables set.

      7. Select the variables set that you just saved from the drop-down menu in the SolarisImage component row of the Plan Parameters table.

  6. On the Plan Details Run page, select the JET image server on which to import the image.

    Tip –

    The host name of the JET image server ends in -jet.

  7. Click Run Plan (includes preflight).

ProcedureHow to Create a Solaris Provisioning Profile (Browser Interface)

Before You Begin

Make sure the JET server exists and that the Solaris OS software is available to that server. For more information about creating the JET server, see Setting up the Solaris JET Server. For more information about creating the Solaris image, see How to Import a Solaris Image.

Steps

  1. In the Common Tasks section of the N1 SPS browser interface, select OS Provisioning.

  2. On the OS Provisioning Common Tasks page, click Create Profile in the Solaris Images section.

  3. On the Plans Details page, click Run.

  4. Choose variables to use for this plan.

    • To use an existing variables set, select a name from the drop-down menu in the SolarisImage component row of the Plan Parameters table.

    • To create a new variables set, click Select from List in the SolarisImage component row of the Plan Parameters table.

      1. Click Create Set.

      2. Type a name for the variables set.

      3. Type the Solaris main version number into the version variable.

      4. Type the Solaris minor version number into the release variable.

      5. Verify the remaining variables and change them, if needed.

        The following table describes the additional variables and their default values.

        Variable Name 

        Description 

        Default Value 

        architecture

        Architecture of the physical system, for example, SPARC or x86 

        sparc

        installPath

        Solaris image name to attach 

        Solaris:[version]_:[release]_:[architecture]

        For example: Solaris9_u7_sparc

        image_path

        Path to location where image file resides 

        /export/osp_image/:[installPath]

        image_subnet_addr

        Subnet address of the image server 

        :[target(/):sys.ipAddress]

        image_subnet_mask

        Subnet mask of the image server 

        255.255.255.0

        media_src

        Path to the image files. By default, the software assumes the files are on a DVD disc. 

        /cdrom/cdrom0/s0

      6. Save the variables set.

      7. Select the variables set that you just saved from the drop-down menu in the SolarisImage component row of the Plan Parameters table.

  5. On the Plan Details Run page, select the JET image server on which to create the profile.

    Tip –

    The host name of the JET image server ends in -jet.

  6. If needed, change the Profile Name.

  7. If needed, change the Profile Description.

  8. Update the list of the JET modules to use.

    The JET product modules are located on the JET server in the directory /opt/SUNWjet/Products.

    By default, the plan variable JET Modules Name(s) lists two JET modules to include in the Solaris profile component:

    base_config is the required JET module for basic Solaris installation. All other /opt/SUNWjet/Products modules are optional. Adding a module name to this list adds the module installation function and configuration variables to the newly created Solaris provisioning profile.

    One of the /opt/SUNWjet/Products optional modules is the custom module. The custom module installs arbitrary lists of Solaris packages, patches, and files, and can run arbitrary collections of scripts. See Using the custom Module for further details. You can also write other JET modules. For information about creating JET modules, see Appendix C, Creating Additional JET Modules.

  9. Click Run Plan (includes preflight).

  10. (Optional) Change default profile values.

    1. Navigate to the Solaris folder that contains the new Provision component.

      For example, /com/sun/n1osp/autogen-biss1-jet/provision/.

    2. Click the Solaris provisioning component name.

      For example, Solaris10_0205_sparc.standard.

    3. Edit default values.

      For information about Solaris profile variables, see Appendix B, Solaris Profile Component Variables.

      1. Click the Edit button at bottom of Details page.

      2. Change values.

      3. Click the Check-in button at the bottom of the Details page.

ProcedureHow to Create a Solaris Provisioning Profile (Command-Line Interface)

Steps

  1. To create a variable set for the SolarisImage component, type a command similar to the following example:


    # cr_cli -cmd cdb.vs.add -comp NM:/com/sun/n1osp/untyped/SolarisImage \
-name "solaris9" -u admin -p admin -vars "version=9;release=u7;architecture=sparc; \
image_path=/export/install/Solaris9product;image_subnet_addr=10.42.42.2; \
image_subnet_mask=255.255.255.0;media_src="

  2. To provide JET module information, create a file /tmp/solaris-image that contains the following entries:

    standard
Standard Solaris
base_config spsra

    Where:

    • The first line in the file corresponds to the Profile Name field in the plan variables section of the browser interface.

    • The second line in the file corresponds to the Profile Description field in the plan variables section of the browser interface.

    • The third line in the file corresponds to the JET Module Name field in the plan variables section of the browser interface.

  3. To run the plan, type a command similar to the following example:


    # cat /tmp/solaris-image|cr_cli -cmd pe.p.run -u admin -p admin
-PID NM:/com/sun/n1osp/untyped/SolarisImage-create-profile
-tar H:NM:biss1-jet -comp - -vs solaris9 -pto 30 -nto 10