Managing Versions

GEMM allows you to upload one or more versions of N1 Grid Engine, and choose which one to deploy on the grid. To do these tasks, click the Versions menu item to display the Version Management page.

Figure 1–3 Version List Page

This page is where you can upload, modify and manage different versions of N1 Grid Engine software.

You can only deploy one version at any given time. If you wish to deploy another version, you must first uninstall the grid from all the hosts.

Versions List Icons

In the Version list, each version has three icons:

• The Minus icon removes a version and all its files.

• The Modify icon lets you rename a version.

• The Inspect icon lets you add or remove individual files from a version.

Adding Grid Engine Versions

The Version Management main page displays a list of versions currently available on the SCS server. Initially, no versions are defined.

To define a version

Steps

1. Click the Add button which produces a dialog where you name a version.

   This version name can be anything, as long as it does not contain any non-whitespace or punctuation characters other than “-” and “_”.

2. After you name the version, click the Submit button.

   Once you submit the name, the Version list displays again with the newly-created version present. You can add more versions at any time.

   Figure 1–4 Add Version Dialog

   
   

Adding Files to a Version

You must first add files to a version before you deploy it to the grid. Adding files consists of adding all N1 Grid Engine package files that are part of the given version.

Package File Criteria

The following criteria apply to the package files:

• GEMM requires N1 Grid Engine 6 Update 4 or later.

• All package files must be in .tar.gz format. Although N1 Grid Engine currently is made available in .pkg format for Solaris, the .pkg format files cannot be used by GEMM.

• For any given version, there must be the “common” package for that version, as well as all the “bin” (binary) packages which support the kinds of hosts in your grid. For example, if your grid consists of Solaris 9 SPARC hosts as well as Solaris 10 and x64 hosts, then you must include in the version these files:

• <name>-bin-solaris-sparcv9.tar.gz

• <name>-bin-solaris-x64.tar.gz

• <name>-common.tar.gz

  where -<name> is the name given to that version, for example n1ge-6_0.

• In any given version, you cannot mix different update levels of N1 Grid Engine. All packages associated with a version must belong to the same update level, for example n1ge-6_0. The only exception is is when you deploy N1GE 6 patches, which will be described ***.

To Add Files

Steps

1. click the Inspect icon in the version list. You will see a list of files currently contained in that version.

2. Clicking the Add button produces a dialog box where you can load version files one at a time. You can also upload files from the local browser using the File browser or from a remote URL.

   Figure 1–5 Add Files Dialog

   
   

   ---

   Note –

   When you upload files from a remote URL, you can only specify a URL which can be accessed from the SCS server directly without going through a proxy server. You cannot specify a proxy server when using the Version Management web dialog. Please see the documentation for the command-line equivalent of Version Management, gemmVersionMgmt.pl, to learn how to upload files using a web proxy.

   ---

To Remove Files

Steps

1. Select a file from the list of files.

2. Click on the Minus icon for that file.

Deploying a Patched Version of N1GE 6 With GEMM

N1GE software updates are made available through the mechanism of patch files. You cannot use an N1GE patch alone; you must use it in conjunction with a full distribution of N1GE software. When you install a patch, it replaces various files in the existing full version.

There are two ways you can install N1GE patches:

• Install patch files on a live N1GE grid already running an existing full installation of N1GE 6. This procedure is described in the patch documentation but is not supported by GEMM.

• Install patch files at the same time as you install a fresh installation of an original, full, N1GE software distribution. You can use this technique when you are creating a new grid and want to install it with the latest N1GE updates. You also can use this approach when you want to use N1GE with the latest updates and don't mind getting rid of your old setup entirely (without worrying about saving old configurations or maintaining jobs currently in the systems). GEMM can handle this procedure automatically as described here.

1. Create a new version in the Version Manager of GEMM. Populate this version with N1GE files from an original full version, just as if you were going to deploy this version.

2. Get the desired patch files. When Sun Microsystems creates and releases patch updates, these files are made available on the SunSolve website (http://sunsolve.sun.com). For each patch release, there is one patch for the N1GE "common" package, as well as one patch for each architecture-specific package. Get all the patch files necessary for your particular environment.

   Patch files are distributed in both .pkg format as well as .tar.gz format. Make sure to obtain only the .tar.gz form of the patches. These patch files are themselves contained in a ZIP archive; be sure to unzip the archive to extract the .tar.gz files.

3. Put these .tar.gz patch files into the previously created version, using either the Version Manager web UI or the command line. Now, You can use GEMM to deploy this version onto any Grid host, just as with an original, unpatched version of N1GE.

   Be sure that only one patch level of N1GE is deployed across the grid. You should take care should to avoid mixing different patch levels in the same distribution. Also do not use patch files for only some but not all of the architecture-specific packages required for your environment.