Negotiate Access to Job

Introduction

A user has already negotiated access to a resource (see NegotiateAccessToResource) using either public or personal permissions. Now the user wants to run a job; this may be a catalogue search, complex query, data mining, modelling code, etc. Depending on the time required to run the job, the user may have to provide permission and be charged for the time. Otherwise, the job may be queued and executed automatically.

Flow of Events

First, the user enters the job that he or she would like to run on the resource. The resource calls its estimator to approximate how much time the job will take. For jobs under 1 ms (or some time to be determined by the resource administrator), the request is automatically placed in a queue and executed. For jobs > 1 ms, the resource must first check that the user has logged on to astrogrid. If the user has not logged on, a message instructs the user to log on (see UserLogsOn). Once the user has logged on, the resource must determine if the user's permissions match the permission required for the request. If the permissions match, the job is placed in a queue and executed (and the user is charged if a charging system is in place). If the permissions do not match, an error message is returned to the user and the job is not executed.

Sequence Diagram

-- ElizabethAuden - 15 Jun 2002

Questions:

• Should the user have an option to abort the job if it is found to be expensive in time or money?

-- GuyRixon - 18 Aug 2002