OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

tosca message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


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


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

                 Key: TOSCA-137
                 URL: http://tools.oasis-open.org/issues/browse/TOSCA-137
             Project: OASIS Topology and Orchestration Specification for Cloud Applications (TOSCA) TC
          Issue Type: Improvement
          Components: Profile-YAML
    Affects Versions: CSD1
            Reporter: Matthew Rutkowski 
            Assignee: Matthew Rutkowski 
             Fix For: CSD1


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 is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]