[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] (TOSCA-137) DEFER - CSD03 - Need to address "optional" and "best can" on node requirements (constraints) for matching/resolution
[ https://issues.oasis-open.org/browse/TOSCA-137?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=52577#comment-52577 ] Matthew Rutkowski commented on TOSCA-137: ------------------------------------------ TOSCA TC approve deferment of this issue at the 2014-11-20 meeting. See https://www.oasis-open.org/apps/org/workgroup/tosca/download.php/54595/TOSCA%20Minutes%202014-11-20.docx > 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: CSD03 > 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)
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]