[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] Updated: (TOSCA-29) Selection of Node Templates types
[ http://tools.oasis-open.org/issues/browse/TOSCA-29?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Derek Palma updated TOSCA-29: ----------------------------- Assignee: Derek Palma > Selection of Node Templates types > --------------------------------- > > Key: TOSCA-29 > URL: http://tools.oasis-open.org/issues/browse/TOSCA-29 > Project: OASIS Topology and Orchestration Specification for Cloud Applications (TOSCA) TC > Issue Type: Improvement > Reporter: Derek Palma > Assignee: Derek Palma > > In certain situations it is desirable to make the selection of the concrete type of a Node Template dependent on the final deployment context. This becomes apparent in selecting scaling/load balancing mechanisms where different clouds might provide varying but suitable implementations of the required functionality or possibly none, requiring the deployment of the components providing this functionality. A ServiceTemplate could represent these functions as well as an actual deployment of an implementation of these functions. > An abstract type (which never can itself be instantiated) could represent the required functionality. Subtypes could represent concrete implementations. A selection mechanism (based on requirements/capabilities constraints) could be used to determine the final NodeType that should be instantiated. A NodeTemplate with NodeType set to the abstract type could represent this scenario and trigger the necessary selection processing. -- 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]