GRIDipedia – The European Grid Marketplace

This Common Capability covers the need of running, monitoring and controlling computational jobs through the portal.

The JSMC Common Capability allows a user to:

• Begin the execution of a computational job.
• View the history and status (finished, suspended, cancelled, failed) of one or more previously submitted jobs as well as monitor and control (i.e. suspend and resume or cancel) the execution of jobs that are not finished yet.
• Negotiate SLAs in the same way as he/she submits a computational job.

Motivation and foreseen Business Value

The motivation for this Common Capability comes directly from Business Needs for job submission monitoring and control functionalities.

The ability to submit jobs through a portal will offer its users an easy to use tool to launch tasks in different platforms. The usability of the system and the simplicity of the job submission procedure shall increase the users’ satisfaction for the system. The addition of job monitoring and control functionality will allow the users to monitor and control the executed tasks in a simple way, and thus increase the user satisfaction and confidence to the system. It will also allow for improved management of resources and the deployment of better accounting and charging mechanisms.

Relationship to other Common Capabilities

The File Management Common Capability interacts with JSMC whenever it is necessary to upload, download or specify a data file, i.e. during Job Initialization and Job Output.

The Job Visualization Common Capability can be called by the Job Output component in order to visualise the output data of a finished job.

The Accounting Common Capability can be called by the Job Monitoring component in order to present accounting information about a specific job, which is finished.

There is also relation to SLA Common Capabilities. As mentioned before, the JSMC Common Capability could be extended in order for the portal’s users to be able to negotiate or re-negotiate an SLA through the Portal, by handling this functionality as a special job submission procedure. In this context, there is a dependency with the SLA Template and Negotiation Common Capability. The SLA negotiation functionality through the portal would start with the presentation of the SLA template, which must be filled in by the user, which points out another dependence with the SLA Template Common Capability.