Right now node just tells if it can or can not provide the label, but for cluster proper working it will be great to have more data about how much it will take to run the resource and properly elect the right executor.
The metrics:
Lifetime of the resource (#28) - will tell how much more time the node driver/resources will be busy.
Time to get the images - quick HEAD request for the URLs will give some idea on the archives size and previous downloads will provide average download speed to calculate the required time.
Storage required for the images could be calculated out of images metadata (which is stored in the head of the tar.xz archive) which contains the size of unpacked files. Maybe it will be not a good idea to cleanup the old images just to fulfill the resource request if the other nodes in the cluster will be faster...
So something like that, quite sure there is alot more and the logic to calculate all those input data will be quite complex, but will optimize the cluster utilization and will help with nodes specialization.
Right now node just tells if it can or can not provide the label, but for cluster proper working it will be great to have more data about how much it will take to run the resource and properly elect the right executor.
The metrics:
So something like that, quite sure there is alot more and the logic to calculate all those input data will be quite complex, but will optimize the cluster utilization and will help with nodes specialization.