search

flux-framework / rfc

Flux RFC project
https://flux-framework.readthedocs.io/projects/flux-rfc/
7 stars 13 forks source link

rfc27: document job feasibility service #425

Closed grondo closed 3 weeks ago

grondo commented 3 weeks ago

This is a first cut at documenting the feasibilty service proposed in #384.

Fixes #384

grondo commented 3 weeks ago

Ok, I've pushed changes that I believe address @garlick's comments (also had to add a URL to linkcheck ignore). This could use another pass.

grondo commented 3 weeks ago

I was wondering about that too. I wasn't sure if it was appropriate to go into that much detail in this RFC. I like your suggestion.

grondo commented 3 weeks ago

so it would work whether loaded on all ranks or just rank 0?

Side note: in the case of the Fluxion feasibility service, there will be a non-trivial memory hit for running this service module, so I think the intent is not to run it on every rank, but possibly rank 0 and the login nodes? I wonder if the sentence "all ranks or just rank 0" should be modified to state something along the lines of

...the service SHALL be loaded on one or more ranks that are upstream of any rank where job submission is expected.

Or something?

garlick commented 3 weeks ago

Works for me.

grondo commented 3 weeks ago

Uhh, I took a stab at it, but not too happy with the result. Feel free to suggest editing.

garlick commented 3 weeks ago

, therefore the feasibility service SHALL be loaded on one or more ranks upstream of any rank where job submission is expected.

maybe instead

. The request is routed to a local feasibility service if available, or an upstream one per RFC 3.

grondo commented 3 weeks ago

Thanks, I took your suggestion verbatim (sorry, having trouble with my prose today) and force-pushed the result.

grondo commented 3 weeks ago

I guess I'll set MWP here since this was approved. We can always update with future PRs.