[ https://issues.oasis-open.org/browse/TOSCA-137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sahdev Zala updated TOSCA-137:
-------------------------------
Affects Version/s: CSD04
(was: CSD03)
> DEFER - CSD03 - Need to address "optional" and "best can" on node requirements (constraints) for matching/resolution
> ---------------------------------------------------------------------------------------------------------------------
>
> Key: TOSCA-137
> URL: https://issues.oasis-open.org/browse/TOSCA-137
> Project: OASIS Topology and Orchestration Specification for Cloud Applications (TOSCA) TC
> Issue Type: Improvement
> Components: Profile-YAML
> Affects Versions: CSD04
> Reporter: Matthew Rutkowski
> Assignee: Derek Palma
>
> 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").
--
This message was sent by Atlassian JIRA
(v6.2.2#6258)
