On 06/16/2016 03:39 AM, Marius Vollmer wrote:
so I had a first go at adding network teaming support to Cockpit:
The current code doesn't expose _any_ configuration settings for a team,
because the defaults are perfect!
At least, that's my working assumption right now. :-)
If you use teams, what settings to do you have to change? Can you see a
way to improve teamd itself so that you could just use the default
Well, at minimum it will need to be able to select the teamd runner. This
fundamentally changes how the team behaves and what it should do when one or
more interfaces go down.
for details on the different runners.
This is important because the runner in use will definitely depend on the
use-case. For example, if the most important thing is maximizing throughput (but
with a higher load on the machine), you will probably want either the
'loadbalance' or 'lacp' runner (the 'lacp' runner requires
If your use-case is to use teaming purely for reliability in the face of
outages, then 'activebackup' where the interfaces each travel on different paths
from the others is probably your preference. 'roundrobin' is lower overhead than
'loadbalance' but since it doesn't measure anything can end up in situations
where one interface is handling far more of the load than others.
Unfortunately, this is not a decision that we can realistically make
automatically for the user.