DEFER - CSD04 - Need to address "optional" and "best can" on node requirements (constraints) for matching/resolution

    • 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").

            Assignee:
            Derek Palma (Inactive)
            Reporter:
            Matthew Rutkowski (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: