-
Type: Improvement
-
Status: Deferred
-
Priority: Major
-
Resolution: Unresolved
-
Affects Version/s: CSD04
-
Fix Version/s: None
-
Component/s: Profile-YAML
-
Labels:None
In order to allow for flexibility when orchestrator "match" one node's requirements to another node's capabilities/features (fulfillment) we need to allow for a syntax/grammar that allows each requirement to be labeled "optional" or "best can" ("best match").