Primer Themes: Creating a Cloud App With TOSCA
description
Transcript of Primer Themes: Creating a Cloud App With TOSCA
Primer Themes:Creating a Cloud App With TOSCA
Gerd BreiterFrank Leymann
Thomas Spatzier
DEFINING A SERVICE TEMPLATE
Scenario:All required types are available, „only“ service template is to be specifiedThis is the “simplest case”
Appl
icati
on
Mod
elle
r
Import Types to Palett
DefineTopology
DefinePlans
X X
Defining a Service Template:The Application Modeler View
Application Modeler Role• Understand application to be managed in cloud
environment– Select required types
• Node Types, Relationship Types– Define application structure (aka topology)– Define management behavior (aka plans)
~+
~+
Define Topology
• Import domain types needed• Node Templates– Set Properties– Set cardinalities– Set properties of Requirements & Capabiliites
• Relationship Templates– Set Properties– Define Source and Target
DefineTopology
~ +
Subprocess Structure:Define Topology
DefineRelationship Templates
DefineNode
Templates
~
Define Your Plans
• Build Plan and Termination Plan incase of an imperative approach
• Management plans in any cases if more that deployment and decommissioning is required
DefinePlans
~ +
CREATING A CSAR
IT S
peci
alist
BuildCSAR
~Import
Artifacts
Creating a CSAR:The IT Specialist View
The IT Specialist Role• Get Service Template to create a CSAR for• Import artifact entities (artifact templates,
implementation artifacts, deployment artifacts,...)• Build the CSAR
+
GetService
Template
Build Your CSAR
• Define directory structure• Provide content for the directories• Update relative URIs in Artifact Templates
accordingly• Copy required .ste files to /Service-Template
directory• Provide TOSCA.meta file– Identify Entry Service Template
• Zip the directories
BuildCSAR
~ +
DEFINING DOMAIN TYPES AND ARTIFACTS
Vend
or DefineArtifacts~
Define Domain Types & Artifacts:The „Vendor“ View
Vendor Role• Get Generic Types• Define Domain/Vendor-specific Types• Provide artifacts for those types
+
GetGeneric Types
DefineDomain Types
~ +
Define Domain Types• Import generic types needed• Node Types
– Properties– Interfaces– Requirement Definitions– Capability Definitions– Usage of inheritance
• Relationship Types– Properties– Source/Target Interfaces– Valid Source/Target– Usage of inheritance
DefineDomain Types
~ +
Subprocess Structure:Define Domain Types
DefineRelationship
Type
DefineNode Type
~
• Artifact Templates– Set Properties (i.e. the invariant values of
metadata)• Associate artifacts with Artifact Templates– Specify inclusion/exclusion of files
• Define Node/Relationship Type Implementations– Set variant metadata as artifact specific content
DefineArtifacts
Define Artifacts
+
Subprocess Structure:Define Artifacts
DefineNode/Rel TypeImplementation
AssociateArtifacts
DefineArtifact
Template
Define a Composable Service Template
• Provide Boundary Definitions– Export corresponding definitions of elements of
the service template
Enable Service Template
Composition~ +
DEFINING GENERIC TYPES
Cros
s-Ve
ndor
DefineGeneric Types
~
Defining Generic Types:The Cross-Vendor View
• Domain-independent types are defined– E.g. by a vendor consortium– E.g. by a standards body– ...
+
Define Generic Types• Requirement Types• Capability Types• Artifact Types– Invariant metadata (in Artifact Types/Templates)– Variant metadata (used in Node/Relationship Type
Implementations)– Decide, which metadata is provided in Artifact
Types/Templates, Implementations vs in .meta file
• Eventually, corresponding ontologies will result from that
DefineGeneric Types
~ +
Subprocess Structure:Define Generic Types
DefineRequirement
Type
DefineCapability Type
DefineArtifact Type
~
SUMMARY
Scenario:You start on a green field, you must define everything for your cloud application by yourselfThis is the “most difficult case”
Clou
d Ap
plic
ation
Spe
cific
ation
Pro
cess
Appl
icati
on
Mod
elle
rIT
Spe
cial
istDo
mai
n Ex
pert
DefineGeneric Types
~Define
Domain Types~
DefineTopology
~
DefinePlans
~
BuildCSAR
~Define
Artifacts~
X X
Steps Towards a Cloud Application
++
+
+
+
+
END OF DOCUMENT