Stephen Gallagher <[email protected]> writes: > 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. > > See > https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/Networking_Guide/sec-Understanding_the_Network_Teaming_Daemon_and_the_Runners.html > 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 supporting > hardware). > 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.
Thanks for the feedback! Broadcast seems to be fundamentally different from the remaining runners. Maybe we can have a checkbox for it. But why would you need to decide between performance and reliability? What's wrong with using all links all the time? I guess there is an answer to that, but would that mean that we need to flag certain links as "Use only as backup"? It's not a fundamental change in what the team does, but a change in the role of a port, no? _______________________________________________ cockpit-devel mailing list [email protected] https://lists.fedorahosted.org/admin/lists/[email protected]
