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
Which would allow fluxion to pick rabbit-ssds and nodes completely independently, which would be a perfect match for lustre file systems. However, if a job also asked for xfs or gfs2 in addition to lustre, I think the only option would be to fall back to forcing all storage to be rack-local.
To enable this, directivebreakdown.py would need to be updated to recognize lustre-only directives, and coral2_dws would need to inspect the JGF output from Fluxion after scheduling to see which rabbits were selected, rather than simply assuming (as it does now) that rabbits were chosen according to the nodes that were chosen.
The text was updated successfully, but these errors were encountered:
If #157 goes in and changes the layout of the resource graph, it will enable jobspecs that look like this:
Which would allow fluxion to pick rabbit-ssds and nodes completely independently, which would be a perfect match for lustre file systems. However, if a job also asked for xfs or gfs2 in addition to lustre, I think the only option would be to fall back to forcing all storage to be rack-local.
To enable this,
directivebreakdown.py
would need to be updated to recognize lustre-only directives, andcoral2_dws
would need to inspect the JGF output from Fluxion after scheduling to see which rabbits were selected, rather than simply assuming (as it does now) that rabbits were chosen according to the nodes that were chosen.The text was updated successfully, but these errors were encountered: