-
Type:
Improvement
-
Resolution: Unresolved
-
Priority:
Major
-
None
-
Affects Version/s: CSD04
-
Component/s: Profile-YAML
-
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").