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] Commented: (TOSCA-35) Question on the definition of "Topology", logically or physically?


    [ http://tools.oasis-open.org/issues/browse/TOSCA-35?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=30705#action_30705 ] 

Thomas Spatzier  commented on TOSCA-35:
---------------------------------------

Good use case :-)

You can have multiple nodes in the topology that are instantiated using the same artifact, i.e. it is not mandated to have an own artifact for each node. In you case, I could imagine that you have just one deployment artifact (the VM image) at the "VirtualMachine" node, and this is the only things that needs to be deployed - it already contains the software. Still in the topology model, we would have nodes representing Tomcat and MySQL to be able to manage it (i.e. first of all, have the information about what is hosted on the VM, and secondly for performing post-deployment management).

Does that make sense?

> Question on the definition of "Topology", logically or physically?
> ------------------------------------------------------------------
>
>                 Key: TOSCA-35
>                 URL: http://tools.oasis-open.org/issues/browse/TOSCA-35
>             Project: OASIS Topology and Orchestration Specification for Cloud Applications (TOSCA) TC
>          Issue Type: Task
>          Components: Spec
>            Reporter: Paul Zhang
>            Priority: Minor
>
> As defined in the specification, a deployment artifact represents the executable for materializing instances of a node. However, the definition cannot be applied to the following cases in which two logically separated nodes are instantiated by one deployment artifact. 
> A web service supported by an appserver and a DB server is developed for small- and medium-sized enterprises. Since it is a very small web application, the application server and the DB server can be hosted on one virtual machine. Therefore, one virtual machine (VM) image installing Linux OS, Tomcat and MySQL can be used to deploy the appserver and the DB server. However, developers have to define two node types in TOSCA for the appserver and DB server respectively, since they are logically separated two nodes. But these two nodes reference the same deployment artifact. The artifact should be imported for just once, and then both nodes are instantiated.
> My question is: is it necessary to define several node types which are logically separated but are physically instantiated by one deployment artifact? Or just define one node type to include all?

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