User Interfaces

This wiki page provides information about user interfaces that provide command line interface (CLI) to the middleware services of the EGI e-infrastructure. The information on this page has been collected by the User Community Support Team of EGI.eu.

• Information about graphical environments to interact with the European Grid Infrastructure can be found in the EGI Application Database: http://appdb.egi.eu. (Both reusable tools for software developers and reusable applications for scientific end users are available through this database.)
• Information about Application Programming Interfaces (API) to interact with the services of the European Grid Infrastructure can be found at Service_APIs.

This Wiki page is a temporary area where information about command line access mechanisms are collected. Once the list is finalised the entries will be registered into the EGI Application Database. (Related request from the user communities: 2nd User Community Board meeting, action 02/12: [1])

For comments and updates please email to ucst@egi.eu.

Software name	Contact(s)	Status	Client type	Supported platform	Supported middleware
MILU (1)	Stefano Cozzini,Tyanko Aleksiev	active / Dec. 2010	CLI	Linux	gLite, ARC, Globus TK
UNICORE - UCC (2,3)	unicore-web@unicore.eu	active / Apr. 2011	CLI	Linux	Unicore, ARC
jLite (6)	Oleg Sukhoroslov	? / Oct. 2010	CLI, API	all	gLite
GILDA UI PnP (8,9)	[2]	? /	CLI	Linux	gLite 3.0/3.1
ARC - command line (10,11)	NorduGrid	active / May 2011	CLI	Linux (deb & rpm)	ARC, Globus, gLite, Unicore
gLite UI (14)	?	?/2011	CLI	Linux	gLite, ARC (via WMS)
EMI - UI (15)		active / June 2011	CLI	Linux (SL 5.5 i386 / x86_64)	ARC, dCache, gLite, UNICORE

Notes:

(1)

Miramare Interoperable Lite UI. It is a software tool which allows seamless usage of different Grid infrastructures from a Linux workstation. It has been implemented by re-packaging of the gLite UI, arc UI, Globus Toolkit software and a few other customizations available for several Linux distributions. It is intended to offer an almost Plug ’n Play environment which enables transparent access of these three Grid infrastructures.It has been tested and is known to be working on several GNU/Linux distributions, including Scientific Linux, CentOS and Ubunto. Milu has already built-in support for several VO’s (e.g. compchem, gilda, enmr.eu ... ) and is easily configurable to add other VO’s. Current User Guide can be found here.

(2)

On the top layer a variety of clients is available to the users, ranging from the command-line interface named UCC , the Eclipse-based UNICORE Rich Client to the programming API named HiLA. UNICORE 6 services can also be accessed from portals, using technologies such as GridSphere and The Vine Toolkit.

(3)

The UNICORE command line client (UCC) is a very versatile command-line tool that allows users to access all features of the UNICORE service layer in a shell or scripting environment. It allows to run jobs, monitor their status and retrieve generated output, both in single job mode or in a powerful and flexible batch mode for multiple jobs. Additionally, workflows can be submitted and controlled with the UCC. UCC includes several data management functions. Remote storages can be listed and files can be transferred from local to remote as well as from server to server. UCC can be used for administrative purposes as well, for example to list all jobs, or to perform some clean up. An important feature of UCC is its extensibility, where new commands can easily be added.

(6)

jLite is a Java library providing simple API for accessing gLite based grid infrastructure. It is intended for Java developers who struggle with gLite middleware and want to reduce time and effort needed to build a cross-platform grid application on top of the EGEE grid infrastructure. jLite also includes a command-line interface which can be used as a simple cross-platform alternative to gLite User Interface on Windows and other operating systems.

Existing Java APIs for gLite are scattered among several packages and expose mostly low-level service operations. Available API usage examples often imply the presence of gLite User Interface environment installed on Scientific Linux. This complicates the use of these APIs for development of cross-platform grid applications. jLite is addressing these problems by providing a high-level Java API with functionality similar to gLite shell commands. Current implementation supports complete gLite job management lifecycle including VOMS proxy creation and delegation, transfer of job input files, job submission, job status monitoring and retrieval of job output files. Normal, collection and parametric gLite jobs are supported. The API hides complexity of underlying middleware and its configuration. jLite is easy to install because it includes all external dependencies and does not require installation of gLite User Interface. The library is pure Java and can be used on any Java-capable platform including Windows.

GILDA VO is supported by default.

(8)

Gilda is a grid testbed and provides a Plug and Play UI (tar ball) for gLite 3.0/3.1 for Linux. Though it is pre-configured to use gilda VO resources, it is straightforward to re-configure it for other VO’s (e.g. enmr.eu did it in the past). Gilda also started to provide VMware instances for gLite UI 3.1. Notice: several links are dead/non-existing, probably due to a recent migration of Gilda portal contents to a LifeRay CMS container.

EGEE/EGI Indico events about this software. Keywords : “user interface”

• PlugAndPlay User Interface: a simple grid access designed on the basis of grid user requirements

(9)

GILDA virtual instances are a valuable example of what can be accomplished with virtualization technology. The user does not need to have a deep knowledge to instantiate a guest with a pre-configured UI to meet his needs. That is to say, mapping a UI with a operating system (as it is done in the above table) does not have anymore a huge relevance if virtualization is in place. Because pre-built virtual machines can be run/played by all users (no matter the OS they work with). The users only need to have an hypervisor up and running on their host machine, and run the guest without any major concerns. Their VO configuration will already be in place, it is just a question of submitting/retrieving grid jobs.

(10)

The command line user interface of ARC consists of a set of commands necessary for job submission and manipulation and data management.

(11)

ARC also provides the Lunarc Application Portal, a lightweight application portal for accessing Grid resources. The Lunarc Application Portal is an ongoing development to provide a framework for developing portals for Grid resources. Existing versions of the portal also used ARC for job submission, job monitoring and job control.

(14)

gLite is a middleware for grid computing that was born from the collaborative efforts of more than 80 people in 12 different academic and industrial research centers as part of the EGEE Project. gLite provides a framework for building grid applications tapping into the power of distributed computing and storage resources across the Internet.

(15)

The EMI-UI is a suite of clients and APIs that users and applications can use to access grid services. The access point to the Grid-Infrastructure is the User Interface (UI). This can be any machine where users have a personal account and where their user certificate is installed. From a UI a user can be authenticated and authorized to use the GRID resources, and can access the functionalities offered by the Information, Workload and Data Management Systems. The user guide can be found here.