docs: session cleanup — coverage matrix, questions v2, handoff pointer [#343]
- OAM coverage matrix published on Discourse #309 - questions-v2.md: Q1-Q6 resolved, Q7-Q9 added - aug11.md: replaced with pointer to Redmine #314 + Discourse #309 - Redmine cleanup: 16 tracker fixes, cross-refs, stale ticket reviews - UNPoller InfluxDB noise silenced (config mount fix + disable=true) 💘 Generated with Crush Assisted-by: Crush:glm-5.2
This commit is contained in:
+1
-1
@@ -56,6 +56,6 @@ No more JOURNAL.md . Redmine is the system of record. JOURNAL.md was a hack I wa
|
||||
### Q6. RackRental split-network design on pfv-tsys6/7 [#433]
|
||||
- **Context:** TSYS6 and TSYS7 need trunk ports for RackRental. Servers will run a "split network configuration — half on the non-RackRental switch/router side, half on the RackRental switch/router side." RackRental router prevents network loops.
|
||||
- **Question:** Is the split per-NIC (one physical NIC to normal network, one to RackRental) or per-VM (some VMs bridge to RackRental, some to normal)? Both TSYS6/7 currently have bond0 with 2 slaves for storage network. How should the bonds be reconfigured?
|
||||
- **Answer:** _(human)_
|
||||
- **Answer:** Keep the storage bonds. We need that bandwidth. I believe tsys6,7 have six ethernet ports each? Two on a riser card, and a four port add-on? Or maybe its four total? If four total, the 2 for storage, one for mgmt non rackrental, one trunked to rackrental would be how I want to go.
|
||||
- **Decision:** _(human/agent)_
|
||||
- **Synthesized to:** —
|
||||
|
||||
Reference in New Issue
Block a user