[LU-11959] Improve handling of 'network' client mount option

• Type: Bug
• Resolution: Unresolved
• Priority: Major
• Affects Version/s: Lustre 2.12.0
• Labels: patch
• Severity: 3
• Assignee: Sebastien Buisson
• Reporter: Sebastien Buisson

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.

Issue Links

• is duplicated by: LU-11977 [mount.lustre] Semantics of option 'network' in routed clients

Comments

[Gerrit Updater]

Sebastien Buisson ([e-mail]) uploaded a new patch: https://review.whamcloud.com/34232
Subject: LU-11959 obd: network restrict with routers
Project: fs/lustre-release
Branch: master
Current Patch Set: 1
Commit: 2456d0e31fbd208edc267c02c3f376cb748560e3

[Gerrit Updater]

Sebastien Buisson ([e-mail]) uploaded a new patch: https://review.whamcloud.com/34231
Subject: LU-11959 obd: restrict network for mgc, failnode/servicenode
Project: fs/lustre-release
Branch: master
Current Patch Set: 1
Commit: b6478646a7e6032df89a7d51fb6d05ee5e835389