Login

EIC/ECCE Computing bi-weekly

→ US/Eastern
Description

Topic: ECCE Computing
Time: Jun 1, 2021 10:00 Eastern Time (US and Canada)
        Every 2 weeks on Tue, 8 occurrence(s)
        Jun 1, 2021 10:00
        Jun 15, 2021 10:00
        Jun 29, 2021 10:00
        Jul 13, 2021 10:00
        Jul 27, 2021 10:00
        Aug 10, 2021 10:00
        Aug 24, 2021 10:00
        Sep 7, 2021 10:00
Please download and import the following iCalendar (.ics) files to your calendar system.
Weekly: https://bnl.zoomgov.com/meeting/vJItceuhrz4tGyXMWH69MkSQ6XVXXTwWk1k/ics?icsToken=98tyKuiurj0oE9WQtxjBeI89FYn4dun71mVps5twqzezWg1YUTKgDtR6CoZoJ9OB

Join ZoomGov Meeting
https://bnl.zoomgov.com/j/1606291571?pwd=WEhaYnZBSGNuT0JvS1R3RVJrUUJPZz09

Meeting ID: 160 629 1571
Passcode: 337630
One tap mobile
+16692545252,,1606291571#,,,,*337630# US (San Jose)
+16468287666,,1606291571#,,,,*337630# US (New York)

Dial by your location
        +1 669 254 5252 US (San Jose)
        +1 646 828 7666 US (New York)
        +1 669 216 1590 US (San Jose)
        +1 551 285 1373 US
Meeting ID: 160 629 1571
Passcode: 337630
Find your local number: https://bnl.zoomgov.com/u/abRL50Tyw

Join by SIP
1606291571@sip.zoomgov.com

Join by H.323
161.199.138.10 (US West)
161.199.136.10 (US East)
Meeting ID: 160 629 1571
Passcode: 337630

Hide
  • Presentation related to SUMS done. A few questions 
    • Where are all the tags related to the OSG etc ... declared? The submission policy takes care of this. SUMS detects the node you are on and tries to guess the default policy but you can also specify from the command line if there are multiple choices.
    • What happens if we want to use containers? SUMS supports containers via the "shell" XML tag.
    • It was noted that SUMS is used in STAR, is it used now and who uses it (graduate student, production teams, ...)? SUMS is the preferred way for graduate students and analyzer to run their analysis jobs because in addition of the advertised features, it also integrate with "a" FileCatalog (hence, input can be specified as a "dataset" and SUMS takes care of job splitting and finding the files, managing the file syntax depending of file location etc ...). It is also used for some workflows from the production teams especially embedding and the microDST to picoDST conversion worflows. The "raw" data reconstructions uses a BNL specific system.
    • Q: any small example we can run as a demonstrator? David note they have set a system from JLab's side already and it would have been good to know ahead (SUMS seems more advanced than the system at JLab).
  • Questions were asked as per
    • Can the read key be redistributed widely: The answer is YES. All users with a write key was told that the use of S3 is for OpenScience only (no PII, no secret proposal and CRADA, no protected information)
    • What mechanism can we used for a write key? We need to use best practices i.e.
      • Keys need to remain nominative (not shared with another user)
      • Keys should be transferred in plain text (encode/binary may be fine)
      • Write keys should be changed / modified frequently enough - suggested to change after each production wave as best practice (if the binary is compromised, it will not be re-usable)
         
  • Past action items and topics
    • Overleaf - the saga continues, the 3rd party intermediate vendor Overleaf used to work with is not "approved" by BNL. Procurement working with Overleaf again directly and reviewing their Terms & Conditions clauses.
    • Zoom for ECCE members not being BNL employees -> ITD indicated at the end that a procedure is too complicated. Jerome asked Rosi/Peter to send a list of ECCE members who would need a full zoom account (poor man's job manual work but OK)
    • Adding "mc" in another path (since the ecce path is not writeable) - done in /cvmfs/eic.opensciencegrid.org/opt/eic/bin/ (but the release did not seem to have worked and trying again)
    • Reported the discussion with Graham and the core ECCG team
      (a) monitoring is on our plate. will do storage simply, CPU needs to have a secondary group and report based on that.
      (b) we feel one meeting a month with the full ECCG would be enough (all together, review of achievements that can be shared with everyone, accounting reports, round table). Please feedback opinions. Reminder - we have Wouter as ATHENA rep for the ECCG, need a nomination from ECCE [NB: 0 feedback from CORE]
      (c) INFN was a possible resource provider for the EIC. Discussion were held and while their initial intents was to provide resources for one proto-collaboration, they now feel that sharing equally is the way to go. Will be working with them on setting an OSG submit host / receiving jobs.
    • Small matter: Discourse / Mattermost integration - if not discussions occurred in ECCE on how to proceed, Jerome suggests he moves forward with "whatever can be done" (setup a Mattermost channel and send messages there) and inform folks afterward. No opposition to it raised.
  • Todo or new items
    • S3 is not accessible from JLab - we understand this and Graham will ensure this is fixed (accessible from anywhere else / this is due to the Cyber traffic analysis but it breaks the CERTificate chain of S3)
    • The BNL grid submission node host CERTificate was broken (oops) - now fixed but this means Grid jobs could ne be accepted not be submitted.
    • Need a list of primary people who would be running samples for ECCE so we can set them with a secondary group.
    • FederatedID news: we have a go from Cyber to raise a Mattermost instance that accepts FederatedID from US National labs + CERN. Important step forward, BNL Indico may also be another service that would be Federated. This has relevance to the Wiki topic raised in the past by Peter and seems to be a major step forward. However, we still need concurrence from the site office.
    • David asked about the use of the grid tag +DESIRED_Sites=“XXX” - BNL team not aware of it (investigating).
There are minutes attached to this event. Show them.
Powered by Indico v3.3.8