|
Hi all,
updates to gdmp and the replica manager attached.
cheers,
gav
---------- Forwarded message ----------
Date: Fri, 09 Aug 2002 17:16:34 +0200
From: Erwin Laure <[log in to unmask]>
To: Anders Waananen <[log in to unmask]>
Cc: Cal Loomis <[log in to unmask]>,
WP2-Managers <[log in to unmask]>
Subject: [WP2-mgmt] WP2 release notes
Hi Anders,
Please find attached the WP2 release notes for TB 1.2
Regards,
-- Erwin
WP2:
====
WP2 released three packages:
edg_replica_manager-1.0 (a new package)
gdmp-3.0
edg_replica_catalog-2.0
============================================================
FEATURES OF EDG-REPLICA-MANAGER-1.0
============================================================
The EDG-Replica-Manager is a wrapper around a patched version of the
Globus replica manager. It provides an API and CLI for copying and
replicating files using gridftp and the edg replica catalog.
It provides the following functionality:
1) registerEntry - registers a file in the RC
2) unregisterEntry - removes a file entry from the RC
3) copyFile - simple file copy
4) copyAndRegisterFile - a combination of 2) and 3)
5) replicateFile - creates a new replica by copying and registering
an already registered file
6) deleteFile - removes a file physically and its entry in the RC
For more information refer to the installation and user guide:
http://www.cern.ch/grid-data-management/edg-replica-manager/edg-replica-manager-1.0.pdf
http://www.cern.ch/grid-data-management/edg-replica-manager/edg-replica-manager-1.0.ps
The following bugzilla bugs have been fixed:
490, 491
Known problems:
---------------
1. Timeout in gsiftp with Globus 2.0b21
============================================================
CHANGES AND NEW FEATURES IN GDMP 3.0
============================================================
Please refer also to Section "2 New Features and Improvements in
Version 3.0" in the GDMP User Guide where you can find details on the
Section numbers where changes are documented in the User Guide. The
GDMP version 3.0.1 to 3.0.10 mainly provided bug fixes but no changes
to interfaces nor functionality.
http://www.cern.ch/GDMP/userguide/userguide-gdmp-3.0.ps
http://www.cern.ch/GDMP/userguide/userguide-gdmp-3.0.pdf
The following bugzilla bugs have been fixed:
5, 122, 125, 162, 187, 293, 296, 304, 401, 424, 432, 444, 472, 483,
487, 488, 489, 498, 512, 515, 516, 520, 521, 522
Changes in commands and API:
---------------------------
1. gdmp_replicate_get will now search for all the possible replicas
for the file which have been published. If a replica is not accessible
or the GDMP server for that replica is down or the replica is not
stagable on the remote GDMP server, gdmp_replicate_get will go for the
next replica to transfer.
2. C++ API to GDMP client commands.
3. The command line tool gdmp_filter_catalogue does not exist
anymore but now the filters can be flexibly applied as command line
arguments.
4. new command line tools: gdmp_job_status, gdmp_replicate_put and
gdmp_remove_local_file
5. Command line options of existing commands have been changed
slightly. Check the syntax for details.
6. Command line tools for the C++ Replica Catalogue API have been
provided and can be used
independently of GDMP to access the Globus Replica Catalogue.
7. Improved error messages in case of communication/connection errors
between client and server.
8. The Replica Catalogue API and CLI do not return anymore multiple
entries for the same PFN for the same LFN.
Changes in configuration, internal mechanisms:
----------------------------------------------
1. The GDMP server can use any host or user certificate that does
not require a password. It is strongly recommended to use the host
certificate/key pair (which is the default one used in the
configuration step. The GDMP_Server cert (as it was used until version
2.1) is not used anymore.
2. Every client request is now delegated to a GDMP server that
checks for authentication/authorisation and then contacts the remote
GDMP server that needs to trust the local server. Thus, GDMP now uses
a delegation mechanism for client server interaction. This also
requires that GDMP servers rather than single users are registered in
the remote GDMP specific grid-mapfile.A client will be authenticated
once per connection. Once a connection b/w client and server is
established, only one authentication is needed (no more authentication
per message/request).
User certificates only need to be entered into the local
grid-mapfile of GDMP servers where they need to have access to. For
remote interaction between GDMP servers, the servers need to trust
each other and no user certificate is used. Thus, the grid-mapfile
needs to have an entry of the remote GDMP server accessing the local
server.
3. New client/server messaging system is added. Now, for each
request there will be an acknowledgement. See the server log file
gdmp_server_log.out for details. (It did not add any feature but just
to make the code easily maintainable.)
4. GDMP exists in the form of a full installation (GDMP server plus
all client application) and a client installation.
5. A GDMP client is now independent of installation and storage
directories for file/objectivity of a remote GDMP server. Now, the
remote GDMP administrator can change the installation directory of
GDMP or storage directories and he/she does not need to inform other
GDMP sites about it. These attributes will be obtained by the client
from the GDMP server at run time.
However, we do not recommend to change the storage directories
since these directory might be stored in the Information Service (as
it is the case for EDG).
6. Hierarchical structure of GDMP configuration files that allow a
single server to be used for multiple Virtual Organisations. Instead
of a single gdmp.conf file, there are now a gdmp.conf,
gdmp.shared.conf and gdmp.private.conf files.
7. ``real'' multiple VO support: one GDMP server can server multiple
VOs and listens only on one port. In GDMP 2.1, we had several ports
for each VO.
8. The directory utils has been changed to sbin.
9. Logging of the server output is new: all log information (stdout
and stderr) is now in file
GDMP_INSTALL_DIR/var/gdmp_server_log.out. gdmp_server_log.err does not
exist anymore.
10. changes of variables in the GDMP configuration file:
GDMP_FLATFILE_ROOT_DIR is now called GDMP_STORAGE_DIR
GDMP_OBJY_ROOT_DIR is now called GDMP_OBJY_STORAGE_DIR
GDMP_REP_CAT_FLATFILE_COLL_NAME is now called GDMP_REP_CAT_FILE_COLL_NAME
GDMP_REP_CAT_FLATFILE_COLL_URL is now called GDMP_REP_CAT_FILE_COLL_URL
11. description of GDMP monitoring tool: GDMP Heartbeat Monitor added.
12. Now it is possible to automatically create rpms using gmake.
13. The installation directory structure for supporting multiple VOs
has been changed.
14. The configuration requires new grid-mapfiles to be installed in
the VO specific directories. A script to automatically
create/update these files has been provided. This script requires
the hostcert.pem to be user readeable.
15. Default behaviour for configuration file is changed: GDMP looks by
default only into /opt/edg/etc and does not look in any other
default locations anymore.
16. configure_gdmp searches for non-default locations of hostcert.pem
and hostkey.pem in /etc/globus.conf
17. create_gridmapfile looks /etc/globus.conf
file to find out the location of the global grid-mapfile. It now
checks for the existence of the VO
specified by the user on the command line, by verifying the
presence of the VO directory under etc; accommodates EDG static
or dynamic account mapping.
18. BrokerInfo and ReplicaCatalogue rpms can be installed concurrently
without conflicts. Also the gdmp and BrokerInfo rpms are independent.
Note that GDMP 3.0 is not backwards compatible to any other previous
GDMP versions !
Known problems:
===============
1. Timeout in gsiftp with Globus 2.0b21
============================================================
CHANGES IN EDG-REPLICA-CATALOG-2.0
============================================================
1) The catalog now uses ldap V3 instead of the old ldap V2.
2) The catalog can be configured to allow GSI authorised access.
For more information on the configuration see the README file
contained in the rpm.
Known problems:
===============
none.
|
