[DRAFT] LNT v5 rewrite

.github/workflows/build-docker.yaml

@@ -38,19 +38,8 @@ jobs:
         # Use the current directory as context, as checked out by actions/checkout -- needed for setuptools_scm
         context: .
 
-    - name: Smoke test - start server and ping it
-      run: |
-        docker compose -f docker/compose.yaml up --build --detach
-        timeout 120 bash -c 'until curl -sf http://localhost:8000; do sleep 2; done'
-        curl -f http://localhost:8000
-      env:
-        LNT_DB_PASSWORD: smoke-test-password
-        LNT_AUTH_TOKEN: smoke-test-token
-
-    - name: Dump logs on failure
-      if: failure()
-      run: docker compose -f docker/compose.yaml logs
-
-    - name: Teardown
-      if: always()
-      run: docker compose -f docker/compose.yaml down
+    - name: Install tox
+      run: pip install tox
+
+    - name: Smoke test - v5 Docker deployment
+      run: tox -e docker

.github/workflows/tox.yaml

@@ -25,6 +25,10 @@ jobs:
       uses: actions/setup-python@83679a892e2d95755f2dac6acb0bfd1e9ac5d548 # v6.1.0
       with:
         python-version: ${{ matrix.python-version }}
+    - name: Set up Node.js
+      uses: actions/setup-node@49933ea5288caeca8642d1e84afbd3f7d6820020 # v4.4.0
+      with:
+        node-version: '22'
     - name: Install dependencies
       run: |
         python -m pip install --upgrade pip
@@ -37,3 +41,5 @@ jobs:
       run: tox -e mypy
     - name: Tox py3
       run: tox -e py3
+    - name: Tox js
+      run: tox -e js

.gitignore

@@ -10,3 +10,8 @@ lnt/server/ui/static/docs
 test_run_tmp
 tests/**/Output
 venv
+lnt/server/ui/v5/frontend/node_modules/
+lnt/server/ui/v5/static/v5/v5.js
+lnt/server/ui/v5/static/v5/v5.js.map
+lnt/server/ui/v5/static/v5/v5.css
+lnt/server/ui/v5/static/v5/favicon.ico

MANIFEST.in

@@ -4,6 +4,7 @@ recursive-include docs *
 recursive-include tests *
 recursive-include examples *
 recursive-include lnt/server/ui/static *.css *.js *.html *.ico *.txt
+recursive-include lnt/server/ui/v5/static *.css *.js *.map
 recursive-include lnt/server/ui/templates *.html
 recursive-include lnt/server/db/migrations *
 include lnt/server/ui/static/flot/Makefile

deployment/README.md

@@ -44,8 +44,8 @@ The Docker Compose service itself should now be running, and it can be inspected
 
 ```bash
 docker ps
-docker logs webserver
-docker logs dbserver # usually less interesting
+docker compose -f docker/compose.yaml logs webserver
+docker compose -f docker/compose.yaml logs db  # usually less interesting
 ```
 
 The database is stored in an independent EBS storage that gets attached and detached

deployment/compose.prod.yaml

@@ -9,7 +9,7 @@
 services:
   webserver:
     build: !reset
-    image: ghcr.io/llvm/llvm-lnt:${LNT_IMAGE:-latest}
+    image: ghcr.io/ldionne/llvm-lnt:${LNT_IMAGE:-latest}
 
 volumes:
   instance:

deployment/main.tf

@@ -4,7 +4,7 @@
 
 terraform {
   backend "s3" {
-    bucket  = "lnt.llvm.org-terraform-state-prod"
+    bucket  = "lnt.llvm.org-terraform-state-ldionne"
     key     = "terraform.tfstate"
     region  = "us-west-2"
     encrypt = true
@@ -37,7 +37,7 @@ data "aws_secretsmanager_secret_version" "lnt_secrets_latest" {
 
 locals {
   # The Docker image to use for the webserver part of the LNT service
-  lnt_image     = "56a3c8974301d2c70cc14676bf29974bb623ca6c"
+  lnt_image     = "v5"
 
   # The port on the EC2 instance used by the Docker webserver for communication
   lnt_external_port = "80"

docker/compose.yaml

@@ -21,6 +21,9 @@
 #
 # Additionally, the following aspects can be customized:
 #
+#   LNT_HOST_PORT
+#     The host port to expose the webserver on. Defaults to '8000'.
+#
 #   LNT_NGINX_CONFIG
 #     The path to the configuration file to use for Nginx. By default, './nginx.conf'
 #     is used, however this must be specified whenever running from a host where the
@@ -35,13 +38,12 @@ name: llvm-lnt
 
 services:
   webserver:
-    container_name: webserver
     build:
       context: ../
       dockerfile: docker/lnt.dockerfile
     environment:
       - DB_USER=lntuser
-      - DB_HOST=dbserver
+      - DB_HOST=db
       - DB_NAME=lnt
       - DB_PASSWORD_FILE=/run/secrets/lnt-db-password
       - AUTH_TOKEN_FILE=/run/secrets/lnt-auth-token
@@ -56,12 +58,12 @@ services:
     volumes:
       - instance:/var/lib/lnt
     ports:
-      - "8000:8000"
+      - "${LNT_HOST_PORT:-8000}:8000"
     networks:
       - lnt_network
+    platform: linux/amd64
 
   db:
-    container_name: dbserver
     image: docker.io/postgres:18-alpine
     environment:
       - POSTGRES_PASSWORD_FILE=/run/secrets/lnt-db-password

docker/docker-entrypoint.sh

@@ -6,22 +6,25 @@ password="$(cat ${DB_PASSWORD_FILE})"
 token="$(cat ${AUTH_TOKEN_FILE})"
 DB_PATH="postgres://${DB_USER}:${password}@${DB_HOST}"
 
+INSTANCE_DIR=/var/lib/lnt/instance
+
 # Set up the instance the first time this gets run.
-if [ ! -e /var/lib/lnt/instance/lnt.cfg ]; then
+if [ ! -e "${INSTANCE_DIR}/lnt.cfg" ]; then
     lnt-wait-db "${DB_PATH}/${DB_NAME}"
-    lnt create /var/lib/lnt/instance    \
-        --wsgi lnt_wsgi.py              \
-        --tmp-dir /tmp/lnt              \
-        --db-dir "${DB_PATH}"           \
-        --default-db "${DB_NAME}"       \
-        --api-auth-token "${token}"
+    lnt create "${INSTANCE_DIR}"         \
+        --wsgi lnt_wsgi.py               \
+        --tmp-dir /tmp/lnt               \
+        --db-dir "${DB_PATH}"            \
+        --default-db "${DB_NAME}"        \
+        --api-auth-token "${token}"      \
+        --db-version 5.0
 fi
 
 # Run the server under gunicorn.
-cd /var/lib/lnt/instance
+cd "${INSTANCE_DIR}"
 exec gunicorn lnt_wsgi:application                      \
     --bind 0.0.0.0:8000                                 \
-    --workers 8                                         \
+    --workers 8                                          \
     --timeout 300                                       \
     --name lnt_server                                   \
     --access-logfile -                                  \

docs/api.rst

@@ -5,6 +5,27 @@ Accessing Data outside of LNT: REST API
 
 LNT provides comprehensive REST APIs to access and manage data stored in the LNT database.
 
+v5 API (Recommended)
+--------------------
+
+The v5 API is the latest REST API for LNT. It provides interactive documentation via
+Swagger UI, available at::
+
+    http://<server>/api/v5/openapi/swagger-ui
+
+The OpenAPI 3.0 specification is also available in JSON format at::
+
+    http://<server>/api/v5/openapi/openapi.json
+
+The v5 API uses Bearer token authentication, natural keys (machine names, test names)
+instead of internal IDs, cursor-based pagination, and a standardized error format.
+Refer to the Swagger UI for the complete list of endpoints and their parameters.
+
+v4 API (Legacy)
+---------------
+
+The v4 API is documented below for reference. New integrations should use the v5 API.
+
 Quick Reference
 ---------------
 

docs/design/README.md

@@ -0,0 +1,81 @@
+# v5 Design Documentation
+
+This directory contains the design documentation for the LNT v5 project. It is
+the authoritative reference for what v5 does and why.
+
+## What is v5?
+
+LNT v5 is a ground-up redesign of the database, REST API, and web UI layers.
+Key changes from v4:
+
+- **Database**: PostgreSQL-only, schema-in-DB, the "Commit" concept replaces
+  "Order" (cleanly separating identity, ordering, and display), no FieldChange
+  table (regressions use direct indicators).
+- **API**: flask-smorest with OpenAPI 3.x, cursor-based pagination, bearer
+  token auth with scope hierarchy, all JSON responses.
+- **UI**: Single-page application in vanilla TypeScript + Vite, client-side
+  routing, all data from the v5 REST API.
+
+v4 and v5 coexist in the same codebase, selected by `db_version` in `lnt.cfg`
+(`'0.4'` for v4, `'5.0'` for v5). They are fully disjoint: a v4 instance
+serves only v4 views, and a v5 instance serves only v5 API endpoints and the
+v5 frontend.
+
+## Design Principles
+
+- **PostgreSQL only**. No SQLite or MySQL support.
+- **SQLAlchemy 1.3** (same version as v4, to avoid upgrade risk).
+- **Python 3.10+** idioms: type hints (`X | Y`, `list[T]`), dataclasses,
+  f-strings, `match` where appropriate.
+- **No backward compatibility** with v4 formats or APIs. Clean break.
+- **No auto-detection** of regressions. External tools create regressions via
+  the API.
+
+## Document Map
+
+### Database Layer — [`db/`](db/)
+
+| Document | Contents |
+|----------|----------|
+| [Data Model](db/data-model.md) | Architecture, Commit concept, schema storage and format, all table definitions |
+| [Operations](db/operations.md) | Run submission, commit metadata, search, time-series queries, ordinal management, v4 migration, deferred features |
+
+### REST API — [`api/`](api/)
+
+| Document | Contents |
+|----------|----------|
+| [Infrastructure](api/infrastructure.md) | Framework (flask-smorest), URL structure, pagination, filtering, response format, authentication, testing, deferred features, AI orientation |
+| [Endpoints](api/endpoints.md) | All entity endpoint specifications: machines, commits, runs, tests, samples, profiles, regressions, time series, schema, admin |
+
+### Web UI — [`ui/`](ui/)
+
+| Document | Contents |
+|----------|----------|
+| [Architecture](ui/architecture.md) | SPA design, client-side routing, Flask backend routes, navigation bar, frontend code structure, build config, implementation phases |
+| [Dashboard](ui/dashboard.md) | Landing page with sparkline trend overview across test suites |
+| [Browsing Pages](ui/browsing.md) | Test Suites page (suite picker + tabs), Machine Detail, Run Detail, Commit Detail, Regression Detail, and inline regression list/triage |
+| [Graph](ui/graph.md) | Time-series visualization: multi-machine, lazy loading, test selection, baselines, regression annotations |
+| [Compare](ui/compare.md) | Side-by-side comparison of two commits/runs: selection panel, ratio chart, geomean summary, bidirectional sync |
+| [Admin](ui/admin.md) | API key management, test suite schema management |
+
+### Historical Discussion
+
+| Document | Contents |
+|----------|----------|
+| [Discussion: Orders](v5-discussion-about-orders.md) | Exploration of approaches that led to the Commit concept (design rationale) |
+
+
+## v4 Features NOT Carried Forward
+
+These v4 pages are intentionally omitted from the v5 UI:
+
+| v4 Feature | Rationale |
+|------------|-----------|
+| Daily Report | Subsumed by Dashboard + Graph. The dashboard shows sparkline trends; the graph page shows detailed time-series. |
+| Latest Runs Report | Subsumed by Dashboard (sparkline trend overview) and Test Suites page (Recent Activity tab). |
+| Summary Report | Low usage, "WIP" in v4. Can be added later if needed. |
+| Matrix View | Niche use case. The Graph page with per-test drill-down covers the same need. |
+| Global Status | Subsumed by Dashboard (sparkline trend overview with per-machine traces). |
+| Profile Admin | Operational concern, not a core user workflow. Keep in v4. |
+| Submit Run page | Runs are submitted via CLI (`lnt submit`) or API. A form-based UI is rarely used. |
+| Rules page | Read-only diagnostic page. Keep in v4 for ops. |