You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We should be able to run "beeflow config new" without interactions. Would we still want the interactive mode?
What would the defaults be? Most likely Slurm and blank times, and optional values for slurm like qos, account, reservation and time-limit. How would it be run for Flux?
Maybe we can have a flag for Flux, keeping in mind that we may need to add another workload scheduler like LSF
beeflow config new --workload_scheduler="Flux"
I think we need to look into the slurm values. What can we already add per job?
Also, the current "beeflow core start" and "beeflow list" now automatically check for a bee.conf and if it doesn't exist it makes one so that will need to be thought about.
The text was updated successfully, but these errors were encountered:
We should be able to run "beeflow config new" without interactions. Would we still want the interactive mode?
What would the defaults be? Most likely Slurm and blank times, and optional values for slurm like qos, account, reservation and time-limit. How would it be run for Flux?
Maybe we can have a flag for Flux, keeping in mind that we may need to add another workload scheduler like LSF
beeflow config new --workload_scheduler="Flux"
I think we need to look into the slurm values. What can we already add per job?
Also, the current "beeflow core start" and "beeflow list" now automatically check for a bee.conf and if it doesn't exist it makes one so that will need to be thought about.
The text was updated successfully, but these errors were encountered: