[OASIS Issue Tracker] (TOSCA-137) DEFER - CSD03 - Need to address "optional" and "best can" on node requirements (constraints) for matching/resolution

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

    [ https://issues.oasis-open.org/browse/TOSCA-137?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=59551#comment-59551 ] 

Sahdev Zala  commented on TOSCA-137:
------------------------------------

Per discussion on 05/07/15 TOSCA TC Special 4 Hour Meeting:

(Luc) We have 'OCCURENCES' keyword now to make requirement optional. 
(Luc) Recommendation:  the better way to is to go through other option that can be done through some policy. So the recommendation is, dig into policy to handle it better way and not through semantic changes in the base spec.

> 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)