Manage Resources

Each agency has a certain amount of compute hours for each resource (for example, x86 or GPU hours in Deucalion or Cloud hours in Cloud and Distributed Systems) on the infrastructures it has access to. This page explains how those hours are granted and how they can be distributed.

Compute hours per agency

Every agency has its own allocation of compute hours per resource. You can see what has been allocated to an agency in the Agency page: select the agency in the tree and check its Resources Allocated section, which shows the current distribution.

Distributing resources to sub-agencies and projects

Once an agency has been given compute hours, its staff can distribute those hours between its sub-agencies and its projects. This is done from the Agency Page page (reachable from the navigation bar), then select one resource in the Resources Allocated group, and click one of the resources.

📸 Screenshot: the "List Resources" / resource distribution page, showing the Agencies and Projects tables for a resource. docs/images/resource-distribution.png — replace this placeholder with a real screenshot from your environment.

Hours can only go up, never down

Once a value has been set for a sub-agency or a project, it cannot be lowered — only increased.

Example: if you give a project 100 hours of the x86 resource, you can later raise that value to 150 hours, but you can no longer set it back down to, 80 hours. If you try to enter a value below the current one, Lince will show a validation message and won't let you save it.

This means resource distribution is a one-way process at each level: hours can be moved down the hierarchy (from an agency to its sub-agencies and projects) and increased over time, but never reclaimed by lowering an existing value. Plan your allocations with this in mind, especially when a project or sub-agency is only expected to need resources for a limited period.