1 / 10

First thoughts on job management

First thoughts on job management. Massimo Sgaravatto INFN Padova. JRA1/SA1. I personally don’t like too much this separation between support/maintenance (SA1) and new developments (JRA1) Given a certain product, the relevant people are the same JRA1 workplan highly affected by SA1 activities

yon
Download Presentation

First thoughts on job management

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. First thoughts on job management Massimo Sgaravatto INFN Padova

  2. JRA1/SA1 • I personally don’t like too much this separation between support/maintenance (SA1) and new developments (JRA1) • Given a certain product, the relevant people are the same • JRA1 workplan highly affected by SA1 activities • Product teams are supposed to be the core of the activities • One should care about JRA1 and SA1 only when filling the timesheets • As also stated in the EMI workshop • We will see if this organization works

  3. Product teams • Which are the relevant product teams ? • ARC ? • gLite • We used to have: • Workload Management System (WMS) • CREAM CE • Batch system support • MPI • Probably 2 and 3 can/must be merged • Unicore ?

  4. Workplan • In the proposal a few specific items are presented • But basically it is (rightly) written that we have to meet the requirements coming from our customers • We are not starting from scratch • Our products are already in use • We all should already have some feedbacks and a list of new requirements/functionality to be implemented •  Each product team should be able to prepare a list of items already in their agenda

  5. Workplan (cont.ed) • The initial workplan will change • New items could (actually for sure will) be added on user requests • Workplan highly impacted by support and maintenance issues • Which have higher priority wrt new developments

  6. Workload Managers and Compute Elements • Standard interfaces (see next) • Some new functionality/improvements • Bulk operations • Interactive access to the running jobs • Load balancing mechanisms • … • Each product team should be able to provide some specific plan here • Explore the utilization of virtualized resources • Also in the “Infrastructure area” • Who does what ? • INFN WNodes, …

  7. Common execution interface • Activities are already proceeding in two fron lines: • AGU • Likely to find an agreement quite soon • PGI • Wider community, but likely taking much much more before finalizing it • Approach • First implementation based on AGU • Refer to PGI specification later, when ready • Consider CEs first. Higher level services (e.g. WMS) later

  8. Common clients and APIs • Consolidation of many different clients and APIs in well defined SDKs and user interfaces • Adoption whenever possible of high level application oriented APIs like SAGA • Just for the common interface ? • Portlets (in collaboration with other projects) • Which ones ?

  9. MPI and parallel job support • Make simpler, more trasparent, etc. the support of MPI and parallel jobs • For gLite (where MPI-START is used) initial work based on the recommendations of the MPI WG • What about ARC and Unicore ? • Some common works ?

  10. Miscellaneous • Other common developments between ARC, gLite and Nordugrid besides the common interface already identified ? • How are we affected by the security plans ?

More Related