[LU-18884] make LWP setup based on IR instead of client config

• Type: Improvement
• Resolution: Unresolved
• Priority: Minor
• Severity: 3
• Assignee: Mikhail Pershin
• Reporter: Mikhail Pershin

Description

right now LWP setup is based on client config fetched from MGS. It scans 'mdc' entires and gets MDT servers connection info from it. This is not always possible though in future development considering LU-10359 and similar setups where all NID information can't be passed to client config and IR remains the only source of such information.

LWP setup can be based on IR only and don't depend on client config

 

Issue Links

• has to be done before: LU-10359 remove NIDs from config llogs

Comments

[Mikhail Pershin]

on further investigation the current approach is not enough to get rid all NIDs in config, DNE setup can't establish OSP devices without NIDs in client config as well and IR doesn't work too because OSP OBD doesn't exists when IR is being processed.

Possible solution can be a local NID table in MGC similar to one MGS has, which is updated along with IR config and can be used for NIDs lookup for particular target by its name, e.g. "lustre-OST0000".