Ryan Day

Cool! That works much better (after substituting `task.` for `shell.`).

Sounds good. I now have: ``` [day36@tioga18:flux_test]$ flux mini run -n1 -g2 -o userrc=./testrc.lua env | grep VIS ROCR_VISIBLE_DEVICES=6,7 [day36@tioga18:flux_test]$ ``` I'll get ansible to stick a lua script that...

I think that `t_submit` probably makes sense for a default `deferred_from` value. I'm not quite clear, does the current implementation allow the user to set an absolute time, or just...

I think that something like this would work if the `flux_pragma_begin`, `flux_pragma_end`, and `flux_pragma` aliases were recognized and parsed by the `flux mini batch` command directly rather than requiring users...

I don't think that this issue (and https://github.com/flux-framework/flux-core/issues/2204) made it into my production RM features list, but I was thinking about it this week due to a 16 node job...

We just had someone asking about MPMD functionality (running multiple executables in the same MPI_COMM_WORLD) on rzvernal (https://llnl.servicenowservices.com/nav_to.do?uri=incident.do?sys_id=d9e2946097f1465484bdb546f053afea). Has anything come of this issue?

That's correct. We do want to charge DAT usage to the users bank(s).

I think that we would want dynamically created queues to be persist through restarts / reconfigs if we're using them for DATs. In that context, they're more like jobs than...

We might also need a `flux queue edit` or something along those lines so that we can take nodes out of, for example, the `batch` queue when we create a...

The overlapping queues are ideally never active at the same time, though if this were to be implemented it would be good to also put some controls in flux-core to...