[LU-7849] Need to purge "DLC" naming from code and user-visible areas Created: 04/Mar/16  Updated: 09/Jun/17

Status: Open
Project: Lustre
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Minor
Reporter: Christopher Morrone Assignee: Amir Shehata (Inactive)
Resolution: Unresolved Votes: 0
Labels: None

Severity: 3
Rank (Obsolete): 9223372036854775807

 Description   

We really need to purge the "DLC" and "Dynamic LNet Configuration" terms from the code and from user visible interfaces, and from documentation. "DLC" was a project to add new functionality, it should not be a name that ever gets embedded anywhere permanent.

For instance, the autoconf function named LN_CONFIG_DLC should not have any reference to "DLC". The check is whether libyaml exists, and that is all that fuction needs to concern itself with.

The --disable-dlc option should almost certainly have another name as well. From a user's standpoint, it would seem to primarily be about whether or not the "lnetctl" command gets built, so it might make a great deal more sense to name the option after lnetctl.

In any event, eventually lnet configuration will just by dynamic, and few users will not care that it wasn't in the past, and embedding the DLC project name everywhere will just be an anachronism.


Generated at Sat Feb 10 02:12:27 UTC 2024 using Jira 9.4.14#940014-sha1:734e6822bbf0d45eff9af51f82432957f73aa32c.