# $Id: README.Upgrade,v 1.4 2007/04/25 02:59:06 kst Exp $ # $Source: /projects/globus/kst/CVS/public_html/gx-map/README.Upgrade,v $ # [ Id: README.Upgrade,v 1.11.2.1 2007/03/02 09:27:35 kst Exp ] # [ Source: /projects/globus/kst/CVS/tools/gx-map/README.Upgrade,v ] As of release 0.4.5, the client command for the gx-map system has been renamed from "gx-map" to "gx-request". For backward compatibility, the "gx-map" command is still available as a symbolic link to "gx-request". Upgrading to 0.5.X. =================== The data files (particularly the requests.log file) for gx-map 0.5.X are incompatible with the data files for gx-map 0.4.X. Install gx-map 0.5.X as described in INSTALL. This will create an initial empty requests.log file. You then need to feed your existing grid-mapfile entries into the new gx-map installation. There are two ways to do this. 1. Use the gx-ingest command on your existing grid-mapfile. This will generate a shell script that invokes gx-request for each entry. Carefully check the script for accuracy, then run it. -- OR -- 2. If you have an existing gx-map installation (release 0.3 or later), you can translate your existing requests.log file using the gx-convert-log command. If you want to change the set of user accounts that have administrative privileges, use the "-old-admins" and "-new-admin" options. Optionally run gx-cleanup-logs to delete or comment out redundant requests (such as an add request followed by a corresponding remove request). If you have multiple requests.log files, use "gx-cleanup-logs" to merge them. Install the generated requests.log file in the gx-map-data directory. If you have an existing gx-map installation, you may have entries for accounts that don't currently exist on your system. These entries will not be included in the generated grid-mapfile, but you might want to keep them; they'll appear if the accounts are created later, or if they exist on other systems within your site. If you translate the requests.log file (option 2), these entries will be included automatically. If you instead process your existing grid-mapfile, consider using your old gx-map installation's "gx-gen-mapfile -all" command to generate a grid-mapfile that contains all the entries. There are also some TeraGrid-specific considerations; see README.TeraGrid for details. Upgrading 0.5.3.2 to 0.5.3.3 / 0.5.3.2p1 ======================================== The 0.5.3.3 release contains some security fixes for 0.5.3.2. This is a strongly recommended upgrade. You can install 0.5.3.3 from scratch as for any other release, or you can apply it as a patch to an existing 0.5.3.2 installation, using the provided "patch-gx-map-0.5.3.2" script. If you have any questions, please feel free to contact me. -- Keith Thompson Thu 2007-03-01