Re: [systemd-devel] is there a plan for NIC teaming support ?
Am 2015-03-12 15:29, schrieb Dax Kelson: > Could you please explain (or link to description of) what teamd can > do that bonding cannot? Table, info, benchmarks here: http://rhelblog.redhat.com/2014/06/23/team-driver/ [2] On a side note, out of curiosity: does teamd support ARP monitoring if the interface is added to a bridge? The bonding driver doesn't and this is something that always bothered me. Christian ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] is there a plan for NIC teaming support ?
On Mar 12, 2015 7:21 AM, "Andrei Borzenkov" wrote: > > > Could you please explain (or link to description of) what teamd can do > that bonding cannot? Table, info, benchmarks here: http://rhelblog.redhat.com/2014/06/23/team-driver/ ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] is there a plan for NIC teaming support ?
On Thu, Mar 12, 2015 at 1:08 PM, Michal Sekletar wrote: > On Thu, Mar 05, 2015 at 05:41:55AM +0100, Branko wrote: >> I have a need to put my NICs in "RAID0" so to speak, but according >> to materials I have found on net I can't use NIC bonding driver >> because I would need LACP (IEEE whatever) aware L2 switch, so I was >> refered to teaming driver, which should be ( if those folks is to be >> believed) replacing bond driver in future. >> >> Since systemd doesn't support teaming ( teaming module + libeteam), >> I had to scotchstape it together under systemd and it was major >> PITA. >> >> libteam doesn't seem to complicated to be included as a module in >> systemd, which should take away most of the headaches... > > I started looking into providing teaming support in networkd. What I am > currently able to do (not much btw) is to create team netdev and > enslave interfaces. Everything else is done via GeNetlink and sd-rtnl doesn't > support that. Also even the most basic balance-rr mode doesn't work without > teamd instance running. Thus naturally I wanted to use libteam, problem is > that > still quite a lot of logic is implemented in teamd daemon and not in > library. > Could you please explain (or link to description of) what teamd can do that bonding cannot? ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] is there a plan for NIC teaming support ?
On Thu, Mar 05, 2015 at 05:41:55AM +0100, Branko wrote: > I have a need to put my NICs in "RAID0" so to speak, but according > to materials I have found on net I can't use NIC bonding driver > because I would need LACP (IEEE whatever) aware L2 switch, so I was > refered to teaming driver, which should be ( if those folks is to be > believed) replacing bond driver in future. > > Since systemd doesn't support teaming ( teaming module + libeteam), > I had to scotchstape it together under systemd and it was major > PITA. > > libteam doesn't seem to complicated to be included as a module in > systemd, which should take away most of the headaches... I started looking into providing teaming support in networkd. What I am currently able to do (not much btw) is to create team netdev and enslave interfaces. Everything else is done via GeNetlink and sd-rtnl doesn't support that. Also even the most basic balance-rr mode doesn't work without teamd instance running. Thus naturally I wanted to use libteam, problem is that still quite a lot of logic is implemented in teamd daemon and not in library. I envision this to work in a following way. networkd will create netdev and enslave interfaces, then it will call systemd dbus API to create instance of teamd for the team device. networkd will then communicate with teamd instance over dbus. Problem I am facing here is not very well designed teamd dbus interface, i.e. you have to pass json config string as parameter. I am not sure we want to get into business of stamping out some json to variable and then passing that string to teamd. It would be much nicer to have v2 of teamd dbus interface. I had a brief discussion about it with teamd maintainer and as always patches are welcome. Michal > > > > ___ > systemd-devel mailing list > systemd-devel@lists.freedesktop.org > http://lists.freedesktop.org/mailman/listinfo/systemd-devel ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] is there a plan for NIC teaming support ?
2015-03-05 5:41 GMT+01:00 Branko : > I have a need to put my NICs in "RAID0" so to speak, but according to > materials I have found on net I can't use NIC bonding driver because I would > need LACP (IEEE whatever) aware L2 switch, so I was refered to teaming > driver, which should be ( if those folks is to be believed) replacing bond > driver in future. > > Since systemd doesn't support teaming ( teaming module + libeteam), I had to > scotchstape it together under systemd and it was major PITA. > > libteam doesn't seem to complicated to be included as a module in systemd, > which should take away most of the headaches... AFAIK (and according to wikipedia) you can also use the bonding driver without LACP. https://en.wikipedia.org/wiki/Link_aggregation#Driver_modes and I don't think the teaming driver can do more without LACP than the bonding driver can. Simon ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] is there a plan for NIC teaming support ?
Hi Branko, We do intend to support teaming, but it is still work in progress. Michal might be able to say more about it. Cheers, Tom On Thu, Mar 5, 2015 at 5:41 AM, Branko wrote: > I have a need to put my NICs in "RAID0" so to speak, but according to > materials I have found on net I can't use NIC bonding driver because I would > need LACP (IEEE whatever) aware L2 switch, so I was refered to teaming > driver, which should be ( if those folks is to be believed) replacing bond > driver in future. > > Since systemd doesn't support teaming ( teaming module + libeteam), I had to > scotchstape it together under systemd and it was major PITA. > > libteam doesn't seem to complicated to be included as a module in systemd, > which should take away most of the headaches... > > > > ___ > systemd-devel mailing list > systemd-devel@lists.freedesktop.org > http://lists.freedesktop.org/mailman/listinfo/systemd-devel ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] is there a plan for NIC teaming support ?
2015-03-06 7:09 GMT+03:00 Andrei Borzenkov : > Linux bonding driver supports LACP (mode 4) As i understand user can't use LACP because it switches does not support it. -- Vasiliy Tolstov, e-mail: v.tols...@selfip.ru jabber: v...@selfip.ru ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] is there a plan for NIC teaming support ?
В Thu, 05 Mar 2015 05:41:55 +0100 Branko пишет: > I have a need to put my NICs in "RAID0" so to speak, but according to > materials I have found on net I can't use NIC bonding driver because I > would need LACP (IEEE whatever) aware L2 switch, so I was refered to > teaming driver, which should be ( if those folks is to be believed) > replacing bond driver in future. > Linux bonding driver supports LACP (mode 4) > Since systemd doesn't support teaming ( teaming module + libeteam), I > had to scotchstape it together under systemd and it was major PITA. > > libteam doesn't seem to complicated to be included as a module in > systemd, which should take away most of the headaches... > > > > ___ > systemd-devel mailing list > systemd-devel@lists.freedesktop.org > http://lists.freedesktop.org/mailman/listinfo/systemd-devel ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
