Skip to content

Conversation

@vsoch
Copy link
Member

@vsoch vsoch commented Sep 8, 2025

I think I know how I'm going to do this now - see notes in README in this PR. It should be fairly simple, and the details will come down to a neat organization of metadata in the user home, and then how that data is queried and sent between stages. Basically:

# Wraps submit command to intercept, perform feasibility checks before the submit # Feasibility will check against cluster metadata / compatibility stuff flux remote submit <same as flux submit>

Then it goes to the delegate JobTap plugin included in this repository, and only includes feasible clusters. I'm designing it so the command can be installed cleanly to a flux install or used a la carte, and can also be extended with other subcommands. With this design, we don't need to reimplement flux submit - the above is using that exact class.

Signed-off-by: vsoch <vsoch@users.noreply.github.com>
This adds the basic structure for flux remote submit, which basically wraps the flux submit command (and is designed to support other subcommands in the future). This can be moved into the flux libexec cmd directory or just used as is. I next need to parse the submit request and then map attributes, etc. to the user defined compatibility data (cluster and resource needs) and I think then we are good. Signed-off-by: vsoch <vsoch@users.noreply.github.com>
Signed-off-by: vsoch <vsoch@users.noreply.github.com>
@vsoch vsoch changed the title wip: plan for fractale feasibility wip: prototype for fractale feasibility and delegation with flux Sep 8, 2025
Signed-off-by: vsoch <vsoch@users.noreply.github.com>
Signed-off-by: vsoch <vsoch@users.noreply.github.com>
This allows adding an --export flag to flux detect, which will either create a temporary context and detect (and export to zip) all local subsytems, or if given a config directory, run detect there (honoring force or not) and then export. Of course not cleaning up if it is not a temporary cluster/subsystem root. Signed-off-by: vsoch <vsoch@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

1 participant