[cluster priority] change how it is defined

If no priority has been defined in cluster.yaml, the priority is now added to the generated json files

• based on manufactured_at instead of created_at
• with +100 for cluster with gpu_devices The generator oar_properties now only reads the value from the json file.

added 3 commits

• 46b8f57a...387e79b7 - 2 commits from branch master
• 5bc2acc0 - [cluster priority] use manufactured_at for default priority, with a gpu + move...

Compare with previous version

added 1 commit

• 19813fb2 - [spec] regenerate with new cluster_priority

Compare with previous version

approved this merge request

approved this merge request

added 10 commits

• 19813fb2...5c22afc2 - 8 commits from branch master
• cc163b3a - [cluster priority] use manufactured_at for default priority, with a gpu + move...
• aad089ee - [spec] regenerate with new cluster_priority

Compare with previous version

attention aux jobs besteffort lorsque tu mettras à jour la propriété scheduler_priority: voir le bug suivant pour les détails, je ne sais pas s'il est applicable en 2025 : https://intranet.grid5000.fr/bugzilla/show_bug.cgi?id=6936

added 19 commits

• aad089ee...8c3a4180 - 17 commits from branch master
• 12951adc - [cluster priority] use manufactured_at for default priority, with a gpu + move...
• 26610b5f - [spec] regenerate with new cluster_priority

Compare with previous version

Discussion mattermost avec Pierre Neyron : le cluster_priority n'a rien à voir avec le scheduler_priority donc ne devrait pas poser le problème.

added 21 commits

• 26610b5f...49725001 - 19 commits from branch master
• 5abf376d - [cluster priority] use manufactured_at for default priority, with a gpu + move...
• a2a9e480 - [spec] regenerate with new cluster_priority

Compare with previous version

merged

mentioned in commit 31a6b04d