This is a static archive of the previous Open Grid Forum GridForge content management system saved from host forge.ogf.org file /sf/wiki/do/viewPage/projects.glue-wg/wiki/NAREGI_Use_Cases at Fri, 04 Nov 2022 18:48:40 GMT SourceForge : View Wiki Page: NAREGI_Use_Cases

Project Home

Tracker

Documents

Tasks

Source Code

Discussions

File Releases

Wiki

Project Admin
Search Wiki Pages Project: GLUE     Wiki > NAREGI_Use_Cases > View Wiki Page
wiki1764: NAREGI_Use_Cases
User stories in NAREGI
  • Story 1
    • Card: A grid scheduler can search for computing resources which meet users' requests for their job execution
    • Conversations:
      • what are computing resources under a job queue: OS (name, type and version) , SMP size, total number of computing nodes and physical/virtual memory size
      • which VO are permitted to submit a job
      • where is a job submitted: URI of job execution services on the computing resources and job queue name
      • how is a job submitted: Type of the job execution service
    • Acceptance test:
      • List of candidate resources for a job should be returned by the information services according to resource properties described in a JSDL document.
      • The same resource should appear once in the candidate list returned by the information services.

  • Story 2
    • Card: A grid scheduler can distinguish which LRMS accept an advanced resource reservation request or don't accept jobs without reservation (reservation necessary).
    • Conversation:
      • which LRMS accept an advanced reservation request for a job execution
      • which LRMS are reservation necessary
    • Acceptance test:
      • A user should be able to submit a job with advanced resource reservation.
      • A user should be able to submit jobs with and without advanced reservation at the same time.

  • Story 3
    • Card: A grid scheduler can distinguish which LRMS accept an array job submission request.
    • Conversation:
      • which LRMS are available for a bulk job submission
    • Acceptance test:
      • A grid scheduler should be able to submit a bulk job request to a LRMS at once.

  • Story 4
    • Card: After a user compiles an application program and deploys it to computer systems, a grid scheduler can search for the computer systems and the executable.
    • Conversation:
      • what is executable path to execute a deployed application on a computer system
    • Acceptance test:
      • A user should be able to deploy an application program to different path on each of computer systems and a grid scheduler should be able to find the executables.
      • A user should be able to execute an application program deployed by a member of the same VO/group.

  • Story 5 (TO BE REWRITTEN)
    • Card: A user wants to discover what is the directory for placing input/output files
    • Conversation:
      • where are input files a user wants to use for a job execution
      • where does a user put output files of a job
    • Acceptance test:
      • A user should be able to execute a job using browsed existing input files, put output files of the job and browse the output files

  • Story 6
    • Card: When an application program, which consists of multiple components, starts to execute on computer systems belonging to multiple sites, each of the components can get information about the systems where other components run to transfer data among them.
    • Conversation:
      • where is a job is submitted
      • it is a specific use case.
    • Acceptance test:
      • A user should be able to execute a coupled job transferring data among the components.

 



Versions Associations Attachments Back Links  
Version Version Comment Created By
Version 2 Sergio Andreozzi - 05/08/2007
Version 1 Yuji Saeki - 05/03/2007



The Open Grid Forum Contact Webmaster | Report a problem | GridForge Help
This is a static archive of the previous Open Grid Forum GridForge content management system saved from host forge.ogf.org file /sf/wiki/do/viewPage/projects.glue-wg/wiki/NAREGI_Use_Cases at Fri, 04 Nov 2022 18:48:47 GMT