eResearch Doc

User Tools

Site Tools

You are here: start » hpc » accounting
hpc:accounting

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
hpc:accounting [2025/12/10 07:31] – [Resource accounting uniformization] Yann Sagonhpc:accounting [2026/03/19 13:51] (current) – Yann Sagon
Line 41: Line 41:
 This approach guarantees consistent, transparent, and fair resource accounting across all heterogeneous components of the cluster. This approach guarantees consistent, transparent, and fair resource accounting across all heterogeneous components of the cluster.
  
-You can check the up to date conversion details by inspecting the parameters of any partition on the clusters. The same conversion table is applied everywhere.+You can check the up to date conversion details by inspecting the parameters of any partition on the clusters. The same conversion table is applied on all our clusters and partitions.
  
 <code> <code>
Line 71: Line 71:
  
 To view details of owned resources, users can run the script:   To view details of owned resources, users can run the script:  
-''ug_getNodeCharacteristicsSummary.py''+''ug_getNodeCharacteristicsSummary''
 This script provides a summary of the node characteristics within the cluster. This script provides a summary of the node characteristics within the cluster.
  
Line 78: Line 78:
 Output example of the script: Output example of the script:
 <code> <code>
-ug_getNodeCharacteristicsSummary.py --partitions private-<group>-gpu private-<group>-cpu --cluster <cluster> --summary+ug_getNodeCharacteristicsSummary --partitions private-<group>-gpu private-<group>-cpu --cluster <cluster> --summary
 host    sn             cpu    mem    gpunumber    gpudeleted  gpumodel                      gpumemory  purchasedate      months remaining in prod. (Jan 2025)    billing host    sn             cpu    mem    gpunumber    gpudeleted  gpumodel                      gpumemory  purchasedate      months remaining in prod. (Jan 2025)    billing
 ------  -----------  -----  -----  -----------  ------------  --------------------------  -----------  --------------  --------------------------------------  --------- ------  -----------  -----  -----  -----------  ------------  --------------------------  -----------  --------------  --------------------------------------  ---------
Line 155: Line 155:
  
 <code> <code>
-(baobab)-[sagon@login1] $ ug_slurm_usage_per_user.py --help +(baobab)-[sagon@login1] $ ug_slurm_usage_per_user --help 
-usage: ug_slurm_usage_per_user.py [-h] [--user USER] [--start START] [--end END] [--pi PI] [--group GROUP] [--cluster {baobab,yggdrasil,bamboo}] [--all-users] [--aggregate] [--report-type {user,account}]+usage: ug_slurm_usage_per_user [-h] [--user USER] [--start START] [--end END] [--pi PI] [--group GROUP] [--cluster {baobab,yggdrasil,bamboo}] [--all-users] [--aggregate] [--report-type {user,account}]
                                   [--time-format {Hours,Minutes,Seconds}] [--verbose]                                   [--time-format {Hours,Minutes,Seconds}] [--verbose]
  
Line 182: Line 182:
 === Usage details of a given PI === === Usage details of a given PI ===
 <code> <code>
-(baobab)-[sagon@login1] $ ug_slurm_usage_per_user.py --pi **** --report-type account --start 2025-01-01+(baobab)-[sagon@login1] $ ug_slurm_usage_per_user --pi **** --report-type account --start 2025-01-01
 -------------------------------------------------------------------------------- --------------------------------------------------------------------------------
  
Line 203: Line 203:
 Usage example to see the resource usage from the beginning of 2025 for all the PIs and associate users of the group private_xxx. The group private_xxx owns several compute nodes: Usage example to see the resource usage from the beginning of 2025 for all the PIs and associate users of the group private_xxx. The group private_xxx owns several compute nodes:
 <code> <code>
-(baobab)-[sagon@login1 ~]$ ug_slurm_usage_per_user.py --group private_xxx --start=2025-01-01 --report-type=account+(baobab)-[sagon@login1 ~]$ ug_slurm_usage_per_user --group private_xxx --start=2025-01-01 --report-type=account
 -------------------------------------------------------------------------------- --------------------------------------------------------------------------------
  
Line 228: Line 228:
 === Aggregate usage by all users of a given PI === === Aggregate usage by all users of a given PI ===
 <code> <code>
-$ ug_slurm_usage_per_user.py --pi ***** --report-type account --start 2025-01-01 --all-users --aggregate+$ ug_slurm_usage_per_user --pi ***** --report-type account --start 2025-01-01 --all-users --aggregate
 -------------------------------------------------------------------------------- --------------------------------------------------------------------------------
  
Line 256: Line 256:
  
 === sreport examples === === sreport examples ===
 +
 +<note important>by default, the TRES (tracking resource) shown by sreport is CPUh. If you want to see what will be accounted and billed, you need to use the TRES "billing".</note>
  
 Here are some examples that can give you a starting point : Here are some examples that can give you a starting point :
hpc/accounting.1765351913.txt.gz · Last modified: by Yann Sagon