We will have the DUNE General computing meeting:
https://fnal.zoom.us/j/336647590
Meeting ID: 336 647 590
standard computing password, will be sent by email for those who don't know it.
One tap mobile
+16699006833,,336647590# US (San Jose)
+16465588656,,336647590# US (New York)
Dial by your location
+1 669 900 6833 US (San Jose)
+1 646 558 8656 US (New York)
Meeting ID: 336 647 590
Find your local number: https://fnal.zoom.us/u/adJsct1aBR
Sites, networking, and central DUNE computing services (GlideinWMS, SAM, RUCIO, CRIC, ETF, Databases).
https://fifemon.fnal.gov/monitor/d/000000053/experiment-batch-details?orgId=1&from=now-30d&to=now-5m&var-experiment=dune
https://samweb.fnal.gov:8483/station_monitor/dune/stations/dune/projects
(This item should probably be split into smaller units?)
Add in Coldbox (Iceberg/np02/np04)
Jake and Tom have deployed the split dunetpc to GitHub, and udpated the Jenkins build script and protoduneana. Still to do: migrate the wiki pages, and exercise the release procedure. Coach users. Maintain the releases. We'd like the art/LArSoft team to continue providing feature branches for the new products similar to how they did for dunetpc when the art and LArSoft APIs change (mostly include-file location changes and CMakeLists.txt file changes). It would be nice to add garsoft, garana and duneanaobj to that list of products with feature branches to be added.
There is a legacy dunetpc repository in https://github.com/DUNE/ made (we think) by Ben Morgan. It is three years old and has no tags. Ben is no longer on the DUNE collaboration list. It would be good to make that one go away, or update it to the final version that's in Redmine and disable pushes, as has been done for the Redmine repo. The history of each file has been preserved in the new split repositories, but the old dunetpc will be kept on Redmine for inspection purposes. We don't want people developing and pushing to the dunetpc in GitHub though -- should use the new repositories. The wiki page and the README.md for dunetpc in GitHub say it's legacy and not maintained.
Chris Backhouse noted that there are mentions of dunetpc in the new repositories. Almost all instances of that reflect poor design choices made over the years and some instances correspond to code that would not work on the grid, or even with recent releases of dunetpc. So there is some cleanup to do. And conventions for library specifications in CMakeLists.txt files have evolved over time, and we have a mixture that currently works, but it may need some maintenance.
Jake has been in touch with Vito about updating the CI tests.
The Spack migration will also need to work with the new products.
duneanaobj is still rather "standalone". We did not touch that product this round. And dune-raw-data is really a daq-group product, but we have been incrementing version numbers and doing small maintenance to it in order to keep ProtoDUNE-SP data readin alive. It still is in Redmine and has a separate release procedure.
SAM, RUCIO etc
WFS, HEPCloud, GlideinWMS, POMS, etc. https://github.com/DUNE/dist-comp/labels/WMSdev
CRIC
ETF site monitoring, RUCIO monitoring, perfSonar network monitoring
https://etf-dune-preprod.cern.ch/etf/check_mk/index.py?start_url=%2Fetf%2Fcheck_mk%2Fview.py%3Fview_name%3Dallhosts
https://dune.monitoring.edi.scotgrid.ac.uk/app/dashboards#/view/7eb1cea0-ca5e-11ea-b9a5-15b75a959b33?_g=(filters:!(),refreshInterval:(pause:!t,value:0),time:(from:now-1d,to:now))