Merging of TOSCA Cloud Topology Templates - IAAS

More documents

Recommendations

Info

2 Fundamentals bination with a public cloud is used. Another important benefit is improved time to market especially for SMEs without the delay for building up an on-premise infrastructure. There also exist some risks when using cloud computing, especially in the Public cloud deployment model. Armbrust et al. [5] name privacy concerns regarding sensitive data, vendor-lock-in that prevents migration to other providers, poor predictability of performance, reputation and liability issues. 2.3 Topology and Orchestration Specification for Cloud Applications The Topology and Orchestration Specification for Cloud Applications (TOSCA) is an XMLbased language and metamodel whose grammar provides the possibility to describe IT services. The main goal of the TOSCA specification is to facilitate a description of these services concerning structure and management aspects during their life cycle which is independent from cloud providers or a certain environment. The structure of a so-called Service Template is described by a Topology Template, whereas means to manage the service instances during run-time are provided by Plans. Plans contribute to the (semi-) automatic creation and management of IT services as suggested by the cloud computing paradigm [6]. A Topology is defined as the “the individual components of a service and their relations” [32]. Ultimately, the definition of the topology and orchestration plans as interoperable artifacts are supposed to make IT services exchangeable between different cloud providers. The following section describes the most important elements of the TOSCA specification [32], [7] using Version 1.0 Working Draft 05. Listing 2.1 shows the overall high-level syntax of a Service Template consisting of a Topology Template or a TopologyTemplateReference, Node Types, Relationship Types and Plans. The ? denotes an optional element or attribute, the | an exclusive decision (xor), the * zero or many and the + one or many elements or attributes. Words written in italics denote XML elements and attributes. 2.3.1 TOSCA Syntax Service Template The ServiceTemplate element is the root element of a TOSCA XML document. It has a set of properties; the most important ones will be discussed next. Every Service Template has a unique id regarding its namespace and a descriptive, human readable name. The target- Namespace attribute declares the namespace of the Service Template, an important feature as a Service Template might be referenced in another Service Template. The optional Extensions element offers an extension mechanism to define additional vendorspecific and domain-specific information. The attribute namespace specifies the namespaces of extension attributes and elements that are used within the Service Template under definition, the attribute mustUnderstand indicates if a TOSCA compliant implementation must adhere to the extension and reject it in case of not understanding. Additionally every XML element specified by the TOSCA specification extends the XML complexType denoted by 8
2 Fundamentals tExtensibleElements. The complexType is depicted in Listing 2.2. It contains a xs:any element that permits the adding of further XML elements that are not defined by the TOSCA schema. The attribute processContents="lax" indicates that a XML processor can validate that element if it is able to obtain any schema information but will not generate error messages if not [50], [49]. High level syntax of TOSCA Service Template 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 ? + * ? * ( ... | )? ? ... ? ... ? ... Listing 2.1: High level syntax of TOSCA Service Template 9
Page 1: Institute of Architecture of Applic
Page 5 and 6: Contents Contents 1 Introduction...
Page 7 and 8: List of Figures List of Figures Fig
Page 9 and 10: List of Listings List of Listings L
Page 11 and 12: List of Tables List of Tables Table
Page 13: List of Abbreviations SaaS SAX SESE
Page 16 and 17: 1 Introduction Not in the scope of
Page 18 and 19: 1 Introduction Chapter 6 - Concept
Page 20 and 21: 2 Fundamentals arcs = (, ) and =
Page 24 and 25: 2 Fundamentals Syntax of the XML co
Page 26 and 27: 2 Fundamentals Additional Relations
Page 28 and 29: 2 Fundamentals However, the TOSCA P
Page 30 and 31: 2 Fundamentals 2.4 Frameworks The f
Page 32 and 33: 2 Fundamentals Framework class usin
Page 34 and 35: 2 Fundamentals Code example for a c
Page 36 and 37: 3 Related Work 3 Related Work The f
Page 38 and 39: 3 Related Work tive algorithm with
Page 40 and 41: 4 Assumptions and Requirements for
Page 46 and 47: 5 Concept for Matching of Topology
Page 72 and 73:
5 Concept for Matching of Topology
Page 74 and 75:
Page 76 and 77:
Page 78 and 79:
Page 80 and 81:
Page 82 and 83:
Page 84 and 85:
Page 86 and 87:
Page 88 and 89:
Page 90 and 91:
Page 92 and 93:
Page 94 and 95:
Page 96 and 97:
Page 98 and 99:
Page 100 and 101:
Page 102 and 103:
6 Concept for Merging of Topology T
Page 104 and 105:
Page 106 and 107:
Page 108 and 109:
Page 110 and 111:
Page 112 and 113:
Page 114 and 115:
Page 116 and 117:
Page 118 and 119:
Page 120 and 121:
Page 122 and 123:
Page 124 and 125:
Page 126 and 127:
Page 128 and 129:
Page 130 and 131:
7 Architecture & Design of an Exten
Page 132 and 133:
Page 134 and 135:
Page 136 and 137:
Page 138 and 139:
Page 140 and 141:
Page 142 and 143:
Page 144 and 145:
Page 146 and 147:
8 Implementation of the Framework (
Page 148 and 149:
8 Implementation of the Framework F
Page 150 and 151:
8 Implementation of the Framework a
Page 152 and 153:
8 Implementation of the Framework 8
Page 154 and 155:
9 Evaluation of the Algorithms and
Page 156 and 157:
Page 158 and 159:
Page 160 and 161:
Page 162 and 163:
10 Conclusion and Future Work 10 Co
Page 164 and 165:
Bibliography Bibliography [1] Amazo
Page 166 and 167:
Bibliography [28] S. Melnik, H. Gar
Page 168:
Erklärung Hiermit erkläre ich, da
show all

Merging of TOSCA Cloud Topology Templates - IAAS

Create successful ePaper yourself

Delete template?

Save as template?