topology and orchestration specification for cloud...

Download Topology and Orchestration Specification for Cloud ...docs.oasis-open.org/tosca/tosca-primer/v1.0/tosca-primer...آ 

Post on 13-Apr-2020

1 views

Category:

Documents

0 download

Embed Size (px)

TRANSCRIPT

Topology and Orchestration Specification for Cloud Applications (TOSCA) Primer Version 1.0

This is a Non-Standards Track Work Product.

The patent provisions of the OASIS IPR Policy do not apply.

Topology and Orchestration Specification for Cloud Applications (TOSCA) Primer Version 1.0

Committee Note Draft 01 31 January 2013

Specification URIs

This version:

http://docs.oasis-open.org/tosca/tosca-primer/v1.0/cnd01/tosca-primer-v1.0-cnd01.doc (Authoritative)

http://docs.oasis-open.org/tosca/tosca-primer/v1.0/cnd01/tosca-primer-v1.0-cnd01.html

http://docs.oasis-open.org/tosca/tosca-primer/v1.0/cnd01/tosca-primer-v1.0-cnd01.pdf

Previous version:

N/A

Latest version:

http://docs.oasis-open.org/tosca/tosca-primer/v1.0/tosca-primer-v1.0.doc (Authoritative)

http://docs.oasis-open.org/tosca/tosca-primer/v1.0/tosca-primer-v1.0.html

http://docs.oasis-open.org/tosca/tosca-primer/v1.0/tosca-primer-v1.0.pdf

Technical Committee:

OASIS Topology and Orchestration Specification for Cloud Applications (TOSCA) TC

Chairs:

Paul Lipton (paul.lipton@ca.com), CA Technologies

Simon Moser (smoser@de.ibm.com), IBM

Editors:

Frank Leymann (Frank.Leymann@informatik.uni-stuttgart.de), IBM

Matt Rutkowski (mrutkows@us.ibm.com), IBM

Adolf Hohl (Adolf.Hohl@netapp.com), NetApp

Marvin Waschke (marvin.waschke@ca.com), CA Technologies

Paul Zhang (paul.zhangyi@huawei.com), Huawei

Related work:

This document is related to:

· Topology and Orchestration Specification for Cloud Applications Version 1.0. Latest version. http://docs.oasis-open.org/tosca/TOSCA/v1.0/TOSCA-v1.0.html.

Abstract:

This document provides an introduction to the Topology and Orchestration Specification for Cloud Applications (TOSCA).

Status:

This document was last revised or approved by the OASIS Topology and Orchestration Specification for Cloud Applications (TOSCA) TC on the above date. The level of approval is also listed above. Check the “Latest version” location noted above for possible later revisions of this document.

Technical Committee members should send comments on this document to the Technical Committee’s email list. Others should send comments to the Technical Committee by using the “Send A Comment” button on the Technical Committee’s web page at http://www.oasis-open.org/committees/tosca/.

Citation format:

When referencing this document the following citation format should be used:

[TOSCA-Primer]

Topology and Orchestration Specification for Cloud Applications (TOSCA) Primer Version 1.0. 31 January 2013. OASIS Committee Note Draft 01. http://docs.oasis-open.org/tosca/tosca-primer/v1.0/cnd01/tosca-primer-v1.0-cnd01.html.

Copyright © OASIS Open 2013. All Rights Reserved.

All capitalized terms in the following text have the meanings assigned to them in the OASIS Intellectual Property Rights Policy (the "OASIS IPR Policy"). The full Policy may be found at the OASIS website.

This document and translations of it may be copied and furnished to others, and derivative works that comment on or otherwise explain it or assist in its implementation may be prepared, copied, published, and distributed, in whole or in part, without restriction of any kind, provided that the above copyright notice and this section are included on all such copies and derivative works. However, this document itself may not be modified in any way, including by removing the copyright notice or references to OASIS, except as needed for the purpose of developing any document or deliverable produced by an OASIS Technical Committee (in which case the rules applicable to copyrights, as set forth in the OASIS IPR Policy, must be followed) or as required to translate it into languages other than English.

The limited permissions granted above are perpetual and will not be revoked by OASIS or its successors or assigns.

This document and the information contained herein is provided on an "AS IS" basis and OASIS DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY OWNERSHIP RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.

Table of Contents

91. Introduction

91.1 Statement of Purpose

91.2 Scope of this Document

101.3 References (non-normative)

101.3.1 Standards

101.3.2 Software and Services

112 What Everybody Should Know About TOSCA

112.1 An overview of TOSCA

112.1.1 Bringing Cloud Services to Market – TOSCA Roles

112.1.2 TOSCA Value Statement

122.1.3 TOSCA Processing Environment

162.2 Roles Involved in Modeling a Cloud Application

172.2.1 Type Architect Role

182.2.2 Artifact Developers Role

192.2.3 Application Architect Role

253 What Type Architects Should Know About TOSCA

253.1 Providing Node Types and Relationship Types

253.1.1 Vendor Perspective

263.1.2 Node Types

263.1.3 The Lifecycle Interface

283.1.4 Relationship Types

283.2 Using Inheritance

303.3 Providing Requirement Types and Capability Types

323.4 Green Field Perspective

323.5 Modular Design of Service Templates

333.6 Simplifying Application Modeling: Composable Service Templates

343.6.1 Turning Service Templates into Composables

343.6.2 Using Abstract Node Types

353.6.3 Substitution of Abstract Node Types by Service Templates

364 What Artifact Developers Should Know About TOSCA

364.1 Defining Artifact Types

374.2 Defining Artifact Templates

394.3 Providing Implementations

404.3.1 Coping With Environment-Specific Implementations

425 What Cloud Service Providers Should Know About TOSCA

425.1 Adaptation to Particular Cloud Providers

425.1.1 Deployment of implementation artifacts and deployment artifacts

446 What Application Architects Should Know About TOSCA

446.1 Single-Tier MySQL Database for our SugarCRM Web Application

456.1.1 Required Node Types

496.1.2 Turning Node Types into Node Templates

516.1.3 Required Artifact Types

536.1.4 Turning Artifact Types into Artifact Templates

536.1.5 Required Relationship Types

546.1.6 Turning Relationship Types into Relationship Templates

566.2 Two-Tier SugarCRM Web Application Example

566.2.1 Required Node Types

616.2.2 Turning Node Types into Node Templates

636.2.3 Required Artifact Types

646.2.4 Turning Artifact Types into Artifact Templates

646.2.5 Required Relationship Types

666.2.6 Turning Relationship Types into Relationship Templates

676.2.7 Creating the Cloud Service Archive (CSAR)

697 Moving Virtual Machines to the TOSCA World

697.1 Deploying a New Virtual Machine (VM)

697.1.1 Required Node Types

707.1.2 Creating the Service Template xml file

738 How TOSCA Works with Other Cloud Standards

738.1 Mapping TOSCA to DMTF OVF

738.1.1 Use Case One: OVF Package for Single Virtual System

768.1.2 Use Case Two. OVF Package for Multiple Virtual Systems

80Appendix A. Acknowledgments

81Appendix B. Terminology & Acronyms

81B.1 Acronyms

82Appendix C. Revision History

List of Figures

13Figure 1 - Sample Architecture of a TOSCA Environment

14Figure 2 - Sample "Declarative" Processing Sequence When Importing a CSAR

15Figure 3 - Sample Extension of a CSAR for "Imperative" Processing

16Figure 4 - Sample "Imperative" Processing Sequence When Importing a CSAR

21Figure 5 - Topology of a Simple Cloud Application

22Figure 6 - Service Template of a Sample Application Including a Build Plan

23Figure 7 - Service Template that Makes Use of Requirements and Capabilities

27Figure 8 – Defining Interfaces and Their Implementations For Particular Node Types

29Figure 9 – Node, Artifact, Relationship, Requirements and Capabilities Type Hierarchies

33Figure 10 - Making Use of Imports

35Figure 11 - Service Template Substituting a Node Type

36Figure 12 - Key Definitions for TOSCA Artifacts and their Relationships

49Figure 13 - Node Type Inheritance for a SugarCRM Database Tier

61Figure 14 - Node Type Inheritance for a SugarCRM Web Application Tier

73Figure 15 - Sample Service Topology for OVF Use Case 1

76Figure 16 - Sample Service Topology for OVF Use Case 2

List of Tables

12Table 1 - TOSCA Benefits by Service Role

45Table 2 – Single-Tier MySQL Database Example's Base Node Types

47Table 3 – Single-Tier MySQL Database Example’s Specific Node Types

48Table 4 – Single-Tier MySQL Database Example's Custom Node Types

52Table 5 – Single-Tier MySQL Database Example's Base Artifact Types

54Table 6 – Single-Tier MySQL Database Example's Base Relationship Types

56Table 7 – SugarCRM Web Application Example's Base Node Types

59Table 8 – SugarCRM Web Application Example’s Specific Node Types

60Table 9 – SugarCRM Web Application Example's Custom Node Types

65Table 10 – SugarCRM Web Application Example's Base Relationship Types

Introduction

1.1 Statement of Purpose

Cloud computing offers a compelling cost-effective model for businesses that wish to host their applications and services in an envi

Recommended

View more >