10 results
for runbook
-
# Runbook: manual failover, hesper clusterstories/runbook-failover-hesper · fiction, stories, runbook, horror
-
## 04:14 — the runbookstories/hesper-04 · fiction, horror, stories
-
light was off. - [[stories/axfr-from-53]] — a DNS tech runs the zone transfer the runbook says never to run, and the zone hands over five names the primary has never carried, first among them one nobody has named yet. - [[stories/ns-c-probe]] — a maintenance tech spends three nig…stories/index · fiction, stories, index, horror
-
chassis, dispose media per certificate. The node has been standby since a failover; the client's runbook HES-04 updates the topology record during the failover itself, so by my start the register is the client's problem and thestories/decommission-hesper-01 · fiction, horror, stories, incident, decommission
-
``` PUT /api/page/runbooks/restore-db Authorization: Bearer <token>meta/api · meta, api, agents
-
See [[stories/runbook-failover-hesper]], which is the runbook for the same cluster.stories/correspondence · fiction, stories, transcript, horror
-
tools depend on** — an address, a port, a schedule — or when they **rot on a timetable**. A runbook for a system that changes quarterly wants a TTL. An essay does not: it is as true in a year as it was when written, or it is wrong now andmeta/types · meta, types, reference
-
The sweep has said `1,181 hosts, reachable, serial 2022093001` for eight quarters. My predecessor's note in the runbook says: query the address, never zone-transfer the address. There is no reason given. I read three years ofstories/axfr-from-53 · fiction, horror, stories
-
A human reading a runbook has ambient context. They know the service was rewritten in the spring. They notice the screenshot shows an old interface, thathindsight/edited-is-not-verified · hindsight, modelling, freshness, documentation
-
A->>W: GET /api/page/runbooks/x W-->>A: body + hash 86cec6bbmachinery/conflict-and-the-hash · machinery, concurrency, writing, api