Merge pull request #31 from miciav/feature/runner-controller-ui

Feature/runner controller UI

Author: miciav

.gitignore

@@ -47,7 +47,7 @@ htmlcov/
 /reports/
 /data_exports/
 /tests/results
-/lb_runner/plugins/_user/
+/lb_plugins/plugins/_user/
 /temp_keys/
 
 # Ansible runtime artifacts

AGENTS.md

@@ -5,7 +5,7 @@
 - Runner code is under `lb_runner/`; controller under `lb_controller/`; app-layer API under `lb_app/`; UI under `lb_ui/`.
 - Reporting and post-processing live under `lb_analytics/`; shared utilities in `lb_common/`; provisioning helpers in `lb_provisioner/`.
 - Use the stable APIs from `lb_runner.api`, `lb_controller.api`, and `lb_app.api` instead of importing deep modules.
-- Collectors sit in `lb_runner/metric_collectors/` (PSUtil, CLI, perf, eBPF) and workload plugins in `lb_runner/plugins/` (stress-ng, dd, fio, hpl), each with base abstractions plus concrete implementations.
+- Collectors sit in `lb_runner/metric_collectors/` (PSUtil, CLI, perf, eBPF) and workload plugins in `lb_plugins/plugins/` (stress-ng, dd, fio, hpl), each with base abstractions plus concrete implementations.
 - Tests are under `tests/`; sample usage is in `example.py`. Output artifacts are written to `benchmark_results/`, `reports/`, and `data_exports/` (these may be absent until generated).
 
 ## Build, Test, and Development Commands

GEMINI.md

@@ -74,5 +74,5 @@ uv run pytest -m tui
 ## File Structure Highlights
 *   `pyproject.toml`: Dependency and build configuration.
 *   `lb_runner/benchmark_config.py`: Configuration dataclasses.
-*   `lb_runner/plugins/`: Workload plugin implementations.
+*   `lb_plugins/plugins/`: Workload plugin implementations.
 *   `lb_controller/ansible/`: Ansible playbooks and roles.

README.md

@@ -25,7 +25,7 @@
   <a href="https://github.com/miciav/linux-benchmark-lib/blob/main/LICENSE">
     <img src="https://img.shields.io/github/license/miciav/linux-benchmark-lib" alt="License" />
   </a>
-  <img src="https://img.shields.io/badge/python-3.11%2B-blue" alt="Python versions" />
+  <img src="https://img.shields.io/badge/python-3.13%2B-blue" alt="Python versions" />
 </p>
 
 ## Highlights
@@ -109,20 +109,22 @@ bash scripts/switch_mode.sh dev
 
 ```
 linux-benchmark-lib/
-|-- lb_runner/        # Runner (plugins, collectors, local execution helpers)
+|-- lb_runner/        # Runner (collectors, local execution helpers)
 |-- lb_controller/    # Orchestration and journaling
 |-- lb_app/           # Stable API for CLI/UI integrations
 |-- lb_ui/            # CLI/TUI implementation
 |-- lb_analytics/     # Reporting and analytics
+|-- lb_plugins/       # Workload plugins and registry
 |-- lb_provisioner/   # Docker/Multipass helpers
+|-- lb_common/        # Shared API helpers
 |-- tests/            # Unit and integration tests
 |-- scripts/          # Helper scripts
 `-- pyproject.toml
 ```
 
 ## Logging policy
 
-- Configure logging via `lb_common.configure_logging()` in your entrypoint.
+- Configure logging via `lb_common.api.configure_logging()` in your entrypoint.
 - `lb_ui` configures logging automatically; `lb_runner` and `lb_controller` do not.
 - Keep stdout clean for `LB_EVENT` streaming when integrating custom UIs.
 

docs/ctrl_c_design.md

@@ -2,7 +2,7 @@
 
 ## Thread and Component Model
 
-- **UI/main thread** drives the dashboard and installs a `SigintDoublePressHandler` through `lb_app.services.run_service.RunService`. It never exits on the first Ctrl+C while the controller thread is active; instead it posts notifications to a queue that the main loop drains.
+- **UI/main thread** drives the dashboard and installs a `SigintDoublePressHandler` through `lb_app.api.RunService`. It never exits on the first Ctrl+C while the controller thread is active; instead it posts notifications to a queue that the main loop drains.
 - **Controller worker thread** (`ControllerRunner`) owns orchestration and transitions a shared `ControllerStateMachine`.
 - **AnsibleRunnerExecutor** executes playbooks in subprocesses and exposes `interrupt()` + `is_running` for safe cancellation.
 - **lb_runner** emits progress/stop events; the controller consumes them for stop confirmation.

docs/ctrl_c_stop_flow.md

@@ -9,7 +9,7 @@
 
 - Ansible subprocesses now run in their own session (`start_new_session=True`). A Ctrl+C in the UI no longer auto-terminates Ansible; the controller remains in charge.
 - `AnsibleRunnerExecutor.interrupt()` is idempotent and clears active process metadata; `is_running` reports in-flight state for diagnostics.
-- `lb_app.services.run_service.RunService` installs a double Ctrl+C handler:
+- `lb_app.api.RunService` installs a double Ctrl+C handler:
   - 1st Ctrl+C: logs a warning (\"Press Ctrl+C again to stop the execution\"), no stop is issued.
   - 2nd Ctrl+C: arms a stop via the controller's `StopToken`/state machine; the UI stays alive.
   - Further Ctrl+C while stopping are ignored; termination remains controller-driven.

docs/interrupts.md

@@ -13,7 +13,7 @@ This document describes the double-Ctrl+C interruption handling for remote bench
 The interrupt handling logic is separated into three layers:
 
 1. **State Machine (`DoubleCtrlCStateMachine`)**
-   - Pure logic component in `lb_controller/interrupts.py`.
+   - Pure logic component in `lb_controller/engine/interrupts.py`.
    - Tracks states: `RUNNING` -> `STOP_ARMED` -> `STOPPING` -> `FINISHED`.
    - Decides action: `WARN_ARM`, `REQUEST_STOP`, or `DELEGATE` (allow default/force kill).
 
@@ -23,10 +23,10 @@ The interrupt handling logic is separated into three layers:
    - Executes callbacks based on decision (`on_first_sigint`, `on_confirmed_sigint`).
 
 3. **Orchestration (`RunService`, `BenchmarkController`)**
-   - `lb_app.services.run_service.RunService` installs the handler and provides UI callbacks.
-   - `StopToken` in `lb_runner.stop_token` signals intent to stop across threads/processes.
-   - `BenchmarkController` and `ControllerRunner` observe the token and coordinate teardown.
-   - `AnsibleRunnerExecutor` interrupts active playbooks when a stop is requested.
+   - `lb_app.api.RunService` installs the handler and provides UI callbacks.
+   - `StopToken` in `lb_runner.api` signals intent to stop across threads/processes.
+   - `lb_controller.api.BenchmarkController` and `lb_controller.api.ControllerRunner` observe the token and coordinate teardown.
+   - `lb_controller.api.AnsibleRunnerExecutor` interrupts active playbooks when a stop is requested.
 
 ## Behavior
 
@@ -46,7 +46,7 @@ The interrupt handling logic is separated into three layers:
 
 ## Files
 
-- `lb_controller/interrupts.py`: state machine and handler.
+- `lb_controller/engine/interrupts.py`: state machine and handler.
 - `lb_app/services/run_service.py`: wiring to UI and controller.
-- `lb_controller/controller.py`: phase-aware stop logic.
-- `lb_controller/ansible_executor.py`: playbook interruption.
+- `lb_controller/engine/controller.py`: phase-aware stop logic.
+- `lb_controller/adapters/ansible_runner.py`: playbook interruption.

docs/plugins.md

@@ -8,7 +8,7 @@ Linux Benchmark Library exposes workloads as plugins. Built-in plugins are loade
 - `hpl`
 - `stream`
 
-Third-party plugins are installed into `lb_runner/plugins/_user` (override with `LB_USER_PLUGIN_DIR`).
+Third-party plugins are installed into `lb_plugins/plugins/_user` (override with `LB_USER_PLUGIN_DIR`).
 
 ### CLI workflow
 

docs/quickstart.md

@@ -42,4 +42,4 @@ summary = controller.run(["stress_ng"], run_id="demo-run")
 print(summary.per_host_output)
 ```
 
-For runner-only integrations, use `lb_runner.api` and `lb_runner.local_runner.LocalRunner`.
+For runner-only integrations, use `lb_runner.api` and `lb_runner.api.LocalRunner`.

docs/reference/analytics.md

@@ -2,6 +2,6 @@
 
 Services for running post-processing on stored benchmark runs.
 
-::: lb_analytics.analytics_service.AnalyticsService
-::: lb_analytics.analytics_service.AnalyticsRequest
+::: lb_analytics.engine.service.AnalyticsService
+::: lb_analytics.engine.service.AnalyticsRequest