Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Asking for specific rabbits in jobspec #198

Open
jameshcorbett opened this issue Aug 19, 2024 · 1 comment
Open

Asking for specific rabbits in jobspec #198

jameshcorbett opened this issue Aug 19, 2024 · 1 comment

Comments

@jameshcorbett
Copy link
Member

Marty has been adding some --requires=hosts constraints to his jobspecs to force flux to pick compute nodes associated with specific rabbits. However, it would be more ergonomic to simply specify the rabbits desired, since that's a much more compact representation. Something like --requires=hosts:rabbit203 to cause the scheduler to only choose compute nodes on the same rack as rabbit203.

@grondo
Copy link
Contributor

grondo commented Aug 23, 2024

I'm more just thinking out loud here, but --requires=hosts:rabbit203 would only work (I think) if constraining the resource graph to only vertexes that match a "hostname" of rabbit203 would result in something that could match the rest of the job request. (Given that I have no idea how the datawarp/rabbit matches work in Fluxion, I could be way off here)

An alternative would be to establish a new requires scheme rabbits which, when used (e.g. as --requires=rabbbits:rabbit203), would activate a custom rabbit constraint that would constrain the graph to only the resources with access or that would use the specified rabbits. A drawback to this is that there is no way that I know of to extend the constraints supported by Fluxion at the moment.

I just thought I'd bring these points up in case they were helpful. If the hosts solution works then that might be preferable.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants