Closed swozniewski closed 1 month ago
Thank you for opening the ticket. @swozniewski and team offered to help with the implementation. I will take a look in the code mid of the week and come up with some instructions how it could be realized. However, please keep in mind that at some point we will potentially stop the support to manage more than one pool in one TARDIS instance. But we did not finally concluded if that affects only multiple sites or also the different machine types of a site.
Concerning the future config layout: I guess we would keep the global (wrt site) quota parameter and add the possibility to override it by optional quota parameters in the machine types? (for backwards-compatibility and flexibility reasons)
The global parameter will correspond to the global quota for all machine types, which can be used or not. In addition, there might be quota entries for each of the machine types itself.
We decided not to implement this feature, since we will remove the support to run multiple sites and machine_types in one TARDIS instance in the future. Instead, you should run multiple TARDIS instances to reach that goal.
Thanks for your understanding, Manuel
It can be necessary to specify individual quotas per machine type, e.g. to use only 50% of nodes with local disk but more of other nodes in the same cluster. This can be solved by defining two separate sites in the config but a (optional) quota per machine type would be more intuitive and save lines in the config.