A Web Portal for the National Grid Service.ppt

A Web Portal for the National Grid Service Xiaobo Yang, Dharmesh Chohan, Xiao Dong Wang and Rob Allan CCLRC e-Science Centre, CCLRC Daresbury Laboratory Warrington WA4 4AD, UK The Grid “Client Problem” Options Provide heavyweight functionality (Globus?), but only on Grid-enabled hosts; Implied need for client-server software architecture, e.g.: Web-based portal with familiar browser Client programming library, API in C, C++ Java, Perl, Python, R etc. Ability to link to existing applications/ GUIs Command-based shell interface Drag and Drop interface (a la Mac) Need a published set of services on Grid hosts – OGSA model, registry, semantics; Need easy development and deployment framework for applications and client tools, e.g. using Web services - encourage community contribution via an open process. Why a Portal Right functionality: Encapsulates Grid functionality Separation of “front-end” session management and presentation layers Model code layer at “back-end” using Globus C/ Java API or other middleware, e.g. SRB Right technology: Good support for portal developments – standards and tooling in Java Web services (Java, Perl, C, Python, PHP, etc.) Knowledge: Previous experience, we have been using Web portals to develop and test Grid functionality since 2000 HPCPortal, InfoPortal, DataPortal Based on work in the Global Grid Forum – Grid Computing Environments research group (GCE-RG) Building on the Infrastructure NGSPortal v1.0 NGSPortal 1.0 was based on OGCE v1.0: the Open Grid Computing Environment portal Adopted in USA by NMI: the National Middleware Initiative /nmi/portal Used the CHEF framework (Comprehensive Collaborative Framework) from U. Michigan Some additional ideas taken from HPCPortal and InfoPortal NGSPortal tools available November 2004: MyProxy management GRAM job submission FileTransfer based on GridFTP MDS resource discovery Feedback at NeSC training event, December 2004 NGSPortal v1.0 file-transfer tool Why change? Was always planned to migrate