Advancing BPaaS Research: PaaS Orchestration & Adaptation
W
P
3
:
B
P
a
a
S
R
e
s
e
a
r
c
h
E
x
e
c
u
t
i
o
n
E
n
v
i
r
o
n
m
e
n
t
PaaS Orchestration and Adaptation
W
P
3
:
B
P
a
a
S
R
e
s
e
a
r
c
h
E
x
e
c
u
t
i
o
n
E
n
v
i
r
o
n
m
e
n
t
:
P
a
a
S
O
r
c
h
e
s
t
r
a
t
i
o
n
a
n
d
A
d
a
p
t
a
t
i
o
n
R
e
s
e
a
r
c
h
P
r
o
b
l
e
m
:
H
o
w
c
a
n
w
e
m
a
k
e
u
s
e
o
f
C
l
o
u
d
p
r
o
v
i
d
e
r
s
o
n
a
l
l
l
a
y
e
r
s
?
H
o
w
c
a
n
w
e
a
d
a
p
t
t
h
e
d
e
p
l
o
y
m
e
n
t
i
n
a
c
r
o
s
s
-
l
a
y
e
r
w
a
y
t
o
f
i
t
t
h
e
c
u
r
r
e
n
t
n
e
e
d
s
?
BPaaS Bundle
M
o
t
i
v
a
t
i
n
g
E
x
a
m
p
l
e
Public IaaS cloud
Ensure a certain
response time
and availability.
Allowed and Availabe Cloud Infrastructures / Providers
Public PaaS cloud
Something happens to
a component on the
IaaS cloud provider.
Migration should
happen.
•
The Cloud-DSL CAMEL was currently restricted to describe
components on IaaS layer
•
The Cloud Provider Engine only provisioned services on the IaaS
layer
•
Most other current Cloud DSLs have single layer-specific descriptions
C
u
r
r
e
n
t
S
t
a
t
e
:
O
r
c
h
e
s
t
r
a
t
i
o
n
„Sword“
IaaS abstraction
Component
Configuration
1
*
Scripts
S
o
l
u
t
i
o
n
A
p
p
r
o
a
c
h
:
O
r
c
h
e
s
t
r
a
t
i
o
n
o
f
P
a
a
S
c
o
m
p
o
n
e
n
t
s
Extensions
Extensions and Integration
P
U
L
PaaS Unified Library
S
p
e
c
i
f
i
c
a
t
i
o
n
E
x
e
c
u
t
i
o
n
S
o
l
u
t
i
o
n
A
p
p
r
o
a
c
h
:
O
r
c
h
e
s
t
r
a
t
i
o
n
o
f
P
a
a
S
c
o
m
p
o
n
e
n
t
s
•
CAMEL extensions towards PaaS deployment
–
Excerpt from the CAMEL configuration additions:
PaaS and IaaS
configuration
come along with
the same
Component
description
Combine PaaS-specific
requirements and re-use
hardware requirements
S
o
l
u
t
i
o
n
A
p
p
r
o
a
c
h
:
O
r
c
h
e
s
t
r
a
t
i
o
n
o
f
P
a
a
S
c
o
m
p
o
n
e
n
t
s
•
CAMEL extensions towards PaaS deployment
–
Example as generated from
Allocation Environment:
<
internalComponents
xsi:type
=
"deployment:InternalServiceComponent"
name
=
“InvoiceNinja"
…
<
configurations
xsi:type
=
"deployment:PaaSConfiguration"
name
=
"CardDesignerPaaSConfiguration"
api
=
"PUL"
/>
<
requiredHost
name
=
"InvoiceNinjaRequiredHost"
/>
</
internalComponents
>
Multiple configurations
allowed in respect to the
underlying host.
PaaS configuration for a
certain PaaS interface. IaaS
configuration can happen as
before in scripts.
Requirements of the platform
are defined in the required
host, e.g. Java or software
components.
Host requirements are cross-layered
Abstraction
S
o
l
u
t
i
o
n
A
p
p
r
o
a
c
h
:
O
r
c
h
e
s
t
r
a
t
i
o
n
o
f
P
a
a
S
c
o
m
p
o
n
e
n
t
s
•
PaaS Unified Library
–
Abstraction from concrete provider APIs to support many at once
–
Integrated from SeaClouds projects by Atos
–
Enhanced to allow for better orchestration from Cloud Provider
Engine
•
Higher abstraction
•
Addition of more PaaS providers
S
o
l
u
t
i
o
n
A
p
p
r
o
a
c
h
:
O
r
c
h
e
s
t
r
a
t
i
o
n
o
f
P
a
a
S
c
o
m
p
o
n
e
n
t
s
•
Extension of Life Cycle Management in Cloud Provider Engine
–
Extended the Component Model of the Cloud Provider Engine
–
Created jobs for PaaS deployment
–
Ensured CAMEL and PUL interoperability (adapter)
Cloud Provider Engine
Sword
Dagger
PUL
C
u
r
r
e
n
t
S
t
a
t
e
:
A
d
a
p
t
a
t
i
o
n
•
CAMEL supports only
–
horizontal scaling
–
vertical scaling
•
Other Cloud DSLs have too generic workflow description
–
e.g. TOSCA with BPMN
•
Cloudiator supports only
–
CAMEL-compatible workflows
10
S
o
l
u
t
i
o
n
A
p
p
r
o
a
c
h
:
M
a
n
a
g
e
m
e
n
t
o
f
C
o
m
p
r
e
h
e
n
s
i
v
e
A
d
a
p
t
a
t
i
o
n
S
c
e
n
a
r
i
o
s
Extensions
Extensions and Implementation
A
d
a
p
t
a
t
i
o
n
M
a
n
a
g
e
m
e
n
t
S
p
e
c
i
f
i
c
a
t
i
o
n
E
x
e
c
u
t
i
o
n
S
o
l
u
t
i
o
n
A
p
p
r
o
a
c
h
:
M
a
n
a
g
e
m
e
n
t
o
f
C
o
m
p
r
e
h
e
n
s
i
v
e
A
d
a
p
t
a
t
i
o
n
S
c
e
n
a
r
i
o
s
•
Extension of CAMEL
–
Task composition
S
o
l
u
t
i
o
n
A
p
p
r
o
a
c
h
:
M
a
n
a
g
e
m
e
n
t
o
f
C
o
m
p
r
e
h
e
n
s
i
v
e
A
d
a
p
t
a
t
i
o
n
S
c
e
n
a
r
i
o
s
•
Extension of CAMEL
–
Complex tasks instead of just scaling
Replace service
with another one
Even change your
application
deployment and
topology
React in case of
violations by service
migration
S
o
l
u
t
i
o
n
A
p
p
r
o
a
c
h
:
M
a
n
a
g
e
m
e
n
t
o
f
C
o
m
p
r
e
h
e
n
s
i
v
e
A
d
a
p
t
a
t
i
o
n
S
c
e
n
a
r
i
o
s
•
Extension of Monitoring Solution by externally hosted services
–
Extended Cloud Provider Engine model by externally hosted monitor
–
Monitoring agent (Visor) in home domain of Cloud Provider Engine
can now pull data from services that are not managed on IaaS
PaaS
Env
MA
MA
S
o
l
u
t
i
o
n
A
p
p
r
o
a
c
h
:
M
a
n
a
g
e
m
e
n
t
o
f
C
o
m
p
r
e
h
e
n
s
i
v
e
A
d
a
p
t
a
t
i
o
n
S
c
e
n
a
r
i
o
s
•
Development of Adaptation Management component that
exposes the Cloud Provider Engine and manages the
adaptation plans
Plans are
composed of
single steps
BPaaS Bundle
D
e
m
o
n
s
t
r
a
t
i
o
n
:
M
o
t
i
v
a
t
i
n
g
E
x
a
m
p
l
e
Public IaaS cloud
Public PaaS cloud
D
e
m
o
n
s
t
r
a
t
i
o
n
:
P
a
a
S
O
r
c
h
e
s
t
r
a
t
i
o
n
Scripts
I
a
a
S
P
a
a
S
PaaS
requirements
Deployment
part of BPaaS
bundle
D
e
m
o
n
s
t
r
a
t
i
o
n
:
P
a
a
S
O
r
c
h
e
s
t
r
a
t
i
o
n
Scripts
I
a
a
S
P
a
a
S
PaaS
requirements
Cloud Provider Engine
Sword
Dagger
PUL
translates
orchestrates
orchestrates
D
e
m
o
n
s
t
r
a
t
i
o
n
:
O
r
c
h
e
s
t
r
a
t
i
o
n
(
V
i
d
e
o
/
L
i
v
e
)
D
e
m
o
n
s
t
r
a
t
i
o
n
:
A
d
a
p
t
a
t
i
o
n
P
l
a
n
D
e
s
c
r
i
p
t
i
o
n
<MonitorSubscription>
ResponseTimeRule
<Sensor>
ResponseTimeSensor
<Component>
InvoiceNinja
<AdaptationTask>
DeployComponent
<AdaptationTask>
UpdateWorkflowDescription
references
triggers
<AdaptationTask>
DeleteComponent
With description or reference
to a VirtualMachine or
PlatformEnvironment
•
Adaptation description for a migration in CAMEL as
executed by the Adaptation Management component
Already available entities of
the Cloud Provider Engine
D
e
m
o
n
s
t
r
a
t
i
o
n
:
A
d
a
p
t
a
t
i
o
n
<AdaptationTask>
DeployComponent
<AdaptationTask>
UpdateWorkflowDescription
<AdaptationTask>
DeleteComponent
D
e
m
o
n
s
t
r
a
t
i
o
n
:
A
d
a
p
t
a
t
i
o
n
<AdaptationTask>
DeployComponent
<AdaptationTask>
UpdateWorkflowDescription
<AdaptationTask>
DeleteComponent
Execution Environment
Execution Environment
Cloud Provider Engine
Workflow
Engine
Adaptation
Engine
Monitoring
Engine
Sword
Dagger
PUL
D
e
m
o
n
s
t
r
a
t
i
o
n
:
A
d
a
p
t
a
t
i
o
n
<AdaptationTask>
DeployComponent
<AdaptationTask>
UpdateWorkflowDescription
<AdaptationTask>
DeleteComponent
Execution Environment
Execution Environment
Cloud Provider Engine
Workflow
Engine
Adaptation
Engine
Monitoring
Engine
Sword
Dagger
PUL
D
e
m
o
n
s
t
r
a
t
i
o
n
:
A
d
a
p
t
a
t
i
o
n
<AdaptationTask>
DeleteComponent
Execution Environment
Execution Environment
Cloud Provider Engine
Workflow
Engine
Adaptation
Engine
Monitoring
Engine
Sword
Dagger
PUL
<AdaptationTask>
DeployComponent
<AdaptationTask>
UpdateWorkflowDescription
D
e
m
o
n
s
t
r
a
t
i
o
n
:
A
d
a
p
t
a
t
i
o
n
Execution Environment
Execution Environment
Cloud Provider Engine
Workflow
Engine
Adaptation
Engine
Monitoring
Engine
Sword
Dagger
PUL
<AdaptationTask>
DeployComponent
<AdaptationTask>
UpdateWorkflowDescription
<AdaptationTask>
DeleteComponent
D
e
m
o
n
s
t
r
a
t
i
o
n
:
A
d
a
p
t
a
t
i
o
n
Execution Environment
Execution Environment
Cloud Provider Engine
Workflow
Engine
Adaptation
Engine
Monitoring
Engine
Sword
Dagger
PUL
<AdaptationTask>
DeployComponent
<AdaptationTask>
UpdateWorkflowDescription
<AdaptationTask>
DeleteComponent
D
e
m
o
n
s
t
r
a
t
i
o
n
:
A
d
a
p
t
a
t
i
o
n
(
V
i
d
e
o
/
L
i
v
e
)
27
W
P
3
:
B
P
a
a
S
R
e
s
e
a
r
c
h
E
x
e
c
u
t
i
o
n
E
n
v
i
r
o
n
m
e
n
t
:
P
a
a
S
O
r
c
h
e
s
t
r
a
t
i
o
n
a
n
d
A
d
a
p
t
a
t
i
o
n
A
d
d
e
d
V
a
l
u
e
:
•
a
l
l
o
w
t
o
d
e
p
l
o
y
c
o
m
p
o
n
e
n
t
s
a
t
a
b
i
g
g
e
r
v
a
r
i
e
t
y
o
f
C
l
o
u
d
p
r
o
v
i
d
e
r
s
•
d
e
s
c
r
i
b
e
c
o
m
p
o
n
e
n
t
s
o
n
m
u
l
t
i
p
l
e
w
a
y
s
a
n
d
p
e
r
C
l
o
u
d
l
a
y
e
r
o
n
a
p
r
o
v
i
d
e
r
-
i
n
d
e
p
e
n
d
e
n
t
w
a
y
•
a
l
l
o
w
t
o
d
e
s
c
r
i
b
e
a
d
a
p
t
a
t
i
o
n
p
l
a
n
s
,
e
.
g
.
s
w
i
t
c
h
p
r
o
v
i
d
e
r
a
t
r
u
n
-
t
i
m
e
o
r
a
d
a
p
t
t
o
n
e
w
c
o
n
d
i
t
i
o
n
s
W
P
3
:
B
P
a
a
S
R
e
s
e
a
r
c
h
E
x
e
c
u
t
i
o
n
E
n
v
i
r
o
n
m
e
n
t
:
P
a
a
S
O
r
c
h
e
s
t
r
a
t
i
o
n
a
n
d
A
d
a
p
t
a
t
i
o
n
Now as the bundle is complete, we can start with the Execution Environment. For that I will present you the PaaS Orchestration and Adaptation.
Delve into the realm of Business Process as a Service (BPaaS) with a focus on PaaS orchestration and adaptation. Explore how to leverage cloud providers across all layers and adapt deployments to meet evolving needs seamlessly. Discover innovative solutions for orchestrating PaaS components and enhancing cross-layer deployment efficiency.
Download Presentation
Please find below an Image/Link to download the presentation.
The content on the website is provided AS IS for your information and personal use only. It may not be sold, licensed, or shared on other websites without obtaining consent from the author.If you encounter any issues during the download, it is possible that the publisher has removed the file from their server.
You are allowed to download the files provided on this website for personal or commercial use, subject to the condition that they are used lawfully. All files are the property of their respective owners.
The content on the website is provided AS IS for your information and personal use only. It may not be sold, licensed, or shared on other websites without obtaining consent from the author.
E N D
Presentation Transcript
WP3: BPaaS Research Execution Environment PaaS Orchestration and Adaptation www.cloudsocket.eu,info@cloudsocket.eu
WP3: BPaaS Research Execution Environment: PaaS Orchestration andAdaptation Research Problem: How can we make use of Cloud providers on all layers? Orchestration How can we adapt the deployment in a cross-layer way to fit the current needs? Adaptation www.cloudsocket.eu,info@cloudsocket.eu
Motivating Example Something happens to a component on the IaaS cloud provider. Ensure a certain response time and availability. Public IaaS cloud BPaaS Bundle Public PaaS cloud Allowed and Availabe Cloud Infrastructures / Providers Migration should happen. www.cloudsocket.eu,info@cloudsocket.eu
Current State: Orchestration The Cloud-DSL CAMEL was currently restricted to describe components on IaaS layer The Cloud Provider Engine only provisioned services on the IaaS layer Most other current Cloud DSLs have single layer-specific descriptions Sword IaaS abstraction * 1 Component Configuration Scripts www.cloudsocket.eu,info@cloudsocket.eu
Solution Approach: Orchestration of PaaS components Specification Execution PUL PaaS Unified Library Extensions Extensions and Integration www.cloudsocket.eu,info@cloudsocket.eu
Solution Approach: Orchestration of PaaS components CAMEL extensions towards PaaS deployment Excerpt from the CAMEL configuration additions: PaaS and IaaS configuration come along with the same Component description Combine PaaS-specific requirements and re-use hardware requirements www.cloudsocket.eu,info@cloudsocket.eu
Solution Approach: Orchestration of PaaS components CAMEL extensions towards PaaS deployment Example as generated from Allocation Environment: Multiple configurations allowed in respect to the underlying host. <internalComponents xsi:type="deployment:InternalServiceComponent" name= InvoiceNinja" <configurations xsi:type="deployment:PaaSConfiguration" name="CardDesignerPaaSConfiguration" api="PUL"/> <requiredHost name="InvoiceNinjaRequiredHost"/> </internalComponents> PaaS configuration for a certain PaaS interface. IaaS configuration can happen as before in scripts. Requirements of the platform are defined in the required host, e.g. Java or software components. Host requirements are cross-layered Abstraction www.cloudsocket.eu,info@cloudsocket.eu
Solution Approach : Orchestration of PaaS components PaaS Unified Library Abstraction from concrete provider APIs to support many at once Integrated from SeaClouds projects by Atos Enhanced to allow for better orchestration from Cloud Provider Engine Higher abstraction environmental independency of calls Addition of more PaaS providers www.cloudsocket.eu,info@cloudsocket.eu
Solution Approach: Orchestration of PaaS components Extension of Life Cycle Management in Cloud Provider Engine Extended the Component Model of the Cloud Provider Engine Created jobs for PaaS deployment Ensured CAMEL and PUL interoperability (adapter) Cloud Provider Engine IaaS Sword Dagger PaaS PUL www.cloudsocket.eu,info@cloudsocket.eu
Current State: Adaptation CAMEL supports only horizontal scaling vertical scaling Other Cloud DSLs have too generic workflow description e.g. TOSCA with BPMN Cloudiator supports only CAMEL-compatible workflows www.cloudsocket.eu,info@cloudsocket.eu 10
Solution Approach: Management of Comprehensive Adaptation Scenarios Specification Execution Adaptation Management Extensions Extensions and Implementation www.cloudsocket.eu,info@cloudsocket.eu
Solution Approach: Management of Comprehensive Adaptation Scenarios Extension of CAMEL Task composition www.cloudsocket.eu,info@cloudsocket.eu
Solution Approach: Management of Comprehensive Adaptation Scenarios Extension of CAMEL Complex tasks instead of just scaling Replace service with another one Even change your application deployment and topology Well-known Scaling definitions Task Modification for Dynamic React in case of violations by service migration www.cloudsocket.eu,info@cloudsocket.eu
Solution Approach: Management of Comprehensive Adaptation Scenarios Extension of Monitoring Solution by externally hosted services Extended Cloud Provider Engine model by externally hosted monitor Allow the same for PaaS as for IaaS Monitoring agent (Visor) in home domain of Cloud Provider Engine can now pull data from services that are not managed on IaaS Execution Environment IaaS MA VM Cloud Provider Engine Monitoring Engine PaaS Env PaaS MA www.cloudsocket.eu,info@cloudsocket.eu
Solution Approach: Management of Comprehensive Adaptation Scenarios Development of Adaptation Management component that exposes the Cloud Provider Engine and manages the adaptation plans Plans are composed of single steps www.cloudsocket.eu,info@cloudsocket.eu
Demonstration: Motivating Example Public IaaS cloud BPaaS Bundle Public PaaS cloud www.cloudsocket.eu,info@cloudsocket.eu
Demonstration: PaaS Orchestration IaaS Scripts PaaS PaaS requirements Deployment part of BPaaS bundle www.cloudsocket.eu,info@cloudsocket.eu
Demonstration: PaaS Orchestration IaaS orchestrates Scripts PaaS PaaS requirements Cloud Provider Engine Sword translates Dagger orchestrates PUL www.cloudsocket.eu,info@cloudsocket.eu
Demonstration: Orchestration (Video / Live) www.cloudsocket.eu,info@cloudsocket.eu
Demonstration: Adaptation Plan Description Adaptation description for a migration in CAMEL as executed by the Adaptation Management component <MonitorSubscription> ResponseTimeRule <Sensor> <Component> InvoiceNinja ResponseTimeSensor Already available entities of the Cloud Provider Engine triggers references <AdaptationTask> DeleteComponent <AdaptationTask> DeployComponent <AdaptationTask> UpdateWorkflowDescription With description or reference to a VirtualMachine or PlatformEnvironment www.cloudsocket.eu,info@cloudsocket.eu
Demonstration: Adaptation <AdaptationTask> DeleteComponent <AdaptationTask> DeployComponent <AdaptationTask> UpdateWorkflowDescription www.cloudsocket.eu,info@cloudsocket.eu
Demonstration: Adaptation <AdaptationTask> DeleteComponent <AdaptationTask> DeployComponent <AdaptationTask> UpdateWorkflowDescription Execution Environment Cloud Provider Engine Monitoring Engine Adaptation Engine Sword Dagger Workflow Engine PUL www.cloudsocket.eu,info@cloudsocket.eu
Demonstration: Adaptation <AdaptationTask> DeleteComponent <AdaptationTask> DeployComponent <AdaptationTask> UpdateWorkflowDescription Execution Environment Cloud Provider Engine Monitoring Engine Adaptation Engine Sword Dagger Workflow Engine PUL www.cloudsocket.eu,info@cloudsocket.eu
Demonstration: Adaptation <AdaptationTask> DeleteComponent <AdaptationTask> DeployComponent <AdaptationTask> UpdateWorkflowDescription Execution Environment Cloud Provider Engine Monitoring Engine Adaptation Engine Sword Dagger Workflow Engine PUL www.cloudsocket.eu,info@cloudsocket.eu
Demonstration: Adaptation <AdaptationTask> DeleteComponent <AdaptationTask> DeployComponent <AdaptationTask> UpdateWorkflowDescription Execution Environment Cloud Provider Engine Monitoring Engine Adaptation Engine Sword Dagger Workflow Engine PUL www.cloudsocket.eu,info@cloudsocket.eu
Demonstration: Adaptation <AdaptationTask> DeleteComponent <AdaptationTask> DeployComponent <AdaptationTask> UpdateWorkflowDescription Execution Environment Cloud Provider Engine Monitoring Engine Adaptation Engine Sword Dagger Workflow Engine PUL www.cloudsocket.eu,info@cloudsocket.eu
Demonstration: Adaptation (Video / Live) www.cloudsocket.eu,info@cloudsocket.eu 27
WP3: BPaaS Research Execution Environment: PaaS Orchestration and Adaptation Added Value: allow to deploy components at a bigger variety of Cloud providers describe components on multiple ways and per Cloud layer on a provider-independent way allow to describe adaptation plans, e.g. switch provider at run-time or adapt to new conditions www.cloudsocket.eu,info@cloudsocket.eu
WP3: BPaaS Research Execution Environment: PaaS Orchestration and Adaptation www.cloudsocket.eu,info@cloudsocket.eu
