Skip to content

Keep SparkGLM independent; make LLooM integration optional - #2

Merged
data-angel merged 1 commit into
mainfrom
fix/standalone-default
Sep 8, 2026
Merged

data-angel merged 1 commit into
mainfrom
fix/standalone-default

Conversation

@data-angel

Copy link
Copy Markdown
Contributor

Keep SparkGLM standalone and make LLooM integration opt-in

SparkGLM's default installer should run independently. Use Docker and SSH for source builds, pinned model downloads, worker-first startup and owned-container lifecycle. Keep the existing LLooM-managed flow behind --lloom; it requires an existing LLooM installation and never installs the gateway. Both paths retain the measured NVFP4 settings, with latest EXL3 explicitly selectable.

Provenance:

  • Copy the measured standalone-capable entrypoint byte-for-byte from https://github.com/Enntity/lloom at 2cc2f0df9ddcb1bb7fe60f7bd6934d2a9de1e4f2, preserving its MIT AND Apache-2.0 notice and the repository license ledger. This script invokes vLLM directly and contains no LLooM runtime dependency.

Original work:

  • Standalone Docker/SSH orchestration, private-fabric binding, owned-container checks, source/default dispatch, optional integration documentation and command-parity tests. No numerical engine changes or new performance claims.

Verification:

  • scripts/check.sh all passed, including measured per-rank argument parity, rejection of foreign container ownership, standalone default and optional LLooM dispatch. All 66 checksum-bound result bundles remain valid. GPU runtime was not restarted; the existing LLooM-managed appliance remains in service.

SparkGLM's default installer should run independently. Use Docker and SSH for source builds, pinned model downloads, worker-first startup and owned-container lifecycle. Keep the existing LLooM-managed flow behind --lloom; it requires an existing LLooM installation and never installs the gateway. Both paths retain the measured NVFP4 settings, with latest EXL3 explicitly selectable.

Provenance:
- Copy the measured standalone-capable entrypoint byte-for-byte from https://github.com/Enntity/lloom at 2cc2f0df9ddcb1bb7fe60f7bd6934d2a9de1e4f2, preserving its MIT AND Apache-2.0 notice and the repository license ledger. This script invokes vLLM directly and contains no LLooM runtime dependency.

Original work:
- Standalone Docker/SSH orchestration, private-fabric binding, owned-container checks, source/default dispatch, optional integration documentation and command-parity tests. No numerical engine changes or new performance claims.

Verification:
- scripts/check.sh all passed, including measured per-rank argument parity, rejection of foreign container ownership, standalone default and optional LLooM dispatch. All 66 checksum-bound result bundles remain valid. GPU runtime was not restarted; the existing LLooM-managed appliance remains in service.
@data-angel
data-angel merged commit c725f54 into main Sep 8, 2026
1 check passed
@data-angel
data-angel deleted the fix/standalone-default branch September 12, 2026 03:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant