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.

Sign up for GitHub

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

Jump to bottom

Flux job submit needs to support workdir and envars #12

Closed
vsoch opened this issue Nov 8, 2022 · 2 comments · Fixed by #13
Closed

Flux job submit needs to support workdir and envars #12

vsoch opened this issue Nov 8, 2022 · 2 comments · Fixed by #13

Comments

@vsoch
Copy link
Member

vsoch commented Nov 8, 2022

We currently (for the operator) have this as part of the CRD, however the working directory for running the original container doesn't have to be where the job runs! Let's expose this.
@vsoch vsoch changed the title Flux job submit needs to support workdir Flux job submit needs to support workdir and envars Nov 8, 2022
@vsoch
Copy link
Member Author

vsoch commented Nov 8, 2022

Updating title - the user should be able to provide one off envars that replace whatever is set in the environment!

@vsoch
Copy link
Member Author

vsoch commented Nov 8, 2022

Actually let's just add all of these!

num_tasks
cores_per_task
gpus_per_task
num_nodes: 
exclusive

And if not defined, stick to defaults.

@vsoch vsoch mentioned this issue Nov 8, 2022
Merged
@vsoch vsoch closed this as completed in #13 Nov 9, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Add python client flux-framework/flux-restful-api
1 participant
@vsoch