Jim Garlick

Well it seems neither the `--requires=host:X` nor starting flux with a node down is required. It works to simply drain a node then submit a job that can't run without...

OK it's trivially reproduceable in a standalone flux instance with no queues if the default queue policy of fcfs is changed to easy: ``` $ cat fluxion.toml [sched-fluxion-qmanager] queue-policy =...

Let's close this issue. I opened flux-framework/flux-sched#1210 for athe sched follow-up

I'm not sure if this is relevant but on the fedora page for mpich, I found this: >This build also include support for using the 'module environment' to select which...

Idea: add a new job state RESERVED between SCHED and RUN such that a job request with a special attribute could get its alloc response _R_ from the scheduler early,...

I guess the main appeal to me is that we wouldn't need to have a separate set of tools and rules for reservations like slurm. A job request would be...

I didn't really say this clearly but yes, I was thinking some new jobspec attributes would be the way a job would request "reserved" resources. We already have a duration,...

I'd say let's hit the reset button on this discussion and start from the requirements. IOW let's drop the idea of RESERVED state and also of "regular jobs" having reservations...

On user restrictions: only the system instance currently loads the `mf_priority` plugin from flux-accounting, so we should think about how we would restrict users in a multi-user sub-instance. A related...

For the record, @kkier voiced the opinion in that meeting that when flux restarts, any dynamically created queues should disappear as it would seem surprising otherwise. Not sure how that...