gLite > gLite 3.1 > glite-AMGA_postgres > Update to glite-AMGA_postgres 3.1.1-0  
 
 

 

 

gLite 3.1

glite-AMGA_postgres - Update to version 3.1.1-0


Date 18.01.08
Priority Normal

Description



This is the initial release of the AMGA metadata catalogue for the gLite 3.1 / SL4 platform. As all the gLite 3.1 services, it uses VDT 1.6 and is totally built with ETICS.

glite-AMGA_postgres

AMGA is a generic metadata catalogue that is intended to provide access to relational data for a wide range of applications. The main features of the AMGA catalogue are high performance access to relational databases, especially on WAN connections. An SQL-like query language providing most of the features of modern SQL dialects provides complex joins and includes string and mathematical functions. This query language serves to hide the differences of various vendor dialects of SQL and is translated into the correct dialect of the back-end. In addition this query language allows to implement a fine grained access control, which is based on the built-in support for user and group management. VOMS groups and roles are supported.

AMGA has two different front-ends, a web service front-end implemented using gSOAP, which strives to become WS-DAIR compliant, and a text-protocol based front-end. Considerable effort has been spent on providing native client APIs for C, C++, Python, Perl and Java, both for the SOAP and the text protocol. A PHP API is available, too. AMGA allows access to existing databases without the need to copy the pre-existing data into the AMGA service to make it available.

To configure AMGA with yaim use "-n glite-AMGA". The postgresql-odbc rpm has to be installed by hand:

https://twiki.cern.ch/twiki/bin/view/LCG/GenericInstallGuide310#The_DAG_repository

This rpm has dependencies on unixODBC and postgresql-libs. If they are not yet present, you can install them with:

yum install unixODBC postgresql-libs

AMGA uses either the "compat" or "oneline" (recommended) representation of the DN when authenticating a user via matching the certificate subject. You can get this representation by issuing:

openssl x509 -subject -in cert.pem -nameopt oneline -noout

This DN then is used in setting up user-credentials via the AMGA user_subject_add administrative command. WARNING: The accepted DN string representations differ from the format displayed by grid-proxy-info and voms-proxy-info.

Please also have a look at the list of known issues.

Updated rpms

Name Version Full RPM name Description
fetch-crl 2.6.3-1 fetch-crl-2.6.3-1.noarch.rpm Tool for periodic retrieval of Certificate Revocation Lists
glite-AMGA_postgres 3.1.1-0 glite-AMGA_postgres-3.1.1-0.noarch.rpm Metapackage for the glite-AMGA_postgres
glite-amga-cli 1.3.0-2 glite-amga-cli-1.3.0-2.i386.rpm gLite AMGA CLI and C++ client API
glite-amga-server 1.3.0-2 glite-amga-server-1.3.0-2.i386.rpm AMGA Server
glite-amga-soapserver 1.3.0-2 glite-amga-soapserver-1.3.0-2.i386.rpm gLite AMGA Server with SOAP interface
glite-version 3.1.0-1.slc4 glite-version-3.1.0-1.slc4.i386.rpm glite-version
glite-yaim-amga 4.0.2-1 glite-yaim-amga-4.0.2-1.noarch.rpm glite-yaim-amga
glite-yaim-core 4.0.3-6 glite-yaim-core-4.0.3-6.noarch.rpm glite-yaim-core
postgresql-odbc 08.02.0500-7.4.slc4 postgresql-odbc-08.02.0500-7.4.slc4.i386.rpm postgresql-odbc v. 08.02.0500
vdt_globus_essentials VDT1.6.0x86_rhas_4-1 vdt_globus_essentials-VDT1.6.0x86_rhas_4-1.i386.rpm Virtual Data Toolkit

The RPMs can be updated using yum via

Service reconfiguration after update

Service must be reconfigured.

Service restart after update

Service must be restarted.

How to apply the fix

  1. Update the RPMs (see above)
  2. Update configuration (see above)
  3. Restart the service if necessary (see above)