Application Hosting Service (AHS)
Application Hosting Service (AHS) provides
Virtual Organizations
repository of application information toGroups
VO１
the research community created by gridVO２VO３
virtual organization (VO). Community
Application
Application
Users
Developers
members can share the applications andA Univ.
DUniv.
their execution environment on the
B Univ.
hierarchical grid environments as shown inNIS
C Univ.
Grid
the right Figure. In a research community,
application users need to know only theapplication specifications, such as theLLS
A Lab.
B Lab.
application name or keywords for selecting
GridD Lab.
C Lab.
the applications.
Joint Research Community
Architecture
AHS basic architecture is constructed as a set of Web/Grid service infrastructure on topof WSRF (Web Services Resource Framework) specifications. WSRF is a messaging
model and provides the ability to model stateful resources in a framework of Webservices. AHS operates cooperatively with the workflow tool and access to NAREGI-SS(Super Scheduler) for the NIS or GridSAM for the LLS as shown in the bottom Figure.
Collaboration in the research community
The developed application is provided to users or user groups who are collaboratingclosely with the developers. Because the application users have relatively lessknowledge about the application than developers, it is necessary to encapsulate that
information at the time of the use of the application. Also, detailed information about
the grid environment should be hidden from the application users.
CLIENT (End Users)
Portal server

AHS

PortalApplication
Register & Delete
Application
CompileCommand Line Interface

Application Pool

Application
Retrieval

WFT

Application
Deployment

NAREGI
SS/ISGridSAM
Data share / DB share

LLS
Resources

NIS
Resources・・・

Grid Interoperation
During the past decade, computing environments for scientific research andengineering have been big innovated by grid technologies. In the past, computing
environment was organization closed systems. But nowadays, many organizations
participate virtual organizations and share their resources with other organizations
using grid technologies. This made that the end users can use variety of systems, data,applications, and so on beyond the wall of real organizations. These resource sharing
are prospected to accelerate scientific collaborations. However, there is a problem ininternational collaborations. The regional grid infrastructures are using different grid
middleware and they can’t share resources across grids because they are using
proprietary specifications. To solve this problem, many grid projects are making efforts
to develop standard specifications in the OGF (Open Grid Forum) and implement them.
The RENKEI project is participating these efforts, The Grid Interoperation.
Architecture
The RENKEI grid interoperation feature isdeveloped as extensions of NAREGI grid
middleware. The extensions are compliant
with the OGF/HPCBP (HPC Basic Profile)and related specifications. Figure 1 shows
the architecture of grid interoperation.
Information Servicein another Grid

User inAnotherGridRENKEI-IS
Schema Translator

NAREGI-IS
NAS / CDAS
RENKEI
PortalJob Submission
Client / Service inAnother Grid

RENKEI-SS
NAREGI-SS Services
NAREGI user

HPCBP-SC

HPCBP
Client

HPCBP Client

HPCBP
Service

HPCBP-Service

Computing
Resource inAnother Grid

Another Grid
Infrastructure

HPCBP Server

NAREGI-SC

NAREGI
GridVMRENKEI-IS
LRPS

LRMS

The IS Schema Translator exchanges
resource information with other grids
using GLUE schema, and translates it to/from CIM schema which is commonlyused in the RENKEI/NAREGI middleware.
The LRPS provides interoperation relatedresource properties to IS.
Interoperation Demonstrations
The RENKEI project participates OGF/GIN(Grid Interoperation Now) activities withsome other grids. We have succeeded insubmitting an application job from UK tofive computing resources on different grid
infrastructures in different countries (Fig.
2). This activity was demonstrated at the
5th IEEE eScience conference and OGF28.

RENKEI NIS Computing Resource
Oxford e-Research Centre：Modification/Addition to NAREGI: HPCBP(BES, JSDL, etc.): FTP or GridFTPRENKEI Grid Infrastructure (NIS)
MinemFig. 1 Grid Interoperation Architecture

The HPCBP-Service accepts the HPCBP
compliant job requests from other grids,
and submit the jobs into under laying
LRMS. The HPCBP-SC is the job submission
point to the HPCBP compliant resources inother grids.

Pre-Processing:
Generate input data (Perl)

UNICORE(DEISA)
GridSAM(UK-NGS/OMII-UK)

Main-Processing:• Data Staging• Job Submission to Grids

ARC(NorduGrid)

Copyright OeRC
Minem
Web Server

Post-Processing-1:
Choice Best Result (Perl)

Genesis II(U of Virginia)

Post-Processing-2:
Upload results to Web

Local System

RENKEI(NII)Internet

Minem

Minem

Minem

Minem

MinemGrid Environments

Fig. 2 Grid Interoperation Demonstration

Grid Technology Enabling e-Science
RENKEI(Resources liNKage for E-scIence) is
computation intensive
database users
application developers
applications users
a new project designed for an softwareenvironment where researchers can create(3) DB federation, and(1) computing resource(4) API for multiple
federation with ID
federation, andgrid middlewareand operate research community easily.
management systems
application hosting
They can develop and run sharing
application programs on distributed various
grid resources without knowing the detailsof any particular underlying grid middleware.
(2) file sharing, andevaluation andAHS(Application Hosting Service) provides (5)collaboration
file catalogue federation
with usersa software environment for developing andcomputation/data intensive
application users
deploying scientific applications on NAREGI
grid resources and on laboratory resources. Application developers use the AHS toregister and deploy applications and to share them within research community members.
WFT(Workflow Tool) provides end users with a single seamless interface to manage
workflow jobs. They use the WFT to discover appropriate resources, to specify workflow
jobs consisting of applications deployed by using the AHS on various grid resources, tolaunch jobs , to monitor running jobs, to terminate jobs and to retrieve files to clientmachine.
The grid interoperation feature enables mutual job submission with other grids using
OGF/HPCBP and related standards (BES, JSDL, etc.). The users can use computing
resources in both RENKEI/NAREGI NIS and other grids seamlessly in a single NAREGI
workflow.
DBDBDBgrid middleware(e.g. NAREGI)

laboratory (LLS)internationalinter-operationDB

computer centers (NIS)

grid middleware

computer users

End user

Workflow

WAN

preprocess
sim 1

sim. 2
postprocess

sim 1

sim. 3interoperation
sim. 2

Laboratory A

importcomputer centersLAN
preprocess
postprocessapplication cataloguesim. 3

LAN
Laboratory B

virtual distributed file system(Gfarm2)

deploy,registerApplication developers
deploy,registerFurther information
http://www.e-sciren.org/

How To Use REKEI -WorkFlow Tool
WFT(WorkFlow Tool) is a set of end-user tools to interact with a service exposing
heterogeneous execution resources uniformly. Using it they can submit and start jobs
to LLS and NIS computer resources, monitor jobs, terminate jobs and transfer files
between them. The following demonstration of a flow simulation around cylinderusing LLS computer resources here in Jimbocho and NIS computer resources in NishiChiba will show a good example of the effectiveness of this interface.
Assumption: Program consists of preprocess code preparing simulation execution,
number crunching simulation code for fluid and postprocess code visualizing numericalresults. They have been already developed, registered and deployed with LLS/NIS
resources by you or a member of a research community using AHS.
1.Single Sign On : Sign on to the RENKEI-Portal, which enables a user to access
WFT/AHS tools, to permit using computer resources in LLS and resources in NIS
belonging to a research community.
2.Workflow Preparation: Create or modify a workflow using LLS, NIS program icons andLLS, NIS data icons. i.e. Specify execution properties for preprocess, postprocess in LLS
and flow simulation in NIS by using Program Icons(■ LLS ■ NIS). They contain genericjob identification information, application description, resource requirements anddescription of required data files. Specify file’s URI for input and output files using LLS,
NIS data icons.
3.Workflow Execution: Submit the coded workflow job into LLS and NIS system. Monitor
its execution. Visualization of flow simulation is displayed in your computer in LLS.
Another scenario execution can be obtained easily by changing the data icons acting forinput files.
NIS

LLS
Preprocess

Simulation

Input file

Visualization
Output file

Gfarm2 file

LLS(Here)

LLS

NIS(Nishi-Chiba
Computing Center)