| Target release | Lustre 2.13 |
|---|---|
| Epic | Link to related Jira epic or feature |
| Document status | |
| Document owner | |
| Designer | Amir Shehata |
| Developers | |
| QA | Lead tester |
|
| ID | Class | Version | Status | Description |
|---|---|---|---|---|
| cfg-095 | REQUIRED | 1.0 | ACCEPTED | DLC shall provide APIs to configure User Defined Selection Policy (UDSP) |
| cfg-100 | REQUIRED | 1.0 | ACCEPTED | UDSP shall be comprised of a set of rules. |
| cfg-105 | REQUIRED | 1.0 | ACCEPTED | Only one UDSP shall be added/removed/modified per configuration operation |
| cfg-110 | REQUIRED | 1.0 | ACCEPTED | UDSP shall allow rules which define network priorities |
| cfg-115 | REQUIRED | 1.0 | ACCEPTED | UDSP shall allow rules which define interface priorities |
| cfg-120 | REQUIRED | 1.0 | ACCEPTED | UDSP shall allow rules which define one local NID to one remote NID mapping (1:1). |
| cfg-125 | REQUIRED | 1.0 | ACCEPTED | UDSP shall allow rules which define mapping priority. |
| cfg-130 | REQUIRED | 1.0 | ACCEPTED | UDSP shall allow rules which define many local NIDs to many remote NIDs mapping (N:N). |
| cfg-135 | REQUIRED | 1.0 | ACCEPTED | UDSP shall allow rules which define many local NIDs to a one remote NID mapping (N:1). |
| cfg-140 | REQUIRED | 1.0 | ACCEPTED | UDSP shall allow rules which define one local NID to many remote NIDs mapping (1:N). |
| cfg-145 | REQUIRED | 1.0 | ACCEPTED | UDSP shall allow rules which define the number of messages that should be sent using one rule. This allows fine grained control over traffic distribution. |
| cfg-150 | REQUIRED | 1.0 | ACCEPTED | UDSP rules shall provide the option to define relative rule priority |
| cfg-155 | REQUIRED | 1.0 | ACCEPTED | If UDSP rule priority is not defined it defaults to highest priority |
| cfg-160 | REQUIRED | 1.0 | ACCEPTED | lnetctl utility shall provide a command line front end interface to configure UDSP by calling the DLC APIs mentioned in the above requirements |
| cfg-165 | REQUIRED | 1.0 | ACCEPTED | lnetctl utility shall accept and parse YAML configuration files specifying UDSP configuration |
Include any mockups, diagrams or visual designs relating to these requirements.
Below is a list of questions to be addressed as a result of this requirements document:
| Question | Outcome |
|---|---|
| (e.g. How we make users more aware of this feature?) | Communicate the decision reached |