Tem
pla
te v
6
© s
cil
lystu
ff o
n fli
ckr
OW2 Annual Conference
November 29, 2012
Pierre CHÂTEL – Thales
CHOReOS - Large Scale Choreographies for the FI from theory to practice
2 OW2 Annual Conference
November 29, 2012
Choreography-centric SOA for Services & Things Why?
Sustaining decentralized service choreographies In order to support Future Internet, Large Scale Focus on Internet of Services and Internet of Things
How? Introducing a specific Development Process and Integrated Development and Runtime Environment (IDRE) for coordination of services through choreographies
What is CHOReOS?
Future
Internet
Ultra
Large
Scale
CHOReOS
3 OW2 Annual Conference
November 29, 2012
1. Orchestration vs. Choreography
2. Choreography exemple in Airport UC
3. CHOReOS contributions extract
1. IDRE
2. Development process
3. Choreography synthesis
4. Conclusion
Outline
4 OW2 Annual Conference
November 29, 2012
1. Orchestration vs. Choreography
2. Choreography exemple in Airport UC
3. CHOReOS contributions extract
1. IDRE
2. Development process
3. Choreography synthesis
4. Conclusion
Outline
5 OW2 Annual Conference
November 29, 2012
Orchestration vs. Choreography
Orchestration: Local / centralized
perspective
"Each player in the orchestra strictly follows instructions from the conductor“
SOA: Refers to a business process, with a specific (business) goal
Choreography:
Global / distributed perspective
“Dancers dance following a global scenario, without a single point of control“
SOA: describes a protocol for peer-to-peer interactions
6 OW2 Annual Conference
November 29, 2012
Scalability
… in the number of users, service instances, composed services, …
Heterogeneity
… in the diversity of service types, technologies, …
Mobility
… leading to mobile and volatile services…
Awareness & adapability
… overcoming the volatility of services…
Choreographies help deal with FI “…ities”
7 OW2 Annual Conference
November 29, 2012
1. Orchestration vs. Choreography
2. Choreography example in Airport UC
3. CHOReOS contributions extract
1. IDRE
2. Development process
3. Choreography synthesis
4. Conclusion
Outline
8 OW2 Annual Conference
November 29, 2012
Passenger-friendly Airport
Context: air transportation / service to passengers
Goal: improvements in services, airport fluidity proof of concept
CHOReOS innovation highlights
To enable dynamic rebinding and replacement of services (loose coupling)
Distributed coordination
Partners
THALES: business Web services provider
Inria: large scale aspects through Things (sensors, actuators) interoperability framework
Linagora: bus provider (EasyESB)
Use case
At home Inside
airport In plane Landed
Image: photostock /
FreeDigitalPhotos.net
9 OW2 Annual Conference
November 29, 2012
Use case
Passengers arrival handling and
tracking at the airport
10 OW2 Annual Conference
November 29, 2012
Use case
11 OW2 Annual Conference
November 29, 2012
1. Orchestration vs. Choreography
2. Choreography example in Airport UC
3. CHOReOS contributions extract
1. IDRE
2. Development process
3. Choreography synthesis
4. Conclusion
Outline
12 OW2 Annual Conference
November 29, 2012
IDRE
Formally grounded abstractions and models
Service-oriented middleware
Service governance, verification, and validation
Dynamic
choreography- centric
development process
Integrated Development and
Runtime Environment
The “Integrated Development and Runtime Environment”
Aim: integrate all CHOReOS components in one platform
13 OW2 Annual Conference
November 29, 2012
Specific development process
Technology-independent characterization of the “strategy” to be used during the choreography life cycle
Usual software definition activities, but structured in a CHOReOS-specific way
High-level development process model specified in BPMN2
Deployment and
Execution
14 OW2 Annual Conference
November 29, 2012
15 OW2 Annual Conference
November 29, 2012
16 OW2 Annual Conference
November 29, 2012
From BPMN2 Choreography Specification to (runtime artifacts) Synthesis and (service) Discovery
Step 1: BPMN specification model to model transformation choreography labelled state transition systems (CLTS)
Choreography global coordination logic specified by the CLTS
Step 2: Projecting the global coordination logic into individual expected participant sub-CLTSs
Expected participants behaviors
Step 3: Discovery of available services, generation of Coordination Delegates (CDs) code, based on actual behaviors + expected behaviors of services
CDs will manage the services at runtime, based on the choreography coordination logic
Choreography synthesis
17 OW2 Annual Conference
November 29, 2012
Choreography synthesis – Step 1
Airport UC choreography CLTS extract
18 OW2 Annual Conference
November 29, 2012
Choreography synthesis: CLT projection – Step 2
Choreography CLTS Projected expected participant CLTSs
19 OW2 Annual Conference
November 29, 2012
Choreography synthesis: Airport UC – Step 3
Stand and gate management
ATC
Airport
Luggage Handling Company
Security Company Airport Noise Sensors
aggregator
Airport Bus Company
Airport Speaker Actuators aggregator
Amenity Provider
Airport infrared Sensors aggregator
CD-ATC
CD-AIR-SGM
CD-SGM-AIR
CD-AIR-ABC
CD-ABS-AIR
CD-AIR-AP
CD-AIR-ASAA
CD-AISA CD-AIR-
ANSA CD-AIR-
SC
CD-AIR-LHC
CD-LHC
CD-SC
20 OW2 Annual Conference
November 29, 2012
Enables choreography-centric SOA
While Sustaining decentralized service choreographies
While Supporting Future Internet, Large Scale
Focusing on IoS and IoT
Coordination Delegates are the “policemen” of the
choreography and ensure its proper execution/enactment,
following its coordination logic, formally defined by a CLTS
1/3 of the project time still to be completed, end of the
project on schedule for end of 2013
All CHOReOS-specific development will be released as
Open Source software (BSD-like license)
Conclusion
21 OW2 Annual Conference
November 29, 2012
Address : Pierre CHATEL Thales Defense & Security C4I Division
Campus de Polytechnique 1, avenue Augustin Fresnel 91767 Palaiseau Cedex - France
Mail : [email protected]
Phone: +33 (0)1 69 41 55 65
Contact
http://choreos.eu