Difference between revisions of "DPM End of legacy-mode support"
Line 15: | Line 15: | ||
=== End users === | === End users === | ||
Traditionally, users interacted with DPM using a separate client, for example, SRM. With DOME, end users typically interact with DPM via a protocol frontend, e.g. HTTP/WebDAV, gridFTP or xrootd, that makes use of DOME in the background. For a comprehensive guide to DOME and its command set, please refer to the | Traditionally, users interacted with DPM using a separate client, for example, SRM. With DOME, end users typically interact with DPM via a protocol frontend, e.g. HTTP/WebDAV, gridFTP or xrootd, that makes use of DOME in the background. For a comprehensive guide to DOME and its command set, please refer to the [https://gitlab.cern.ch/lcgdm/dmlite/blob/master/doc/dome/dome.pdf DOME guide] | ||
=== DPM administrators and site admins === | === DPM administrators and site admins === |
Revision as of 10:57, 21 May 2019
Main | EGI.eu operations services | Support | Documentation | Tools | Activities | Performance | Technology | Catch-all Services | Resource Allocation | Security |
Documentation menu: | Home • | Manuals • | Procedures • | Training • | Other • | Contact ► | For: | VO managers • | Administrators |
What's happening?
DPM (Disk Pool Manager) is the most widely deployed solution for storage of large data repositories on Grid sites for a wide range of applications. In May 2018 during the DPM Workshop the announcement was made that from June 2019 it would be deprecating its so-called "legacy" mode. This includes its support for SRM (Storage Resource Broker) and the old rfio protocol. It's also related to the deprecation of the lcg-utils clients, which already happened years ago.
Why?
The new DPM core, known as DOME (Disk Operations Management Engine) brings significant enhancements and is based on the secure, industry-standard HTTPS protocol and web services. Discontinuing the legacy mode allows the developers to concentrate on the new scalable and future-proof DOME, without the overhead of maintaining the legacy functionality.
What do I need to do?
End users
Traditionally, users interacted with DPM using a separate client, for example, SRM. With DOME, end users typically interact with DPM via a protocol frontend, e.g. HTTP/WebDAV, gridFTP or xrootd, that makes use of DOME in the background. For a comprehensive guide to DOME and its command set, please refer to the DOME guide
DPM administrators and site admins
System administrators interact with the system using a frontend protocol (e.g. with a Web browser) or in a root session in the head node running the tool named dmlite-shell, instead of the older command-line executables dpm-* or dpns-*. The main authentication mechanism remains X.509 with (or without) VOMS extensions, and the new system architecture will allow an easier integration path with possible future alternate authentication systems (e.g. OpenID-Connect).
To see whether end users are making use of legacy tools (e.g. lcg-utils), an easy rule of thumb is to check the contents of your srmv2.2 logfile /var/log/srmv2.2/log
. If this file only records routine reports (e.g. daemon stop/start, ping etc.) then that indicates that SRM is not being actively used by users.
Information about installing DPM and enabling DOME may be found here: [1]. Please note that the site does not necessarily need to use the configuration management tool puppet.
To determine whether lcg-utils clients are being used, please look for occurrences of PASV
in the gridftp logfile /var/log/dpm-gsiftp/gridftp.log
and /var/log/dpm-gsiftp/dpm-gsiftp.log
. (Newer clients such as gfal2 use STOR
instead, meaning a delayed passive ftp.)