cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Marcus <shadow...@gmail.com>
Subject Re: Add Storage Network
Date Thu, 18 Dec 2014 16:58:39 GMT
My guess is that you're right. I haven't seen anything that ties the
'physical network' to a specific NIC, thus if you register the traffic type
it should work so long as the hosts are able to route to that subnet on
*any* NIC. I'm not sure what hypervisor you're using, but for KVM at least,
you've also got to think about the bridge that SSVMs will want to attach
to. This is determined by bridge name (traffic label), and I believe if it
is set up in advance on the hosts it won't try to bridge to the primary
interface.

On Thu, Dec 18, 2014 at 8:06 AM, Logan Barfield <lbarfield@tqhosting.com>
wrote:
>
> During initial deployment we went with a simpler network design by letting
> secondary storage traffic run over the management network.  We would like
> to offload secondary storage to a separate network, and are trying to
> figure out the best method of doing so.
>
> Based on the recommendations in the documentation we would need to add a
> new Physical Network, and add the "Storage" traffic type to that network.
>
> Could we instead just add a new traffic type to the existing network, just
> set up the specified VLAN + Storage subnet on a separate NIC on the
> hypervisor?
>
> For Primary Storage the NIC used is just determined by the hypervisor's
> routing table, so wouldn't it work the same for the secondary storage
> network, or is there a reason it should be added as a separate Physical
> Network in CloudStack?
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message