370 likes | 560 Views
Edge Services Framework ESF in Open Science Grid. Joint OSG and EGEE Operations Workshop September 27-29, 2005 RAL, UK. Abhishek Singh Rana UC San Diego | USCMS | DISUN rana@fnal.gov. Kate Keahey Argonne Lab | Globus Alliance keahey@mcs.anl.gov. Outline. OSG-ESF Activity. ESF Phase 1.
E N D
Edge Services FrameworkESF in Open Science Grid Joint OSG and EGEE Operations Workshop September 27-29, 2005 RAL, UK Abhishek Singh Rana UC San Diego | USCMS | DISUN rana@fnal.gov Kate Keahey Argonne Lab | Globus Alliance keahey@mcs.anl.gov
Outline • OSG-ESF Activity. • ESF Phase 1. • Concepts and Design. • ESF future direction. • Xen overview. • Plan for Phase 1 on OSG. • Site admin responsibilities. • VO admin responsibilities. • Status and Next Steps.
Vision From talk by Frank Wuerthwein at OSG Consortium Meeting 2005 (simplified snapshot of a typical OSG/LCG site in 2007)
OSG-ESF Activity • Started in September 2005. • Physicists, Computer Scientists & Engineers, Software Architects. • Chairs: Kate Keahey and Abhishek Singh Rana. • Workspace Services Design: • Timothy Freeman & Kate Keahey (Globus Alliance). • Edge Services Implementations: • USATLAS: Rob Gardner (U Chicago), Alexander Vaniachine (ANL). • USCMS: Frank Wuerthwein, Abhishek Singh Rana (UC San Diego). • Mailing List – osg-edgeservices at opensciencegrid.org • Web collaborative area – http://osg.ivdgl.org/twiki/bin/view/EdgeServices
No ESF - Phase 0 CE SE Site
No ESF - Phase 0 Static deployment CE CMS ATLAS CDF SE Site
ESF? CE SE Site
ESF - Phase 1 Snapshot of ES Wafers implemented as Virtual Workspaces ESF ATLAS CMS CE SE CDF Guest VO Site
An attempt at ESF Terminology • Edge Services Wafer (ES Wafer) • A specific instance of a dynamically-created VM (workspace) is called an Edge Services Wafer. • An ES Wafer can have several Edge Services running. • A VO can have multiple ES Wafers up at a Site. • Edge Services Slot (ES Slot) • An ES Slot has hardware characteristics specified by the Site Admin. • An ES Slot can be leased by a VO to host an ES Wafer. • Edge Service (ES) • A VO-specific service instantiated by a VO in a Wafer. • Workspace Service (WS) • Service at a Site that allows VOs to instantiate ES Wafers in ES Slots.
ESF - Phase 1 Snapshot of ES Wafers implemented as Virtual Workspaces Dynamically deployed ES Wafers for each VO GT4 Workspace Service & VMM ESF Wafer images stored in SE ATLAS CMS CE SE CDF Guest VO Site Compute nodes and Storage nodes
User jobs at Compute nodes using ES Wafers for VO Edge Services ESF ATLAS CMS CE SE CDF Guest VO Site
VO Admin transporting/storing ES image to a remote Site....Deploying ES using image stored in Site’s local repository
ESF - Phase 1 Role=VO Admin CMS ESF CE SE Site
ESF - Phase 1 Role=VO Admin CMS ESF CE SE Site
ESF - Phase 1 Role=VO Admin ESF CE SE Site
ESF - Phase 1 Role=VO Admin ESF CE SE Site
ESF - Phase 1 Role=VO Admin ESF CMS CE SE Site
ESF - Phase 1 Role=VO Admin ESF CMS CE SE Site
ESF - Phase 1 Role=VO Admin ESF CMS CE SE Site
ESF - Phase 1 Role=VO User ESF CMS CE SE Site
ESF - Phase 1 Role=VO User ESF CMS CE SE Site
ESF - Phase 1 Role=VO User ESF CMS CE SE Site
ESF - Phase 1 Role=VO User ESF CMS CE SE Site
ESF - future direction • Same concept. • ES Wafers to be deployed as an ESF cluster and be fully schedulable by any OSG VO.
ESF - future direction ESF Dynamically deployed ES Wafers for many VOs Brokering and Scheduling by Edge Services Framework ATLAS2 CMS ATLAS1 CDF Cluster of ES Slots with different properties Site
Xen overview Public Network Private Network Virtual Machine Monitor (VMM) Hardware
Plan for Phase 1 on OSG • ATLAS & CMS procure one piece of hardware at their Sites on OSG that runs ESF (called ESF node). • Dual CPU. • 4GB RAM (No PAE support in Xen2, we will exploit only 4GB until we migrate to Xen3). • Site administrators install: • Xen (We will go for Xen 2.0.7). • GT4 Workspace Service. • VO administrators use ESF to fire-up Xen VMs that instantiate VO Services – Edge Services in an ES Wafer. • A single ESF node hosts ES Wafers for both ATLAS & CMS.
Site Administrator Responsibilities • Start with FC4 and deploy: • Xen (We will go for Xen 2.0.7). • Custom kernel for domain 0 (grub required). • Custom kernel for domain U. • GT4. • GT4 Workspace Service. • Provision: • One public IP, One private IP per VM. • Host certificates per VM. • Disk space per VM. • Declare available ES Slots and their properties to ESF.
VO Administrator Responsibilities • Prepare (freeze) ES Wafer instance as disk image. • Prepare image into file for transport. • SRMCP the image to remote Site’s SE. • Use ESF to fire-up Xen VM with VO-Services (ES Wafer) at remote Site, from image file in remote SE, using role based authorization (OSG-RBAC). • Advertise the running Edge Services as needed.
Status • Xen3 on testbed. • GT4 Workspace Service being used. • Prototype 0 of ESF. Next Steps • Revert back to Xen2. • Develop VO-Service images. • Verify performance, functionality, robustness.