You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »

Target releaseLustre 2.13
Epic
Document status
DRAFT
Document owner
DesignerAmir Shehata
Developers
QA

Scope

Problem Statement


Project Overview


Assumptions

Requirements

IDClassVersionStatusDescription
cfg-095REQUIRED1.0ACCEPTEDDLC shall provide APIs to configure User Defined Selection Policy (UDSP)
cfg-100REQUIRED1.0ACCEPTEDUDSP shall be comprised of a set of rules.
cfg-105REQUIRED1.0ACCEPTEDOnly one UDSP shall be added/removed/modified per configuration operation
cfg-110REQUIRED1.0ACCEPTEDUDSP shall allow rules which define network priorities
cfg-115REQUIRED1.0ACCEPTEDUDSP shall allow rules which define interface priorities
cfg-120REQUIRED1.0ACCEPTEDUDSP shall allow rules which define one local NID to one remote NID mapping (1:1).
cfg-125REQUIRED1.0ACCEPTEDUDSP shall allow rules which define mapping priority.
cfg-130REQUIRED1.0ACCEPTED

UDSP shall allow rules which define many local NIDs to many remote NIDs mapping (N:N).

cfg-135REQUIRED1.0ACCEPTED

UDSP shall allow rules which define many local NIDs to a one remote NID mapping (N:1).

cfg-140REQUIRED1.0ACCEPTED

UDSP shall allow rules which define one local NID to many remote NIDs mapping (1:N).

cfg-145REQUIRED1.0ACCEPTED

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-150REQUIRED1.0ACCEPTEDUDSP rules shall provide the option to define relative rule priority
cfg-155REQUIRED1.0ACCEPTED

If UDSP rule priority is not defined it defaults to highest priority

cfg-160REQUIRED1.0ACCEPTEDlnetctl utility shall provide a command line front end interface to configure UDSP by calling the DLC APIs mentioned in the above requirements
cfg-165REQUIRED1.0ACCEPTEDlnetctl utility shall accept and parse YAML configuration files specifying UDSP configuration

User interaction and design

Questions

Below is a list of questions to be addressed as a result of this requirements document:

QuestionOutcome

Not Doing

  • No labels