• No results found

Beyond Mere Application Structure

N/A
N/A
Protected

Academic year: 2021

Share "Beyond Mere Application Structure"

Copied!
36
0
0

Loading.... (view fulltext now)

Full text

(1)

Thoughts on the Future of Cloud Orchestration Tools

Jörg Domaschka

a

,

Frank Griesinger

a

, Daniel Baur

a

, Alessandro Rossini

b

aOMI, University of Ulm, Germany bSINTEF, Oslo, Norway

(2)

Targeted shortcomings

1) 

Communication description abilities

(3)
(4)

What we want to do

Load balancer

Application server (blog)

(5)

Deploying in the Cloud

Deploying an application in the Cloud

:

1) Describe the application

(6)

Application

Deploying in the Cloud

Deploying an application in the Cloud

:

1) Describe the application

Component A

Component B Communication

(7)

Deploying in the Cloud

Deploying an application in the Cloud

:

1) Describe the application

(8)

Deploying in the Cloud

Deploying an application in the Cloud

:

1) Describe the application

2) Click the

green button

(9)

Deploying in the Cloud

Deploying an application in the Cloud

:

1) Describe the application

2) Click the

green button

3) Enjoy your application in the Cloud!

Component instance 1 Component instance 2 Component instance 3 install start stop shutdown initialize

(10)

Application in the Cloud

Load balancer Application server (blog) DBMS Component Communication Type level Blog application

(11)

Application in the Cloud

Load balancer Application server (blog) DBMS Component Communication Type level Deploy Blog application

(12)

Application in the Cloud

Load balancer Application server (blog) DBMS Component Communication Type level Deploy Load balancer Application server (blog) Application server (blog) DBMS

Component instance Instance level Channel instance Blog application

(13)

Cloud Orchestration Tools

Upcoming publication at UCC 2015 by Daniel Baur et al.

• 

cloud deployment

• 

life-cycle handling

• 

monitoring

• 

application description

• 

infinite ca

rdinality

(14)
(15)

Generic Communication Patterns

(16)

Generic Communication Patterns

(17)

Generic Communication Patterns

(18)

Generic Communication Patterns

(19)

Advanced Application Deployment

Assumption: Best performance if each DBMS interface is addressed by a maximum of 2 blog applications. è 1-M mapping (M=2) Load balancer Application server (blog) DBMS Deploy

(20)

Advanced Application Deployment

Assumption: Best performance if each DBMS interface is addressed by a maximum of 2 blog applications. è 1-M mapping (M=2) Load balancer Application server (blog) DBMS Deploy Load balancer Application server (blog) Application server (blog) DBMS DBMS Application server (blog)

(21)

Port and Link Boundaries

A

à

B : ([ out

low

, out

up

],[ in

low

, in

up

])

(22)

Port and Link Boundaries

A

à

B : ([ out

low

, out

up

],[ in

low

, in

up

])

A

B

Out:

Low .. Up

In:

Low .. Up

(23)

Port and Link Boundaries

A

à

B : ([ out

low

, out

up

],[ in

low

, in

up

])

Differentiation

:

- 

Component

- 

Application

- 

Application instance

A

B

Out:

Low .. Up

In:

Low .. Up

(24)

Port and Link Boundaries

A

à

B

Component: -

Application: [ 1 , 1 ] , [ 1 , 2 ]

Application instance: -

Load balancer Application server (blog) DBMS

A

B

(25)

Where are we?

• 

Basic communication patterns

(26)

VM 1 VM 4 VM 2 VM 5 VM 3 VM 6

Multi-tenant Deployments

Load balancer Application server (blog) DBMS Deploy Load balancer Application server (blog) DBMS Load balancer Application server (blog) DBMS

(27)

VM 1 VM 2 VM 4 VM 3

Multi-tenant Deployments

Load balancer Application server (blog) DBMS Deploy Load balancer Application server (blog) DBMS Application server (blog)

(28)

Apply a Facet

Load balancer Application server placeholder DBMS facet (blog) Application server (blog) path port application server cluster app. server port DBMS: connection properties Database port facet ports Load balancer Application server (blog) DBMS

(29)

Realizing a Facet

Properties:

• 

Mechanisms to introduce properties to the runtime system

• 

Components need advanced life-cycle actions

(30)

Beyond Facets and Port Boundaries

Resource allocation

When?

Which?

Where?

Affection?

VM 1 VM 2 VM 4 VM 3 Load balancer Application server (blog) DBMS Application server (blog) Application server (blog)

(31)

Beyond Facets and Port Boundaries

Resource allocation

VM 1 VM 2 VM 4 VM 3 Load balancer Application server (blog) DBMS Application server (blog) Application server (blog) VM 5 VM 6 VM 7 Load balancer Application server (blog) DBMS

Migration

(32)

Beyond Facets and Port Boundaries

Advanced communication patterns:

• 

Groupcast, multicast

• 

Strategy-based (e.g. fault tolerance)

Life-cycle actions:

• 

Adding and removing facets

(33)

Conclusion

i) 

Port and Link Boundaries

à

Modelling

more complex communications and dependencies,

based on instance level.

ii) 

Facets

à

Modelling

the groups of logical dependent component

instances / data

(34)

Future Work

Cloudiator – Cloud Orchestration Tool

à

Extend the life-cycle management

à

https://github.com/cloudiator

PaaSage Modelling Language (CAMEL)

(35)

Thank you.

(36)

References

Related documents