vh/esh-pfi-infrastructure
1
0
Fork 0
Code Issues 7 Pull Requests Actions Packages Projects Releases Wiki Activity

fv-ml1: the playbook + homepage body edits the rename commit missed

Browse Source 
A zsh glob failure in the staging step of 91bda3c meant the five renamed
playbooks went in as pure renames with their bodies still saying ana-ml2 and
10.250.50.54, and the homepage docker.yaml direct-connection edit from 17586ab
did not stage either. Same content, just the half that got dropped.
This commit is contained in:
vh
2026-09-12 22:04:20 -07:00
parent 17586abb19
commit 87d7555fcf
6 changed files with 19 additions and 22 deletions
Download Patch File Download Diff File Expand all files Collapse all files
playbooks/fv-ml1-overcommit-memory.yaml
+3 -3
View File
@@ -1,6 +1,6 @@
# Make vm.overcommit_memory=1 durable on ana-ml2 (GPU inference host).
# Make vm.overcommit_memory=1 durable on fv-ml1 (GPU inference host).
#
# Why: ana-ml2 runs vm.overcommit_memory=0 (heuristic) with zero swap, so the
# Why: fv-ml1 runs vm.overcommit_memory=0 (heuristic) with zero swap, so the
# CommitLimit is ~RAM/2 (~283 GB of 566 GB). The resident vLLM services already
# commit ~224 GB of address space, leaving < 60 GB of headroom. A large model-file
# mmap (e.g. the 50 GB NVFP4 shard during HF->native conversion, or a vLLM model
@@ -12,7 +12,7 @@
# accounting is the only thing in the way. Operator-directed permanent + durable
# (2026-06-17). A drop-in under /etc/sysctl.d/ applies at every boot.
#
# Run: scripts/elway infra-ops@ana-ml2 --playbook playbooks/ana-ml2-overcommit-memory.yaml
# Run: scripts/elway infra-ops@fv-ml1 --playbook playbooks/fv-ml1-overcommit-memory.yaml
# Rerunnable: a second run shows the write step `skipped` (idempotent via when:).
vars: