Jim Garlick

> I'm not sure how flux-core gets away with not setting the environment variable) There are a number of compiled-in paths that are altered if flux detects that it is...

Renaming this issue to reflect a more specific problem: that of deciding when to start a job when it exceeds one time of day dependent limit set but not another.

Also, the annotation of the queue in the alloc response should be dropped, as this is not information that the scheduler needs to provide. Tools should instead be using the...

The test script `t/t1006-qmanager-multiqueue.t` will need to be changed as a result of this change. That script might be a good place to start to understand how the current queue...

@JaeseungYeom - FYI I've made some progress on this today and will get a PR posted shortly.

Now that we have configurable limits defined in RFC 33 and enforcement at ingest by flux-core, I'll rename this issue to indicate the gap that remains, which I *think* is...

For a workaround, the qmanager module command line options also work from TOML, e.g. ```toml [sched-fluxion-qmanager] queues = "batch debug" queue-policy-per-queue="batch:easy debug:fcfs" ``` If we initially require queues to be...

In the meeting today we discussed whether we should try to do this in the context of the `qmanager_opts_t` class or use the C approach used throughout flux-core, the gist...

Just noticed that there are a couple more "per-queue" configuration variables in fluxion e.g. ``` policy-params-per-queue = "batch:max-reservation-depth=100000,reservation-depth=64" queue-params-per-queue = "debug:queue-depth=16" ``` Presumably we will need to map these into...

Closing this one, as I think the main fluxion issue is covered in #642. @cmoussa1 if this was tracking work to be done in flux-accounting, please open an issue there.