1 / 15

A Grid Service for Management of Multiple HLA Federate Processes

A Grid Service for Management of Multiple HLA Federate Processes. Katarzyna Rycerz, Marian Bubak , Maciej Malawski, Peter M.A. Sloot ICS AGH, Kraków & UvA, Amsterdam. Outline. Motivation Grid HLA Management System HLA-Speaking Service for multiple processes

verena
Download Presentation

A Grid Service for Management of Multiple HLA Federate Processes

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. A Grid Service for Management of Multiple HLA Federate Processes Katarzyna Rycerz, Marian Bubak,Maciej Malawski, Peter M.A. Sloot ICS AGH, Kraków & UvA, Amsterdam

  2. Outline • Motivation • Grid HLA Management System • HLA-Speaking Service for multiple processes • Performance results on the example of N-body simulation of dense stallar system • Conclusions and future work

  3. Interactive simulation HLA Grid HLA Management System Grid Infrastructure (Grid Services,GRAM, GSI, MDS) Grid HLA Management System (G-HLAM) Motivation • A system designed for management and steering of HLA-based distributed interactive simulations in a non-dedicated, shared and unpredictable Grid environment • Allows for application performance to achieve the most efficient execution on the available resources in the Grid. • Uses the High Level Architecture (HLA) - the standard for distributed interactive simulations

  4. G-HLAM Architecture User Site A Application Benchmark Application Broker HLA Speaking Federate Services Monitoring Client Service Code Services RTIExec Migration Service Service Site B Broker Infrastructure Service Monitoring Migration HLA Services HLA Performance Support Interfacing Bus Decision Services Services Broker Support Service Services Application N - th Grid site supporting HLA Monitoring Main Service Manager Broker Support HLA Speaking Services Site Site C C Service RTIExec HLA Registry Registry Migration Interfacing Service Service Support Services RTIExec Services Service Grid site supporting HLA • HLA interfacing services • HLA-Speaking Service for managing federates • (partly presented on GAMW’03 and DSRT’03) • RTIExec Service for managing RTIExec (coordination process in RTI) • Broker for setting up a federation and making migration decisions • Broker decision services • Registry for storinglocation of HLA-speaking services • Infrastructure Monitoring/Benchmarks for checking environment of HLA service • (presented on ICCS’04) • Application Monitoring for monitoring performance • (presented on DSRT’04) • Migration support services • Migration Servicefor performing migration • Migration partly presented at GAMW’03 and DSRT’03

  5. Site B Site A Site C HLA-Speaking Service RTIExec Service HLA-Speaking Service Management level Grid Service Communication RTI bus Communication Application level RTI Exec Fed Fed Fed Fed Fed Functionality of HLA-Speaking Service • Manages execution of legacy HLA federates on a single site • Submits federates on its site and forwards saving/restoring requests • Two kinds of HLA-Speaking Services were created: • For single federate process (presented on GAMW’03, DS-RT’03) • For multiple federate processes (presented here)

  6. HLA-Speaking Service multiple processes HLA-Speaking Service Grid Service Porttype • Command for submission based on globus RSL • GRAM used for actual submission • Control federation for sending save and restore commands • GridHLA Controller library as an interface between user code and G-HLAM HLA-Speaking Porttype Process 1 Process N Start GHCL GHCL GHCL GHCL Save state GHCL GHCL Restore Control Federate Control Federate Control Federate User Federate 1 User Federate N save, restore control federation at site A user federation HLA-Speaking Service Grid Service Porttype HLA-Speaking Porttype Process1 Process M Start GHCL GHCL GHCL GHCL Save state GHCL GHCL Restore Control Federate Control Federate Control Federate User Federate 1 User Federate M control federation at site B save, restore

  7. migrate migrate from A to B startControl requestMigrationSave save save resign user fed resign control fed save done save done take and submit get codes and checkpoints restore join application fed join control fed restore done done done done Federate Migration multiple processes HLA Speaking Service site B HLA Speaking Service site A GridFTP Server Site A Federates site B Federates site A Monitoring Service Broker Service RTI Migration Service

  8. Possible HLA Migration Support Approaches How to migrate one federate without disturbing others ? • Develop new HLA standard implementation • Transparent, but sticks to particular implementation • Use HLA Management Object Model to save federates state • No support for user state, MOM information can get old (no state coherency) • Use HLA save/restore API • Assures internal RTI state coherency (and HLA RTI specific services), but no support for user data • Sophisticated migration algorithms • [Z. Yuan at al. - ICCS 2004]– efficient, but require from a user to port his HLA application to some high level library

  9. Grid HLA Controller Library (GHCL) Design • We have chosen to: • Use HLA save API • Build runtime support to facilitate that API • Build runtime support to facilitate saving user data • GHCL contains functions to: • Start up and connect to RTI API classes • Check if external (Migration Service) save/restore request came • Check if internal (RTI) save/restore request came • Save/restore user values

  10. Testbed Infrastructure

  11. Application Architecture • N-body simulation of dense stellar system parallelized with MPI • Requires variable time step in simulation (i.e. for binary stars) • Many stars to calculate (order 10^6) • requires computational power • A user can change stars parameters at any time during simulation

  12. Impact of Migration 20 MPI Processes, 24000 stars

  13. Migration Stages 5000 stars

  14. Conclusions HLA-Speaking Serviceenables efficient management ofthe execution of HLA federates on the Grid: • provides universal interface for user HLA federates to G-HLAM, • used for running, saving and restoring one or more federate processes on the Grid site on which it resides, • the whole Grid site is efficiently used by taking advantage of GRAM interface to local job manager, • GridHLAController library is an easy to use API for interaction of user codes with the HLA-Speaking Service, • HLA standard advanced features useful for distributed simulation are ported to the Grid, • legacy HLA applications are adapted to the Grid environment in a robust and efficient way.

  15. Future Work • Possible extension of the G-HLAM functionality • Broker Service • many already exist • Performance Decision Service • Fault tolerance • migration mechanisms is a first step we already have • CrossGrid Medical Application in GHMS • Technological migration • WSRF • Component technologies

More Related