This message was deleted.
# longhorn-storagea
adamant-kite-43734
05/11/2022, 4:08 PMThis message was deleted.
s
sticky-truck-78998
05/12/2022, 6:13 AMI'm no expert but I'll share my two cents. Running it (converged)with workloads on the same nodes hasn't been a problem for us. I think the obvious here is the hardware your trying to use it with when going converged. We only see it use 1-3% on r630’s with dual 14c CPU with 10 SSDs x 3 nodes.
sticky-truck-78998
05/12/2022, 6:34 AMI just caught the hypervisor part. I'm curious for production why hypervisor with a converged approach. Maybe you should check out harvester or kubevirt if you need VMs.
w
wide-easter-7639
05/12/2022, 9:41 AMHi Garet, thanks for your reply.
wide-easter-7639
05/12/2022, 9:42 AMwhen you say converged you mean running in the same nodes longhorn, workloads and share the underlying disks via longhorn, right?
👍 1
wide-easter-7639
05/12/2022, 9:51 AMalso I have a doubt. as far as I understand, just to state it: longhorn (or any other storage manager) shares de volumes with the requester pod via network.
I have only used kubernetes over EKS and never had to worried about this.
how do you manage to isolate the workloads network bandwith from the storage network bandwith?
I mean, to avoid the IO throttle the application traffic performance
s
sticky-truck-78998
05/12/2022, 3:20 PMsticky-truck-78998
05/12/2022, 3:22 PMThat feature is hopefully coming in 1.3. We currently run everything on 10G LAGs and haven't had any issues but, this enhancement will follow best practice designs.
sticky-truck-78998
05/12/2022, 3:26 PMThanks for making me look. Now we have to accommodate the storage network in 1.3 😁 I've been wanting to play with Multis for other reasons like VLAN to Pod.
w
wide-easter-7639
05/13/2022, 5:16 PMGreat to know you're not having issues on a 10G network.
wide-easter-7639
05/13/2022, 5:18 PMThanks for your comments!
9 Views