Catalogue Description¶
The following section describe the purpose of each catalogue table which you can see in the schema drawing available for download as a generated artifact for every commit to the CTA main branch here.
Mount Rule Tables¶
There are 3 mount rule tables defined:
requester_activity_mount_rule
requester_group_mount_rule
requester_mount_rule
The Scheduler code checks these 3 tables for each archive/retrieve request at queueing time by the CTA-Frontend. The purpose is to find a matching mount rule row(s) and resolve the appropriate mount policy. mount_policy_name is a column referencing the Mount Policy table.
Mount Policy Table¶
The schema can be found via to-be-added-link.
This table stores named mount policies which are matched with each archive/retrieve request at queueing time via the Mount Rule tables. They are one of the key parameters determining if the Scheduler shall schedule a mount.
Each row corresponds to a mount policy defined by the following 5 values which are being assigned to each queued Archive and Retrieve Requests:
| Value | Type | Description |
|---|---|---|
| mount_policy_name | String | The name of the mount policy |
| archive_priority | Unsigned int | The priority of Archive Requests. If this number is high, the Archival priority will be high |
| archive_min_request_age (in seconds) | Unsigned int | The minimum age of the queued Archive Request to trigger a mount |
| retrieve_priority | Unsigned int | The priority of RetrieveRequests. If this number is high, the Retrieval priority will be high |
| retrieve_min_request_age (in seconds) | Unsigned int | The minimum age of the queued Retrieve Request to trigger a mount |