3:17 p.m.
Hello,
In VMware it is possible to bond two network interfaces and for each
Portgroup (equivalent to a VLAN) is possible to tell which of the
physical interfaces underneath it you wish the traffic to flow primarily
and which stays as secondary(bond mode=1 equivalent). So for certain
VLANs (Management, Live Migration, etc) is possible to force traffic
flow via one physical NIC of the bond and for other VLANs (Virtual
Machine's traffic) outs via the other NIC with failover to each other
should a cable or switch fails.
This is specially good for better utilize the fewer NICs available and
still have redundancy.
In oVirt it is also possible to have bonds, but would it still be
possible to do that same and favor the traffic per VLAN basis ? I guess
it is something related to Linux Bond module but perhaps someone has
done this already.
Thanks
Fernando
8:37 a.m.
Dan, Edy,
Could you guys answer this?
IIUC, the requirements are:
- stream the traffic of few VLANs(network roles) through a single bond
- be able to bind a VLAN to a bond slave with an option of fallback
- have redundancy
- assign different QoS to every VLAN (my addition)
I guess this is a new RFC that we do not support currently, but would we be
able to provide in any future?
---------- Forwarded message ----------
From: Fernando Frediani <fernando.frediani(a)upx.com.br>
Date: Sat, Jun 25, 2016 at 11:17 PM
Subject: [ovirt-users] Network redundancy with Manual balancing per VLAN
To: users(a)ovirt.org
Hello,
In VMware it is possible to bond two network interfaces and for each
Portgroup (equivalent to a VLAN) is possible to tell which of the physical
interfaces underneath it you wish the traffic to flow primarily and which
stays as secondary(bond mode=1 equivalent). So for certain VLANs
(Management, Live Migration, etc) is possible to force traffic flow via one
physical NIC of the bond and for other VLANs (Virtual Machine's traffic)
outs via the other NIC with failover to each other should a cable or switch
fails.
This is specially good for better utilize the fewer NICs available and
still have redundancy.
In oVirt it is also possible to have bonds, but would it still be possible
to do that same and favor the traffic per VLAN basis ? I guess it is
something related to Linux Bond module but perhaps someone has done this
already.
Thanks
Fernando
_______________________________________________
Users mailing list
Users(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
1 a.m.
On Sun, Jun 26, 2016 at 4:37 PM, Yevgeny Zaspitsky <yzaspits(a)redhat.com>
wrote:
Dan, Edy,
Could you guys answer this?
IIUC, the requirements are:
- stream the traffic of few VLANs(network roles) through a single bond
- be able to bind a VLAN to a bond slave with an option of fallback
- have redundancy
- assign different QoS to every VLAN (my addition)
I guess this is a new RFC that we do not support currently, but would we
be able to provide in any future?
---------- Forwarded message ----------
From: Fernando Frediani <fernando.frediani(a)upx.com.br>
Date: Sat, Jun 25, 2016 at 11:17 PM
Subject: [ovirt-users] Network redundancy with Manual balancing per VLAN
To: users(a)ovirt.org
Hello,
In VMware it is possible to bond two network interfaces and for each
Portgroup (equivalent to a VLAN) is possible to tell which of the physical
interfaces underneath it you wish the traffic to flow primarily and which
stays as secondary(bond mode=1 equivalent). So for certain VLANs
(Management, Live Migration, etc) is possible to force traffic flow via one
physical NIC of the bond and for other VLANs (Virtual Machine's traffic)
outs via the other NIC with failover to each other should a cable or switch
fails.
This is specially good for better utilize the fewer NICs available and
still have redundancy.
In oVirt it is also possible to have bonds, but would it still be possible
to do that same and favor the traffic per VLAN basis ? I guess it is
something related to Linux Bond module but perhaps someone has done this
already.
Thanks
Fernando
_______________________________________________
Users mailing list
Users(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
Hello Fernando,
As you mentioned, oVirt is using the Linux Bond and the solution you are
looking for is not supported.
The oVirt way to handle this is by applying QoS on the networks, providing
the guaranteed rates for each and utilizing the bond for throughput beyond
the one link limit.
With the introduction of OVS as an alternative networking infrastructure
for the hosts, you could create a hook that implements some special
functionality, but ovs is not in yet.
Thanks,
Edy.
7:31 a.m.
This is a multi-part message in MIME format.
--------------060804090703060803060201
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Thanks for the reply.
Perhaps is the case of contacting the maintainer of Linux Bond module
and see if there is room for this feature to be implement anytime. OVS
is great in the coming future, but Bond module is still something very
handy that simplify the things a lot.
Thanks
Fernando
Em 27/06/2016 03:00, Edward Haas escreveu:
On Sun, Jun 26, 2016 at 4:37 PM, Yevgeny Zaspitsky
<yzaspits(a)redhat.com <mailto:yzaspits@redhat.com>> wrote:
Dan, Edy,
Could you guys answer this?
IIUC, the requirements are:
* stream the traffic of few VLANs(network roles) through a
single bond
* be able to bind a VLAN to a bond slave with an option of fallback
* have redundancy
* assign different QoS to every VLAN (my addition)
I guess this is a new RFC that we do not support currently, but
would we be able to provide in any future?
---------- Forwarded message ----------
From: *Fernando Frediani* <fernando.frediani(a)upx.com.br
<mailto:fernando.frediani@upx.com.br>>
Date: Sat, Jun 25, 2016 at 11:17 PM
Subject: [ovirt-users] Network redundancy with Manual balancing
per VLAN
To: users(a)ovirt.org <mailto:users@ovirt.org>
Hello,
In VMware it is possible to bond two network interfaces and for
each Portgroup (equivalent to a VLAN) is possible to tell which of
the physical interfaces underneath it you wish the traffic to flow
primarily and which stays as secondary(bond mode=1 equivalent). So
for certain VLANs (Management, Live Migration, etc) is possible to
force traffic flow via one physical NIC of the bond and for other
VLANs (Virtual Machine's traffic) outs via the other NIC with
failover to each other should a cable or switch fails.
This is specially good for better utilize the fewer NICs available
and still have redundancy.
In oVirt it is also possible to have bonds, but would it still be
possible to do that same and favor the traffic per VLAN basis ? I
guess it is something related to Linux Bond module but perhaps
someone has done this already.
Thanks
Fernando
_______________________________________________
Users mailing list
Users(a)ovirt.org <mailto:Users@ovirt.org>
http://lists.ovirt.org/mailman/listinfo/users
Hello Fernando,
As you mentioned, oVirt is using the Linux Bond and the solution you
are looking for is not supported.
The oVirt way to handle this is by applying QoS on the networks,
providing the guaranteed rates for each and utilizing the bond for
throughput beyond the one link limit.
With the introduction of OVS as an alternative networking
infrastructure for the hosts, you could create a hook that implements
some special functionality, but ovs is not in yet.
Thanks,
Edy.
--------------060804090703060803060201
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 8bit
<html>
<head>
<meta content="text/html; charset=utf-8"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
Thanks for the reply.<br>
<br>
Perhaps is the case of contacting the maintainer of Linux Bond
module and see if there is room for this feature to be implement
anytime. OVS is great in the coming future, but Bond module is still
something very handy that simplify the things a lot.<br>
<br>
Thanks<br>
Fernando<br>
<br>
<div class="moz-cite-prefix">Em 27/06/2016 03:00, Edward Haas
escreveu:<br>
</div>
<blockquote
cite="mid:CALmkdFTCJdpeEKGe0qE4O9x+yik24UOraMJRfEDLos9bByacmA@mail.gmail.com"
type="cite">
<div dir="ltr"><br>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Sun, Jun 26, 2016 at 4:37 PM,
Yevgeny Zaspitsky <span dir="ltr"><<a
moz-do-not-send="true"
href="mailto:yzaspits@redhat.com"
target="_blank"><a
class="moz-txt-link-abbreviated"
href="mailto:yzaspits@redhat.com">yzaspits@redhat.com</a></a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left:1px solid
rgb(204,204,204);padding-left:1ex">
<div dir="ltr">
<div>Dan, Edy,<br>
<br>
Could you guys answer this?<br>
<br>
</div>
IIUC, the requirements are:<br>
<ul>
<li>stream the traffic of few VLANs(network roles)
through a single bond</li>
<li>be able to bind a VLAN to a bond slave with an
option of fallback<br>
</li>
<li>have redundancy</li>
<li>assign different QoS to every VLAN (my addition)<br>
</li>
</ul>
<div>
<div>I guess this is a new RFC that we do not support
currently, but would we be able to provide in any
future?<br>
</div>
<div>
<div>
<div><br>
<div class="gmail_quote">---------- Forwarded
message ----------<br>
From: <b class="gmail_sendername">Fernando
Frediani</b> <span
dir="ltr"><<a
moz-do-not-send="true"
href="mailto:fernando.frediani@upx.com.br"
target="_blank"><a
class="moz-txt-link-abbreviated"
href="mailto:fernando.frediani@upx.com.br">fernando.frediani@upx.com.br</a></a>></span><br>
Date: Sat, Jun 25, 2016 at 11:17 PM<br>
Subject: [ovirt-users] Network redundancy with
Manual balancing per VLAN<br>
To: <a moz-do-not-send="true"
href="mailto:users@ovirt.org"
target="_blank">users(a)ovirt.org</a><br>
<br>
<br>
Hello,<br>
<br>
In VMware it is possible to bond two network
interfaces and for each Portgroup (equivalent
to a VLAN) is possible to tell which of the
physical interfaces underneath it you wish the
traffic to flow primarily and which stays as
secondary(bond mode=1 equivalent). So for
certain VLANs (Management, Live Migration,
etc) is possible to force traffic flow via one
physical NIC of the bond and for other VLANs
(Virtual Machine's traffic) outs via the other
NIC with failover to each other should a cable
or switch fails.<br>
<br>
This is specially good for better utilize the
fewer NICs available and still have
redundancy.<br>
<br>
In oVirt it is also possible to have bonds,
but would it still be possible to do that same
and favor the traffic per VLAN basis ? I guess
it is something related to Linux Bond module
but perhaps someone has done this already.<br>
<br>
</div>
</div>
</div>
</div>
</div>
</div>
</blockquote>
<div><br>
</div>
<div> </div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left:1px solid
rgb(204,204,204);padding-left:1ex">
<div dir="ltr">
<div>
<div>
<div>
<div>
<div class="gmail_quote">
Thanks<br>
<br>
Fernando<br>
<br>
_______________________________________________<br>
Users mailing list<br>
<a moz-do-not-send="true"
href="mailto:Users@ovirt.org"
target="_blank">Users(a)ovirt.org</a><br>
<a moz-do-not-send="true"
href="http://lists.ovirt.org/mailman/listinfo/users"
rel="noreferrer"
target="_blank">http://lists.ovirt.org/mailman/listinfo/user...
</div>
<br>
</div>
</div>
</div>
</div>
</div>
</blockquote>
</div>
<br>
</div>
<div class="gmail_extra">Hello Fernando,<br>
<br>
</div>
<div class="gmail_extra">As you mentioned, oVirt is using the
Linux Bond and the solution you are looking for is not
supported.<br>
</div>
<div class="gmail_extra">The oVirt way to handle this is by
applying QoS on the networks, providing the guaranteed rates
for each and utilizing the bond for throughput beyond the one
link limit.<br>
<br>
</div>
<div class="gmail_extra">With the introduction of OVS as an
alternative networking infrastructure for the hosts, you could
create a hook that implements some special functionality, but
ovs is not in yet.<br>
<br>
</div>
<div class="gmail_extra">Thanks,<br>
</div>
<div class="gmail_extra">Edy.<br>
<br>
</div>
<div class="gmail_extra"><br>
</div>
</div>
</blockquote>
<br>
</body>
</html>
--------------060804090703060803060201--
7:39 a.m.
--Apple-Mail=_C94BBAD9-CF4E-4EF0-8F61-197B7219C318
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
charset=utf-8
Isn't teaming[1] the futur, instead of bonding ?
[1] http://rhelblog.redhat.com/2014/06/23/team-driver/
Le 27 juin 2016 =C3=A0 14:31, Fernando Frediani =
<fernando.frediani(a)upx.com.br> a =C3=A9crit :
=20
Thanks for the reply.
=20
Perhaps is the case of contacting the maintainer of Linux Bond module =
and see if
there is room for this feature to be implement anytime. OVS =
is great in the coming future, but Bond module is still something very =
handy that simplify the things a lot.
=20
Thanks
Fernando
=20
Em 27/06/2016 03:00, Edward Haas escreveu:
>=20
>=20
> On Sun, Jun 26, 2016 at 4:37 PM, Yevgeny Zaspitsky < =
<mailto:yzaspits@redhat.com>yzaspits@redhat.com =
<mailto:yzaspits@redhat.com>> wrote:
> Dan, Edy,
>=20
> Could you guys answer this?
>=20
> IIUC, the requirements are:
> stream the traffic of few VLANs(network roles) through a single bond
> be able to bind a VLAN to a bond slave with an option of fallback
> have redundancy
> assign different QoS to every VLAN (my addition)
> I guess this is a new RFC that we do not support currently, but would =
we be
able to provide in any future?
>=20
> ---------- Forwarded message ----------
> From: Fernando Frediani < =
<mailto:fernando.frediani@upx.com.br>fernando.frediani@upx.com.br =
<mailto:fernando.frediani@upx.com.br>>
> Date: Sat, Jun 25, 2016 at 11:17 PM
> Subject: [ovirt-users] Network redundancy with Manual balancing per =
VLAN
> To: users(a)ovirt.org <mailto:users@ovirt.org>
>=20
>=20
> Hello,
>=20
> In VMware it is possible to bond two network interfaces and for each =
Portgroup (equivalent to a VLAN) is possible to tell which of the =
physical interfaces underneath it you wish the traffic to flow primarily =
and which stays as secondary(bond mode=3D1 equivalent). So for certain =
VLANs (Management, Live Migration, etc) is possible to force traffic =
flow via one physical NIC of the bond and for other VLANs (Virtual =
Machine's traffic) outs via the other NIC with failover to each other =
should a cable or switch fails.
>=20
> This is specially good for better utilize the fewer NICs available =
and still
have redundancy.
>=20
> In oVirt it is also possible to have bonds, but would it still be =
possible to
do that same and favor the traffic per VLAN basis ? I guess =
it is something related to Linux Bond module but perhaps someone has =
done this already.
>=20
>=20
> =20
> Thanks
>=20
> Fernando
>=20
> _______________________________________________
> Users mailing list
> Users(a)ovirt.org <mailto:Users@ovirt.org>
> http://lists.ovirt.org/mailman/listinfo/users =
<http://lists.ovirt.org/mailman/listinfo/users>
>=20
>=20
> Hello Fernando,
>=20
> As you mentioned, oVirt is using the Linux Bond and the solution you =
are
looking for is not supported.
> The oVirt way to handle this is by applying QoS on the networks,
=
providing the guaranteed rates for each and utilizing the bond for =
throughput beyond the one link limit.
>=20
> With the introduction of OVS as an alternative networking =
infrastructure for
the hosts, you could create a hook that implements =
some special functionality, but ovs is not in yet.
>=20
> Thanks,
> Edy.
>=20
>=20
=20
_______________________________________________
Users mailing list
Users(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
--Apple-Mail=_C94BBAD9-CF4E-4EF0-8F61-197B7219C318
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
charset=utf-8
<html><head><meta http-equiv=3D"Content-Type"
content=3D"text/html =
charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" =
class=3D"">Isn't teaming[1] the futur, instead of bonding ?<div =
class=3D""><br class=3D""><div
class=3D"">[1] <a =
href=3D"http://rhelblog.redhat.com/2014/06/23/team-driver/" =
class=3D"">http://rhelblog.redhat.com/2014/06/23/team-driver...
v class=3D""><br class=3D""></div><div
class=3D""><br =
class=3D""><div><blockquote type=3D"cite"
class=3D""><div class=3D"">Le =
27 juin 2016 =C3=A0 14:31, Fernando Frediani <<a =
href=3D"mailto:fernando.frediani@upx.com.br" =
class=3D"">fernando.frediani(a)upx.com.br</a>&gt; a =C3=A9crit
:</div><br =
class=3D"Apple-interchange-newline"><div class=3D"">
=20
<meta content=3D"text/html; charset=3Dutf-8" =
http-equiv=3D"Content-Type" class=3D"">
=20
<div text=3D"#000000" bgcolor=3D"#FFFFFF"
class=3D"">
Thanks for the reply.<br class=3D"">
<br class=3D"">
Perhaps is the case of contacting the maintainer of Linux Bond
module and see if there is room for this feature to be implement
anytime. OVS is great in the coming future, but Bond module is still
something very handy that simplify the things a lot.<br class=3D"">
<br class=3D"">
Thanks<br class=3D"">
Fernando<br class=3D"">
<br class=3D"">
<div class=3D"moz-cite-prefix">Em 27/06/2016 03:00, Edward Haas
escreveu:<br class=3D"">
</div>
<blockquote =
cite=3D"mid:CALmkdFTCJdpeEKGe0qE4O9x+yik24UOraMJRfEDLos9bByacmA@mail.gmail=
.com" type=3D"cite" class=3D"">
<div dir=3D"ltr" class=3D""><br
class=3D"">
<div class=3D"gmail_extra"><br class=3D"">
<div class=3D"gmail_quote">On Sun, Jun 26, 2016 at 4:37 PM,
Yevgeny Zaspitsky <span dir=3D"ltr"
class=3D""><<a =
moz-do-not-send=3D"true" href=3D"mailto:yzaspits@redhat.com" =
target=3D"_blank" class=3D""></a><a
class=3D"moz-txt-link-abbreviated" =
href=3D"mailto:yzaspits@redhat.com">yzaspits@redhat.com</a>></span>
wrote:<br class=3D"">
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px =
0px
0.8ex;border-left:1px solid
rgb(204,204,204);padding-left:1ex">
<div dir=3D"ltr" class=3D"">
<div class=3D"">Dan, Edy,<br class=3D"">
<br class=3D"">
Could you guys answer this?<br class=3D"">
<br class=3D"">
</div>
IIUC, the requirements are:<br class=3D"">
<ul class=3D"">
<li class=3D"">stream the traffic of few VLANs(network
=
roles)
through a single bond</li>
<li class=3D"">be able to bind a VLAN to a bond slave =
with an
option of fallback<br class=3D"">
</li>
<li class=3D"">have redundancy</li>
<li class=3D"">assign different QoS to every VLAN (my =
addition)<br class=3D"">
</li>
</ul>
<div class=3D"">
<div class=3D"">I guess this is a new RFC that we do =
not support
currently, but would we be able to provide in any
future?<br class=3D"">
</div>
<div class=3D"">
<div class=3D"">
<div class=3D""><br class=3D"">
<div class=3D"gmail_quote">---------- Forwarded
message ----------<br class=3D"">
From: <b class=3D"gmail_sendername">Fernando
Frediani</b> <span dir=3D"ltr" =
class=3D""><<a moz-do-not-send=3D"true" =
href=3D"mailto:fernando.frediani@upx.com.br" target=3D"_blank" =
class=3D""></a><a class=3D"moz-txt-link-abbreviated" =
href=3D"mailto:fernando.frediani@upx.com.br">fernando.frediani@upx.com.br<=
/a>></span><br class=3D"">
Date: Sat, Jun 25, 2016 at 11:17 PM<br =
class=3D"">
Subject: [ovirt-users] Network redundancy with
Manual balancing per VLAN<br class=3D"">
To: <a moz-do-not-send=3D"true" =
href=3D"mailto:users@ovirt.org" target=3D"_blank" =
class=3D"">users(a)ovirt.org</a><br class=3D"">
<br class=3D"">
<br class=3D"">
Hello,<br class=3D"">
<br class=3D"">
In VMware it is possible to bond two network
interfaces and for each Portgroup (equivalent
to a VLAN) is possible to tell which of the
physical interfaces underneath it you wish the
traffic to flow primarily and which stays as
secondary(bond mode=3D1 equivalent). So for
certain VLANs (Management, Live Migration,
etc) is possible to force traffic flow via one
physical NIC of the bond and for other VLANs
(Virtual Machine's traffic) outs via the other
NIC with failover to each other should a cable
or switch fails.<br class=3D"">
<br class=3D"">
This is specially good for better utilize the
fewer NICs available and still have
redundancy.<br class=3D"">
<br class=3D"">
In oVirt it is also possible to have bonds,
but would it still be possible to do that same
and favor the traffic per VLAN basis ? I guess
it is something related to Linux Bond module
but perhaps someone has done this already.<br =
class=3D"">
<br class=3D"">
</div>
</div>
</div>
</div>
</div>
</div>
</blockquote>
<div class=3D""><br class=3D"">
</div>
<div class=3D""> </div>
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px =
0px
0.8ex;border-left:1px solid
rgb(204,204,204);padding-left:1ex">
<div dir=3D"ltr" class=3D"">
<div class=3D"">
<div class=3D"">
<div class=3D"">
<div class=3D"">
<div class=3D"gmail_quote">
Thanks<br class=3D"">
<br class=3D"">
Fernando<br class=3D"">
<br class=3D"">
_______________________________________________<br class=3D"">
Users mailing list<br class=3D"">
<a moz-do-not-send=3D"true" =
href=3D"mailto:Users@ovirt.org" target=3D"_blank" =
class=3D"">Users(a)ovirt.org</a><br class=3D"">
<a moz-do-not-send=3D"true" =
href=3D"http://lists.ovirt.org/mailman/listinfo/users"
rel=3D"noreferrer" =
target=3D"_blank" =
class=3D"">http://lists.ovirt.org/mailman/listinfo/users<... =
class=3D"">
</div>
<br class=3D"">
</div>
</div>
</div>
</div>
</div>
</blockquote>
</div>
<br class=3D"">
</div>
<div class=3D"gmail_extra">Hello Fernando,<br
class=3D"">
<br class=3D"">
</div>
<div class=3D"gmail_extra">As you mentioned, oVirt is using the
Linux Bond and the solution you are looking for is not
supported.<br class=3D"">
</div>
<div class=3D"gmail_extra">The oVirt way to handle this is by
applying QoS on the networks, providing the guaranteed rates
for each and utilizing the bond for throughput beyond the one
link limit.<br class=3D"">
<br class=3D"">
</div>
<div class=3D"gmail_extra">With the introduction of OVS as an
alternative networking infrastructure for the hosts, you could
create a hook that implements some special functionality, but
ovs is not in yet.<br class=3D"">
<br class=3D"">
</div>
<div class=3D"gmail_extra">Thanks,<br class=3D"">
</div>
<div class=3D"gmail_extra">Edy.<br class=3D"">
<br class=3D"">
</div>
<div class=3D"gmail_extra"><br class=3D"">
</div>
</div>
</blockquote>
<br class=3D"">
</div>
_______________________________________________<br class=3D"">Users =
mailing list<br class=3D""><a href=3D"mailto:Users@ovirt.org"
=
class=3D"">Users(a)ovirt.org</a><br =
class=3D"">http://lists.ovirt.org/mailman/listinfo/users<br =
class=3D""></div></blockquote></div><br =
class=3D""></div></div></body></html>=
--Apple-Mail=_C94BBAD9-CF4E-4EF0-8F61-197B7219C318--
7:44 a.m.
This is a multi-part message in MIME format.
--------------020307040000010903080703
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Well, yes. That's actually the name VMware uses.
If it bring similar functionalities then that's the solution. Thanks for
sharing. looks pretty intresting.
Fernando
Em 27/06/2016 09:39, Fabrice Bacchella escreveu:
Isn't teaming[1] the futur, instead of bonding ?
[1] http://rhelblog.redhat.com/2014/06/23/team-driver/
> Le 27 juin 2016 à 14:31, Fernando Frediani
> <fernando.frediani(a)upx.com.br <mailto:fernando.frediani@upx.com.br>>
> a écrit :
>
> Thanks for the reply.
>
> Perhaps is the case of contacting the maintainer of Linux Bond module
> and see if there is room for this feature to be implement anytime.
> OVS is great in the coming future, but Bond module is still something
> very handy that simplify the things a lot.
>
> Thanks
> Fernando
>
> Em 27/06/2016 03:00, Edward Haas escreveu:
>>
>>
>> On Sun, Jun 26, 2016 at 4:37 PM, Yevgeny Zaspitsky
>> <yzaspits(a)redhat.com> wrote:
>>
>> Dan, Edy,
>>
>> Could you guys answer this?
>>
>> IIUC, the requirements are:
>>
>> * stream the traffic of few VLANs(network roles) through a
>> single bond
>> * be able to bind a VLAN to a bond slave with an option of
>> fallback
>> * have redundancy
>> * assign different QoS to every VLAN (my addition)
>>
>> I guess this is a new RFC that we do not support currently, but
>> would we be able to provide in any future?
>>
>> ---------- Forwarded message ----------
>> From: *Fernando Frediani* <fernando.frediani(a)upx.com.br>
>> Date: Sat, Jun 25, 2016 at 11:17 PM
>> Subject: [ovirt-users] Network redundancy with Manual balancing
>> per VLAN
>> To: users(a)ovirt.org <mailto:users@ovirt.org>
>>
>>
>> Hello,
>>
>> In VMware it is possible to bond two network interfaces and for
>> each Portgroup (equivalent to a VLAN) is possible to tell which
>> of the physical interfaces underneath it you wish the traffic to
>> flow primarily and which stays as secondary(bond mode=1
>> equivalent). So for certain VLANs (Management, Live Migration,
>> etc) is possible to force traffic flow via one physical NIC of
>> the bond and for other VLANs (Virtual Machine's traffic) outs
>> via the other NIC with failover to each other should a cable or
>> switch fails.
>>
>> This is specially good for better utilize the fewer NICs
>> available and still have redundancy.
>>
>> In oVirt it is also possible to have bonds, but would it still
>> be possible to do that same and favor the traffic per VLAN basis
>> ? I guess it is something related to Linux Bond module but
>> perhaps someone has done this already.
>>
>>
>> Thanks
>>
>> Fernando
>>
>> _______________________________________________
>> Users mailing list
>> Users(a)ovirt.org <mailto:Users@ovirt.org>
>> http://lists.ovirt.org/mailman/listinfo/users
>>
>>
>> Hello Fernando,
>>
>> As you mentioned, oVirt is using the Linux Bond and the solution you
>> are looking for is not supported.
>> The oVirt way to handle this is by applying QoS on the networks,
>> providing the guaranteed rates for each and utilizing the bond for
>> throughput beyond the one link limit.
>>
>> With the introduction of OVS as an alternative networking
>> infrastructure for the hosts, you could create a hook that
>> implements some special functionality, but ovs is not in yet.
>>
>> Thanks,
>> Edy.
>>
>>
>
> _______________________________________________
> Users mailing list
> Users(a)ovirt.org <mailto:Users@ovirt.org>
> http://lists.ovirt.org/mailman/listinfo/users
--------------020307040000010903080703
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 8bit
<html>
<head>
<meta content="text/html; charset=utf-8"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
Well, yes. That's actually the name VMware uses.<br>
<br>
If it bring similar functionalities then that's the solution. Thanks
for sharing. looks pretty intresting.<br>
<br>
Fernando<br>
<br>
<div class="moz-cite-prefix">Em 27/06/2016 09:39, Fabrice Bacchella
escreveu:<br>
</div>
<blockquote
cite="mid:DCB689B5-9CEA-4C41-B952-BE40CC824052@icloud.com"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=utf-8">
Isn't teaming[1] the futur, instead of bonding ?
<div class=""><br class="">
<div class="">[1] <a moz-do-not-send="true"
href="http://rhelblog.redhat.com/2014/06/23/team-driver/"
class="">http://rhelblog.redhat.com/2014/06/23/team-driver/&...
<div class=""><br class="">
</div>
<div class=""><br class="">
<div>
<blockquote type="cite" class="">
<div class="">Le 27 juin 2016 à 14:31, Fernando Frediani
<<a moz-do-not-send="true"
href="mailto:fernando.frediani@upx.com.br"
class="">fernando.frediani(a)upx.com.br</a>&gt;
a écrit :</div>
<br class="Apple-interchange-newline">
<div class="">
<meta content="text/html; charset=utf-8"
http-equiv="Content-Type" class="">
<div text="#000000" bgcolor="#FFFFFF"
class=""> Thanks
for the reply.<br class="">
<br class="">
Perhaps is the case of contacting the maintainer of
Linux Bond module and see if there is room for this
feature to be implement anytime. OVS is great in the
coming future, but Bond module is still something very
handy that simplify the things a lot.<br class="">
<br class="">
Thanks<br class="">
Fernando<br class="">
<br class="">
<div class="moz-cite-prefix">Em 27/06/2016 03:00,
Edward Haas escreveu:<br class="">
</div>
<blockquote
cite="mid:CALmkdFTCJdpeEKGe0qE4O9x+yik24UOraMJRfEDLos9bByacmA@mail.gmail.com"
type="cite" class="">
<div dir="ltr" class=""><br
class="">
<div class="gmail_extra"><br
class="">
<div class="gmail_quote">On Sun, Jun 26, 2016 at
4:37 PM, Yevgeny Zaspitsky <span dir="ltr"
class=""><<a
moz-do-not-send="true"
class="moz-txt-link-abbreviated"
href="mailto:yzaspits@redhat.com">yzaspits@redhat.com</a>></span>
wrote:<br class="">
<blockquote class="gmail_quote"
style="margin:0px 0px 0px
0.8ex;border-left:1px solid
rgb(204,204,204);padding-left:1ex">
<div dir="ltr" class="">
<div class="">Dan, Edy,<br
class="">
<br class="">
Could you guys answer this?<br class="">
<br class="">
</div>
IIUC, the requirements are:<br class="">
<ul class="">
<li class="">stream the traffic of few
VLANs(network roles) through a single
bond</li>
<li class="">be able to bind a VLAN to a
bond slave with an option of fallback<br
class="">
</li>
<li class="">have redundancy</li>
<li class="">assign different QoS to
every VLAN (my addition)<br class="">
</li>
</ul>
<div class="">
<div class="">I guess this is a new RFC
that we do not support currently, but
would we be able to provide in any
future?<br class="">
</div>
<div class="">
<div class="">
<div class=""><br
class="">
<div class="gmail_quote">----------
Forwarded message ----------<br
class="">
From: <b
class="gmail_sendername">Fernando
Frediani</b> <span dir="ltr"
class=""><<a
moz-do-not-send="true"
class="moz-txt-link-abbreviated"
href="mailto:fernando.frediani@upx.com.br"><a
class="moz-txt-link-abbreviated"
href="mailto:fernando.frediani@upx.com.br">fernando.frediani@upx.com.br</a></a>></span><br
class="">
Date: Sat, Jun 25, 2016 at 11:17
PM<br class="">
Subject: [ovirt-users] Network
redundancy with Manual balancing
per VLAN<br class="">
To: <a moz-do-not-send="true"
href="mailto:users@ovirt.org"
target="_blank"
class="">users(a)ovirt.org</a><br
class="">
<br class="">
<br class="">
Hello,<br class="">
<br class="">
In VMware it is possible to bond
two network interfaces and for
each Portgroup (equivalent to a
VLAN) is possible to tell which
of the physical interfaces
underneath it you wish the
traffic to flow primarily and
which stays as secondary(bond
mode=1 equivalent). So for
certain VLANs (Management, Live
Migration, etc) is possible to
force traffic flow via one
physical NIC of the bond and for
other VLANs (Virtual Machine's
traffic) outs via the other NIC
with failover to each other
should a cable or switch fails.<br
class="">
<br class="">
This is specially good for
better utilize the fewer NICs
available and still have
redundancy.<br class="">
<br class="">
In oVirt it is also possible to
have bonds, but would it still
be possible to do that same and
favor the traffic per VLAN basis
? I guess it is something
related to Linux Bond module but
perhaps someone has done this
already.<br class="">
<br class="">
</div>
</div>
</div>
</div>
</div>
</div>
</blockquote>
<div class=""><br class="">
</div>
<div class=""> </div>
<blockquote class="gmail_quote"
style="margin:0px 0px 0px
0.8ex;border-left:1px solid
rgb(204,204,204);padding-left:1ex">
<div dir="ltr" class="">
<div class="">
<div class="">
<div class="">
<div class="">
<div class="gmail_quote">
Thanks<br
class="">
<br class="">
Fernando<br class="">
<br class="">
_______________________________________________<br class="">
Users mailing list<br class="">
<a moz-do-not-send="true"
href="mailto:Users@ovirt.org"
target="_blank"
class="">Users(a)ovirt.org</a><br
class="">
<a moz-do-not-send="true"
href="http://lists.ovirt.org/mailman/listinfo/users"
rel="noreferrer"
target="_blank"
class="">http://lists.ovirt.org/mailman/listinfo/users</a...
class="">
</div>
<br class="">
</div>
</div>
</div>
</div>
</div>
</blockquote>
</div>
<br class="">
</div>
<div class="gmail_extra">Hello Fernando,<br
class="">
<br class="">
</div>
<div class="gmail_extra">As you mentioned, oVirt
is using the Linux Bond and the solution you are
looking for is not supported.<br class="">
</div>
<div class="gmail_extra">The oVirt way to handle
this is by applying QoS on the networks,
providing the guaranteed rates for each and
utilizing the bond for throughput beyond the one
link limit.<br class="">
<br class="">
</div>
<div class="gmail_extra">With the introduction of
OVS as an alternative networking infrastructure
for the hosts, you could create a hook that
implements some special functionality, but ovs
is not in yet.<br class="">
<br class="">
</div>
<div class="gmail_extra">Thanks,<br
class="">
</div>
<div class="gmail_extra">Edy.<br
class="">
<br class="">
</div>
<div class="gmail_extra"><br
class="">
</div>
</div>
</blockquote>
<br class="">
</div>
_______________________________________________<br
class="">
Users mailing list<br class="">
<a moz-do-not-send="true"
href="mailto:Users@ovirt.org"
class="">Users(a)ovirt.org</a><br
class="">
<a class="moz-txt-link-freetext"
href="http://lists.ovirt.org/mailman/listinfo/users">http://...
class="">
</div>
</blockquote>
</div>
<br class="">
</div>
</div>
</blockquote>
<br>
</body>
</html>
--------------020307040000010903080703--
3240
days inactive
3242
days old
5 comments
4 participants
participants (4)
-
Edward Haas -
Fabrice Bacchella -
Fernando Frediani -
Yevgeny Zaspitsky