[LU-13642] lnetctl: Allow IP specification

• Type: Bug
• Resolution: Unresolved
• Priority: Minor
• Severity: 3
• Assignee: Frank Sehr
• Reporter: Amir Shehata (Inactive)

Description

Allow adding network interfaces with specific IP addresses. It is possible that an interface can have multiple IP addresses assigned to it. Since the IP address is explicitly used to describe an LNet NID, we should allow specifying network interfaces via their IP addresses. Linux routing can route packets based on their source IP addresses differently. It is potentially possible that routing can be setup such that Lustre traffic can be routed different from other application traffic, even though both are originating from the same interface.

Issue Links

• is related to: LU-17967 Configuring an o2ib NI using lnetctl net add --nid causes memory leak
• is related to: LU-17914 lnetctl net set command issues false error
• is related to: LU-13625 socklnd can select the wrong IP address to bind socket to
• is related to: LU-18417 Finish IPv6 support
• is related to: LU-10391 LNET: Support IPv6

Comments

[Gerrit Updater]

"James Simmons <[e-mail]>" uploaded a new patch: https://review.whamcloud.com/c/fs/lustre-release/+/53605
Subject: LU-13642 lnet: Allow dynamic IP specification
Project: fs/lustre-release
Branch: master
Current Patch Set: 1
Commit: b16477bb1d7aa3abe4215d862c034b6b2f855c9f

[Gerrit Updater]

"Oleg Drokin <[e-mail]>" merged in patch https://review.whamcloud.com/c/fs/lustre-release/+/49525/
Subject: LU-13642 lnet: modify lnet_inetdev to work with large NIDS
Project: fs/lustre-release
Branch: master
Current Patch Set:
Commit: 0b406c91d175b6cdbdf472b70a37e618cd66a72d

[Gerrit Updater]

"Oleg Drokin <[e-mail]>" merged in patch https://review.whamcloud.com/c/fs/lustre-release/+/47660/
Subject: LU-13642 lnet: Allow IP specification
Project: fs/lustre-release
Branch: master
Current Patch Set:
Commit: 14cdcd61985aa02097791ff7a8173c2e62030697

[Gerrit Updater]

"James Simmons <[e-mail]>" uploaded a new patch: https://review.whamcloud.com/c/fs/lustre-release/+/49525
Subject: LU-13642 lnet: modify lnet_inetdev to work with large NIDS
Project: fs/lustre-release
Branch: master
Current Patch Set: 1
Commit: 29189e13a53cd2544d1e14942011f3b37c2e0277

[Gerrit Updater]

"Frank Sehr <[e-mail]>" uploaded a new patch: https://review.whamcloud.com/c/fs/lustre-release/+/49281
Subject: LU-13642 lnet: Allow static IP specification
Project: fs/lustre-release
Branch: master
Current Patch Set: 1
Commit: 65c7faa92d9cec6028b623ff5fb3c659cfb74c6b

[Gerrit Updater]

"Frank Sehr <[e-mail]>" uploaded a new patch: https://review.whamcloud.com/48300
Subject: LU-13642 lnet: Allow IP specification
Project: fs/lustre-release
Branch: master
Current Patch Set: 1
Commit: 2a70b25550a0fb370b81b247e7d2ad74e3489de9

[Gerrit Updater]

"Frank Sehr <[e-mail]>" uploaded a new patch: https://review.whamcloud.com/47660
Subject: LU-13642 lnet: Allow IP specification
Project: fs/lustre-release
Branch: master
Current Patch Set: 1
Commit: 2250cf8ac13789fa6c15a4160d6e8d249e3d962b

[Frank Sehr]

I will soon add the patches. Please see  IP specification in LNet for more info

https://wiki.whamcloud.com/display/LNet/IP+specification+in+LNet

[James A Simmons]

Note much work is being done for 2.16 to support IPv6. I have a patch that updates lnetctl to use netlink for configuration. I will push in the next few weeks. We can add this work on top of that patch.

[Frank Sehr]

After some consideration and to keep a the syntax consistent between static and dynamic configuration the interface (–if flag) will be extended by the ip address. The format will be interface@ipaddress. The syntax will be backward compatible, no changes are necessary. The following combinations will be possible --if interface, --if interface@ipaddress or --if @ipaddress, (the first found interface will be chosen). The additional flag --ip to the "lnetctl net add" command to specify the ip address  will not be used. The ip address is set in the LNet NID and passed through the ioctl call to the ksocklnd kernel module. The module is enumerating the interfaces, but ignores  the ip address in the LNet NID. I am currently changing the behaviour to consider the ip address in the LNet NID in the choice of the interface. The default behaviour is maintained in case no IP address is found. Which means it picks the first available interface entry that corresponds to the specified physical interface. 

[Frank Sehr]

I started to look into it.