[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] Commented: (TOSCA-12) Set of Basic Node Types for Defining Topology Templates
[ http://tools.oasis-open.org/issues/browse/TOSCA-12?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=35395#action_35395 ]
Paul Lipton commented on TOSCA-12:
-----------------------------------
The TC discussed the runtime PaaS types and then Application types on 17 Oct 2013 (see full discussion in minutes posted to https://www.oasis-open.org/committees/document.php?document_id=51143&wg_abbrev=tosca). Edited discussion below:
[13:08] Krishna Raman (Scribe - Red Hat): Discussion about "Web Server" vs "Web Framework". Or distinguish "Web Server" vs "HTTP server"
[13:09] Krishna Raman (Scribe - Red Hat): php runs a module on httpd web server. Node.js runs as an application which happens to listen on port 80 and support websockets
[13:11] Krishna Raman (Scribe - Red Hat): It might be useful to distinguish between a SQL DB, No-SQL DB vs a Web-cache
[13:12] Krishna Raman (Scribe - Red Hat): Paul: Might need something like type on the DB. Should also consider adding Queues, etc. which all manage and store data
[13:12] Krishna Raman (Scribe - Red Hat): Paul Also might add query language and query language version
[13:13] Krishna Raman (Scribe - Red Hat): Paul: the work DBMS might be the wrong word here
[13:15] Krishna Raman (Scribe - Red Hat): Paul: perhaps name it information manager with a type
[13:15] Paul Lipton (co-chair) Web Conf: Need generic entity (above database). DBMS is not, IMHO, the right level. Call it something like InformationManager or something. Types needed (queue?, DBMS, whatever) or more specific types?
[13:16] Paul Lipton (co-chair) Web Conf: Many cloud use cases call for these sorts of InformationManagers (like queues). <<all prior comments of mine on this are co-chair hat off>>
[13:17] Krishna Raman (Scribe - Red Hat): Simon: Perhaps even information manager the level
[13:20] Paul Lipton (co-chair) Web Conf: Derek: Some of this tied to use cases loosely discussed in SC.
[13:20] Simon Moser (co-chair)1: -- discusssion about the granularity of the types - generic vs. more specific
[13:20] Paul Lipton (co-chair) Web Conf morphed into Paul Lipton (co-chair) co-scribe
[13:21] Paul Lipton (co-chair) co-scribe: Slide on software component:
[13:22] Paul Lipton (co-chair) co-scribe: General slide for deployable things.
[13:22] Paul Lipton (co-chair) co-scribe: Next two slides (webapplication) and database slide.
[13:23] Simon Moser (co-chair)1: pairing between webServer and WebApplicatin
[13:23] Paul Lipton (co-chair) co-scribe: Pairing of the two (software component) and app contained by it.
[13:23] Simon Moser (co-chair)1: and DBMS and Databas
[13:23] Stephane Maes (HP): if yes can we haveteh URL?
[13:25] Simon Moser (co-chair)1: dbcontent is separated, as clients dont connect a database, but to a specific schema
[13:28] Paul Lipton (co-chair) co-scribe: There are many other informationManagers (and cloud use cases of great importance). There needs to be a more abstract layer than DBMS, which is only one type of InformationManager -- thank Hadoop/queues, etc. that are very important in the cloud (co-chair hat off)
[13:31] Paul Lipton (co-chair) co-scribe: HOMEWORK TO ALL TC MEMBERS: 1) Think of InformationManager concept (Paul's co-chair hat off request) and 2) PLEASE study the proposal (we will talk about it for over an hour next week!)
> Set of Basic Node Types for Defining Topology Templates
> -------------------------------------------------------
>
> Key: TOSCA-12
> URL: http://tools.oasis-open.org/issues/browse/TOSCA-12
> Project: OASIS Topology and Orchestration Specification for Cloud Applications (TOSCA) TC
> Issue Type: Task
> Components: Primer , Spec
> Affects Versions: V1.1_CSD01
> Reporter: Frank Leymann
> Assignee: Derek Palma
> Fix For: V1.1_CSD01
>
>
> TOSCA provides a metamodel that allows users to specify their service templates. For this purpose, Node Types must be defined that are referenced from Node Templates of a Topology Template. It is expected that some particular Node Types will occur frequently (like a "DBMS" Node Type, an "OperatingSystem" Node Type etc). Providing a corresponding set of Node Types by the TOSCA TC will limit the burden of using TOSCA for specifying particular service templates. This in turn will increase the likelihood for broad acceptance of TOSCA in the industry.
> The issue at hand is to agree on a set of such basic Node Types and specify them using the TOSCA language. The corresponding specification should be an additional deliverable of the TOSCA TC. The set of basic Node Types should be "small", i.e. no attempt should be made to specify all Node Types needed to define most cloud applications. Instead, Node Types should be specified that are required by "typical" cloud applications today.
--
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]