Stockholm

1
GeneSyS Project Supervision of Distributed
Systems Jean-Eric BOHDANOWICZ, Antoine LAYDIER
European Aeronautic Defence and Space Company -
Launch Vehicles JeanEric.Bohdanowicz,
Antoine.Laydier_at_launchers.eads.net Alexander
VANKOV, Petr CHLIAEV, Vladimir VOLOSHINOV D-3-Grou
p GmbH Alexander.Vankov, Petr.Chliaev,
Vladimir.Voloshinov_at_d3group.com Andrey
SADOVYKH Laboratoire dInformatique, Université
Paris 6 (LIP6) Andrey.Sadovykh_at_lip6.fr
2
OUTLINE

• Introduction
• Objectives of GeneSyS
• Architecture
• Major Components
• Distributed Engineering as a Validation Scenario
• Distributed Training as a Validation Scenario
• Conclusions

3

• GeneSyS is a European Union project
  (IST-2001-34162) co-funded by the Commission of
  the European Community
• (started in March 02 with planned completion in
  August 04)
• Partners
• European Aeronautic Defense and Space Company
  Launch Vehicles (France)
• NAVUS (Germany)
• D-3-Group (Germany)
• HLRS (Germany)
• MTA SZTAKI (Hungary)
• LIP6 (University Paris 6, France)

4
Top-level objectives of the GeneSyS project

• To specify and develop an open, generic, modular
  and comprehensive supervision concept,
• To integrate and validate this supervision
  structure within various industrial contexts,
• To ensure that the vision of the proposed
  generic structure will be taken into account
  while defining new standards on distributed
  systems supervision and interoperability.

5
Common constraints faced by existing approaches
and practices

• Closed proprietary interfaces
• Proprietary protocols dependent on operating
  systems
• There is no general approach to supervise
  applications
• Homogeneous infrastructure (operating system,
  network, middleware)
• Problems with deployment on WAN (security
  issues, firewall settings)

6
GeneSyS General Architecture

• Architecture includes several types of
  components
• Collecting Agents
• Complex Agents
• Console Agents
• Communication CORE
• Directory Server
• Repository

7
GeneSyS Components (1/3)

• Directory Lookup service (DLS)
  register/store/search/remove reference to agents
• Data producing agents (DPA) register/un-registe
  r themselves on/from DLS, monitor
  application/systems, send data to consuming
  agents (consoles, repositories)
• Data consuming agents (DCA) register/un-registe
  r themselves on/from DLS, search registered
  agents on DLS, receive data from DPA/repositories
  (query/subscribe modes)
• Consoles special kind of DCAs supplied with GUI
  that present monitoring data in a human-readable
  form and interacts with DLS, DCAs and
  repositories
• Repositories special data consuming/producing
  agents to store/retrieve logs of monitoring data

8
GeneSyS Components (2/3)

• Basic architecture principles
• Uniformity all components (DLS, DPAs, DCAs,
  consoles, repositories) implement the same
  interface of an abstract GeneSyS agent
• Message oriented API all payload data are
  encapsulated in messages, which agents exchange
• XML syntax all messages represent XML messages
  to be valid according to special schemas (service
  messages, monitoring applications/systems
  specific messages)
• Direct connection between DPAs and DCAs DLS
  used only occasinally to register/un-register/look
  up
• As a result, GeneSyS prototype becomes
• Platform independent
• Rather easy to implement and scale

9
GeneSyS Components (3/3) General Overview
10
Technology

• In Version 1 (Q1/2003), a Publish/Subscribe and
  Query/Response communication model is implemented
• The communication is done via a XML based
  messaging protocol on top of SOAP-RPC
• Communication Core and Directory Lookup
  service are implemented in Java/Axis and
  HSQLDB/Java relational database engine
• The implementations are done using C/gSOAP,
  PHP/nuSOAP, C/.NET and Java/Axis
• Information is being regularly updated on
  http//genesys.sztaki.hu

11
Distributed Engineering as a Validation Scenario
(1/2)
ATV spacecraft development
12
Distributed Engineering as a Validation Scenario
(2/2)
13
Distributed Training as a Validation Scenario
(1/2)

• Several complex real-time simulators
  interconnected to simulate a space mission
  rehearsal.
• Training activities of astronauts, ground
  controllers and technical operators in a
  distributed environment will be supported by
  GeneSyS infrastructure.

14
Distributed Training as a Validation Scenario
(2/2)

• Three different kinds of users will use this
  application and GeneSyS
• Trainees (astronauts and ground controllers)
• Instructors
• Technical operators in charge of controlling the
  whole infrastructure (network, systems, RTI and
  involved applications).
• The GeneSyS agents will implement a front-end to
  Management Object Model of HLA to supervise RTI
  and Federations. Besides them, some other Agents
  will be deployed for monitoring of
• - WAN
• - Simulation hosts
• - Groupware tools/facilities.

15
Conclusions

• GeneSyS proposes an open and extensible
  supervision framework
• GeneSyS uses commonly accepted XML-based
  protocols and open interfaces for inter-agent
  communication
• GeneSyS provides generic agents and consoles for
  system and network supervision
• GeneSyS provides robust infrastructure for
  application supervision