1 / 11

GridPP Meeting 17 th September 2002

GridPP Meeting 17 th September 2002. After the retreat Emphasis on supporting current release and bug fixes Quality assurance (UK involvement) Lower priority to future functionality Fortunately everybody seems more happy with 1.2 than 1.1.4. This is more of a problem for WP 1 than other WPs

denton
Download Presentation

GridPP Meeting 17 th September 2002

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. GridPP Meeting 17th September 2002

  2. After the retreat • Emphasis on supporting current release and bug fixes • Quality assurance (UK involvement) • Lower priority to future functionality • Fortunately everybody seems more happy with 1.2 than 1.1.4

  3. This is more of a problem for WP 1 than other WPs as release 2 is NOT based on release 1.2 Large parts of the code will be reused however there is a brand new architecture (see deliverable D1.4)

  4. Reasons: Simplify flow control Increase the reliability and stability Minimise duplicate persistent information about the same event Support for new functionality Make WP 1 software more useable by other communities… possible to take parts.

  5. From D1.4

  6. UI although there are changes, user interaction will be unchanged apart from additional functionality. Network server takes input from UI and if valid passes it on to the Workload Manager, uses Protocol to determine whether or not conforms to agreed standards. Workload Manager is the central part of new architecture. Given a valid request it performs the required action to satisfy them … this may well involve other components.

  7. RB is responsible for performing matchmaking, ranking and scheduling strategy (easy hooks to be provided). Reservation and co-allocation will be provided agent. LRMS need to support reservation and have this published in their MDS Job interdependencies will be handled by DAGman. Job partitioner handles job partitioning.

  8. Helper is a class that has a single that contains a single method, resolve(), which takes one set of jdl and returns another e.g. in the case of the RB the it may be sent user jdl and return the jdl corresponding to the matched resource.

  9. New functionality in release 2 (I am not up to date as I missed Budapest meeting and so don’t know if everything is on time) Partitioning and checkpointing Dependent jobs Reservation and co-allocation Accountancy MPI jobs

  10. By release 2 all these should have both ClassAd implementations eg [ Type = “Reservation”; ReservationType = “computing”; ReservationStart = 1021539656; ReservationEnd = 1021541000; ReservationDuration = 300; ReservationParameters = [ nodes = 3; ]; ... And as APIs

  11. Conclusions: Priority is making what is already there work reliably Complete redesign of the WP 1… however reuses large amounts of exiting code. QA is particularly important in an environment were such large changes are being made.

More Related