[LU-11959] Improve handling of 'network' client mount option Created: 12/Feb/19 Updated: 23/Jan/23 |
|
| Status: | Open |
| Project: | Lustre |
| Component/s: | None |
| Affects Version/s: | Lustre 2.12.0 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major |
| Reporter: | Sebastien Buisson | Assignee: | Sebastien Buisson |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | patch | ||
| Issue Links: |
|
||||||||
| Severity: | 3 | ||||||||
| Rank (Obsolete): | 9223372036854775807 | ||||||||
| Description |
|
The 'network' client mount option enables to limit connections from the client to be on the specified network NID. At the moment, connection to the MGS is out of the scope of this option, which lets a Lustre client use a different LNet network for the mgc. And when used in a routed environment, the network specified as a restriction has to be the one defined on server side, which is conflicting with the definition given for the 'network' option. I will push patches to address these two points. |
| Comments |
| Comment by Gerrit Updater [ 12/Feb/19 ] |
|
Sebastien Buisson (sbuisson@ddn.com) uploaded a new patch: https://review.whamcloud.com/34231 |
| Comment by Gerrit Updater [ 12/Feb/19 ] |
|
Sebastien Buisson (sbuisson@ddn.com) uploaded a new patch: https://review.whamcloud.com/34232 |