[LU-13642] lnetctl: Allow IP specification Created: 05/Jun/20 Updated: 06/Jan/24 |
|
| Status: | Open |
| Project: | Lustre |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Minor |
| Reporter: | Amir Shehata (Inactive) | Assignee: | Frank Sehr |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Issue Links: |
|
||||||||
| Severity: | 3 | ||||||||
| Rank (Obsolete): | 9223372036854775807 | ||||||||
| 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. |
| Comments |
| Comment by Frank Sehr [ 08/Apr/22 ] |
|
I started to look into it. |
| Comment by Frank Sehr [ 15/Apr/22 ] |
|
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. |
| Comment by James A Simmons [ 06/May/22 ] |
|
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. |
| Comment by Frank Sehr [ 13/Jun/22 ] |
|
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 |
| Comment by Gerrit Updater [ 16/Jun/22 ] |
|
"Frank Sehr <fsehr@whamcloud.com>" uploaded a new patch: https://review.whamcloud.com/47660 |
| Comment by Gerrit Updater [ 23/Aug/22 ] |
|
"Frank Sehr <fsehr@whamcloud.com>" uploaded a new patch: https://review.whamcloud.com/48300 |
| Comment by Gerrit Updater [ 30/Nov/22 ] |
|
"Frank Sehr <fsehr@whamcloud.com>" uploaded a new patch: https://review.whamcloud.com/c/fs/lustre-release/+/49281 |
| Comment by Gerrit Updater [ 28/Dec/22 ] |
|
"James Simmons <jsimmons@infradead.org>" uploaded a new patch: https://review.whamcloud.com/c/fs/lustre-release/+/49525 |
| Comment by Gerrit Updater [ 07/Jan/23 ] |
|
"Oleg Drokin <green@whamcloud.com>" merged in patch https://review.whamcloud.com/c/fs/lustre-release/+/47660/ |
| Comment by Gerrit Updater [ 19/Jan/23 ] |
|
"Oleg Drokin <green@whamcloud.com>" merged in patch https://review.whamcloud.com/c/fs/lustre-release/+/49525/ |
| Comment by Gerrit Updater [ 06/Jan/24 ] |
|
"James Simmons <jsimmons@infradead.org>" uploaded a new patch: https://review.whamcloud.com/c/fs/lustre-release/+/53605 |