You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I understand that ParallelCluster does not support user or cost tracking natively at this moment, therefore I would like to put in this feature request of allowing:
The tagging a slurm compute node dynamically when a user procures a compute node from slurm. Such as to add/update a subset of tags based on values passed to slurm node (eg. login name).
To allow the setting of other compute node tagging based on other rules apart from CustomActions.
Another way to do this would be to use an RDS database for Slurm accounting. It would cost a bit for the database, but it might be worth it if you want to track usage and costs.
I had users add the below to their sbatch submission file, the goal being to track costs in AWS Cost Explorer. -
MyInstID=$(srun --nodes=15 ec2-metadata --instance-id | cut -d " " -f 2)
srun --nodes=15 aws ec2 create-tags --resources $MyInstID --tags Key=Name,Value="Compute-Joe Vanilla" --region us-east-1
Hello Team,
I understand that ParallelCluster does not support user or cost tracking natively at this moment, therefore I would like to put in this feature request of allowing:
Currently the below blog has been suggested as a potential workaround:
https://swsmith.cc/posts/cost-explorer-pcluster.html
However I would like this to be a native feature.
The text was updated successfully, but these errors were encountered: