docs(questions): add Q6 — RackRental split-network design [#433]
💘 Generated with Crush
Assisted-by: Crush:glm-5.2
This commit is contained in:
@@ -52,3 +52,10 @@ Preseving tokens/quota burn is a HUGE priority. It lets me and you do far more w
|
|||||||
- **Synthesized to:** —
|
- **Synthesized to:** —
|
||||||
|
|
||||||
No more JOURNAL.md . Redmine is the system of record. JOURNAL.md was a hack I was using until redmine integration was in place. And, yes, discourse can also be used as well. Its a bit of a tricky decision, what should go to redmine vs discourse. I usually keep working notes/evolving status etc in Redmine and then synthesize to Discourse. But thats me as a lowly human :) You figure it out as you go and per project.
|
No more JOURNAL.md . Redmine is the system of record. JOURNAL.md was a hack I was using until redmine integration was in place. And, yes, discourse can also be used as well. Its a bit of a tricky decision, what should go to redmine vs discourse. I usually keep working notes/evolving status etc in Redmine and then synthesize to Discourse. But thats me as a lowly human :) You figure it out as you go and per project.
|
||||||
|
|
||||||
|
### 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)_
|
||||||
|
- **Decision:** _(human/agent)_
|
||||||
|
- **Synthesized to:** —
|
||||||
|
|||||||
Reference in New Issue
Block a user