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

Conversion of JGF version and grow support #7

Open
2 of 3 tasks
vsoch opened this issue Feb 24, 2024 · 1 comment
Open
2 of 3 tasks

Conversion of JGF version and grow support #7

vsoch opened this issue Feb 24, 2024 · 1 comment

Comments

@vsoch
Copy link
Member

vsoch commented Feb 24, 2024

Fluxion currently requires JGF version 1. The version 2 is a better design that allows for indexing the nodes based on name (as opposed to a list) and there are subtle differences in the design. I would prefer to continue developing tools (e.g., compspec-go) anticipating v2, so I think an OK strategy for the time being will be to allow fluence to accept a v2 and convert to v1 to give to flux. I'll be able to implement this shortly when I'm ready (I'm currently adding the export of the cluster graph from compspec-go, which I'm going to use version 2 for). This will mean that:

  • compspec-go extracts node-level metadata comspec extract
  • the nodelevel metadata is assembled into JGF v2 compspec create nodes
  • the nodes (v2) are sent to the rainbow scheduler, which TBA will have some variant of fluxion (I hope) that can accept the v2 and convert to v1 before sending to the underlying library via the bindings.
@vsoch vsoch changed the title Conversion of JGF v2 to JGF v1 Conversion of JGF version and grow support Feb 25, 2024
@vsoch
Copy link
Member Author

vsoch commented Feb 25, 2024

I realize we will need not just an ability to convert JGF for rainbow, but also the grow functionality in flux-sched. I think @zekemorton is working on the guts of that? And I think a part of it might be here? flux-framework/flux-sched#1061

In the meantime I'll prototype a faux fluxion that can accept (and merge) different resource graphs to do some very questionable, and janky scheduling. 😆

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

1 participant