server-ops
Skill337 starsChanged 18 days agoApache-2.0View on GitHub
Configure or diagnose OrbitKV Cache Managers, local process transport, DRAM/SSD budgets, etcd membership, inventory-fed global indexes and peer transfers. Use for deployment and runtime incidents.
We split this skill into the rules it gives an agent
10 rules. About 0 are common, 4 are distinctive, and 6 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
6
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 13
Start with docs/deployment.md for topology and docs/p2p.md for distributed startup.
- Very specific: line 34
Check process health and the engine's UDS/iceoryx2 registration before diagnosing a cache miss as a transport failure.
- Very specific: line 36
Check /cache/metadata: membership validity/revision, explicit coverage, scope digest/kind/count, active/staging index bytes, installed …
- Very specific: line 43
Check source grants and generation checks in crates/orbitkv-core/src/peer/, then TENT READ/completion.
- Distinctive: line 48
Use native TENT for payloads and OrbitKV source-control RPCs.
- Distinctive: line 50
Use test-owned processes for faults.
- Very specific: line 66
Keep CPU host-registration/C ABI test-shim controls separate from real CUDA registration and installed hardware gates.
- Distinctive: line 71
Do not accept a test helper's SIGKILL fallback as graceful shutdown evidence.
- Distinctive: line 72
Verify the member key is absent before reusing a node ID, and require a larger epoch plus a different incarnation after restart.
- Very specific: line 137
Treat publish_manager_response_publish as the before-publication boundary.
≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
OrbitKV Manager operations
Resolve paths from the Git root and read AGENTS.md. Use the built
orbitkv-cache-manager --help and docs/server.md for current flags; do not copy
an old flag list. The source binary is orbitkv-cache-manager; the wheel exposes
the same console command and bundles orbitkv-cache-manager-py.
Start with docs/deployment.md for topology and docs/p2p.md for distributed
startup. Every node has an independent Manager. Distributed mode needs a concrete
peer address, etcd endpoints, a unique stable node ID and the same cluster name.
orbitkv-catalog is an embedded local index, not a separate service.
Client and Manager CUDA ordinals may differ. Registration joins the tensor's full
GPU UUID to the Manager-visible device and retains that route for Publish/Restore;
use matching lifecycle-protocol-8 artifacts. NUMA selection uses those visible
UUIDs. Known payload placement uses mbind before first touch and requires the
selected memory node in the process's allowed nodes. CPU affinity alone cannot
override an inherited interleave memory policy; inspect actual resident pages.
For remote metadata scope, omission means AllNamespaces. Repeat
--metadata-namespace only with complete storage namespaces logged by actual
registration, or use --metadata-empty-scope for an explicit empty set. Scope is
startup configuration: change it by restarting and fully bootstrapping the
Manager. Never infer it from model display names, prefixes or query misses. The
allowlist reduces record bytes, not peer-session fanout, and is not tenant auth.
Trace an incident through its owner:
- Check process health and the engine's UDS/iceoryx2 registration before diagnosing
a cache miss as a transport failure. See
crates/orbitkv-server/src/endpoint/. - Check
/cache/metadata: membership validity/revision, explicit coverage, scope digest/kind/count, active/staging index bytes, installed views and stream queues. Distinguish a complete empty owner view from a missing view. A scope-outside remote lookup is unavailable even when local cache service works./cache/syncreturns a source inventory fence; a controlled requester must install it with the same scope via/cache/metadata/await. A received frame or source head is not that watermark. - Check source grants and generation checks in
crates/orbitkv-core/src/peer/, then TENT READ/completion. Index freshness does not authorize an address. - Inspect query, source export, SSD staging and GPU admission budgets using
docs/metrics.md. Lease expiry or a deadline cannot establish native drain.
Use native TENT for payloads and OrbitKV source-control RPCs. Do not revive Catalog placement/lookup RPCs or change etcd's transport to fix a payload problem. Use test-owned processes for faults; preserve other workloads and collect logs outside the repo. Keep same-host TCP, physical two-host TCP and RDMA evidence separate. Build first, then test with native binaries/libraries frozen.
The source-shutdown candidate calls the irreversible native source gate before
unregistering the pinned-pool owner. Only CPU-only/TCP-only handler drain plus
empty Rust requester admission permits release. Unsupported paths or errors
retain engine, tokens and pool in the bounded source registry; do not retry
unregister from token Drop or reset its process admission. Native Delegate is
rejected in this narrow profile because its pointer wire has no source epoch.
This is whole-engine shutdown, not a per-ticket orphan, GPU or RDMA receipt.
Pin/Unpin and queued global-executor handlers require the same ownership:
dispatch is counted before offload and drained before service deletion. Source
close shares its deadline with that drain; server I/O shutdown alone is not
proof that a global-executor callback ended. Readiness is published after all
native worker initialization.
Keep CPU host-registration/C ABI test-shim controls separate from real CUDA
registration and installed hardware gates; see S3 and docs/transport.md.
For a normal Manager stop, require SIGTERM to fence membership before gRPC waits for inventory streams, then drain lifecycle ownership and revoke the member lease. Do not accept a test helper's SIGKILL fallback as graceful shutdown evidence. Verify the member key is absent before reusing a node ID, and require a larger epoch plus a different incarnation after restart. Current/peak inventory session counters are abort-safe diagnostics: a replaced follower must return current sessions to the real live count even when its task is aborted.
For repeated-key metadata traffic, --inventory-stream-coalesce-ms selects a
0–5 ms quiet window; the default is 0. A requested fence interrupts intentional
wait but still requires complete input-interval installation. Compare inventory
input/output counters and stream encoded bytes with measured observer visibility
and effective hits. Etcd network counters now cover membership/configuration,
not block propagation. A lower mutation count alone does not establish serving
improvement.
For S2.10 performance qualification, keep s2.10-performance-v2 endpoint names
separate. Serial or concurrent /cache/metadata/await duration measures barrier
verification, not ordinary visibility. Ordinary visibility uses the source
inventory_last_change_mono_ns and matching owner installed_mono_ns without a
sync/flush in the measured path; compare them only on one host after matching the
node epoch, incarnation, scope digest and sequence. Report HTTP observation delay
separately. All/scoped establishes filtering benefit, while save/query isolation
uses the same scope and matched quiet versus metadata-only pressure controls.
Reject pressure runs whose foreground always lands in a quiet phase. Source
cadence, actual publication/operation clocks, advancing observer windows and
sampler overhead must be recorded symmetrically. Short capacity runs and runs
that skip real restore cannot qualify the 16-owner threshold. Formal metadata-only
pressure uses a release-built server-test fixture with the same frozen record
cadence and budgets; preserve dev-profile observations separately. Controllers
must reject optimized Python, validate cadence after each cell, and bound helper
and measurement waits against the fresh global deadline. A watchdog leaves an
active native process isolated; it does not establish drain.
For scoped-stream qualification, pair all-domain and scoped runs with the same exact namespace/key/payload mutations and coalescing. Report input/output filter records and CPU, encoded bytes/frames, scope-bound coverage, active/staging/index bytes, RSS, queue peaks, visibility, bootstrap/repair, and lookup/update lock wait/hold time. Empty filtered intervals must advance only source-proven coverage.
For inference interference, measure the physical NIC/direction, PCIe/NUMA and engine collective traffic as well as TENT transfers. Manager query-byte budgets are not a node-wide network scheduler; engine-local P/D WRITE is a separate submitter. Receiver credit/pacing is planned in S6, not an existing runtime flag. Source authority, network credits and destination lifetime need separate drain evidence. Report that distinction when diagnosing congestion or retained memory.
Pressure qualification must pace after the prior completed source iteration as well as the original schedule. A delayed tick cannot emit compressed catch-up bursts. Keep the frozen minimum interval and mutation count; never fix this by lowering a threshold or dropping events. A terminal exposure failure remains an invalid run, but should still execute explicit local drain, unregister and normal Manager shutdown before raising and preserve that cleanup evidence.
For S2.10a stage diagnosis, enable ORBITKV_TRACE_TRANSFERS=1 and a positive
ORBITKV_DIAGNOSTIC_TIMELINE_LIMIT symmetrically in quiet and pressure runs.
The latter is capped at 65,536 events and zero means off. Correlate client,
Manager, insert and SSD stages only by session epoch/token plus channel request
ID on one host monotonic clock. A limit event or missing required stage invalidates
the run. Save return means GPU copy/encode completed and insertion was queued;
insert and SSD completion are later diagnostic stages. Use per-thread schedstat
when perf is unavailable, and report that precision limit instead of inferring
scheduler causality. Diagnostic results never replace the frozen isolation cohort.
With a positive limit, all transfer/stage records share the bounded asynchronous
writer; required stage/query-path entries are fixed-size until that writer
formats them. Require normal Manager shutdown to flush it before accepting linkage.
An instrumentation pilot that fails its frozen overhead guard blocks a diagnostic
matrix even when correlation, correctness and cleanup otherwise pass.
Treat publish_manager_response_publish as the before-publication boundary; its
client interval includes publication plus notification. Writer-start failure or
missing post-drain flush invalidates linkage rather than permitting fallback logs.
Shutdown must stop channel admission, await all admitted Publish continuations,
then flush insert/SSD owners before flushing diagnostic output.
Manager worker raw-copy shapes share that bounded timeline. After independently
checking normal shutdown and owned-resource cleanup, use benches.raw_copy_shapes
to require complete flush/count/shape coverage. Bind raw batches to the actual
Manager receipt and require one completion process for a one-Manager gate.
Engine-local asynchronous H2D is outside this trace. CPU submission and host
stream waiting include instrumentation and scheduling; a structural model pass
does not replace matched overhead, device-event or application performance gates.
Other versions3 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 3
- novitalabs/pegaflow★ 214same name
- CheshireMew/server-ops★ 3same name
- wlkerwong-boop/china-web-deployment★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository4 other files it gives its agents.
- AGENTS.mdAGENTS.md
- engine-integrationSkill
- python-bindingSkill
- version-bumpSkill
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

