test

Sun N1 Service Provisioning System User's Guide for Solaris Plug-In 4.0

Chapter 3 Installing and Configuring the Solaris Plug-In

This chapter contains the following information:

Acquiring the Solaris Plug-In

Acquiring the Solaris containers plug-in is a two-step process. First, you must add the package file that contains the Solaris containers plug-in JAR file to your system. Then you must import the Solaris containers plug-in JAR file.

The Solaris Plug-In is packaged as a plug-in to the Sun N1 Service Provisioning System software. Plug-ins are packaged in JavaTM Archive (JAR) files. The plug-in files for the Solaris Plug-In are available from the Sun N1 Service Provisioning System 5.2 Supplement CD or from the Sun Download Center.

Once the package file is added to your system, the Solaris Plug-In is available for import from two different JAR files. Choose the correct file depending on your situation.

  1. Add the file containing the JAR file.

  2. Import the JAR file –Importing the Solaris Plug-In to the Sun N1 Service Provisioning System

Adding the Solaris Plug-In for Solaris

The Solaris plug-in is contained in the SUNWspssol package.

ProcedureTo Add the Solaris Plug-In for Solaris

Steps

  1. In a terminal window, become superuser.

  2. Move to the directory containing the plug–in package.

  3. Type the following command and press Return.

    # pkgadd -d . SUNWspssol

    The standalone JAR file is in the /opt/SUNWn1sps/plugins/com.sun.solaris/ directory. The upgrade JAR file is in the /opt/SUNWn1sps/plugins/com.sun.solaris/Upgrade directory.

Adding the Solaris Plug-In for Linux

The Solaris plug-in is contained in the SUNWspssol.rpm file.

ProcedureTo Add the Solaris Plug-In for Linux

Steps

  1. In a terminal window, become superuser.

  2. Move to the directory containing the SUNWspssol.rpm file.

  3. Type the following command and press Return.

    # rpm –i package_directory/SUNWspssol

    The standalone JAR file is in the /opt/sun/N1_Service_Provisioning_System/plugins/com.sun.solaris/ directory. The upgrade JAR file is in the /opt/sun/N1_Service_Provisioning_System/plugins/com.sun.solaris/Upgrade directory.

Adding the Solaris Plug-In for Windows

The Solaris plug-in is contained in the SUNWspssol.msi file.

ProcedureTo Add the Solaris Plug-In for Windows

Steps

  1. Move to the directory containing the SUNWspssol.msi file.

  2. Double-click the SUNWspssol.msi file.

    The Installer GUI starts. The JAR file is copied to the C:\Program Files\N1 Service Provisioning System\plugins\com.sun.solaris directory.

Importing the Solaris Plug-In to the Sun N1 Service Provisioning System

To make a given plug-in known to the Sun N1 Service Provisioning System, you need to import the plug-in to the Master Server. If you have already imported a previous version of the Solaris Plug-In, you will need to upgrade to the new plug-in.

ProcedureHow to Import the Solaris Plug-In Using the Browser Interface

To import or upgrade a plug-in, follow these steps as explained in detail in Chapter 5, Plug-In Administration, in Sun N1 Service Provisioning System 5.2 System Administration Guide.

Caution – Caution –

The Solaris Plug-In 4.0 runs in the Sun N1 Service Provisioning System 5.2 environment. Do not install the Solaris Plug-In 4.0 on any other version of the Sun N1 Service Provisioning System.

Steps

  1. In the Administrative section of the browser interface main window, click Plug-ins.

  2. In the Action column of the Plug-ins page, click Import.

  3. Navigate to the location of the JAR file.

    • If you are importing the Solaris Plug-In for the first time, select the com.sun.solaris_4.0.jar file.

    • If you have already imported a previous version of the Solaris Plug-In, select the com.sun.solaris_3.0_4.0.jar file.

  4. Click the Continue to Import button.

    When the import completes successfully, a plug-in details page appears and shows you the objects that the plug-in provides.

ProcedureHow to Import the Solaris Plug-In Using the CLI

You can also import a plug-in archive file by using the command line.

Step

    To import a plug-in file from the CLI, type:


    % cr_cli -cmd plg.p.add -path plugin-filename -u username -p password

    • If you are importing the Solaris Plug-In for the first time, plugin-filename is com.sun.solaris_4.0.jar.

    • If you have already imported the previous version of the Solaris Plug-In, plugin-filename is com.sun.solaris_3.0_4.0.jar.

Upgrading Considerations

Upgrading Existing Local Zones

If you have created global and local zones by using the Solaris Plug-In in the Sun Sun N1 Service Provisioning System 5.0, after you migrate the Master Server to the Sun N1 Service Provisioning System 5.2 and you import the Solaris Plug-In 4.0, you must upgrade the zones. You can then control the upgraded zones with the Solaris Plug-In 4.0.

ProcedureHow to Upgrade Global Zones

Steps

  1. In the Common Tasks section of the browser interface main window, click the Solaris icon.

  2. Click the Solaris Container: Create and Manage link.

  3. In the Referenced Components list, click /com/sun/solaris/container_util.

  4. In the Component Procedures list, click the Run action next to install:default.

  5. On the Run Details page select the global zone target hosts to upgrade.

  6. Click the Run Plan (includes preflight) button.

ProcedureHow to Upgrade a Local Zone that is Running

Use the following steps to upgrade a local zone that is running.

Before You Begin

After migrating to the Sun N1 Service Provisioning System 5.2, upgrade the Remote Agents. For instructions see Upgrading Remote Agents and Local Distributors in Sun N1 Service Provisioning System 5.2 Installation Guide.

Steps

  1. In the Common Tasks section of the browser interface main window, click the Solaris icon.

  2. Click the Solaris Containers: Create and Manage link.

  3. In the Component Procedures list, click the Run action next to markOnly: install.

  4. Select the target global zone host in which the local zone that you want to upgrade is installed.

  5. Select the local zone host name from the Plan Variables settings.

    If desired local zone names are not present, you can add the zone names. To add the zone names, follow these steps:

    1. Click Select From List in the plan variable settings table.

    2. In the Variable Setting window, click Create Set.

    3. Type the zone set name in the New Set Name field.

    4. Click the box next to Zone Name prompt and type the zone name.

      Note –

      Zone names become network Zone Host Names during local zone creation. Zone Host Names should resolve to matching available local network IP addresses.

  6. Click the Run Plan (includes preflight) button.

  7. In the Common Tasks section of the browser interface main window, click the Solaris icon.

  8. Click the Solaris Containers: Create and Manage link.

  9. In the Component Procedures list, click the Run action next to activate.

  10. On the Plan Details page, in the Current Installations list, select the local zones to activate.

  11. Click the Run Selected Installations button.

ProcedureHow to Upgrade a Local Zone that is Not Running

Use the following steps to upgrade a local zone that has been deactivated.

Steps

  1. In the Common Tasks section of the browser interface main window, click the Solaris icon.

  2. Click the Solaris Containers: Create and Manage link.

  3. In the Component Procedures list, click the Run action next to attach: install.

  4. Select the target global zone host in which the local zone that you want to upgrade is installed.

  5. Select the local zone host name from the Plan Variables settings.

    If desired local zone names are not present, you can add the zone names. To add the zone names, follow these steps:

    1. Click Select From List in the plan variable settings table.

    2. In the Variable Setting window, click Create Set.

    3. Type the zone set name in the New Set Name field.

    4. Click the box next to Zone Name prompt and type the zone name.

      Note –

      Zone names become network Zone Host Names during local zone creation. Zone Host Names should resolve to matching available local network IP addresses.

  6. Click the Run Plan (includes preflight) button.

    The provisioning system upgrades the local zone from the 3.0 version to the 4.0 version.

    Note –

    If you want to activate the local zone, run the activate Component Procedure.

Accessing Previous Versions of a Component

When you upgrade to a new version of a plug-in, the Common Tasks page for the plug-in is updated to provide links to components that are installed with the new plug-in version. This feature enables you to easily view components that contain the most current features and improvements. Components that rely on old functionality are not linked to from the Common Tasks page.

ProcedureHow to Access Previous Versions of a Component

If you have trouble finding a component that you previously installed, the component was likely created from the previous version of the plug-in. Follow these steps to view or work with a previous version of the component:

Steps

  1. Click the appropriate component procedure on the Common Steps Tasks page.

    The Component Detail page appears.

  2. On the Component Details page, click Version History.

    A list of components and versions appears.

  3. Click the appropriate link.

    • To perform a task with a component, click the version number or the details link that applies to the component that you want to use.

    • To view where a component is installed, click Where Installed.

Customizing the Solution for Your Environment

Before you deploy Solaris zones from the Master Server, you must modify the Master Server config.properties file.

ProcedureHow to Customize the config.properties File

Steps

  1. On the Master Server, using a text editor, access the config.properties file.

    By default, the configuration file for the Master Server resides in the following directory: /opt/SUNWn1sps/N1_Service_Provisioning_System_5.2/server/config

  2. Add the following lines to the config.properties file:

    config.allowSessionIDOnHosts=masterserver 
          pe.defaultPlanTimeout=6000

    The config.allowSessionIDOnHosts variable enables the plug-in to communicate with the Master Server through the Sun N1 Service Provisioning System Remote Agent and Command Line Interface (CLI).

    By default, the timeout value for plans is set to 1800 seconds or 30 minutes. In some instances, such as when executing a plan on older hardware, the amount of time that is needed for a plan to complete exceeds 30 minutes. To increase the plan timeout value, add the pe.defaultPlanTimeout line to the config.properties file. In the example that is shown, the value is set to 100 minutes.

  3. After you modify the config.properties file, you must restart the Master Server.

Patching the Solaris Plug-In

Check the SunSolve site for available patches for the Solaris plug-in. To apply the patch, follow the instructions in the patch README file.