- Nov 28, 2022
-
-
Joao Afonso authored
New states REPACKING/EXPORTED, new internal states, new maintenance runner for cleaning-up retrieve queue requests
-
- Nov 16, 2022
-
-
Jorge Camarero Vera authored
-
- Oct 31, 2022
-
-
Lasse Tjernaes Wardenaer authored
-
- Oct 07, 2022
-
-
Jorge Camarero Vera authored
-
- Oct 06, 2022
-
-
Lasse Tjernaes Wardenaer authored
-
- Oct 04, 2022
-
-
Jorge Camarero Vera authored
-
- Sep 06, 2022
-
-
Jorge Camarero Vera authored
-
- Aug 15, 2022
-
-
Jorge Camarero Vera authored
-
- Aug 12, 2022
-
-
Jorge Camarero Vera authored
-
- Aug 09, 2022
-
-
Jorge Camarero Vera authored
-
- Jul 19, 2022
-
-
David Smith authored
-
- Jul 15, 2022
-
-
Cedric Caffy authored
-
- Jun 14, 2022
-
-
Julien Leduc authored
current preflight tests are targetting eos/xrootd regressions
-
- Jun 10, 2022
-
-
Volodymyr Yurchenko authored
-
- Apr 26, 2022
-
- Apr 22, 2022
-
-
mvelosob authored
-
- Apr 11, 2022
-
-
Miguel Barros authored
-
- Mar 28, 2022
-
-
Jorge Camarero Vera authored
-
- Mar 24, 2022
-
-
Miguel Barros authored
Remove catalogue version 5.0 from CTA and move backwards compatible changes to catalogue version 4.6
-
- Mar 23, 2022
-
-
Joao Afonso authored
-
- Mar 14, 2022
-
-
Joao Afonso authored
-
- Mar 04, 2022
-
-
mvelosob authored
-
- Feb 15, 2022
-
-
Joao Afonso authored
-
- Feb 09, 2022
-
-
Joao Afonso authored
-
- Feb 07, 2022
-
-
Joao Afonso authored
-
- Jan 14, 2022
-
-
Joao Afonso authored
-
- Dec 08, 2021
-
-
Julien Leduc authored
-
- Dec 02, 2021
-
-
Jorge Camarero Vera authored
-
- Nov 30, 2021
-
-
mvelosob authored
Activity Mount Rules associate a Mount Policy to an activity regex. When recalling a file, the users can specify an activity (i.e. by using filepath?activity=x). If specified, this activity will be used to select a matching activity mount rule, if one exists. If more than one Activity Mount Rule matches the activity, the one with highest retrieve priority will be chosen. Acitivity Mount Rules take precedence over Requester Mount Rules.
-
- Oct 21, 2021
-
-
mvelosob authored
-
- Oct 07, 2021
-
-
mvelosob authored
Remove the looping through the retrieve queue jobs while holding the global lock in OStoreDB::fetchMountInfo. This was done when a tape was disabled, since we mount disabled tapes if they have pending retrieve requests. Instead we now mount the tape if the queue object info as in the mount policy map a mount policy whose name starts with "repack". With this change, cta-admin now forces repacks added with the --disabledtape to have a mount policy prefixed with repack (without the --disabledtape flag, the mount policy can have any name) Also Removed the criteria that a disabled/broken tape is mounted if the queue is filled with deleted retrieved jobs. Eventually the maxrequestage for the queue will expire, the tape will be mounted and the queue flushed
-
- Aug 02, 2021
-
-
Jorge Camarero Vera authored
-
- Jun 15, 2021
-
-
Jorge Camarero Vera authored
-
- Jun 02, 2021
-
-
Jorge Camarero Vera authored
-
- May 06, 2021
-
-
Michael Davis authored
-
- Feb 18, 2021
-
-
Cedric Caffy authored
-
Cedric Caffy authored
-
- Feb 02, 2021
-
-
Cedric Caffy authored
-
Cedric Caffy authored
-
Cedric Caffy authored
- Removed the counting of the readonly tapes as they don't exist - Count the ACTIVE tapes instead of not disabled ones - Repack disabled tape system test now undisables the tape after having reclaimed it
-