HOW TO: Upgrade from 1.0 to 1.1

This contains all the information you need to know to upgrade from 1.0 to 1.1.


The schema of the database has changed: the upgrade script will create the new database and move the data from the old to the new. The old database will be left intact: this allows you to go back to your old installation without having to touch anything.

Configuration file

The configuration file has some minor changes: the upgrade script will take care of them. The old configuration will work anyway under the new version, but some warnings will be displayed in the log.

The changes are:

  • MySQLPersistenceFactory is deprecated and substituted by HibernatePersistenceFactory: GUMS uses a different library to access the database, and parameters need to be specified in a slightly different way. For backward compatibility, the MySQLPersistenceFactory is still included. Changes include better transaction handling and support for any major database.
  • in VOMSGroup, ignoreFQAN is deprecated, and substituted by matchFQAN and acceptProxyWithoutFQAN: this allows better description on how the both the normal and VOMS proxies should be handled
  • WildcardHostGroup is deprecated and substituted by CertificateHostGroup: this means you can now match against the certificate DN or CN (which also means better handling of service certificates).

Main differences

There are a couple of differences that will make GUMS 1.1.x behave a little bit differently:

  • Maps are now assigned to "DNs" instead of "hostnames". In the configuration file, you will use DNs (or CNs for brevity) to associates maps to a service; also in the user interface you will have to use the full DN. This allows better identification of the mappings than before, and allows handling of service certificates.
  • The updateGroups command in all its flavors (i.e. automatic, command line or web interface) is now non-blocking. That is, read queries (map generation, PRIMA calls, ...) can now be performed at the same time as an update. Be aware that, since the automatic update is triggered, as usual, by the first command, that first command will most probably do not see a perfectly up-to-date VO table.

Compatibility with PRIMA

GUMS 1.1 is fully compatible with PRIMA: no changes in the PRIMA configuration are needed.

Compatibility with GUMS Client

GUMS 1.1 is compatible with the previous versions of the client, with one important caveat: in 1.0.x the service is name is simply the hostname while in 1.1 is the full DN. For example:

./gums generateGridMapfile /DC=org/DC=doegrids/OU=Services/

To avoid confusion:

  • If you are planning in upgrading all clients to 1.1, use CertificateHostGroup only.
  • If you are not planning in upgrading all client to 1.1, keep using WildcardHostGroup. This will accept hostname as well as full DNs, and will make GUMS 1.1 respond in the same way as GUMS 1.0.x