2:59 p.m.
Hi All
I'm looking to add a new host to my oVirt lab installation.
I'm going to share out some LVs from a separate box over iSCSI and will
hook the new host up to that.
I have 2 NICs on the storage host and 2 NICs on the new Ovirt host to
dedicate to the iSCSI traffic.
I also have 2 separate switches so I'm looking for redundancy here. Both
iSCSI host and oVirt host plugged into both switches.
If this was non-iSCSI traffic and without oVirt I would create bonded
interfaces in active-backup mode and layer the VLANs on top of that.
But for iSCSI traffic without oVirt involved I wouldn't bother with a
bond and just use multipath.
From scanning the oVirt docs it looks like there is an option to have
oVirt configure iSCSI multipathing.
So what's the best/most-supported option for oVirt?
Manually create active-backup bonds so oVirt just sees a single storage
link between host and storage?
Or leave them as separate interfaces on each side and use oVirt's
multipath/bonding?
Also I quite like the idea of using IPv6 for the iSCSI VLAN, purely down
to the fact I could use link-local addressing and not have to worry
about setting up static IPv4 addresses or DHCP. Is IPv6 iSCSI supported
by oVirt?
Thanks, Ben
2:32 a.m.
On Wed, Sep 27, 2017 at 10:59 PM, Ben Bradley <listsbb(a)virtx.net> wrote:
Hi All
I'm looking to add a new host to my oVirt lab installation.
I'm going to share out some LVs from a separate box over iSCSI and will
hook the new host up to that.
I have 2 NICs on the storage host and 2 NICs on the new Ovirt host to
dedicate to the iSCSI traffic.
I also have 2 separate switches so I'm looking for redundancy here. Both
iSCSI host and oVirt host plugged into both switches.
If this was non-iSCSI traffic and without oVirt I would create bonded
interfaces in active-backup mode and layer the VLANs on top of that.
But for iSCSI traffic without oVirt involved I wouldn't bother with a bond
and just use multipath.
From scanning the oVirt docs it looks like there is an option to have
oVirt configure iSCSI multipathing.
Look for iSCSI bonding - that's the feature you are looking for.
So what's the best/most-supported option for oVirt?
Manually create active-backup bonds so oVirt just sees a single storage
link between host and storage?
Or leave them as separate interfaces on each side and use oVirt's
multipath/bonding?
Also I quite like the idea of using IPv6 for the iSCSI VLAN, purely down
to the fact I could use link-local addressing and not have to worry about
setting up static IPv4 addresses or DHCP. Is IPv6 iSCSI supported by oVirt?
No, we do not. There has been some work in the area[1], but I'm not sure it
is complete.
Y.
[1]
https://gerrit.ovirt.org/#/q/status:merged+project:vdsm+branch:master+top...
Thanks, Ben
_______________________________________________
Users mailing list
Users(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
5:54 a.m.
On Wed, Sep 27, 2017 at 11:01 PM Ben Bradley <listsbb(a)virtx.net> wrote:
Hi All
I'm looking to add a new host to my oVirt lab installation.
I'm going to share out some LVs from a separate box over iSCSI and will
hook the new host up to that.
I have 2 NICs on the storage host and 2 NICs on the new Ovirt host to
dedicate to the iSCSI traffic.
I also have 2 separate switches so I'm looking for redundancy here. Both
iSCSI host and oVirt host plugged into both switches.
If this was non-iSCSI traffic and without oVirt I would create bonded
interfaces in active-backup mode and layer the VLANs on top of that.
But for iSCSI traffic without oVirt involved I wouldn't bother with a
bond and just use multipath.
From scanning the oVirt docs it looks like there is an option to have
oVirt configure iSCSI multipathing.
So what's the best/most-supported option for oVirt?
oVirt support only multipath devices, so the best way is to use multipath
features.
Manually create active-backup bonds so oVirt just sees a single
storage
link between host and storage?
This will always be on top of multipath device, giving you the same
capabilities, so why would you want to do that?
Or leave them as separate interfaces on each side and use
oVirt's
multipath/bonding?
Yes.
Also I quite like the idea of using IPv6 for the iSCSI VLAN, purely down
to the fact I could use link-local addressing and not have to worry
about setting up static IPv4 addresses or DHCP. Is IPv6 iSCSI supported
by oVirt?
Thanks, Ben
_______________________________________________
Users mailing list
Users(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
7:18 a.m.
On Thu, Sep 28, 2017 at 1:54 PM, Nir Soffer <nsoffer(a)redhat.com> wrote:
On Wed, Sep 27, 2017 at 11:01 PM Ben Bradley <listsbb(a)virtx.net> wrote:
> Hi All
>
> I'm looking to add a new host to my oVirt lab installation.
> I'm going to share out some LVs from a separate box over iSCSI and will
> hook the new host up to that.
> I have 2 NICs on the storage host and 2 NICs on the new Ovirt host to
> dedicate to the iSCSI traffic.
> I also have 2 separate switches so I'm looking for redundancy here. Both
> iSCSI host and oVirt host plugged into both switches.
>
> If this was non-iSCSI traffic and without oVirt I would create bonded
> interfaces in active-backup mode and layer the VLANs on top of that.
>
> But for iSCSI traffic without oVirt involved I wouldn't bother with a
> bond and just use multipath.
>
> From scanning the oVirt docs it looks like there is an option to have
> oVirt configure iSCSI multipathing.
>
> So what's the best/most-supported option for oVirt?
>
oVirt support only multipath devices, so the best way is to use multipath
features.
> Manually create active-backup bonds so oVirt just sees a single storage
> link between host and storage?
>
This will always be on top of multipath device, giving you the same
capabilities, so why would you want to do that?
If the link is not only for storage traffic, then it makes sense to use
bonding.
Active-Active is much better, of course, if possible.
Y.
> Or leave them as separate interfaces on each side and use oVirt's
> multipath/bonding?
>
Yes.
>
> Also I quite like the idea of using IPv6 for the iSCSI VLAN, purely down
> to the fact I could use link-local addressing and not have to worry
> about setting up static IPv4 addresses or DHCP. Is IPv6 iSCSI supported
> by oVirt?
>
> Thanks, Ben
> _______________________________________________
> Users mailing list
> Users(a)ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
_______________________________________________
Users mailing list
Users(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
4:27 p.m.
On 28/09/17 08:32, Yaniv Kaul wrote:
On Wed, Sep 27, 2017 at 10:59 PM, Ben Bradley <listsbb(a)virtx.net
<mailto:listsbb@virtx.net>> wrote:
Hi All
I'm looking to add a new host to my oVirt lab installation.
I'm going to share out some LVs from a separate box over iSCSI and
will hook the new host up to that.
I have 2 NICs on the storage host and 2 NICs on the new Ovirt host
to dedicate to the iSCSI traffic.
I also have 2 separate switches so I'm looking for redundancy here.
Both iSCSI host and oVirt host plugged into both switches.
If this was non-iSCSI traffic and without oVirt I would create
bonded interfaces in active-backup mode and layer the VLANs on top
of that.
But for iSCSI traffic without oVirt involved I wouldn't bother with
a bond and just use multipath.
From scanning the oVirt docs it looks like there is an option to
have oVirt configure iSCSI multipathing.
Look for iSCSI bonding - that's the feature you are looking for.
Thanks for the replies.
By iSCSI bonding, do you mean the oVirt feature "iSCSI multipathing" as
mentioned here
https://www.ovirt.org/documentation/admin-guide/chap-Storage/ ?
Separate links seems to be the consensus then. Since these are links
dedicated to iSCSI traffic, not shared. the ovirtmgmt bridge lives on
top of an active-backup bond on other NICs.
Thanks, Ben
So what's the best/most-supported option for oVirt?
Manually create active-backup bonds so oVirt just sees a single
storage link between host and storage?
Or leave them as separate interfaces on each side and use oVirt's
multipath/bonding?
Also I quite like the idea of using IPv6 for the iSCSI VLAN, purely
down to the fact I could use link-local addressing and not have to
worry about setting up static IPv4 addresses or DHCP. Is IPv6 iSCSI
supported by oVirt?
No, we do not. There has been some work in the area[1], but I'm not sure
it is complete.
Y.
[1]
https://gerrit.ovirt.org/#/q/status:merged+project:vdsm+branch:master+top...
Thanks, Ben
_______________________________________________
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>
6:18 p.m.
On 28/09/17 22:27, Ben Bradley wrote:
On 28/09/17 08:32, Yaniv Kaul wrote:
>
>
> On Wed, Sep 27, 2017 at 10:59 PM, Ben Bradley <listsbb(a)virtx.net
> <mailto:listsbb@virtx.net>> wrote:
>
> Hi All
>
> I'm looking to add a new host to my oVirt lab installation.
> I'm going to share out some LVs from a separate box over iSCSI and
> will hook the new host up to that.
> I have 2 NICs on the storage host and 2 NICs on the new Ovirt host
> to dedicate to the iSCSI traffic.
> I also have 2 separate switches so I'm looking for redundancy here.
> Both iSCSI host and oVirt host plugged into both switches.
>
> If this was non-iSCSI traffic and without oVirt I would create
> bonded interfaces in active-backup mode and layer the VLANs on top
> of that.
>
> But for iSCSI traffic without oVirt involved I wouldn't bother with
> a bond and just use multipath.
>
> From scanning the oVirt docs it looks like there is an option to
> have oVirt configure iSCSI multipathing.
>
>
> Look for iSCSI bonding - that's the feature you are looking for.
Thanks for the replies.
By iSCSI bonding, do you mean the oVirt feature "iSCSI multipathing" as
mentioned here
https://www.ovirt.org/documentation/admin-guide/chap-Storage/ ?
Separate links seems to be the consensus then. Since these are links
dedicated to iSCSI traffic, not shared. the ovirtmgmt bridge lives on
top of an active-backup bond on other NICs.
Thanks, Ben
And an extra question about oVirt's iSCSI multipathing - should each
path be a separate VLAN+subnet?
I assume it should be separate VLANs for running separate physical
fabrics if desired.
Thanks, Ben
> So what's the best/most-supported option for oVirt?
> Manually create active-backup bonds so oVirt just sees a single
> storage link between host and storage?
> Or leave them as separate interfaces on each side and use oVirt's
> multipath/bonding?
>
> Also I quite like the idea of using IPv6 for the iSCSI VLAN, purely
> down to the fact I could use link-local addressing and not have to
> worry about setting up static IPv4 addresses or DHCP. Is IPv6 iSCSI
> supported by oVirt?
>
>
> No, we do not. There has been some work in the area[1], but I'm not
> sure it is complete.
> Y.
>
> [1]
>
https://gerrit.ovirt.org/#/q/status:merged+project:vdsm+branch:master+top...
>
>
>
> Thanks, Ben
> _______________________________________________
> 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>
>
>
_______________________________________________
Users mailing list
Users(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
1:54 a.m.
On Sun, Oct 1, 2017 at 2:18 AM, Ben Bradley <listsbb(a)virtx.net> wrote:
On 28/09/17 22:27, Ben Bradley wrote:
> On 28/09/17 08:32, Yaniv Kaul wrote:
>
>>
>>
>> On Wed, Sep 27, 2017 at 10:59 PM, Ben Bradley <listsbb(a)virtx.net
>> <mailto:listsbb@virtx.net>> wrote:
>>
>> Hi All
>>
>> I'm looking to add a new host to my oVirt lab installation.
>> I'm going to share out some LVs from a separate box over iSCSI and
>> will hook the new host up to that.
>> I have 2 NICs on the storage host and 2 NICs on the new Ovirt host
>> to dedicate to the iSCSI traffic.
>> I also have 2 separate switches so I'm looking for redundancy here.
>> Both iSCSI host and oVirt host plugged into both switches.
>>
>> If this was non-iSCSI traffic and without oVirt I would create
>> bonded interfaces in active-backup mode and layer the VLANs on top
>> of that.
>>
>> But for iSCSI traffic without oVirt involved I wouldn't bother with
>> a bond and just use multipath.
>>
>> From scanning the oVirt docs it looks like there is an option to
>> have oVirt configure iSCSI multipathing.
>>
>>
>> Look for iSCSI bonding - that's the feature you are looking for.
>>
>
> Thanks for the replies.
>
> By iSCSI bonding, do you mean the oVirt feature "iSCSI multipathing" as
> mentioned here https://www.ovirt.org/documentation/admin-guide/chap-
> Storage/ ?
>
> Separate links seems to be the consensus then. Since these are links
> dedicated to iSCSI traffic, not shared. the ovirtmgmt bridge lives on top
> of an active-backup bond on other NICs.
>
> Thanks, Ben
>
And an extra question about oVirt's iSCSI multipathing - should each path
be a separate VLAN+subnet?
I assume it should be separate VLANs for running separate physical fabrics
if desired.
Depends on your network architecture. Doesn't have to be.
Y.
Thanks, Ben
> So what's the best/most-supported option for oVirt?
>> Manually create active-backup bonds so oVirt just sees a single
>> storage link between host and storage?
>> Or leave them as separate interfaces on each side and use oVirt's
>> multipath/bonding?
>>
>> Also I quite like the idea of using IPv6 for the iSCSI VLAN, purely
>> down to the fact I could use link-local addressing and not have to
>> worry about setting up static IPv4 addresses or DHCP. Is IPv6 iSCSI
>> supported by oVirt?
>>
>>
>> No, we do not. There has been some work in the area[1], but I'm not sure
>> it is complete.
>> Y.
>>
>> [1] https://gerrit.ovirt.org/#/q/status:merged+project:vdsm+bran
>> ch:master+topic:ipv6-iscsi-target-support
>>
>>
>> Thanks, Ben
>> _______________________________________________
>> 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>
>>
>>
>>
> _______________________________________________
> Users mailing list
> Users(a)ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
2:24 a.m.
On Sun, Oct 1, 2017 at 2:19 AM Ben Bradley <listsbb(a)virtx.net> wrote:
On 28/09/17 22:27, Ben Bradley wrote:
> On 28/09/17 08:32, Yaniv Kaul wrote:
>>
>>
>> On Wed, Sep 27, 2017 at 10:59 PM, Ben Bradley <listsbb(a)virtx.net
>> <mailto:listsbb@virtx.net>> wrote:
>>
>> Hi All
>>
>> I'm looking to add a new host to my oVirt lab installation.
>> I'm going to share out some LVs from a separate box over iSCSI and
>> will hook the new host up to that.
>> I have 2 NICs on the storage host and 2 NICs on the new Ovirt host
>> to dedicate to the iSCSI traffic.
>> I also have 2 separate switches so I'm looking for redundancy here.
>> Both iSCSI host and oVirt host plugged into both switches.
>>
>> If this was non-iSCSI traffic and without oVirt I would create
>> bonded interfaces in active-backup mode and layer the VLANs on top
>> of that.
>>
>> But for iSCSI traffic without oVirt involved I wouldn't bother with
>> a bond and just use multipath.
>>
>> From scanning the oVirt docs it looks like there is an option to
>> have oVirt configure iSCSI multipathing.
>>
>>
>> Look for iSCSI bonding - that's the feature you are looking for.
>
> Thanks for the replies.
>
> By iSCSI bonding, do you mean the oVirt feature "iSCSI multipathing" as
> mentioned here
> https://www.ovirt.org/documentation/admin-guide/chap-Storage/ ?
>
> Separate links seems to be the consensus then. Since these are links
> dedicated to iSCSI traffic, not shared. the ovirtmgmt bridge lives on
> top of an active-backup bond on other NICs.
>
> Thanks, Ben
And an extra question about oVirt's iSCSI multipathing - should each
path be a separate VLAN+subnet?
I assume it should be separate VLANs for running separate physical
fabrics if desired.
Check this:
https://www.centos.org/docs/5/html/5.2/DM_Multipath/MPIO_description.html
Thanks, Ben
>
>> So what's the best/most-supported option for oVirt?
>> Manually create active-backup bonds so oVirt just sees a single
>> storage link between host and storage?
>> Or leave them as separate interfaces on each side and use oVirt's
>> multipath/bonding?
>>
>> Also I quite like the idea of using IPv6 for the iSCSI VLAN, purely
>> down to the fact I could use link-local addressing and not have to
>> worry about setting up static IPv4 addresses or DHCP. Is IPv6 iSCSI
>> supported by oVirt?
>>
>>
>> No, we do not. There has been some work in the area[1], but I'm not
>> sure it is complete.
>> Y.
>>
>> [1]
>>
https://gerrit.ovirt.org/#/q/status:merged+project:vdsm+branch:master+top...
>>
>>
>>
>> Thanks, Ben
>> _______________________________________________
>> 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>
>>
>>
>
> _______________________________________________
> Users mailing list
> Users(a)ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
_______________________________________________
Users mailing list
Users(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
10:30 a.m.
--_000_03468DF4AA234FCC80074739E2D985D1ifufrjbr_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
On 30 Sep 2017, at 20:18, Ben Bradley <listsbb@virtx.net<mailto:listsbb@vir=
tx.net>> wrote:
On 28/09/17 22:27, Ben Bradley wrote:
On 28/09/17 08:32, Yaniv Kaul wrote:
On Wed, Sep 27, 2017 at 10:59 PM, Ben Bradley <listsbb@virtx.net<mailto:lis=
tsbb(a)virtx.net> <mailto:listsbb@virtx.net>> wrote:
Hi All
I'm looking to add a new host to my oVirt lab installation.
I'm going to share out some LVs from a separate box over iSCSI and
will hook the new host up to that.
I have 2 NICs on the storage host and 2 NICs on the new Ovirt host
to dedicate to the iSCSI traffic.
I also have 2 separate switches so I'm looking for redundancy here.
Both iSCSI host and oVirt host plugged into both switches.
If this was non-iSCSI traffic and without oVirt I would create
bonded interfaces in active-backup mode and layer the VLANs on top
of that.
But for iSCSI traffic without oVirt involved I wouldn't bother with
a bond and just use multipath.
From scanning the oVirt docs it looks like there is an option to
have oVirt configure iSCSI multipathing.
Look for iSCSI bonding - that's the feature you are looking for.
Thanks for the replies.
By iSCSI bonding, do you mean the oVirt feature "iSCSI multipathing" as men=
tioned here https://www.ovirt.org/documentation/admin-guide/chap-Storage/ ?
Separate links seems to be the consensus then. Since these are links dedica=
ted to iSCSI traffic, not shared. the ovirtmgmt bridge lives on top of an a=
ctive-backup bond on other NICs.
Thanks, Ben
And an extra question about oVirt's iSCSI multipathing - should each path b=
e a separate VLAN+subnet?
I assume it should be separate VLANs for running separate physical fabrics =
if desired.
Thanks, Ben
Take a look at this Ben:
https://bugzilla.redhat.com/show_bug.cgi?id=3D1474904
oVirt is a little bit different with iSCSI MPIO.
So what's the best/most-supported option for oVirt?
Manually create active-backup bonds so oVirt just sees a single
storage link between host and storage?
Or leave them as separate interfaces on each side and use oVirt's
multipath/bonding?
Also I quite like the idea of using IPv6 for the iSCSI VLAN, purely
down to the fact I could use link-local addressing and not have to
worry about setting up static IPv4 addresses or DHCP. Is IPv6 iSCSI
supported by oVirt?
No, we do not. There has been some work in the area[1], but I'm not sure it=
is complete.
Y.
[1] https://gerrit.ovirt.org/#/q/status:merged+project:vdsm+branch:master+t=
opic:ipv6-iscsi-target-support
Thanks, Ben
_______________________________________________
Users mailing list
Users@ovirt.org<mailto:Users@ovirt.org> <mailto:Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
<http://lists.ovirt.org/mailman/listinfo/users
_______________________________________________
Users mailing list
Users@ovirt.org<mailto:Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
_______________________________________________
Users mailing list
Users@ovirt.org<mailto:Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
--_000_03468DF4AA234FCC80074739E2D985D1ifufrjbr_
Content-Type: text/html; charset="iso-8859-1"
Content-ID: <8742F9D5CFE6964EB85063889CAE8F1B(a)if.ufrj.br
Content-Transfer-Encoding: quoted-printable
<html <head <meta http-equiv=3D"Content-Type"
content=3D"text/html; charset=3Diso-8859-=
1" </head <body
style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; line-break:=
after-white-space;" class=3D"" <br
class=3D"" <div><br
class=3D"" <blockquote
type=3D"cite" class=3D"" <div
class=3D"">On 30 Sep 2017, at 20:18, Ben Bradley <<a
href=3D"mailto=
:listsbb@virtx.net" class=3D"">listsbb(a)virtx.net</a>&gt;
wrote:</div <br
class=3D"Apple-interchange-newline" <div
class=3D""><span style=3D"font-family: Helvetica; font-size: 12px;
fon=
t-style: normal; font-variant-caps: normal; font-weight: normal; letter-spa=
cing: normal; text-align: start; text-indent: 0px; text-transform: none; wh=
ite-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; float=
: none; display: inline !important;" class=3D"">On
28/09/17 22:27, Ben Bradley wrote:</span><br style=3D"font-family:
Helveti=
ca; font-size: 12px; font-style: normal; font-variant-caps: normal; font-we=
ight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-=
stroke-width: 0px;" class=3D""
<blockquote type=3D"cite" style=3D"font-family: Helvetica;
font-size: 12px;=
font-style: normal; font-variant-caps: normal; font-weight: normal; letter=
-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-=
transform: none; white-space: normal; widows: auto; word-spacing: 0px; -web=
kit-text-size-adjust: auto; -webkit-text-stroke-width: 0px;" class=3D"" On 28/09/17 08:32, Yaniv Kaul wrote:<br
class=3D"" <blockquote
type=3D"cite" class=3D""><br class=3D"" <br class=3D"" On Wed,
Sep 27, 2017 at 10:59 PM, Ben Bradley <<a href=3D"mailto:listsbb=
@virtx.net" class=3D"">listsbb(a)virtx.net</a> <<a
href=3D"mailto:listsbb@=
virtx.net" class=3D"">mailto:listsbb@virtx.net</a>>>
wrote:<br class=
=3D"" <br class=3D"" Hi All<br
class=3D"" <br class=3D"" I'm looking to add a new host
to my oVirt lab installatio=
n.<br class=3D""
I'm going to share out some LVs from a separate
box over =
iSCSI and<br class=3D""
will hook the new host up to that.<br
class=3D"" I have
2 NICs on the storage host and 2 NICs on the new O=
virt host<br class=3D""
to dedicate to the iSCSI traffic.<br
class=3D"" I also
have 2 separate switches so I'm looking for redund=
ancy here.<br class=3D""
Both iSCSI host and oVirt host plugged into both
switches=
.<br class=3D"" <br class=3D"" If this was non-iSCSI traffic and
without oVirt I would c=
reate<br class=3D"" bonded
interfaces in active-backup mode and layer the VLA=
Ns on top<br class=3D""
of that.<br class=3D"" <br class=3D""
But for iSCSI traffic without oVirt involved I
wouldn't b=
other with<br class=3D""
a bond and just use multipath.<br
class=3D"" <br class=3D"" From scanning the oVirt
docs it looks like there is=
an option to<br class=3D""
have oVirt configure iSCSI multipathing.<br
class=3D"" <br class=3D"" <br class=3D"" Look for
iSCSI bonding - that's the feature you are looking for.<br class=
=3D"" </blockquote Thanks for the replies.<br class=3D"" By iSCSI bonding, do you mean the oVirt feature "iSCSI
multipathing&qu=
ot; as mentioned here
<a href=3D"https://www.ovirt.org/documentation/admin-guide/chap-Storage... c=
lass=3D""
https://www.ovirt.org/documentation/admin-guide/chap-Storage/</a> ?<br
clas=
s=3D"" Separate links seems to be the
consensus then. Since these are links dedica=
ted to iSCSI traffic, not shared. the ovirtmgmt bridge lives on top of an a=
ctive-backup bond on other NICs.<br class=3D"" Thanks,
Ben<br class=3D"" </blockquote <br style=3D"font-family: Helvetica; font-size: 12px;
font-style: normal; f=
ont-variant-caps: normal; font-weight: normal; letter-spacing: normal; text=
-align: start; text-indent: 0px; text-transform: none; white-space: normal;=
word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=3D"" <span style=3D"font-family: Helvetica; font-size: 12px;
font-style: normal;=
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; te=
xt-align: start; text-indent: 0px; text-transform: none; white-space: norma=
l; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display:=
inline !important;" class=3D"">And
an extra question about oVirt's iSCSI multipathing - should each path be a=
separate VLAN+subnet?</span><br style=3D"font-family: Helvetica;
font-=
size: 12px; font-style: normal; font-variant-caps: normal; font-weight: nor=
mal; letter-spacing: normal; text-align: start; text-indent: 0px; text-tran=
sform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-wi=
dth: 0px;" class=3D"" <span
style=3D"font-family: Helvetica; font-size: 12px; font-style: normal;=
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; te=
xt-align: start; text-indent: 0px; text-transform: none; white-space: norma=
l; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display:=
inline !important;" class=3D"">I
assume it should be separate VLANs for running separate physical fabrics i=
f desired.</span><br style=3D"font-family: Helvetica; font-size: 12px;
font=
-style: normal; font-variant-caps: normal; font-weight: normal; letter-spac=
ing: normal; text-align: start; text-indent: 0px; text-transform: none; whi=
te-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=
=3D"" <br style=3D"font-family:
Helvetica; font-size: 12px; font-style: normal; f=
ont-variant-caps: normal; font-weight: normal; letter-spacing: normal; text=
-align: start; text-indent: 0px; text-transform: none; white-space: normal;=
word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=3D"" <span style=3D"font-family: Helvetica; font-size: 12px;
font-style: normal;=
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; te=
xt-align: start; text-indent: 0px; text-transform: none; white-space: norma=
l; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display:=
inline !important;" class=3D"">Thanks,
Ben</span><br style=3D"font-family: Helvetica; font-size: 12px;
font-style=
: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: n=
ormal; text-align: start; text-indent: 0px; text-transform: none; white-spa=
ce: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;"
class=3D"" </div </blockquote
<div><br class=3D""
</div <div>Take a look at this
Ben:</div <div><a
href=3D"https://bugzilla.redhat.com/show_bug.cgi?id=3D1474904" clas=
s=3D"">https://bugzilla.redhat.com/show_bug.cgi?id=3D1474904... <div><br class=3D"" </div
<div>oVirt is a little bit different with iSCSI MPIO.</div <br class=3D""
<blockquote type=3D"cite" class=3D"" <div class=3D""
<blockquote type=3D"cite" style=3D"font-family: Helvetica;
font-size: 12px;=
font-style: normal; font-variant-caps: normal; font-weight: normal; letter=
-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-=
transform: none; white-space: normal; widows: auto; word-spacing: 0px; -web=
kit-text-size-adjust: auto; -webkit-text-stroke-width: 0px;" class=3D"" <blockquote type=3D"cite"
class=3D""> So what's the best/m=
ost-supported option for oVirt?<br class=3D""
Manually create active-backup bonds so oVirt just sees
a =
single<br class=3D""
storage link between host and storage?<br
class=3D"" Or
leave them as separate interfaces on each side and use=
oVirt's<br class=3D""
multipath/bonding?<br class=3D"" <br class=3D""
Also I quite like the idea of using IPv6 for the iSCSI
VL=
AN, purely<br class=3D""
down to the fact I could use link-local addressing and
no=
t have to<br class=3D""
worry about setting up static IPv4 addresses or DHCP.
Is =
IPv6 iSCSI<br class=3D""
supported by oVirt?<br class=3D"" <br class=3D"" <br
class=3D"" No, we do not. There has been some
work in the area[1], but I'm not sure it=
is complete.<br class=3D"" Y.<br
class=3D"" <br class=3D"" [1] <a
href=3D"https://gerrit.ovirt.org/#/q/status:merged+project:v...
#43;branch:master+topic:ipv6-iscsi-target-support" class=3D""
https://gerrit.ovirt.org/#/q/status:merged+project:vdsm+b...
er+topic:ipv6-iscsi-target-support</a><span
class=3D"Apple-converted-sp=
ace"> </span><br class=3D"" <br class=3D"" <br
class=3D""
Thanks, Ben<br class=3D""
_______________________________________________<br
class=
=3D"" Users
mailing list<br class=3D""
<a href=3D"mailto:Users@ovirt.org"
class=3D"">Users@ovirt=
.org</a> <<a href=3D"mailto:Users@ovirt.org"
class=3D"">mailto:Users@ovi=
rt.org</a>><br class=3D""
<a
href=3D"http://lists.ovirt.org/mailman/listinfo/users"=
class=3D"">http://lists.ovirt.org/mailman/listinfo/users<...
class=3D""=
<<a
href=3D"http://lists.ovirt.org/mailman/listinfo/us=
ers"
class=3D"">http://lists.ovirt.org/mailman/listinfo/users<...
cl=
ass=3D"" <br class=3D"" <br class=3D""
</blockquote
_______________________________________________<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"" </blockquote <br
style=3D"font-family: Helvetica; font-size: 12px; font-style: normal; f=
ont-variant-caps: normal; font-weight: normal; letter-spacing: normal; text=
-align: start; text-indent: 0px; text-transform: none; white-space: normal;=
word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=3D"" <span style=3D"font-family: Helvetica; font-size: 12px;
font-style: normal;=
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; te=
xt-align: start; text-indent: 0px; text-transform: none; white-space: norma=
l; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display:=
inline !important;"
class=3D"">___________________________________________=
____</span><br style=3D"font-family: Helvetica; font-size: 12px;
font-style=
: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: n=
ormal; text-align: start; text-indent: 0px; text-transform: none; white-spa=
ce: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;"
class=3D"" <span style=3D"font-family:
Helvetica; font-size: 12px; font-style: normal;=
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; te=
xt-align: start; text-indent: 0px; text-transform: none; white-space: norma=
l; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display:=
inline !important;" class=3D"">Users
mailing list</span><br style=3D"font-family: Helvetica; font-size: 12px;
f=
ont-style: normal; font-variant-caps: normal; font-weight: normal; letter-s=
pacing: normal; text-align: start; text-indent: 0px; text-transform: none; =
white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;" cl=
ass=3D"" <a
href=3D"mailto:Users@ovirt.org" style=3D"font-family: Helvetica; font-si=
ze: 12px; font-style: normal; font-variant-caps: normal; font-weight: norma=
l; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0=
px; text-transform: none; white-space: normal; widows: auto; word-spacing: =
0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px;" class=
=3D"">Users(a)ovirt.org</a><br style=3D"font-family: Helvetica;
font-size: 12=
px; font-style: normal; font-variant-caps: normal; font-weight: normal; let=
ter-spacing: normal; text-align: start; text-indent: 0px; text-transform: n=
one; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px=
;" class=3D"" <a
href=3D"http://lists.ovirt.org/mailman/listinfo/users" style=3D"font-fam=
ily: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: nor=
mal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align=
: start; text-indent: 0px; text-transform: none; white-space: normal; widow=
s: auto; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-st=
roke-width: 0px;"
class=3D"">http://lists.ovirt.org/mailman/listinfo/users<=
/a></div </blockquote </div <br
class=3D"" </body </html
--_000_03468DF4AA234FCC80074739E2D985D1ifufrjbr_--
2408
days inactive
2412
days old
8 comments
4 participants
participants (4)
-
Ben Bradley -
Nir Soffer -
Vinícius Ferrão -
Yaniv Kaul