109 lines
2.6 KiB
Markdown
109 lines
2.6 KiB
Markdown
# Network Cutover Live Change Log Template
|
|
|
|
Use this during the live window.
|
|
|
|
Rule:
|
|
- every meaningful change gets a row
|
|
- if something breaks, the last row is your first suspect
|
|
- do not trust memory
|
|
|
|
---
|
|
|
|
## Session header
|
|
|
|
Date:
|
|
Operator:
|
|
Primary control box: Rocinante
|
|
Fallback admin path:
|
|
Start time:
|
|
Stop time:
|
|
|
|
In scope tonight:
|
|
- Google: yes, but narrow/reversible only
|
|
- U6 LR: only if needed
|
|
- FlyingDutchman: stay Trusted unless explicitly reclassified
|
|
- Server batch: Nomad + Serenity + PD
|
|
|
|
Out of scope / defer if ugly:
|
|
-
|
|
-
|
|
-
|
|
|
|
---
|
|
|
|
## Live log
|
|
|
|
| Time | Change ID | Area | Exact change made | Expected result | Validation performed | Result | Rollback needed? | Notes |
|
|
|---|---|---|---|---|---|---|---|---|
|
|
| | 001 | baseline | captured screenshots/exports | rollback baseline exists | exports saved | pass/fail | n | |
|
|
| | 002 | management | | | | | y/n | |
|
|
| | 003 | camera/security | | | | | y/n | |
|
|
| | 004 | server-batch | move Nomad to Servers | Nomad on correct subnet and reachable | IP + service check | pass/fail | y/n | |
|
|
| | 005 | server-batch | move Serenity to Servers | Serenity on correct subnet and reachable | IP + service check | pass/fail | y/n | |
|
|
| | 006 | server-batch | move PD to Servers | PD on correct subnet and reachable | IP + service check | pass/fail | y/n | |
|
|
| | 007 | iot | | | | | y/n | |
|
|
| | 008 | google-test | | | | | y/n | |
|
|
| | 009 | guest/ssid | | | | | y/n | |
|
|
|
|
---
|
|
|
|
## Batch validation block: Nomad + Serenity + PD
|
|
|
|
After the three-host move wave, record this before touching anything else:
|
|
|
|
- Nomad subnet/gateway correct: yes/no
|
|
- Serenity subnet/gateway correct: yes/no
|
|
- PD subnet/gateway correct: yes/no
|
|
- Rocinante can still reach PD: yes/no
|
|
- NFS/share relationships recovered: yes/no
|
|
- Critical service checks passed: yes/no
|
|
- Need immediate rollback: yes/no
|
|
|
|
If no to any critical line above:
|
|
- stop
|
|
- revert last moved host first
|
|
- unwind in reverse order
|
|
|
|
---
|
|
|
|
## Temporary exceptions added
|
|
|
|
| Time | Rule / exception | Why it was added | Narrow enough? | Remove before end? |
|
|
|---|---|---|---|---|
|
|
| | | | yes/no | yes/no |
|
|
|
|
---
|
|
|
|
## Devices intentionally deferred
|
|
|
|
| Device | Why deferred | Safe current lane | Follow-up needed |
|
|
|---|---|---|---|
|
|
| | | | |
|
|
|
|
---
|
|
|
|
## End-of-window summary
|
|
|
|
Minimum success criteria:
|
|
- Management materially cleaner: yes/no
|
|
- Camera/Security lane sane: yes/no
|
|
- Nomad/Serenity/PD batch completed or deliberately rolled back: yes/no
|
|
- Easy IoT wins done: yes/no
|
|
- Legacy CIA explicitly quarantine/sunset: yes/no
|
|
- No broad panic rules added: yes/no
|
|
|
|
What changed successfully:
|
|
-
|
|
-
|
|
-
|
|
|
|
What was reverted:
|
|
-
|
|
-
|
|
-
|
|
|
|
What remains for later:
|
|
-
|
|
-
|
|
-
|