List view
- Due by June 7, 2024•6/6 issues closed
Point release to go in El Cal TOSS release on monday
Due by April 12, 2024•2/2 issues closed- Due by May 6, 2024•7/7 issues closed
- Due by March 5, 2024
- Due by February 5, 2024•1/1 issues closed
- Due by January 4, 2024•1/1 issues closed
- Due by September 5, 2023•2/2 issues closed
- No due date•6/6 issues closed
- Due by June 9, 2023•2/2 issues closed
- Due by May 2, 2023•1/1 issues closed
- Due by April 4, 2023•3/3 issues closed
- Due by March 7, 2023•1/1 issues closed
- Due by February 7, 2023•20/20 issues closed
- Due by December 16, 2022•4/4 issues closed
- Due by November 1, 2022•9/9 issues closed
- Due by October 3, 2022•10/10 issues closed
- Due by September 6, 2022•5/5 issues closed
- Due by August 2, 2022•2/4 issues closed
- Due by July 1, 2022•3/3 issues closed
- Due by March 2, 2022•5/5 issues closed
- Due by December 3, 2021•8/8 issues closed
Tag next release of flux-core
Due by June 12, 2020•10/10 issues closedThis release should contain a minimum viable version of the new execution system and simple scheduler.
Due by July 31, 2019•4/4 issues closed- No due date•24/24 issues closed
- No due date•16/16 issues closed
Some KVS changes are planned to support the KVS job schema proposed in RFC 16. This milestone tracks progress towards those changes.
No due date•4/6 issues closed- No due date•12/12 issues closed
- No due date•8/8 issues closed
- No due date•18/18 issues closed
Tag and release flux-core 0.6.0
No due date•1/1 issues closed- No due date•3/3 issues closed
- No due date•9/9 issues closed
- No due date•6/6 issues closed
- No due date
- No due date•4/4 issues closed
Multi-user Requirements/Use Cases Containers Requirements Resource Info Redesign RDL db (document) Scalable Launch Simple remote execution + design full WRECK replacement Job Accounting Requirements & Use Cases User Bank Acct. Requirements & Use Cases Job Provenance Design +KVS Persistence Monitoring Design + Working prototype Scheduling Simsched Testing Increase test coverage, distributed testing
No due dateThis is where flux will be considered sufficient to be used in place of SLURM or Torque for a production system. A more complete specification is listed on the plans wiki [here](https://github.com/flux-framework/flux-plans/wiki/s4). Planned components include: * Multi-user support * Containers * Resource Info (e.g. sinfo equivalent) * Queue Info (e.g. squeue equivalent) * Scalable Launch * Job Accounting * User Bank Accounting (No integration with Slurm/Moab) * Job Provenance (capture only) * Monitoring * Scheduling - Deliver 1) Fair share and 2) FCFS+backfill schedulers
No due date