-
Type:
Task
-
Status: Closed
-
Priority:
Major
-
Resolution: Fixed
-
Component/s: Ballot request
-
Labels:None
-
Environment:
TOSCA
Submitted on Tuesday, September 26, 2017 - 20:52
Submitted by user:
Submitted values are:
Your name: Paul Lipton
TC name: Paul Lipton
TC email address: paul.lipton@ca.com
Title: TOSCA Simple Profile in YAML Version 1.1
Committee Specification URI:
http://docs.oasis-open.org/tosca/TOSCA-Simple-Profile-YAML/v1.1/cs01/TOSCA-Simple-Profile-YAML-v1.1-cs01.pdf
Committee Specification editable source URI(s):
http://docs.oasis-open.org/tosca/TOSCA-Simple-Profile-YAML/v1.1/cs01/TOSCA-Simple-Profile-YAML-v1.1-cs01.docx
Certification by the TC that all schema and XML instances are well-formed and
that expressions are valid: We do not certify
Clear English-language summary of the specification: The TOSCA metamodel uses
the concept of service templates to describe cloud workloads as a topology
template, which is a graph of node templates modeling the components a
workload
is made up of and as relationship templates modeling the relations between
those
components. TOSCA further provides a type system of node types to describe
the
possible building blocks for constructing a service template, as well as
relationship type to describe possible kinds of relations. Both node and
relationship types may define lifecycle operations to implement the behavior
an
orchestration engine can invoke when instantiating a service template. For
example, a node type for some software product might provide a ‘create’
operation to handle the creation of an instance of a component at runtime, or
a
‘start’ or ‘stop’ operation to handle a start or stop event triggered
by
an orchestration engine. Those lifecycle operations are backed by
implementation
artifacts such as scripts or Chef recipes that implement the actual behavior.
Relationship of this specification to similar work: TOSCA provides a
machine-readable description that could provide value not just to cloud
computing in general, but potentially other platforms and domains such as
IoT.
There is no direct overlap between TOSCA and other specifications, but TOSCA
provides essential capabilities, definitions, and other abstractions to
related
domains such as NFV.
-Statements of Use-
Link to Statement of Use #1:
https://www.oasis-open.org/apps/org/workgroup/tosca/email/archives/201708/msg00061.html
Link to Statement of Use #2:
https://www.oasis-open.org/apps/org/workgroup/tosca/email/archives/201708/msg00062.html
Link to Statement of Use #3:
https://www.oasis-open.org/apps/org/workgroup/tosca/email/archives/201708/msg00034.html
Additional Statements of Use:
https://www.oasis-open.org/apps/org/workgroup/tosca/email/archives/201708/msg00070.html
https://www.oasis-open.org/apps/org/workgroup/tosca/email/archives/201708/msg00025.html
https://www.oasis-open.org/apps/org/workgroup/tosca/email/archives/201708/msg00023.html
https://www.oasis-open.org/apps/org/workgroup/tosca/email/archives/201708/msg00019.html
-Public Reviews-
First public review announcement URI: On file with TCAdmin
through previous requests and postings
Comment resolution log: On file with TCAdmin through previous
requests and postings
Additional public review announcement URIs:
Public review announcement was 02 posted by TC Admin. Here is the
TC approval for comment resolution log for second PR:
Additional comment resolution log URIs:
Approval link:
https://www.oasis-open.org/apps/org/workgroup/tosca/download.php/61493/TOSCA%20TC%20Minutes%202017-08-31.docx
Earlier attempts to standardize: No
Sources of explanatory information:
Notes:
The results of this submission may be viewed at:
http://tools.oasis-open.org/issues/browse/TCADMIN