gflow 0.3.7

A lightweight, single-node job scheduler written in Rust.
Documentation 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38

# gflow Binary Refactoring Design

This document outlines the plan to refactor `gflow` into multiple binaries, inspired by the design of Slurm.

## New Binary Structure

The `gflow` project will be split into the following binaries:

- **`gflowd`**: The core daemon responsible for job scheduling and execution. This remains the central component.
- **`gbatch`**: The core client for submitting (`add`) and creating (`new`) jobs. Inspired by `sbatch`.
- **`gqueue`**: Queries the job queue (replaces `gflow list`). Inspired by `squeue`.
- **`gsignal`**: Sends signals to a job (e.g., finish, fail). Replaces `gcancel`.
- **`gctl`**: Manages the daemon (replaces `gflow daemon`). Inspired by `scontrol`/`systemctl`.

## Architecture Diagram

```mermaid
graph TD
    subgraph User Commands
        A[gbatch] --> C{gflowd}
        B[gqueue] --> C
        D[gsignal] --> C
        F[gctl] --> C
    end

    subgraph Core
        C
    end
```

## Implementation Plan

1.  Define the new binaries in `Cargo.toml`.
2.  Create a `main.rs` file for each new binary.
3.  Move the logic from the existing `gflow` subcommands into the corresponding new binaries.
4.  Refactor shared code (like the client and configuration) into the `gflow` library crate to be used by all binaries.
5.  Update the main `gflow` command to either act as a dispatcher or provide documentation for the new commands.
6.  Ensure all binaries compile and all tests pass.