1 / 12

ANR CIGC LEGO (ANR-CICG-05-11) Bordeaux, 2006, December 11 th

Learn how to deploy your application on grid resources, either manually or automatically, and hide the complexities of the grid infrastructure. Explore the steps of automatic deployment and the tools available for deployment planning and execution.

gpeterson
Download Presentation

ANR CIGC LEGO (ANR-CICG-05-11) Bordeaux, 2006, December 11 th

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. Automatic Application Deployment on GridsLandry Breuil, Boris Daix,Sébastien Lacour, Christian PérezPARIS Research TeamINRIA/IRISARennes ANR CIGC LEGO (ANR-CICG-05-11) Bordeaux, 2006, December 11th

  2. Controller SAN LAN scalars Visualization scalars Homogeneous cluster WAN SAN velocity Transport code Flow code Supercomputer Homogeneous cluster concentration How to Deploy my Applicationon Grid Resources?

  3. Manual Deployment • Discover available grid resources • Select grid resources for execution • OS, architecture compatibility • Map the application onto the selected resources • MPI processes • Components • Select compatible compiled executables • Upload and install executables, stage input files in • Launch processes on remote computers • Set configuration parameters of the application • Components' attributes • Network topology information Too complex!

  4. Grid stop reading your e-mails! Automatic Deployment • Automatic • Resource discovery • Execution node selection • File installation • Process launch • Application configuration • Hide application complexity • Hide grid complexity

  5. Generic Application Description • Translator • From specific to generic application description • Straightforward to write CCM Appl. Description MPI Appl. Description GridCCM Appl. Description CCM Appl. Description MPI Appl. Description GridCCM Appl. Description Generic Application Description CCM Planner MPI Planner GridCCM Planner Deployment Planner Plan Execution Plan Execution Plan Execution Deployment Plan Execution

  6. Identification of the Stepsof Automatic Deployment MPI Application Description CCM Application Description Resource Description Generic Application Description Control Parameters Deployment Planning Static Applications Deployment Tool Deployment Plan Execution Application Configuration

  7. ADAGE Feature List • MPI, JXTA, CCM application descriptions • Network topology description • Generic application description • Simple control parameters, simple planner • Deployment plan execution (RSH/SSH) • Basic file transfer support • Aware of file visibility (~NFS) • Does not check for already available files • Redeployment support • Either re-play or add/remove elements

  8. How Easy is it, in Practice? • As simple as A-B-C • adage-deploy –resource http://host/file.xml –application my_appl.zip –ctrl_param my_control_parameters • Grid resource description • Written once for all by grid admins • Optional control_parameters constraints • Keep control on the deployment process

  9. ADAGE & Grid5000 • ADAGE is not able to directly talk with OAR • PERL script to automatically generate resource description from OARgrid id • oarstat2resources.pl –g 6332 –outputfile r.xml • adage-deploy –inres r.xml …

  10. Some ADAGE results • JXTA • 1 peer == 1 process • M. Jan deployed • ~ 29.000 peers on ~ 145 machines in ~ 95 seconds • Most of the time take by ssh commands • CCM • 1 component == 1 process • H. Bouziane deployed • 4000 components on 974 processors machines • 432 machines on several G5K sites • Enable to CCM-plugin optimization

  11. Towards ADAGE v2 • Complete rewrite of ADAGE • By L. Breuil • Objectives of ADAGE v2 • Provide a clean code architecture • Ease the additions of • Programming model (GridCCM), ie plugins • Planner • Better back-end support • GAT, Taktuk, … • Support of “dynamic” applications • In cooperation with B. Daix, PhD

  12. Discussion • ADAGE: a model to support automatic application deployment • Ongoing/Future work • Finish ADAGE v2 (~ begining 2007 ) • Stabilize plugins API • Stabilize planner API wrt to resources • Dynamic application management • PadicoTM support? • Adapt application description in function of resources • DIET support • Not directly targeted • Fault tolerance • Application monitoring

More Related