Merging of TOSCA Cloud Topology Templates - IAAS

More documents

Recommendations

Info

2 Fundamentals arcs = (, ) and = (, ) are parallel if their head and tail are the identical in each case. A simple directed graph is a graph that has neither loops nor parallel arcs. For every simple directed graph = (, ) the following always holds true: ⊆ × . The definition 2.4 of subgraphs can also be applied to directed graphs. Note: A graph can also have assigned types and label to its vertices and edges [25]. Definition 2.7 (Trees): A connected graph = (, ) is called a tree if it does not contain any circles. In a tree there exists only one path between two vertices , ∈ . One vertex is called root. If the graph G is directed, there exists only one path from the root to every vertex in the tree. Vertices with only one incident edge are called leafs. 2.2 Cloud Computing According to Mell and Grance from the National Institute of Standards and Technology (NIST) [27] Cloud Computing is “a model for enabling ubiquitous, convenient, on-demand network access to a shared pool of configurable computing resources (e.g., networks, servers, storage, applications, and services) that can be rapidly provisioned and released with minimal management effort or service provider interaction.“ The authors define five essential characteristics, three service models and four deployment models. These properties also coincide with the definitions and explanations of [43] that are also used in this section. Characteristics of Cloud Computing The five characteristics are on-demand-self-service, broad-network-access, resourcepooling, rapid-elasticity and measured service. On-demand-self-service connotes that a consumer in need of a cloud service, e.g. processing power or storage, does not require any human interaction by the service provider to provision it. Service capabilities are accessed over network using client agnostic standard mechanisms (broad-network-access). Resource-pooling refers to cloud providers pooling their resources to serve multiple customers at the same time. This is also called multi-tenancy. Resources, physical and virtual, are assigned respectively removed dynamically to that pool to satisfy the respective demand. Consumers usually do not know the exact location of the resource they obtain, but some service providers offer the possibility to specify some high level location parameters, e.g. Amazon with its concept of availability zones that are distributed around the world [1]. The ability to provision and release resources automatically and fast to scale according to demand is called rapid elasticity. This creates the illusion of unlimited resources that can be acquired at any time for the consumer. The last of the five characteristics is the measured service. Automatic control and metering helps optimizing the resource allocation. The resources are monitored and reported to enable a pay-per-use billing model. Service Models of Cloud Computing Typically there exist three types of Cloud Computing offerings at different layers: Infrastructure, platform and applications. Infrastructure as a Service (IaaS), also called Resource Cloud, provides enhanced virtualization capabilities. The consumer has access to computation power, networks and storage and can install and use arbitrary software raging from 6
2 Fundamentals operating systems to business applications. The underlying cloud infrastructure, however, is not controlled or managed by the consumer. Platform as a Service (PaaS) resides conceptually one layer above IaaS often using the underlying capabilities of the latter. The PaaS cloud provider offers a platform including programming languages, Application Programming Interfaces (API), libraries, services and tools to the consumer to run self-created or purchased software. The consumer does not manage the underlying infrastructure such as operating systems and servers but can use the APIs to specify the behavior of the platform. The programmatic use of the provider’s APIs often binds the created software to the specific cloud provider and impedes migration to other providers. Software as a Service (SaaS) provides consumers with complete applications accessible through a web browser or through a client program interface. The applications are running on a cloud infrastructure that is beyond the consumer’s control. Only some limited application parameters may be configured. Combinations of the three service models are also common, e.g. the Google App Engine [17] as a PaaS offering in combination with a SaaS application such as Google Docs [18]. Furthermore Salesforce.com has augmented its SaaS offering with the PaaS platform force.com where consumers can write extensions to the existing application [41]. Deployment Models Four Deployment Models of Cloud Computing are commonly differentiated in literature: Private cloud, Community cloud, Public cloud and Hybrid cloud. A Private cloud is exclusively available for a single organization. The location of the cloud can be on-premise in a datacenter of the organization or off-premise hosted by a third party. The same holds true for ownership, management and operation. Multiple consumers, e.g. several small and medium enterprises (SMEs), with shared interests, such as their mission and security requirements use Community clouds. Hosting, operation and management is done by one of the community organizations, a third party or a combination of both. A Public cloud is hosted on the premises of a cloud provider and offered to the general public. A Hybrid cloud is the combination of two or more of the aforementioned cloud deployment models. The distinct cloud infrastructures are combined to enable particular benefits, e.g. cloud bursting to transfer additional computation load that cannot be handled on-premise from a Private cloud to a Public cloud. Benefits and Risks To finish the Cloud Computing section some of the benefits and risks will be illustrated. According to Schubert [43] some of the benefits of Cloud Computing are cost reduction as infrastructure purchase and operational costs can possibly be reduced. Moving to the cloud, private or public, is an investment that has to be calculated beforehand and a positive Return on Investment (ROI) is not always certain. Modifications on applications or the own data center may be necessary. However, in extreme cases capital expenditures (CAPEX) can be completely turned into operational expenditures (OPEX) if a pay-per-use model in com- 7
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 22 and 23: 2 Fundamentals bination with a publ
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 70 and 71:
5 Concept for Matching of Topology
Page 72 and 73:
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

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?