1 / 27

NGS in the future:  emerging middleware

NGS in the future:  emerging middleware. Mike Mineter mjm@nesc.ac.uk. Goal of talk. The NGS is running a production service Different middleware may be deployed in the future. The talk seeks to outline some of the possibilities. NGS middleware evolution. EGEE…. ETF. NGS.

willem
Download Presentation

NGS in the future:  emerging middleware

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. NGS in the future:  emerging middleware Mike Minetermjm@nesc.ac.uk

  2. Goal of talk • The NGS is running a production service • Different middleware may be deployed in the future. • The talk seeks to outline some of the possibilities

  3. NGS middleware evolution EGEE… ETF NGS Other software sources UK,Campus and other grids Software with proven capability & realistic deployment experience Prototypes & specifications Operations ‘Gold’ services Feedback & future requirements Engineering Task Force Deployment/testing/advice

  4. Outline • Middleware currently being prepared for deployment • Resource broker • Under assessment: • gLite middleware from EGEE • OMII • GT4

  5. Resource broker • (This is NOT the SRB!!!) • Current NGS middleware : Toolkits inviting development of higher level services • On the current NGS we have • GRAM to submit jobs • Information service to tell us what queues are busy • The RB takes the work out of deciding where to run a job

  6. Input “sandbox” DataSets info Output “sandbox” SE & CE info Job Submit Event Job Query Publish Job Status Storage Element Major components Replica Catalogue “User interface” Information Service Resource Broker Author. &Authen. Input “sandbox” + Broker Info Output “sandbox” Logging & Book-keeping Computing Element Job Status

  7. Resource broker • Job Description Language file: describes resources needed by a job • Commands analogous to GT2: • edg-job-submit <jdl filename> • edg-job-status <dg-job-id> • edg-job-get-output <dg-job-id>

  8. Example • edg-job-submit myjob.jdl • Myjob.jdl • JobType = “Normal”; • Executable = "$(CMS)/exe/sum.exe"; • InputSandbox = {"/home/user/WP1testC","/home/file*”, "/home/user/DATA/*"}; • OutputSandbox = {“sim.err”, “test.out”, “sim.log"}; • Requirements = other. GlueHostOperatingSystemName == “linux" && • other. GlueHostOperatingSystemRelease == "Red Hat 7.3“ && other.GlueCEPolicyMaxCPUTime > 10000; • Rank = other.GlueCEStateFreeCPUs;

  9. More about the RB • Developed by the European DataGrid project, EDG then “hardened” by LCG, and now one of the sources for the EGEE middleware • Uses components of Condor • matchmaker and Condor-G • Try the GENIUS portal on GILDA • GILDA is a dissemination grid running the LCG-2 middleware • Demo site: https://grid-demo.ct.infn.it/ • And look athttp://lcg.web.cern.ch/LCG/http://www.hep.ph.ic.ac.uk/e-science/projects/demo/index.html

  10. Resource broker -summary • The resource broker receives a job description in JDL • It chooses a batch queue for job submission, using the information services • Its an example of the higher services that can be deployed for the NGS, built upon the current toolkits

  11. Outline • Middleware currently being prepared for deployment • Resource broker • (NGS portal – yesterday!) • Under assessment: • gLite middleware from EGEE • OMII • GT4

  12. EGEE is building a large-scale production grid service to: Underpin research, technology and public service Link with and build on national, regional and international initiatives Foster international cooperation both in the creation and the use of the e-infrastructure Collaboration Pan-European Grid Operations, Support and training Network infrastructure& Resource centres EGEE – towards e-infrastructure

  13. Pilot New In the first 2 years EGEE will • Establish production quality sustained Grid services • 3000 users from at least 5 disciplines • integrate 50 sites into a common infrastructure • offer 5 Petabytes (1015) storage • Demonstrate a viable general process to bring other scientific communities on board • Propose a second phase in mid 2005 to take over EGEE in early 2006

  14. 70 leading institutions in 27 countries, federated in regional Grids ~32 M Euros EU funding for first 2 years starting April 2004(matching funds from partners) Leveraging national and regional gridactivities Promoting scientific partnershipoutside EU EGEE Organisation

  15. Activities Definition • Network Activities • NA1: Project Management • NA2: Dissemination and Outreach • NA3: User Training and Induction • NA4: Application Identification and Support • NA5: Policy and International Cooperation • Service Activities • SA1: Grid Support, Operation and Management • SA2: Network Resource Provision • Joint Research Activities • JRA1: Middleware Reengineering + Integration • JRA2: Quality Assurance • JRA3: Security • JRA4: Network Services Development Emphasis in EGEE is on operating a production grid and supporting the end-users

  16. Co-existence with deployed infrastructure Co-existence with LCG-2 and OSG (US) are essential for the EGEE Grid services Site autonomy Reduce dependence on ‘global, central’ services Open source license Service oriented approach Allow for multiple interoperable implementations Lightweight (existing) services Easily and quickly deployable Use existing services where possible Condor, EDG, Globus, LCG, … Portable Being built on Scientific Linux and Windows Security Sites and Applications Performance/Scalability & Resilience/Fault Tolerance Comparable to deployed infrastructure VDT EDG . . . AliEn LCG . . . gLite: Guiding Principles

  17. gLite Services for Release 1 JRA3 UK Access Services Grid AccessService API CERN IT/CZ Security Services Authorization Information & Monitoring Services Application Monitoring Information &Monitoring Auditing Focus on key services Authentication Data Services Job Management Services MetadataCatalog File & ReplicaCatalog JobProvenance PackageManager Accounting StorageElement DataManagement WorkloadManagement ComputingElement Site Proxy

  18. Open MiddlewareInfrastructure Institute • The slides that follow were selected and (in a few cases) modified by Mike Mineter (NeSC) from those presented in January 2005 at an OMII training daySteven Newhouse, Peter HendersonStephen Crouch & Karen Ng • Goal of this presentation: to raise awareness of the OMII and its OMII_1 release MM

  19. Open MiddlewareInfrastructure Institute OMII goal: to be the source of open source grid software • Institute of the University of Southampton • Utilise existing software and standards • Production focused software development • Integrate, test & document ‘a product’ • Focus on the user experience • Easy to install & use • Utilise existing software and standards • Provide a solid web service base for others to build on

  20. Where does our software come from? • Open Source Community • Tomcat, Axis, etc., • Software Repository • Accept software contributions • Software deployed, tested & graded to provide feedback • Managed Programme • Fill gaps to build a solid enabling infrastructure • Projects to bring research software to production quality

  21. Managed Programme • GridSAM (Job Submission & Monitoring service) • BPEL (Workflow service) • Grimoires (Registry service based on UDDI) • FIRMS (Reliable messaging) • FINS (Notification) • GeodiseLab (Matlab toolbox) • WSRF::Lite integration • OGSA-DAI (Database service) • WSeSS (Using SSH to tunnel requests to resources)

  22. OMII_1 release:A basic File-Compute Grid • Enables a generic computational task • Move input data from the client to the service provider • Process the data using an application on the service provider • Retrieve the output data from the service provider

  23. Resource Mgmt Servlet Acct Mgmt Servlet Account Allocation Data Job TestService Happy Axis Static Webpage AXIS TOMCAT OMII Server Infrastructure ExampleService PBAC WS-Security

  24. Try out the OMII_1 client ! • Register at www.omii.ac.uk & login • Goto the downloads page • Download the client distribution • SuSE 9.0 • Client may work on other Linuxs but no exhaustive testing • Windows XP (SP 1 & 2) • Distribution requires JDK 1.4.2_04 • Does not work with ‘just’ a JRE • Will not work with JDK 1.4.2_05/06 & JDK 1.5.0 • No testing with earlier JDKs.

  25. Outline • Middleware currently being prepared for deployment • Resource broker • (NGS portal – yesterday!) • Under assessment (by ETF for NGS): • gLite middleware from EGEE • OMII • GT4

  26. A Service-Oriented Infrastructure • Service-oriented applications • Wrap applications asservices • Compose applicationsinto workflows • Service-orientedinfrastructure • Provision physicalresources to support application workloads Users Composition Workflows Invocation ApplnService ApplnService Provisioning • Carl Kesselman at Globus Week, NeSC, 4th April – 8th April 2005

  27. Summary • Middleware currently being prepared for deployment • Resource broker • (NGS portal – yesterday!) • The context for the next generation of middleware:service orientation, based on WS and the emerging standards • Under assessment by the Engineering Task Force: • gLite middleware from EGEE • OMII • GT4

More Related