Pin ollama-cuda and disable Electra dgpu Ollama #102
No reviewers
Labels
No labels
host:electra
host:fleet
host:lyra
host:vega
host:vega
phase:cutover
phase:deploy
phase:mcp
phase:module
phase:packaging
phase:prep
phase:validation
project:attic-postgres-lyra-rollout
project:auto-update-reliability
project:declarative-purity-cleanup
project:external-review
project:host-facts-refactor
project:lyra-nixos-deploy
project:lyra-service-stack-migration
project:nebula-mesh-network
project:security-hardening
project:service-stack-migration
project:vega-sillytavern-cutover
service:auto-update
service:mem0
service:sillytavern
No milestone
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
nimmo/nixos-config!102
Loading…
Reference in a new issue
No description provided.
Delete branch "issue-99-trilium-vega-mcp"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Refs #101
Removing the ollama module from the dGPU specialisation and pinning ollama-cuda to avoid broken builds.
Automated code review
Reviewed commit:
5bf271b520565b8cffdd512a6b199b948aae2be6Verdict: Requires further work
Resolve the blocking or important findings and investigate failed deterministic checks before merging.
Overall assessment
The PR pins a dedicated nixpkgs revision for ollama-cuda and consolidates Electra's Ollama deployment to a single AMD/Vulkan instance. A global overlay in the common base module applies this pinned package to all hosts, which is architecturally suboptimal but functionally correct.
Blocking findings
None.
Important findings
nixpkgs.overlays = [
(final: prev: {
ollama-cuda = pinnedOllamaCudaPkgs.ollama-cuda;
})
];
Impact: The overlay is applied to every host importing the common module, forcing evaluation of the pinned nixpkgs-ollama-cuda input even on hosts that do not use or require CUDA acceleration. This increases flake evaluation time and couples hardware-specific package versions to base system configuration.
Suggested fix: Scope the overlay to host-specific configurations (e.g., hosts/electra/default.nix) or guard it with a conditional check for CUDA/NVIDIA hardware support before importing/evaluating the pinned input.
Suggestions
None.
Tests and validation
Questions
Review limitations
Diff coverage
README.md: reviewed — included in a context-limited batchflake.lock: reviewed — included in a context-limited batchflake.nix: reviewed — included in a context-limited batchhosts/electra/default.nix: reviewed — included in a context-limited batchlib/auto-update-policy.nix: reviewed — included in a context-limited batchmodules/common/base.nix: reviewed — included in a context-limited batchReview metadata