POMS: Difference between revisions
(→UconDB) |
(→UconDB) |
||
Line 22: | Line 22: | ||
https://dbdata0vm.fnal.gov:8444/mu2e_ucondb_prod/app/... - cached, external and internal access | https://dbdata0vm.fnal.gov:8444/mu2e_ucondb_prod/app/... - cached, external and internal access | ||
http://dbdata0vm.fnal.gov:9091/mu2e_ucondb_prod/app/... - cached, internal access only | http://dbdata0vm.fnal.gov:9091/mu2e_ucondb_prod/app/... - cached, internal access only | ||
FCL files are saved to the UconDB in dedicated folders. It's not possible to use dots in the name of the database folders, so we replace with underscores, as in: | |||
https://dbdata0vm.fnal.gov:9443/mu2e_ucondb_prod/app/UI/folder?folder=cnf_mu2e_pot_db_test_v12_fcl | |||
The POMS FCL stages take care of creating the folders and saving the FCL files. The SAM location of the files stored in the database looks like this: | |||
$ samweb locate-file cnf.mu2e.POT.db_test_v12.001201_00000001.fcl | |||
dbdata0vm.fnal.gov:/mu2e_ucondb_prod/app/data/cnf_mu2e_POT_db_test_v12_fcl | |||
==References== | ==References== |
Revision as of 01:32, 18 December 2021
Introduction
The Production Operations Management Service (POMS) is a computing division tool that helps users to run large and complex grid campaigns. It provides
- control scripts and GUI interface
- chaining of multiple stages of a grid campaign
- re-submission of failed jobs
- analysis of logs and database entries for results
Currently (8/2021), we are only using POMS for Production as a test. Users can use Mu2e tools
project-py is s python scripts which provides a command line interface.
UconDB
mu2e_ucon_prod - created 11/2021 to help with MDC2020
- database mu2e_ucon_prod owned by nologin role mu2e_ucon_prod;
- Kerberos-authenticated roles: brownd kutschke srsoleti
- md5 authenticated role 'mu2e_ucon_web' (for POMS)
- port is 5458 (on ifdbprod/ifdb08)
https://dbdata0vm.fnal.gov:9443/mu2e_ucondb_prod/app/... - not cached, external and internal access http://dbdata0vm.fnal.gov:9090/mu2e_ucondb_prod/app/... - not cached, internal access only https://dbdata0vm.fnal.gov:8444/mu2e_ucondb_prod/app/... - cached, external and internal access http://dbdata0vm.fnal.gov:9091/mu2e_ucondb_prod/app/... - cached, internal access only
FCL files are saved to the UconDB in dedicated folders. It's not possible to use dots in the name of the database folders, so we replace with underscores, as in:
https://dbdata0vm.fnal.gov:9443/mu2e_ucondb_prod/app/UI/folder?folder=cnf_mu2e_pot_db_test_v12_fcl
The POMS FCL stages take care of creating the folders and saving the FCL files. The SAM location of the files stored in the database looks like this:
$ samweb locate-file cnf.mu2e.POT.db_test_v12.001201_00000001.fcl dbdata0vm.fnal.gov:/mu2e_ucondb_prod/app/data/cnf_mu2e_POT_db_test_v12_fcl
References
- POMS production top
- redmine
- DUNE video tutorial