Abstract
The DPM (Disk Pool Manager) project is the most widely deployed solution for storage of large data repositories on Grid sites, and is completing the most important upgrade in its history, with the aim of bringing important new features, performance and easier long term maintainability. Work has been done to make the so-called “legacy stack” optional, and substitute it with an advanced implementation that is based on the fastCGI and RESTful technologies. Beside the obvious gain in making optional several legacy components that are difficult to maintain, this step brings important features together with performance enhancements. Among the most important features we can cite the simplification of the configuration, the possibility of working in a totally SRM-free mode, the implementation of quotas, free/used space on directories, and the implementation of volatile pools that can pull files from external sources, which can be used to deploy data caches. Moreover, the communication with the new core, called DOME (Disk Operations Management Engine) now happens through secure HTTPS channels through an extensively documented, industry-compliant protocol. For this leap, referred to with the codename “DPM Evolution”, the help of the DPM collaboration has been very important in the beta testing phases, and here we report about the technical choices.
Highlights
The Disk Pool Manager (DPM) is a lightweight solution for grid enabled disk storage management
The development direction of the last years has been towards simplifying the system, while supporting all the advanced features that are needed by the Grid computing and helping sites to incrementally renew their setups. This effort is dictated by the difficulty of maintaining software libraries that have been written in the 80s and 90s [8], over which the oldest core components of DPM are based
Work had been done in the last years to create the dmlite [3] framework and a set of plugins that started complementing the core features of DPM by giving support for the more recent data access protocols used by HEP (HTTP with multi-range requests and xrootd ), while keeping the older core components as an internal coordination layer that includes support for the SRM protocols
Summary
- Direct data access protocols benchmarking on DPM Fabrizio Furano, Adrien Devresse, Oliver Keeble et al. - Towards an HTTP Ecosystem for HEP Data Access Fabrizio Furano, Adrien Devresse, Oliver Keeble et al. - Towards more stable operation of the Tokyo Tier center T Nakamura, T Mashimo, N Matsui et al. CHEP IOP Conf.
Sign-in/Register to view highlights & summary Sign-in/Register to access full text options 
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a callDisclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.
