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] (TOSCA-266) Creating an abstract or phantom node


Luca Gioppo created TOSCA-266:
---------------------------------

             Summary: Creating an abstract or phantom node
                 Key: TOSCA-266
                 URL: https://issues.oasis-open.org/browse/TOSCA-266
             Project: OASIS Topology and Orchestration Specification for Cloud Applications (TOSCA) TC
          Issue Type: New Feature
            Reporter: Luca Gioppo


In the standard we already have an abstract definition:
"Node Types might be declared as abstract, meaning that they cannot be instantiated. The purpose of such abstract Node Types is to provide common properties and behavior for re-use in specialized, derived Node Types. Node Types might also be declared as final, meaning that they cannot be derived by other Node Types"
This imply that in the topology we HAVE to substitute the abstract with a concrete implementation.
We need to manage in the topology nodes that are not "created" in the service, but are there to have a reference for relations like central system like monitoring system or backup server; those system are not installed but we need to tell to the orchestrator "you have to add something to the monitoring server".



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