Presentation is loading. Please wait.

Presentation is loading. Please wait.

GPE4UNICORE Grid Programming Environment for UNICORE

Similar presentations

Presentation on theme: "GPE4UNICORE Grid Programming Environment for UNICORE"— Presentation transcript:

1 GPE4UNICORE Grid Programming Environment for UNICORE
Ralf Ratering, Hans–Christian Hoppe Intel Software&Solutions Group

2 ? What is GPE good for? What does GPE provide? How about other Grid
GPE turns a collection of distributed computers/data centers into a Grid What does GPE provide? A full Grid Software stack including graphical user interfaces and programming libraries How about other Grid Software? GPE services run in the Globus Toolkit 4 container GPE client framework works with UNICORE6 and ChinaGrid ? Why does Intel develop GPE? GPE is an Open Source technology demonstrator for customers and ISVs Influence standards Drive new technologies into market

3 GPE Current Status GPE included in UNICORE6 alpha6 release at Application Client and GridBeans Expert Client BPEL workflow service UNICORE-specific source code available from CVS Main GPE development under Complete GPE sources available under BSD license Server implementation uses Globus Toolkit 4 container

4 GPE Ecosystem GPE4GTK as standalone solution
Intel software testing Proof of concepts at customers Research and Education GPE user interfaces and GridBeans UNICORE 6 China Education Grid (Ministry of Education) South Korea (K-Grid) Support for virtual machine technology Cooperation with Globus team Cooperation with CERN Strong interest in industry

5 Why do we engage in UNICORE?
Major Grid platform in European HPC community UNICORE is great for “HPC on demand” UNICORE6 implementation will have great performance and scalability Join forces in standards bodies

6 Globus Toolkit 4 Container
GPE Components GridBeans GridBeans GridBeans File Manager Application Client Portal Client Expert Client Admin Client GPE Client API Globus Toolkit 4 Container UNICORE6 container Service Registry BPEL Workflow Service Resource Broker OS Repository Service Service Registry BPEL Workflow Service Resource Broker Atomic Services Atomic Services TSI TSI

7 Atomic Services: Standard Grid Interfaces using WSRF
Add target system to Grid Target System Resource Hardware and software properties, workload, etc. Manage file transfers Use target system Job Resource Job status, description, owner, etc. Manage jobs Storage Resource Available file space, mount point, etc. Access storages File Transfer Resource Transferred bytes, used port numbers, etc. Operations Target System Factory Target System Service Job Management Service Storage Management Service File Transfer Service Services Resources Properties

8 How do GridBeans work? GridBeans encapsulate application logic
Expert Client Portal Client Applications Apps Client App1GB Application GridBean Application GridBean App2GB App3 GB Services download GridBean Service GridBeans encapsulate application logic GridBeans provide Swing interfaces for Java clients and JSR-168 portlets for web portals GridBeans create JSDL descriptions from user input

9 GPE: Running a Workflow
Applications send job description including workflow Implements Target System Service Interface BPEL Workflow Service Services Other web services Resource Broker orchestrate Atomic Services Data Center 1 Utility ...

10 A GPE-BPEL Workflow JSDL Submit JSDL to target system service
<invoke inputVariable="submitJobRequest" operation="Submit" outputVariable="submitJobResponse" partnerLink="targetSystem" portType="tss:TargetSystem" /> <assign> <copy> <from part="SubmitResponse" query="/tss:SubmitResponse/tss:JobReference" variable="submitJobResponse" /> <to partnerLink="jobManagement" /> </copy> </assign> <while condition="bpws:getVariableData('getJob1StateResponse', 'GetResourcePropertyResponse')/child::text()[1]!='READY' and bpws:getVariableData('getJob1StateResponse', 'GetResourcePropertyResponse')/child::text()[1]!='FAILED'"> <invoke inputVariable="getJobStateRequest" operation="GetResourceProperty" outputVariable="getJobStateResponse" partnerLink="jobManagement“ portType="u-rp:ResourcePropertiesPortType" /> </while> <invoke inputVariable="startJobRequest" operation="Start" outputVariable="startJobResponse" partnerLink="jobManagement" portType="jms:JobManagement" /> <while condition="bpws:getVariableData('getJobStateResponse', 'GetResourcePropertyResponse')/child::text()[1]!= 'SUCCESSFUL' and bpws:getVariableData('getJobStateResponse', Submit JSDL to target system service Retrieve the job EPR from the SubmitResponse through jobManagement partnerlink A GPE-BPEL Workflow Wait until the job status is READY or FAILED Start the job: Start request is stored in startJobRequest variable Wait until job status is SUCCESSFUL or FAILED

11 Implementing and Influencing Standards with GPE
Open Grid Forum (OGF) JSDL (Job Submission Description Language) GPE-BPEL extension OGSA (Open Grid Services Architecture) BES (Basic Execution Services) DMI (Data Movement Interface) ByteIO (File Transfer and Streaming) OASIS WSRF (Web Services Resource Framework) WSN (Web Services Notification) WSS (Web Services Security) WSBPEL (WS-Business Process Execution Language) W3C WS-Addressing, SOAP, WSDL, XML, etc.

12 Expert Client DEMO

13 Outlook: Using Virtual Machine Technology on the Grid
Reliability: Partitions remain unaffected if other partitions crash Security: Protect sensitive user data in VM instance Flexibility: VMs can checkpoint and migrate during run-time I want to move to a faster system, when it becomes available My job has high priority, please free the fastest machine for me Configurability: Dynamically deployed OS images and applications on user request I need two cores on a fast CPU with 1Gb of memory and RedHat Linux 9 Management: Maintenance of systems, software and users in centralized services

14 GPE Virtualization Globus virtual workspaces integrated in GPE
Collaboration with ANL team led by Kate Keahey Virtual target system factory invokes Globus workspace service to create XEN virtual machines OS Images are fetched from GPE OS Image Repository Service Available since GPE 1.3 Create show cases with CERN in OpenLab collaboration Use virtual machines for gLite testing Implement prototypes for virtual machines hosting gLite computing elements Create show cases with industrial customers

15 GPE Plans for 2007 Further exploit Intel technology
Use virtualization, management and security capabilities on new Intel platforms Leverage virtualization technology in the Grid Move towards Enterprise SOA Run proof of concepts at Intel customers and partners Identify concrete business needs Harden HPC-centric implementation for production environments Scalability, Robustness, Performance Implement prototypes of upcoming OGF specifications participate in “interop feasts”

16 Backup

17 History: From UNICORE to GPE
Pallas: German HPC software company implemented UNICORE client software Commercial version UNICOREpro in 2003 Other products included Vampir and VampirTrace (now Intel Trace Collector and Trace Analyzer) After Pallas’ acquisition by Intel in 2003, the new Open Source project GPE started Idea: Support Globus and other Grid Middleware implementations, too Keep the good concepts from UNICORE Graphical User Interfaces Resource Abstraction Client Plug-in Concept Ease of use

18 GridBean creates JSDL description from user interface
Running a Simple Job Applications GridBean creates JSDL description from user interface Application GridBean transfer input/output control job Services send job description Target System Service Job Mgmt. Service File Transfer Service Data Center Utility TSI TSI TSI

Download ppt "GPE4UNICORE Grid Programming Environment for UNICORE"

Similar presentations

Ads by Google