Differences between revisions 4 and 5
Revision 4 as of 2007-04-03 09:16:15
Size: 2964
Editor: MarkNorman
Comment:
Revision 5 as of 2013-05-17 16:26:48
Size: 2964
Editor: localhost
Comment: converted to 1.6 markup
No differences found!

Project notes about Use Cases for Advance Reservation and Co-allocation. Presented at PSNC Workshop on Resource Management, Poznan, 22 October 2003 by Stephen Pickles http://www.realitygrid.org http://www.man.poznan.pl/10years/papers/pickles.ppt

  • In summary:
    • Computational steering + remote, on-line visualization demand:
    • co-allocation of HPC (processors) and visualization (graphics pipes and processors) resources
    • at times to suit the humans in the loop
    • advanced reservation
    • For medium to large datasets, Network QoS is important
    • between simulation and visualization,
    • visualisation and display
    • Integration with Access Grid
    • want to book rooms and operators too
    • Cannot assume that all resources are owned by same VO
    • Want programmable interfaces that we can rely on
    • must be ubiquitous, standard, and robust
    • Reservations (agreements) should be re-negotiable
    • Hard to change attitudes of sysadmins and (some) vendors
  • Notes:
    • Use case = 'Steering Grid Service' (SGS) (SGS provides public interface to application’s steering controls. Use standard grid service technology to do steering. Easy to publish our protocol. Interoperability with other steering clients, portals, or Modular Visualisation. Environments with steering capabilities. Application source is unchanged. SGSs used to bootstrap direct inter-component connections for large data transfers)
    • Scheduling requirements (A typical RealityGrid scenario involves. A simulation running on a massively parallel system, coupled to a visualization running on a high-end graphics system.)

    • The two sets of resources will often be located on remote systems owned and administered by different organisations. (The administration teams within the two organisations, if aware of each other’s existence at all, are unlikely to have established comprehensive Service Level Agreements or Memorandums of Understanding.)
    • Reservations: (The ability for a user to reserve processors and graphics pipes manually without involving system administrators would remove a significant barrier to the routine use of computational steering. The ability for an agent or service to do the same will be important for resource brokers later. ...Therefore want ability to reserve network bandwidth with certain quality of service characteristics, using the same protocols as for reservation of processors.)
    • More complex configurations (RealityGrid's "deep track" is enabling more complex configurations involving finer-grained componentisation. The application is composed out of more than two communicating components, each of which must be deployed onto (possibly remote) computational resources at run-time. Co-allocation mechanisms must therefore be robust and scalable. If we're paying for usage, and cancelling a reservation incurs a charge, then two-phase commit is highly desirable.)

    • References reservation models

ESPGRIDwiki: UsecasesAdvancedreservation (last edited 2013-05-17 16:26:48 by localhost)