[Sheepdog] Config for dedicated storage network and NIC bonding?
Fernando Frediani (Qube)
fernando.frediani at qubenet.net
Wed Jul 27 15:12:49 CEST 2011
My understanding is that depending how you LACP is configured (what policy) it will make use of one Physical Nic maximum per stream, so if you have one server replicating data to two others, each stream will use up to 1Gbp/s and therefore 2Gbp/s combined.
From: sheepdog-bounces at lists.wpkg.org [mailto:sheepdog-bounces at lists.wpkg.org] On Behalf Of Matthew Law
Sent: 27 July 2011 12:59
To: sheepdog at lists.wpkg.org
Subject: [Sheepdog] Config for dedicated storage network and NIC bonding?
I would like to setup sheepdog on 3 hosts. Each host has several ethernet NICs and we have a dedicated storage switch available so I would like to bond 2 NICs on each host (using 802.3ad LACP) and dedicate those to storage traffic and have the VM traffic go out over a separate network interface.
How is sheepdog configured to use a separate storage network to that which is used for accessing the VMs? Is this just in the corosync config?
Can sheepdog work with LACP and will there be any increase in throughput over a single NIC? (even if not, I would like to have some failover)
I have seen mention of Sheepdog support in OpenStack. Is this available now?
sheepdog mailing list
sheepdog at lists.wpkg.org
More information about the sheepdog