1 / 49

New Ideas for Computing Environments

New Ideas for Computing Environments. The Grid Portal for Industry and Research. Alberto Falzone, Andrea Rodolico NICE srl www.nice-italy.com e-mail: info@nice-italy.com. Contents. EnginFrame: the Framework for Computing Portals/Gateways Evolution from 3.2 to 4.1 version

Download Presentation

New Ideas for Computing Environments

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. New Ideas for Computing Environments The Grid Portal for Industry and Research Alberto Falzone, Andrea Rodolico NICE srl www.nice-italy.com e-mail: info@nice-italy.com

  2. Contents • EnginFrame: the Framework for Computing Portals/Gateways • Evolution from 3.2 to 4.1 version • Industrial adoption overview • GENIUS: new features, improvements • The Changes in the backend and the stack on the gLite UI • New Features, Improvements • Management of User Security • GENIUSphere • JSR168 compliance from GENIUS/EnginFrame • EnginFrame Portlets in GridSphere

  3. A grid portal: why and how • It can be accessed from everywhere and by “everything” (desktop, laptop, PDA, cell phone). • It can keep the same user interface to several back-ends. • It must be redundantly “secure” at all levels: • 1) secure for web transactions, • 2) secure for user credentials, • 3) secure for user authentication, • 4) secure at VO/VOMS level. • 5) secure in data management • All available grid services must be incorporated in a logic way, just “one mouse click away”. • Its layout must be easily understandable and user friendly.

  4. The Grid Portal vision Licenses & Data Clients Inter/Intranet Server(s) Interactive Apps Standard Web Technology Grid / Compute Farm

  5. EnginFrame as Grid Gateway Portlet Containers 3rd party Apps RSS Clients WSDL/SOAP HTTP JSR168 End users Portlet GW RSS GW WS GW ISV 1 - XML Application Kit ISV n - XML Application Kit Compute Grid (Globus, LSF, SGE, …) COTS WF manager Data Grid (AFS, SRB, …) Internal HW/SW On-demand HW/SW Workflows Storage Skins / Themes Presentation engine Single-Sign-On Authentication – ACL management GUI Virtualization Custom XML Application Kits Accounting / Billing Data Management & Virtualization

  6. EnginFrame evolution 1.x - LAN Integration (1998) • Unix-Windows integration for simplified parallel and distributed computing 2.x - WAN MetaComputing interface (1999) • Standards convergence, dynamic contents management 3.x - Computing Portal (2000-2003) • Web architecture, JS independence, Globus integration 3.5 – Enterprise Grid Portal (2004) • Fault tolerance, Auth delegation, Authorization 4.x – Grid Gateway (2005) • WS-I compliancy, user mapping, enhanced Data management, RSS notification, JSR168 portlet gateway

  7. Flexible Input data access • Client-side data • HTTP(S) data transfer • Single/multiple upload • Progress bars for large file tracking • Server-side data • Standards-based remote navigation • Single-multiple selections • Flexible navigation sources • Support for Windows, Linux and UNIX browsers

  8. Comprehensive Output data management • File management • Flexible MIME type detection • Single / multiple download • Zip, tar, delete and other actions • Progress monitoring • “tail –f” streaming download • Stdout/stderr display • Can be extended with custom progress reporting • Flexible data life-cycle management

  9. Authorization system End users ACL management Services Option sets Field contents XML output

  10. The Authorization Framework • Authorization System is aimed to authorize useraccesses to resources • allowing or denying operations • according to a set of predefined policies. • Actor concept abstracts users. An actor can represent • single user • group of users • EnginFrame resources are: • folders • services • service options • service action • service output • Authorization policiesare defined by Access Control Lists

  11. The Grid Gateway WS Client WebServices gateway Presentation layer Service discovery Service execution Data retrieval Flow monitoring

  12. Client Reference Implementation Software Bundle • It is possible to request the EF Web Services Java Client Reference Implementation from support@enginframe.com • The Java Client Reference Implementation software bundle includes • Java stubs classes • Java client layer: client + utility classes • Required Java libraries: Axis, Jakarta-httpclient • Javadoc of the client API • Client examples with sources • Implementation for other languages (.NET, Phyton, Perl) are also available

  13. Who uses EnginFrame? Mechanical Ferrari, Audi, BMW, FIAT Auto, Delphi, Elasis, Magneti Marelli, P+Z, Swagelok, Toyota, TRW Manufacturing Bridgestone, Procter & Gamble, Galileo Avionica, Pirelli Oil&Gas Slavneft, Schlumberger, TOTAL, VNIIGaz Electronics STMicroelectronics, Accent, SensorDynamics, Motorola Others Telecom Italia Research INFN, ASSC, CCLRC, CERN, CILEA, CINECA, CNR, CNRS/IN2P3, ENEA, FzU, ICI, IFAE, ITEP, JSC G.G.M., KU Leuven, SSC-Russia, SDSC Education Dresda University, Ferrara University, ITU, Messina University, Politecnico of Milan, Technische Universität Dresden, Trinity College Dublin, Salerno University, S-PACI

  14. Corporate ASPs

  15. E-Design collaboration Black-box for EDA simulation

  16. HPC demo-center & ASP http://www.GridAge.com

  17. Application integrations

  18. How they look like

  19. 3D preview integration

  20. Portal to multiple Grids

  21. Contents • EnginFrame: the Framework for Computing Portals/Gateways • Evolution from 3.2 to 4.1 version • Industrial adoption overview • GENIUS: new features, improvements • The Changes in the backend and the stack on the gLite UI • New Features, Improvements • Management of User Security • GENIUSphere • JSR168 compliance from GENIUS/EnginFrame • EnginFrame Portlets in GridSphere

  22. GENIUS: new version • Powered by EnginFrame 4.1 !! • The Stack on the User Interface: • Apache + Mod_JK2 ; • Mod_SSL for secure encrypted connections ; • Tomcat as servlets container ; • EnginFrame 4.1.1 as core of 3-tier model • Thanks to New EF 4.1.1 features, NOW GENIUS Portal can export its services in JSR168 as portlets! • New Flexibility of EF 4.1.1 improves the ways to write the code for grid integrations: plugins as independent modules • Improved virtualization of Remote File Browsing • A power GridML has been created for Job details • Available the MyProxy Applet for MyProxy Inizialization!

  23. GENIUS architecture 3rd party Apps RSS Clients Portlet Contaiers WSDL/SOAP HTTP JSR168 End users Portlet GW RSS GW WS GW VO 1 - XML Application Kit VO n - XML Application Kit EGEE middleware LCG-2 / gLite Globus middleware Local Data Distributed Data Compute resources Classic GENIUS Presentation engine MyProxy auth. w/ VOMS extensions Authentication – ACL management VNC remote Desktop over SSL General XML Application Kits Monitoring & Accounting Data Management & Virtualization

  24. The GENIUS hourglass model GENIUS web portal Applications’ specific layer ALICE ATLAS CMS LHCb Other apps EGEE (LCG/gLite) architecture High level GRID middleware Basic Services GLOBUS toolkit OS & Net services GENIUS Grid Enabled web eNvironment for site Independent User job Submission INFN / NICE Collaboration

  25. GENIUS: files management Remote File Browser On the User Interface

  26. GENIUS: files management Multiple Action in a Single Service <ef:service id="edit-file"> <ef:name>View/Edit a File</ef:name> <ef:info>With this service you may edit a file in your home directory. </ef:info> <ef:option id="filetoedit" label="Select File to View/Edit" type="rfb" base="${HOME}" target="@genius"/> <ef:action id="view" label="View"> $EF_ROOT/plugins/genius/bin/geniusgrid.sh view-file <ef:result type="text/html"/> </ef:action> <ef:action id="edit" label="Edit"> $EF_ROOT/plugins/genius/bin/geniusgrid.sh edit-file <ef:result type="text/xml"/> </ef:action> </ef:service>

  27. GENIUS: Grid Authentication with Myproxy myproxy-get-delegation

  28. GENIUS: security GILDA Collaboration: Thanks to the contribute of Valeria Ardizzone Loaded on laptop or local WS!

  29. GENIUS: security

  30. GENIUS: preferences

  31. GENIUS:Graphic Workflow Editor(Integration with TRIANA from GridLab Project)

  32. GENIUS: Job Queue Code for Job Queue management rewritten using GridML tags

  33. GridML sample: job <grid:job-list type="lsf" xmlns:grid="http://www.enginframe.com/2000/GRID"> <grid:job type="lsf" id="4120"> <grid:owner>andrea</grid:owner> <grid:account>default</grid:account> <grid:status>DONE</grid:status> <grid:queue>priority</grid:queue> <grid:command>/usr/bin/spamc</grid:command> <grid:submission-time month="Jan" day="21" hour="23" minute="06" year="2005"/> <grid:submission-host>mail</grid:submission-host> <grid:submission-directory>$HOME</grid:submission-directory> <grid:execution-time month="Jan" day="21" hour="23" minute="06" year="2005"/> <grid:execution-host>mail</grid:execution-host> <grid:termination-time month="Jan" day="21" hour="23" minute="06" year="2005"/> <grid:total-cpu-usage>0.0</grid:total-cpu-usage> <grid:exit-code>0</grid:exit-code> </grid:job> </grid:job-list>

  34. GENIUS: Job Queue New Confirmation Message!

  35. GENIUS: Job Queue - Spooler Actions can be performed as facilities in downloading operations!

  36. Contents • EnginFrame: the Framework for Computing Portals/Gateways • Evolution from 3.2 to 4.1 version • Industrial adoption overview • GENIUS: new features, improvements • The Changes in the backend and the stack on the gLite UI • New Features, Improvements • Management of User Security • GENIUSphere • JSR168 compliance from GENIUS/EnginFrame • EnginFrame Portlets in GridSphere

  37. GENIUSphere: How it works GENIUS Server (UI) GridSphere portlet container + EF Portlets https + genius auth Instance of JSR168 portlets WebServices Output Every Genius Service can be considered as a singol atom to build a specific custom portal based on a portlet container like GridSphere that can dialog with the EGEE Grid Middleware !

  38. GENIUSphere : files

  39. GENIUSphere: files Files on the User Interface , where GENIUS is running!

  40. GENIUSphere: files

  41. GENIUSphere: security

  42. GENIUSphere: Accounting

  43. GENIUSphere: Jobs

  44. GENIUSphere: Jobs

  45. GENIUSphere: Jobs

  46. GENIUSphere: Jobs

  47. GENIUSphere: Data - Navigate

  48. Grid Gateway User Group proposal • Open community for GENIUS and EnginFrame plugin developers • Info forum on major happenings in the Grid Gateway arena • Blog / newsgroup for technical discussions • Repository for portlet / plug-in developers • Industrial plug-ins for EnginFrame • Open source plug-ins for GENIUS • Other contributed components (e.g. GridSphere portlets, etc.) • Volunteers are welcome! • Please contact: • roberto.barbera@ct.infn.it • livia@bio.dist.unige.it • info@nice-italy.com

  49. Thanks for your attention! Q&A

More Related