On Thu, Sep 3, 2020 at 3:51 PM Fernando Fernandez Mancera
<ferferna(a)redhat.com> wrote:
Hello everyone,
After discussing the inclusive language topic with the core Nmstate
team and listening to the NetworkManager team suggestions, we have
decided to go to use of the word "ports" for the API in replacement of
"slaves" as this is the only occurrence that needs to be changed in
the public API. This decision has been taken because VLAN is already
using "parent/child" and it could be a port of a bridge so it will
cause confusion.
The idea is to use "port" because team and linux bridge interfaces are
using it currently, too. The change will only be needed on bond and
ovs-bridge interfaces. On the API there is no mention of "master".
Therefore, no change is needed on that.
On the internal code, “master” will be replaced with “controller”.
The plan action is:
1. Add the new words to the API and mark as deprecated the old ones.
That means the users will be able to use the old one but they are
going to get a warning.
2. Replace the words in the internal code.
3. In the future, we are going to remove the old words. There is not a
date, yet, but please move to the new terms now..
4. If there is any agreement/standard in the future, we are going to
consider adopting the proposed new terms.
Thank you for the hard work and your interest in discussing this. We
really appreciate all your different perspectives and we can continue
this discussion on the kernel or IEEE/IETF.
Well. That was an unfortunate decision from a bonding driver point of
view. As I thought I'd previously mentioned, 'port' is already used
quite extensively in the bonding driver's 802.3ad/lacp code.
--
Jarod Wilson
jarod(a)redhat.com