Difference between revisions of "DUNE"

From GridPP Wiki
Jump to: navigation, search
(Supporting DUNE storage)
 
(7 intermediate revisions by 2 users not shown)
Line 5: Line 5:
 
=== DUNE in the UK ===
 
=== DUNE in the UK ===
  
GridPP point of contact: Andrew McNab  
+
GridPP point of contact: Andrew McNab, Steve Jones, Raja Nandakumar
 +
 
 +
Please contact Raja and Steve if you want to participate in the testing of job submission or storage for DUNE.
  
 
Mailing list: [https://www.jiscmail.ac.uk/cgi-bin/webadmin?A0=DUNE-UK-COMP DUNE-UK-COMP@jiscmail.ac.uk] (join in the usual way or ask Andrew)
 
Mailing list: [https://www.jiscmail.ac.uk/cgi-bin/webadmin?A0=DUNE-UK-COMP DUNE-UK-COMP@jiscmail.ac.uk] (join in the usual way or ask Andrew)
  
=== Supporting DUNE via GridPP dirac ===
+
For our US Collaborators: The [https://www.gridpp.ac.uk/wiki/GridPP_nitty_gritty nitty-gritty] or How does GridPP work in daily life ?
 +
 
 +
=== Supporting DUNE job submission ===
  
''This route was used Jan-Apr 2017.''
+
DUNE uses glideinWMS at FNAL and so should be able to support the same range of site types as CMS (i.e. everyone using CREAM or ARC and possible even HTCondor).
  
* To enable DUNE at your site, please enable it according to [https://www.gridpp.ac.uk/wiki/GridPP_approved_VOs#DUNE DUNE config]. <br>
+
Details of the DUNE VO are in the [https://www.gridpp.ac.uk/wiki/GridPP_approved_VOs#DUNE GridPP Approve VOs list], and an RPM exists to install it. DUNE uses the CILogon OSG CA for production job submission, but some testing is done with user certificates from the CILogon Basic CA (these are normally hidden with the glideinWMS framework from the point of view of the CE.)
* Please don't forget to enable the pilot role. <br>
+
* If you want to test your site, please email [mailto:lcg-site-admin@imperial.ac.uk Simon and Daniela at Imperial].<br>
+
* At the moment DUNE does not request storage at the sites they run. They currently use storage at Sheffield with a minor outpost at Imperial<br>
+
* If the accounting data are to be believed, we have so far run one million DUNE jobs in the UK :-) (May 2017)
+
  
=== Supporting DUNE via the Fermilab ITB ===
+
=== Supporting DUNE storage ===
  
''This route is still (April 2018) being used, almost exclusively at Imperial and Sheffield. We still (April 2018) need to check the details and for updated requirements/desirables from the FNAL side.''
+
This is currently being tested in the UK with DPM, dCache, and ECHO.
  
* DUNE might contact your site, or failing that, please contact [mailto:kherner@fnal.gov Ken Herner] at Fermilab.
+
Third party copy transfer test Imperial dCache &rarr; RAL ECHO: [Write-up]
* DUNE will usually request 8 core jobs. At Imperial we are running DUNE as single core jobs, as they are currently mainly running single core jobs within their 8 core slots and this model has proven very inefficient when used by CMS. Which configuration is run is obviously a site decision.
+
* Some DUNE users will use proxies issued by cilogon-basic, this is not a proper CA (details in the ticket below if you are interested). For all practical purposes this means glexec will not work and should be turned off on the factory side.
+
* Here is the [https://ticket.opensciencegrid.org/33389 Imperial OSG ticket], where most of these issues are discussed.
+

Latest revision as of 14:14, 12 September 2018

Overview

The DUNE experiment and DUNE Wiki.

DUNE in the UK

GridPP point of contact: Andrew McNab, Steve Jones, Raja Nandakumar

Please contact Raja and Steve if you want to participate in the testing of job submission or storage for DUNE.

Mailing list: DUNE-UK-COMP@jiscmail.ac.uk (join in the usual way or ask Andrew)

For our US Collaborators: The nitty-gritty or How does GridPP work in daily life ?

Supporting DUNE job submission

DUNE uses glideinWMS at FNAL and so should be able to support the same range of site types as CMS (i.e. everyone using CREAM or ARC and possible even HTCondor).

Details of the DUNE VO are in the GridPP Approve VOs list, and an RPM exists to install it. DUNE uses the CILogon OSG CA for production job submission, but some testing is done with user certificates from the CILogon Basic CA (these are normally hidden with the glideinWMS framework from the point of view of the CE.)

Supporting DUNE storage

This is currently being tested in the UK with DPM, dCache, and ECHO.

Third party copy transfer test Imperial dCache → RAL ECHO: [Write-up]