Science gateways made easy: the In-VIGO approach

Transcription

1 Science gateways made easy: the In-VIGO approach A. Matsunaga, M. Tsugawa, S. Adabala, R. Figueiredo, H. Lam and J. Fortes Advanced Computing and Information Systems Laboratory University of Florida June 28, 2005 GGF 14 Chicago, IL, USA Workshop: Science Gateways: Common Community Interfaces to Grid Resources

2 What is In-VIGO? Enables computational engineering and science In- Information Grid Organizations

3 Motivations and goals for science gateways Motivations: Need middleware to hide complexity of dealing with cross-domain issues From application developers From end users While preserving security and privacy of data, codes and other users information Goals: Application-centric: Support unmodified applications Sequential, parallel Batch, interactive Open-source, commercial Support automated Grid-enabling of applications User-centric: support Grid-unaware users

4 What does In-VIGO bring to science gateways? Enables simple, flexible and sustainable addition of computational applications and computing power nanohub: ~20 tools in 3 months GUI and batched applications

5 In-VIGO Approach UIML interfaces XUL Nanohub XML OGSA HTTP Netcare BMI UDDI information grids Other portal WSDL SOAP s s s s computing grids Globus/Condor.net JINI VMware IBMz800 machines Java C# applications NFS data networks Machines Applications Data Networks SQL NFS TCP/IP UDP

6 In-VIGO Approach Extensive use of virtualization Security Flexibility/customization Decouples grid users from resources Users do not have to manage several credentials In-VIGO proxies on behalf of user(s) simplify resource administration for providers Provides execution environments transparently Turns tools into Grid-services accessible via a user-friendly Web-interface efficiently

7 Grid-enabling unmodified applications Enabler provides Command-line syntax Application-related labels Parameter(s), type-set values, entire applications Resource and execution environment metadata Architecture, OS libraries, environment variables Grid-services are created, deployed and possibly customized using Generic Application (GAP) Application (VAS) Grid-user interacts with the virtual application through a Web-portal to execute applications on virtualized resources Portal Tier Application Tier Grid Tier VA 1 Application Utilization User Portal Interface VA 2 VM VA 3 VA Framework Other Frameworks VFS Application Customization and Generation Administrator Portal Interface Customization GAP/VAS Generator VN Application Enabling Enabler Portal Interface Enabling IS Enabling Customization and Generation Utilization

8 Machine System Provides means to efficiently create/configure/destroy VMs, that is generic across VM technologies [SC 2004] Directed Acyclic Graph (DAG) model for defining application-centric VMs VM Creation Request from Client (e.g. In-VIGO) (1) VM Request (6) VM ClassAd VMShop (VMArchitect VMCreator, VMCollector, VMReporter) Cost-bidding model for choosing compute servers for VM instantiation (2) Request Estimate (3) VM Creation Cost (4) Create VM (5) VM ClassAd brady vws001 mcnair vws002 manning vws003 VMPlant Daemon favre vws005 VMPlant Daemon Host OS (VMPlant) Host OS (VMPlant)

9 Logical User Accounts Traditional user account User is assigned fixed identifier (e.g. Unix UID) Logical user account Physical (shadow) account temporarily assigned to a user by resource management in In- VIGO User logical account [HCW01, HPDC01] In-VIGO User shadow account file account login account disk space file system

10 Grid File System (GVFS) Distributed virtual file system [HPDC 2001, 2004, 2005] ization on Network File System (NFS) User-level proxy based implementation Compute Server NFS Client Authenticate, Identity map, Forward Proxy NFS Server File Server Application job00x user kernel vfs000 on-demand, cross-domain data access Support for unmodified binary applications unmodified NFS clients/servers

11 Putting it all together: GUI Application example User Y 6: VNC X-window Role-Based Access Control enables Single Sign-On to VNC X-window User request Information service 2: query (user data, compute server) 4: copy/access user data V1 X User X 1: user request 5: return handler to user (URL) Front end F 3: get VM or shadow account Physical server pool P V2 Y CMS/Portal Engine isolation via shadow accounts or virtual machines Data Server D1 Data Server D2

12 In-VIGO Status Portals SCOOP, HPC, Netcare, nanohub Publications IEEE Proc., FGCS, DCS, HPDC, SC, IPDPS, ICAC, Europar, GGF, Classes Distributed Computing Computers Team: 10 Ph.D. students, 4 Faculty