[OASIS Issue Tracker] Updated: (TOSCA-61) Section: 2: Deploying a New Virtual Machine

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

     [ http://tools.oasis-open.org/issues/browse/TOSCA-61?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Paul Lipton  updated TOSCA-61:
------------------------------

    Description: 
The TC approved this initial approach:

a.	Application Developers Role
•	You took that role in the chapters before
•	Expert in application structure and "global" management of an application
•	The concept of Plans
•	Sketch difference between imperative approach and declarative approach
b.	Type Developers Role (Domain Expert Role and Vendor Point of View)
•	Expert in application componentry and "local" management of individual components  Node Types
•	Expert in establishing connections between components  Relationship Types
•	Providing reusable service templates  Boundary Definitions  Abstract Node Types
•	Vendor does above to provide types that reflect its products
c.	Artifact Developers Role (IT Specialist Role and Vendor Point of View)
•	Expert in code artifacts  Implementation artifacts and Deployment artifacts
•	In charge of Artifact Templates and Node/Relationship Type Implementations
•	Vendor packages its node types and relationship types into CSAR that customers can use to define its own cloud apps




  was:
The TC reviewed this initial approach (see minutes of 10/11): 

a.	Explain how many people's first migration step to the cloud will be to snapshot an existing machine and move it to a Cloud. This scenario's main purpose is to introduce the basic concepts of NodeTypes, Svc Templates and CSAR files.
b.	Explain the basic NodeType(s) needed to support this scenario
•	Hopefully just one NodeType is needed
c.	Create the service template xml file
d.	Create the CSAR file


       Assignee: Frank Leymann 

> Section: 2: Deploying a New Virtual Machine
> -------------------------------------------
>
>                 Key: TOSCA-61
>                 URL: http://tools.oasis-open.org/issues/browse/TOSCA-61
>             Project: OASIS Topology and Orchestration Specification for Cloud Applications (TOSCA) TC
>          Issue Type: Task
>          Components: Primer 
>            Reporter: Paul Lipton 
>            Assignee: Frank Leymann 
>
> The TC approved this initial approach:
> a.	Application Developers Role
> •	You took that role in the chapters before
> •	Expert in application structure and "global" management of an application
> •	The concept of Plans
> •	Sketch difference between imperative approach and declarative approach
> b.	Type Developers Role (Domain Expert Role and Vendor Point of View)
> •	Expert in application componentry and "local" management of individual components  Node Types
> •	Expert in establishing connections between components  Relationship Types
> •	Providing reusable service templates  Boundary Definitions  Abstract Node Types
> •	Vendor does above to provide types that reflect its products
> c.	Artifact Developers Role (IT Specialist Role and Vendor Point of View)
> •	Expert in code artifacts  Implementation artifacts and Deployment artifacts
> •	In charge of Artifact Templates and Node/Relationship Type Implementations
> •	Vendor packages its node types and relationship types into CSAR that customers can use to define its own cloud apps

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