Open gcpmendez opened 1 month ago
I'm not sure what the solution is here. Sure you can define an initializer to filter based on the cluster if you don't already have it, but if you've defined 2 clusters, OnDemand will act as if they're actually two clusters.
I'm not aware of the virtual cluster pattern here where teide is actually just a partition on anaga (or vice versa), but I guess I'd ask if you actually need the two separate cluster definitions.
We notice that in the
Jobs
->Active jobs
tab there are duplicate jobs per cluster as both have the same slurm configuration and slurm is configured with a single cluster:and in ondemand we can verify the cluster configurations:
According to the following thread https://discourse.openondemand.org/t/configure-partitions-as-clusters/701/2 we can try to create an "initialiser" to filter the jobs.
The best would be to filter the jobs by "partition" and assign the "anaga" cluster when the jobs are in the "gpu" partition and assign them to the "teide" cluster in the rest of the cases.
Any help is welcome in order to correctly view the jobs associated to each virtual cluster having a single cluster configured in Slurm. thanks in advance))