Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
dws: crudely enforce storage count constraints
Problem: as described in issue #171, creating many MDTs is a bad for performance, and usually goes against what is explicitly required by directivebreakdown resources. However, there is not yet a good way to get Fluxion to handle MDT allocation. Bypass Fluxion allocation completely, and tell DWS to create exactly the number of allocations requested in the .constraints.count field (which is usually found on MDTs). Place the allocations on the rabbits which have the most compute nodes allocated to the job. This is intended to be only a temporary solution, since it adds a new potential problem, in that some rabbit storage is used which is not tracked by Fluxion. This could lead to overallocation of resources, causing jobs to fail with errors. However, this seems unlikely to occur in practice, since MDTs are small and Fluxion always gives jobs more storage than they asked for, so there should usually be some spare storage.
- Loading branch information