1 / 8

Datamat Status Report

Datamat Status Report. F. Pacini fabrizio.pacini@datamat.it. Outline. APIs/commands GUI Some Issues. APIs - C++ (1/4). Development of C++ API terminated for the classes in the API spec JobId JobAd Job JobCollection NotificationAd UserJobs UserCredential

forrest-marshall
Télécharger la présentation

Datamat Status Report

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. Datamat Status Report F. Pacini fabrizio.pacini@datamat.it

  2. Outline • APIs/commands • GUI • Some Issues

  3. APIs - C++ (1/4) • Development of C++ API terminated for the classes in the API spec • JobId • JobAd • Job • JobCollection • NotificationAd • UserJobs • UserCredential • Currently collaborating with Francesco G. for the DAG-related classes

  4. APIs - Java (2/4) • Completely rewritten • JobId • Completely rewritten using the Java ClassAd package • JobAd • Use of JNI to wrap RB/LB APIs (development still on going) • Job • JobCollection • NotificationAd • UserJobs • Use of Globus CoG package • UserCredential

  5. APIs/commands (3/4) • Never tested integration with RB/LB • Only unit tests could be performed • stubs for RB/LB • ClassAd C++/Java not always aligned • There are missing Java methods • Not continuously maintained • Will have to change behavior in some methods/commands due to the new architecture. Many details are still missing for the job control commands: • Job cancel • Job output retrieval • Input sandbox transfer

  6. APIs/commands (4/4) • Gradually including new functionalities: • MPI - done • Interactivity – done only for the command-line • Not yet clear how to manage it within the API • DAG – just started • Checkpointing – not yet started • We strongly depend on the other components • Investigating possible wrapping (SWIG) of ClassAd/JobAd for use in the command line UI

  7. GUI • JDL Editor • Development almost complete • Accept/produces JDL/XML job descriptions • Need to be updated with new attributes • Also thinking to a ‘DAG Editor’ • Job Monitoring component • Development begun • Short term/Long term solution agreed with CESNET People • Polling • Notification (from R-GMA?) • Is a Job Submission graphical component needed? • API seems to be sufficient • Will investigate possibility to write a pure Java Network Client (incl. Security) • As an applet seems not to completely solve the security problem raised during Genius demo (proxy)

  8. Some Issues • JDL: • Make [] mandatory • Make JDL case sensitive (as classad is) • Multiple line attributes (\ no more needed) • Slightly change comments formats (//, #) • Support for JDL file containing multiple job descriptions • Put OutBoundIP automatically in job requirements if staging in/out is needed (it is already the case for interactive jobs) • Put Active automatically in job requirements • Impacts from GLUE • Bypass (grid_console) • Separate component (third party) • Part of UI

More Related