1 / 5

Deployment of DIET and JuxMem using JDF: ongoing work

Deployment of DIET and JuxMem using JDF: ongoing work. Mathieu Jan Projet PARIS. Rennes, 4 May 2004. JXTA Distributed Framework: JDF. A framework for automated testing of JXTA-based systems from a single node (control node) http://jdf.jxta.org/ JDF: several shell scripts Deployment

desirae-fowler
Download Presentation

Deployment of DIET and JuxMem using JDF: ongoing work

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. Deployment of DIET and JuxMem using JDF: ongoing work Mathieu Jan Projet PARIS Rennes, 4 May 2004

  2. JXTA Distributed Framework: JDF • A framework for automated testing of JXTA-based systems from a single node (control node) • http://jdf.jxta.org/ • JDF: several shell scripts • Deployment • Configuration of JXTA peers • Launch peers • Collect logs and results files of each node • Analyze results on the control node • Cleanup deployed and generated files • Kill remaining processes • Update resource • Ongoing work: • Use the new ext.config package to generate PlatformConfigs • Calvin Cheng (Sun Microsystems)

  3. Deployment of DIET and JuxMem • Goal: first step towards combining DIET-JuxMem • Common tools for testing • Based of DIET 1.0 • How: using JDF • 1 Java class for each entity DIET (Agent, SeD, Client) • Deployment of DIET configuration files • Use of NFS for libraries • Between DIET and JuxMem: Java Native Interface (JNI) • For each Java class: startSeD or StartAgent or StartClient • Based on the scalar example of DIET • Build shared libraries loaded by the JVM

  4. Deployment of DIET <profile name=“MA" instances="1“ > <bootstrap class="juxmem.service.test.diet.Agent“ delay=“0”> <arg value=“MA.cfg“ /> </bootstrap> </profile> <profile name=“LA" instances=“1“ > <bootstrap class="juxmem.service.test.diet.Agent" delay=“5”> <arg value=“LA.cfg“ /> </bootstrap> </profile> <profile name=“SeD" instances=“1“ > <bootstrap class="juxmem.service.test.diet.SeD" delay=“10”> <arg value=“SeD.cfg“ /> </bootstrap> </profile> <profile name=“Client" instances=“1“ > <bootstrap class="juxmem.service.test.diet.Client" delay=“15”> <arg value=“SeD.cfg“ /> </bootstrap> </profile> Client MA LA SeD

  5. Ongoing and Future work • Deployment on several clusters • May require modifications in JDF • Where to put DIET entities and JuxMem peers? • Shared • Concurrently • DIET using JuxMem • Real calls to JuxMem API • Alloc, write/put, read/get

More Related