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/UseCases at Thu, 03 Nov 2022 00:06:06 GMT SourceForge : View Wiki Page: UseCases

Project Home

Tracker

Documents

Tasks

Source Code

Discussions

File Releases

Wiki

Project Admin
Search Wiki Pages Project: GLUE     Wiki > UseCases > View Wiki Page
wiki1698: UseCases

Use Cases

This document presents the collection of use cases that are driving the definition of GLUE 2.0.

Each use case is written following the template presented in this page.

  • 1
    • Presented by: EGEE, NorduGrid
    • Scenario: resource selection for job submission, inventory
    • Short Description: A user can search for the number of used and total computing resources for a certain computing element
    • Actors: site administrator, grid operator, VO manager, "politicians", resource selection service
    • Conversation:
      • keep in mind the end-user viewpoint (job slot) and the physical resources; job slots should have a different user story
      • what is the unit of computing resource that can be free/used/unavailable
      • when a unit of computing resource is free/used/unavailable
      • what do you count in the total that is what draws the border of the system; how do you group resource into a computing element
    • Acceptance Test:
      • we need acceptance test to check for double-counting
      • we need acceptance test to check if multi-core CPUs and virtual nodes are properly counted
  • 2
    • Presented by: EGEE, NorduGrid
    • Scenario: resource selection for job submission, inventory
    • Short Description: A user wants to search for the share of resources available to his group in a certain computing element;
    • Actors: end-user
    • Conversation:
      • A group-specific share should be modeled in the same way, regardless the possible local allocation strategies implemented via site config
      • a group can be a whole VO or a subset of users part of a VO
      • a group is identified by a set of privilege attributes
      • what kind of relationships are possible between groups and shares?
      • A group-specific share should be modeled in the same way, regardless the possible local allocation strategies implemented via site config
    • Acceptance Test:
      • A site admin implements per-group guaranteed share by using a per-group batch queue strategy
      • A site admin implements per-group guaranteed share by using a batch queue with hierarchical share allocation
  • 3
    • Presented by: EGEE, NorduGrid
    • Scenario: resource provider advertising
    • Short Description: a site administrator wants to advertise the share related to a resource allocation regardless the local allocation strategies
    • Actors: site administrator
    • Conversation:
      • A group-specific share should be modeled in the same way, regardless the possible local allocation strategies implemented via site config
      • a group can be a whole VO or a subset of users part of a VO
      • a group is identified by a set of privilege attributes
      • what kind of relationships are possible between groups and shares?
      • A group-specific share should be modeled in the same way, regardless the possible local allocation strategies implemented via site config
    • Acceptance Test:
      • A site admin implements per-group guaranteed share by using a per-group batch queue strategy
      • A site admin implements per-group guaranteed share by using a batch queue with hierarchical share allocation
  • 4
    • Presented by: NAREGI
    • Scenario: resource selection for job submission
    • Short Description: a user wants to search for computing resources which meet the requirements for his job execution; in particular, he wants to search for OS (name, type and version) , SMP size and physical/virtual memory size
    • Actors: user, resource selection service
    • Conversation:
    • Acceptance Test:
  • 5
    • Presented by: NAREGI, EGEE; NorduGrid
    • Scenario: service and resource discovery
    • Short Description: a user wants to discover the available service endpoints to access a certain computing resource (URI, type of job execution service, queue name)
    • Actors: user, resource selection service
    • Conversation:
      • is the job queue part of the URI? possibly not
    • Acceptance Test:
  • 6
    • Presented by: NAREGI
    • Scenario: resource selection for job submission
    • Short Description: a user wants to discover which computing resources are authorized to the VO to which he belongs to
    • Actors: user, resource selection service
    • Conversation:
    • Acceptance Test:
  • 7
    • Presented by: NAREGI
    • Scenario: high-level management
    • Short Description: a grid operator wants to discover which VOs can access a certain computing resource
    • Actors: grid operator
    • Conversation:
    • Acceptance Test:

Checked until here


  • 8
    • Presented by: NAREGI
    • Scenario: A grid scheduler can distinguish which LRMS accept an advanced resource reservation request or don't accept jobs without reservation (reservation necessary).
    • Short Description:
    • Actors:
    • 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.
  • 9
    • Presented by: NAREGI
    • Scenario:
    • Short Description: A grid scheduler can distinguish which LRMS accept an array job submission request.
    • Actors:
    • 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.

  • 10
    • Presented by: NAREGI
    • Scenario:
    • Short Description: 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.
    • Actors:
    • 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.
  • 11 (TO BE REWRITTEN)
    • Presented by: NAREGI
    • Scenario:
    • Short Description: A user wants to discover what is the directory for placing input/output files
    • Actors:
    • 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
  • 12
    • Presented by:
    • Scenario:
    • Short Description: 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.
    • Actors:
    • 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.
  • 13
    • Presented by: APAC
    • Scenario:
    • Short Description: A user wants to know if software package X is installed on a compute resource somewhere on the Grid
    • Actors:
    • Conversation:
      • ....
    • Acceptance Test:
  • 14
    • Presented by: APAC
    • Scenario:
    • Short Description:
    • Actors:
    • Conversation:
      • ....
    • Acceptance Test:
  • 15
    • Presented by: APAC
    • Scenario:
    • Short Description: A user wants to know the available versions of software package X installed on compute resources somewhere on the Grid
    • Actors:
    • Conversation:
      • ....
    • Acceptance Test:
  • 16
    • Presented by: APAC
    • Scenario:
    • Short Description: A user wants to know which sites are running software Package X with version Y
    • Actors:
    • Conversation:
      • ....
    • Acceptance Test:
  • 17
    • Presented by: APAC
    • Scenario:
    • Short Description: A user wants to know if VO V have permissions of submitting a job which will use package X at site A
    • Actors:
    • Conversation:
      • ....
    • Acceptance Test:
  • 18
    • Presented by: APAC
    • Scenario:
    • Short Description: A user wants to know if software package X contain a parallel or sequential version of software executable Z
    • Actors:
    • Conversation:
      • ....
    • Acceptance Test:
  • 19
    • Presented by: APAC
    • Scenario:
    • Short Description: + Is the a software executable Z under the software package X installed on resource R at Site A support parallel/sequential execution?
    • Actors:
    • Conversation:
      • ....
    • Acceptance Test:
  • 20
    • Presented by: APAC
    • Scenario:
    • Short Description: A user needs to know what module to load to set the user environment is he/she wants to use software package X at site A
    • Actors:
    • Conversation:
      • ....
    • Acceptance Test:
  • 21
    • Presented by: APAC
    • Scenario:
    • Short Description: A user wants to know the maximum number of CPU that can be used if software package X with executable Z is used at site A
    • Actors:
    • Conversation:
      • ....
    • Acceptance Test:
  • 22
    • Presented by: APAC
    • Scenario:
    • Short Description: A user wants to know what type of parallel application software executable Z support (mpi, openmp, etc)
    • Actors:
    • Conversation:
      • ....
    • Acceptance Test:
  • 23
    • Presented by: APAC
    • Scenario:
    • Short Description: A user wants to know the number of free CPUs available for him/her (as a member of VO V) to use when he/she submits a software package X job at site A.
    • Actors:
    • Conversation:
      • ....
    • Acceptance Test:
  • 24
    • Presented by: APAC
    • Scenario:
    • Short Description: A user wants to know the number of free job seats available for him/her (as a member of VO V) to use when he/she submits a software package X job at site A
    • Actors:
    • Conversation:
      • ....
    • Acceptance Test:
  • 25
    • Presented by: APAC
    • Scenario:
    • Short Description: A user wants to know the number of free user seats available for him/her (as a member of VO V) to use when he/she submits a software package X job at site A
    • Actors:
    • Conversation:
      • ....
    • Acceptance Test:
  • 26
    • Presented by: EU.INT.GRID
    • Scenario:
    • Short Description: A user submitting an MPI job wants to know the technology of the local network (providing clue about the performance, e.g., gigabit ethernet, myrinet, infiniband)
    • Actors:
    • Conversation:
      • ....
    • Acceptance Test:
  • 27
    • Presented by: EU.INT.GRID
    • Scenario:
    • Short Description: A user submitting an MPI job wants to know the maximum number of slots that can be assigned to a single MPI job
    • Actors:
    • Conversation:
      • ....
    • Acceptance Test:
  • 28
    • Presented by: EU.INT.GRID
    • Scenario:
    • Short Description: A user submitting an MPI job wants to know the type of MPI implementation available in an execution environment (e.g., MPICH, OpenMPI, LAMMPI)
    • Actors:
    • Conversation:
      • ....
    • Acceptance Test:
  • 29
    • Presented by:
    • Scenario:
    • Short Description: A user submitting an MPI job wants to know if there is a shared file system among the execution environments where its job could be executed
    • Actors:
    • Conversation:
      • also the location of this file should be available (maybe by using environment variables)
    • Acceptance Test:
  • 30
    • Presented by: NGS
    • Scenario:
    • Short Description: A user wants to submit a job to an application, and if he wishes, be isolated from the local application installation environment
    • Actors:
    • Conversation:
      • The site administrator can choose to install the appliciation under any local path, where the environment and dependencies may be different from other sites.
      • The user should not be required to know these site-specific details.
      • The user may choose to specify additional requirements about the local appliciation installation environment.
      • Note: This may not be relevant to the usecase, but our GLUE-1.* implementation details is available here: http://wiki.ngs.ac.uk/index.php?title=NGS_Uniform_Execution_Environment
    • Acceptance Test:
  • 31
    • Presented by: NGS
    • Scenario:
    • Short Description: A user may have restraints on the application version when submitting a job to the application.
    • Actors:
    • Conversation:
      • The user may:
        1. not care about the application version.
        2. require a specific version,
        3. require a version later (or earlier) than a specific version
        4. specify multiple allowed versions
    • Acceptance Test:
  • 32
    • Presented by: APACGrid
    • Scenario:
    • Short Description: A site administrator wants to advertise the fact a single grid interface offers access to different batch queues managed by different batch systems (see email from Gerson to the list)
    • Actors:
    • Conversation:
      • The user may:
    • Acceptance Test:
  • 33
    • Presented by: EGEE
    • Scenario:
    • Short Description: A user wants to discover which myproxy servers he/she can use in order to retrieve/renew his/her proxy using a given Resource Broker
    • Actors:
    • Conversation:
      • usually you want to find a service where you are authorised, but in this case you want a service where another service (the RB) is authorised
    • Acceptance Test:


To be digested and to be added above

Digested and added above


References

OGF Use Case repository
about user stories
a book review

Attachments:
SASGridUseCase.pdf [UseCases/SASGridUseCase.pdf]
bdii-query.log [UseCases/bdii-query.log]
 




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/UseCases at Thu, 03 Nov 2022 00:06:06 GMT