Prepration for the first EMI release (EMI - 1).

EMI-1 is expected to be frozen in Feb 2010. Date of publishing depends on interoperabilty testing and certification.

Features and improvements in common areas

Unfortunately, according to the EMI data proposal, there are not many milestones, in terms of product features, which will be available in Feb 2010. However, based on the good progress we are making with some of the data activities, we expect the following features to be available ahead of time, in other words for EMI-1.

  • 2.1 SRM security : We expect the dCache server and the dCache SRM client to communicate using the X509/SSL protocol instead of GSI (httpg) without delegation functionality.
  • 3.1 NFS 4.1 : dCache will provide a production ready NFS 4.1 (pNFS) implementation with standard Unix security. Kerberos security is envisioned but not guarantied. DPM will provide a pre-production version for the NFS 4.1. (pNFS) server.
  • 4.0 Web access, http(s) and WebDav : DPM and dCache already provide http(s) access right now. For EMI-1 StoRM will provide http(s) and dCache WebDav access.
  • 7.0 GLUE 2.0 : The Information Provider in dCache, DPM and StoRM will publish data using the GLUE 2.0 and GLUE 1.3 schema in parallel. However, initially the content will be the same. Over time the information published with GLUE 2.0 will become richer.

Non of the 4 tasks listed about depend on other groups or activities. It might be worth mentioning :
  • As soon as SRM security considers to handle delegation, it will depend on the EMI-Security groups delegation service.
  • Providing GLUE 2.0 by the SE's and FTS as well as interpreting GLUE 2.0 doesn't depend on other other activities. However making sure that the clients will have access to server information depends on EMI-Infrastructure. (Namely BDII)

Situation for EMI - 1

http(s) WebDav GLUE 2.0
SRM/SSL NFS 4.1 Argus Blacklisting
DPM P - P - beta -
dCache P P P beta P -
StoRM P - P - - beta

P = Production Quality
beta = Pre-Production Quality

Individual features and improvements by component.

  • HSM support : Using GPFS as StoRM storage backend, migrating and retrieving data to and from the TSM Storage System will be supported.
  • High availability : StoRM will provide a cluster solution for high availability.
  • Log analyzer : An administrative tool to interrogate StoRM log files.

  • libarcdata2 DM components
    • Improved HTTP(S) transfer performance: The HTTP DMC will support parallel transfers and asynchronous read/write.
    • Recursiveness in the Chelonia data management component: The ARC DMC will have better support for recursiveness.
  • Web Interface : Authenticated/Authorized web interface to manage pools and other system components.
  • WebDav : WebDav authentication via User/Password.
  • Data re-balancing : Re-balancing data on pools after new pools are added or filled unbalanced.
  • Improved drain performance : DPM will speed up the draining of data pools in case of hardware maintenance or decommissioning.
  • Instrumentation of disk servers
    • Monitoring : In preparation of the EMI common task [11] Monitoring the DPM storage element will improve the internal monitoring and will provide more information to track down problems.
    • Management of streams to pools : DPM will provide mechanisms to steer the number of streams from individual pools to better manage resources.
  • Roles : With DPM priorities can be given to particular Roles.
  • Remote access to log files : To improve the speed and quality of tracing transfer problems, FTS transfer logs will be made available remotely. The target are people from the experiments on shift. Access control is managed by the site, running the FTS instance.

-- PatrickFuhrmann - 06-Sep-2010

Edit | Attach | Watch | Print version | History: r6 < r5 < r4 < r3 < r2 | Backlinks | Raw View | WYSIWYG | More topic actions
Topic revision: r6 - 2010-09-07 - PatrickFuhrmann
    • Cern Search Icon Cern Search
    • TWiki Search Icon TWiki Search
    • Google Search Icon Google Search

    EMI All webs login

This site is powered by the TWiki collaboration platform Powered by PerlCopyright & 2008-2023 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
or Ideas, requests, problems regarding TWiki? use Discourse or Send feedback