tosca message

Subject: [OASIS Issue Tracker] Created: (TOSCA-71) Chapter 10: Providing Generic Types

From: OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>
To: tosca@lists.oasis-open.org
Date: Wed, 31 Oct 2012 18:18:24 -0400 (EDT)

Chapter 10: Providing Generic Types
-----------------------------------

                 Key: TOSCA-71
                 URL: http://tools.oasis-open.org/issues/browse/TOSCA-71
             Project: OASIS Topology and Orchestration Specification for Cloud Applications (TOSCA) TC
          Issue Type: Task
          Components: Primer 
            Reporter: Paul Lipton 


The TC tentatively approved this  approach on 10/25:

a.	Artifact Types 
•	The kind of executables and their invariant properties/metadata
•	Variant metadata that need to be described in body of artifact-specific content of corresponding element or in corresponding block of TOSCA.meta file
b.	Requirements and Capabilities
•	Distinguish between quality of services (scalability, availability, pricing,...) and dependencies  QoS become Policies, dependencies become Requirements and Capabilities
c.	Explain that this is done "once and forever" by vendor consortium  primer will define samples (i.e. non-normative) for the types SugarCRM requires


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