CHOReOS presented @CeBIT 2013, Hannover, Germany

CeBIT 2013 – Open Source Forum
Mars 9th, 2013
Dr. Pierre CHÂTEL – Thales

2
Mars 9th, 2013
Help with the next big step in
system architectures
Context
…
Interconnected
mainframes
through dedicated
channels
Local networks of
small computers
Future Internet
Large Scale
Highly
Distributed
Systems
High
Heterogeneity
Cloud
Computing
Today
Individual
“disconnected”
computers
1980
Internet
revolution
Interconnected
computers
around the globe
Web Services

3
Mars 9th, 2013
Choreography-centric SOA, middleware and tooling for
Services & Things
 Why?
Need to support Future Internet (Internet of Services (IoS) and Internet of
Things (IoT)), Large Scale, Distribution in modern systems
 How?
 Enabling service choreographies definition and “execution”
 Introducing a specific Development Process and Integrated Development and
Runtime Environment (IDRE) for coordination of services through choreographies
CHOReOS
Future
Internet
Ultra
Large
Scale
CHOReOS

4
Mars 9th, 2013
Future Internet? A reminder
FP7 / Cross-ETP (European Technology Platforms) vision
http://www.future-internet.eu
Future Networked Society
Future Network Infrastructure
Internet
of
Contents
and
Knowl.
Internet
of
Things
Internet
of
Services
Internet
by and
for
People
Accomodation of
all users
requirements
Interactive
multimedia content
everywhere
Context aware
autonomic
objects
Permanent
seamless
services
Scalable & dynamic routing and addressing Security, privacy, trust
Efficient data & traffic management Availability, ubiquity, simplicity
Adaptability to heterogeneous environments Energetic and economic sustainability

5
Mars 9th, 2013
CHOReOS manages:
Major characteristics of “Internet of Things”
 High heterogeneity: totally different objects in terms of
functionality, technology and application fields that need to be
integrated
 Scalability: large number of “objects” (Pervasive technologies) that
need to communicate with each-other in a meaningful way
Major characteristic of “Internet of Services”
 Distributivity: numerous service orchestrations, dispatched over
the Internet, that need to communicate through message
exchanges, but avoiding a single point of control – or because a
single control point cannot be defined in a specific business
case!
Future Internet & CHOReOS
Future Networked Society
Future Network Infrastructure
Internet
of
Contents
and
Knowl.
Internet
of
Things
Internet
of
Services
Internet
by and
for
People
Accomodation of
all users
requirements
Interactive
multimedia content
everywhere
Context aware
autonomic
objects
Permanent
seamless
services
Scalable & dynamic routing and addressing Security, privacy, trust
Efficient data & traffic management Availability, ubiquity, simplicity
Adaptability to heterogeneous environments Energetic and economic sustainability

6
Mars 9th, 2013
Duration:
October 2010 –
September 2013
Consortium of 15
partners:
7 industrials
10 academics
Total budget:
~ 9M€
European programme:
Call FP7-ICT-2009-5
 Grant n°257178
CHOReOS at a glance

7
Mars 9th, 2013
Consortium
7 industrials 10 academics
UOI
SSEI
UDA

8
Mars 9th, 2013
1. Choreography
2. Use Case and BPMN models
3. Main CHOReOS solutions
4. OW2 Consortium, Open Source and
Community strategy
5. Conclusion
Outline

9
Mars 9th, 2013
1. Choreography
1. Orchestration vs. Choreography
2. Choreography & SOA
Community strategy
5. Conclusion
Outline

10
Mars 9th, 2013
Orchestration vs. Choreography
Orchestration:
Local / centralized
perspective
"Each player in the
orchestra strictly follows
instructions from the
conductor“
Choreography:
Global / distributed
perspective
“Dancers dance following a
global scenario, without a
single point of control”

11
Mars 9th, 2013
Choreography & SOA
Service orchestration:
 Refers to an executable
business process, with a
specific (business) goal
 Represents control from one
party’s perspective (the
orchestrator)
 Interactions occur at the
message level
 Between orchestrator and services
 Message sequence controlled by
orchestrator
 Allows recursive combination
Service choreography:
 Describes a protocol for peer-to-
peer interactions
 Legal sequences of exchanged
messages between peers
 Tracks the message exchange
among multiple parties
 More collaborative: allows each party
involved in the interaction to describe
its part
 Guarantees interoperability by
reflecting obligations and constraints
between parties
 Interactions still occur at the
message level
 But directly between services

12
Mars 9th, 2013
Choreography & SOA
Choreography
Orchestration
WS WS
WS
Orchestration
WS WS
WS
Composite WS Composite WS
(..)
Orchestrator Orchestrator
Message exchange
Message exchange
Complex conversations
beetween orchestrations
No “Orchestrator” for choreographies  CHOReOS provides the middleware
that enables their distributed enactment = execution of their coordination logic,
dealing with control flow discrepancies in conversations

13
Mars 9th, 2013
Community strategy
5. Conclusion
Outline

14
Mars 9th, 2013
 “Passenger-friendly Airport”
 Context: air transportation / service to passengers
 Goal: improvements in services, airport fluidity  proof of concept
 Bad weather at destination  flight rerouted to another airport
 Passengers p.o.v.: stress, lack of information, delays everywhere
 Choreographies are introduced as part of a global solution
 Already existing business processes (orchestrations) for specific/local
parts of the scenario, with well-known orchestrators (e.g. air traffic control,
airport authorities, airlines)
 But lack of broad-spectrum/global choreographies between these areas of
responsibility
Use case
At home
Inside
airport
In plane Landed
Image: photostock /
FreeDigitalPhotos.net

15
Mars 9th, 2013
CHOReOS innovation highlights
 To enable dynamic rebinding and replacement of services
(loose coupling)
 Distributed coordination
Partners contributions
 THALES: business Web services provider
 Inria: large scale aspects through Things (sensors, actuators)
interoperability framework
 Linagora: bus provider (EasyESB)
Scenario particularly suited to illustrate FI/scalability
aspects
 Average of 180.000 passengers per day at an Airport like CDG
 Number that varies greatly depending on the airport, time of the day,
season, …
Use case

16
Mars 9th, 2013
 Two paradigms [Decker, 2008]:
I. Interconnected Interfaces Modeling: choreography logic split across its
participants through the roles they play, as specified by their interfaces.
II. Interaction Modeling: choreography logic as a workflow, elementary
interactions represent message exchanges between participants
BPMN 2
BPSS
Let’s Dance
WS-CDL
WSCI
WSFL
BPEL4Chor
BPMN1.x
Interface (type I) Interaction (type II)
IndependentDependent
BPMN for Choreography specification

17
Mars 9th, 2013
BPMN (Business Process Modeling Notation)
 “De-facto standard for process modeling on the implementation
independent level” [Decker, 2008], maintained by the OMG
 v2.0 (2010) introduces type II paradigm (Interaction):
 each step (Choreography Task) involves at least two participants
BPMN for Choreography specification
Seller
Customer
Order request
Seller
Customer
Order
confirmation
Seller
Customer
Deliver product
Order
Confirmation Product

18
Mars 9th, 2013
Use case – Global choreography
 Passengers arrival handling and
tracking at the airport

19
Mars 9th, 2013
Use case – Before arrival

20
Mars 9th, 2013
Use case – After arrival

21
Mars 9th, 2013
Use Case - Expected impact
Before CHOReOS
At alternate airport
 Delays everywhere (plane
logistics, handling
passengers luggage, …)
At airline level
 impervious dedicated
logistics for each situation
For passengers
 Poor indications
 Extra costs
 Waste of time
 … extra stress !
After CHOReOS
At alternate airport
 Less delays in rerouting-
consequences
At airline level
 Efficient coordinated
logistics
 Costs reduction
 Improved flight rescheduling
process
For passengers
 Better information
 Less waste of time and
money
 Improved airline/brand
image

22
Mars 9th, 2013
1. Abstractions and models
2. IDRE
3. Development process
4. Choreography synthesis
Community strategy
5. Conclusion
Outline

23
Mars 9th, 2013
Initial need to identify key architectural abstractions for
choreographies in the FI
 Dedicated architectural style to face FI challenges based
on SOA
 Web-based services at large (WS* & Rest, ...)
 Paradigm independent definition of “services”
 Highly heterogeneous interaction paradigms
 Multi-Paradigm Connectors to sustain interoperability
 Choreography-based composition of services
 Distributed Coordination Algorithm
  Synthesis of decentralized choreographers called
Coordination Delegates
From abstractions and models…
Abstractions and
models

24
Mars 9th, 2013
… to IDRE
Abstractions and
models
Service-oriented
middleware
Service
governance,
verification, and
validation
Choreography-
centric
development process
Integrated
Development and
Runtime
Environment (IDRE)
The “Integrated Development and Runtime Environment”
 Aim: integrate all CHOReOS components in one platform

25
Mars 9th, 2013
IDRE is all about…
 Defining integration requirements
 Development, design, enactment,
governance and monitoring
requirements for a choreography
 Defining the overall Architecture
 Identifying the integration Dependencies
 Defining the integration Plan
 Implementing the CHOReOS Testbed
 Releasing integrated CHOReOS software
 Packaging and delivering software prototypes
 Providing developer and user manuals
 The CHOReOS IDRE relies on a modular service-oriented
architecture. The IDRE top-level components are following:
 CHOReOS Development Environment
 The CHOREOS Middleware: composed of the eXtensible Service Access (XSA),
eXecutable Service Composition (XSC), eXtensible Service Discovery (XSD),
and Cloud & Grid Middleware
 CHOReOS Governance and V&V Framework
IDRE
Integrated
Development and
Runtime
Environment (IDRE)

26
Mars 9th, 2013
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
Choreography-
centric
development process

27
Mars 9th, 2013
Choreography-
centric
development process

28
Mars 9th, 2013
Choreography-
centric
development process

29
Mars 9th, 2013
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), based on
actual behaviors + expected behaviors of services
 CDs will manage the services at runtime,
based on the choreography coordination logic
Choreography synthesis
Service-oriented
middleware

30
Mars 9th, 2013
Choreography synthesis – Step 1
Airport UC choreography CLTS extract
Service-oriented
middleware

31
Mars 9th, 2013
Choreography synthesis: CLT projection – Step 2
Choreography CLTS Projected expected participant CLTSs
Service-oriented
middleware

32
Mars 9th, 2013
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
Service-oriented
middleware

33
Mars 9th, 2013
SOA & Coordination Delegates
Choreography
Orchestration
WS WS
WS
Orchestration
WS WS
WS
Composite WS Composite WS
(..)
Orchestrator Orchestrator
Message exchange
Message exchange
Complex conversations
beetween orchestrations
CD CD
Service-oriented
middleware

34
Mars 9th, 2013
1. Choreography
Community strategy
1. OW2 Consortium
2. OW2 impact as a CHOReOS member
3. Open Sourcing CHOReOS
4. CHOReOS as part of OW2 strategy
5. FISSi: OW2 Future Internet Software and Services
initiative
5. Conclusion
Outline

35
Mars 9th, 2013
OW2 Consortium
''A global community working together to
develop open source infrastructure software*
and to foster a vibrant business ecosystem''
*Includes generic solutions in all product categories and middleware at large, including tools for the
development, deployment and management of distributed applications

36
Mars 9th, 2013
OW2 Community activities
Projects
 Technology Innovation
Initiatives
 Business Leverage
Local Chapters
 Global Governance
Open source infra-
structure software
Community governance
SQuAT Quality program
Joint members efforts
Open to non-members
Market driven activities
Will drive and help
grow community locally.

37
Mars 9th, 2013
Foster community building to extend project value,
sustainability
 Attract people that are interested in choreography technologies :
enables the pursuit of the development and business activities
beyond the original scope of the project.
OW2 act as a business ecosystem platform for
CHOReOS. Providing:
 Infrastructure services: technical resources
 Governance services: decision making rules
 Marketing services: branding & communication
Drive OSS approach at the project level
 Help define deliverables structure for community sharing
 Help select open source licenses
 Move project to an open source community
OW2 impact as a CHOReOS member

38
Mars 9th, 2013
Why OSS ?
Facilitates deployment of complex technologies
 Helps combine multiple technologies and know-how from
independent providers
 Makes multi-tier cooperation easier by enhancing trust and reducing
coordination costs
Lower barriers to access
 Legal barriers: open source licences enable sharing
 Economic barriers: no monetary entry cost
IDRE code structure
 Modular project structure to facilitate third party contributions
Chosen licenses
 IDRE development modules
 Eclipse Public Licence (EPL)
 Affero General Public License (AGPL)
 IDRE runtime modules : Lesser General Public License (LGPL)
 Documentation: Creative Commons License
Open sourcing CHOReOS

39
Mars 9th, 2013
The OW2 Future Internet Software and
Services initiative (FISSi)
 An “initiative”: “joint efforts by OW2 Members
aimed at facilitating the use of OW2
technologies [here including CHOReOS] by
mainstream Systems Integrators, End-Users
and Software Vendors”
 An opportunity: today's Internet shows its
limitations in the context of emerging and
pervasive mobile platforms, IoT becoming a
reality, a new world of Distributed Systems
of Systems… as Identified by the EU through
the EFII PPP.
 The plan: provides our definition of Future
Internet, and solutions, as formalized in FISSi
 Third Initiative after the Open Cloudware and
Business Intelligence initiatives
 Participating Strategic Members: INRIA, Orange Labs
CHOReOS as part of OW2 strategy

40
Mars 9th, 2013
FISSi Targets One of Three FI Challenges
Networks and shared infrastructure
Services and applications
Media and content
FISSi mission
Develop, integrate, deliver and promote FI-oriented open
source technologies
Drive OW2 projects evolution toward Future Internet
Promote and integrate the CHOReOS platform
Leverage OW2 Open Source Cloudware initiative
In FISSi, CHOReOS will be the engine that powers
the very large scale interconnection of smart data,
objects and services

41
Mars 9th, 2013
Software Vendors
Systems Integrators
Academia
Enterprises
SMEs
Public Entities
Consultants
OW2 CODE BASE
FI trends
New application
architecture
OSS FI software
Use cases and
best practices
OW2 Future Internet
Software and Services
Business Ecosystem
VISION & GOALS
OW2 FISSi Participants
CHOReOS
GASP
Open Mobile IS
Petals
Service4All
A Business Ecosystem at Work

42
Mars 9th, 2013
1. Choreography
Community strategy
5. Conclusion
Outline

43
Mars 9th, 2013
CHOReOS prepares SOAs for the Future Internet (FI)
 While Sustaining decentralized service choreographies
 While Supporting Large Scale
 Focusing on IoS and IoT
CHOReOS offers innovative solutions (middleware, tooling)
for the FI:
 e.g. usage of choreographies, Coordination Delegates
End of the project on schedule for end of 2013
All CHOReOS-specific development will be released as
Open Source software
The pursuit of the development, valorization and business
activities beyond the original scope of the project is
enabled through the FISSi OW2 initiative
Conclusion

44
Mars 9th, 2013
Address :
Dr. Pierre CHATEL
Thales Defense &
Security C4I Division
Campus de Polytechnique
1, avenue Augustin Fresnel
91767 Palaiseau Cedex - France
Mail :
pierre.chatel@thalesgroup.com
Phone:
+33 (0)1 69 41 55 65
Contact
http://choreos.eu

CHOReOS presented @CeBIT 2013, Hannover, Germany

Recomendados

Recomendados

Mais conteúdo relacionado

Mais procurados

Mais procurados (14)

Semelhante a CHOReOS presented @CeBIT 2013, Hannover, Germany

Semelhante a CHOReOS presented @CeBIT 2013, Hannover, Germany (20)

Mais de choreos

Mais de choreos (10)

Último

Último (20)

CHOReOS presented @CeBIT 2013, Hannover, Germany