Transition from egee to egi l.jpg
This presentation is the property of its rightful owner.
Sponsored Links
1 / 19

Transition from EGEE to EGI PowerPoint PPT Presentation


  • 57 Views
  • Uploaded on
  • Presentation posted in: General

Transition from EGEE to EGI. Bob Jones – Project Director - CERN EGI workshop (CERN) 30 June 2007. Contents. EGEE-III to EGI transition as seen from EGEE’s side

Download Presentation

Transition from EGEE to EGI

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.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.


- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -

Presentation Transcript


Transition from egee to egi l.jpg

Transition from EGEE to EGI

Bob Jones – Project Director - CERN

EGI workshop (CERN)

30 June 2007


Contents l.jpg

Contents

  • EGEE-III to EGI transition as seen from EGEE’s side

  • Based on feedback received from the EGEE-III activity managers to v1.0 of the EGI blueprint that was distributed on Monday 23rd June 2008

EGEE to EGI transition - Bob Jones - EGI workshop - 30 June 2008


Egee iii l.jpg

EGEE-III

  • EGEE-III

    • Co-funded under European Commission call INFRA-2007-1.2.3

    • 32.0M€ EC funds compared to ~36.9M€ for EGEE-II

    • Total of 375 FTEs in EGEE-III (combining funded and matching contributions)

      • ~20% less than EGEE-II

  • Key objectives

    • Expand/optimise existing EGEE infrastructure, include more resources and user communities

    • Prepare migration from a project-based model to a sustainable federated infrastructure based on National Grid Initiatives

  • 2 year period – 1 May 2008 to 30 April 2010

    • No gap between EGEE-II and EGEE-III (1 month extension to EGEE-II, ended 30 April 2008)

  • Similar consortium

    • Now structured on a national basis (National Grid Initiatives/Joint Research Units)

EGEE to EGI transition - Bob Jones - EGI workshop - 30 June 2008


The european grid initiative l.jpg

The European Grid Initiative

  • A plan has been madewith the EGI Design Study project to ensure the knowledge and experience gained by EGEE is fed intothe EGI planning process

  • EGI_DS produced and discussed a draft blueprint in June 2008

  • Updated blueprint to be discussed at EGEE’08

  • Produce revised programme of work based on changes possible in year 2 of EGEE-III

EGEE to EGI transition - Bob Jones - EGI workshop - 30 June 2008


Consortium l.jpg

Consortium

  • From 91 partners in EGEE-II (+ further 48 JRU members)

  • To 42 Beneficiaries in EGEE-III (+ 100 JRU members)

    • This change has been made in preparation for a sustainable infrastructure based on a federation of national e-Infrastructures

  • Joint Research Units (precursors to National Grid Initiatives):

    • Austria

    • Belgium

    • Bulgaria

    • Croatia

    • Cyprus

    • France

    • Germany

    • Greece

    • Hungary

    • Israel

    • Italy

  • JRU members are invited to Collaboration Board meetings as Observers

  • Netherlands

  • Norway

  • Poland

  • Romania

  • Russia

  • Spain

  • Sweden

  • Switzerland

  • Turkey

  • United Kingdom

EGEE to EGI transition - Bob Jones - EGI workshop - 30 June 2008


Country reviews l.jpg

Country Reviews

The EGEE-III consortium is notable by its size and the inclusion of Joint Research Units and National Grid Initiatives facilitating the evolution to national structures

Take into account the experience gained from the activity and partner reviews introduced during EGEE-II

Goals

Monitor the progress of the programme of work in each country and the involvement of individual partners

Provide a forum to discuss issues, examine progress and contribution and establish better communication between individual partners, the activity managers and project management

Identify and promote regional successes and initiatives for re-use in other countries

Encourage national responsibility and reporting

Verify the state of readiness for the transition to EGI

Output

Publishable report at the end of each year (spring 2009, spring 2010)

EGEE to EGI transition - Bob Jones - EGI workshop - 30 June 2008

6


Activity feedback on draft blueprint l.jpg

Activity feedback on draft blueprint

Questions posed:

  • What are the keys differences you see between how your EGEE-3 activity is organised and the proposed functions/structure in the blueprint?

  • Do you see any gaps in the proposed functions that could inhibit the operation of the infrastructure or its use by existing and new user communities?

  • Do you foresee any problems with the proposed distribution of responsibility across EGI.org and NGIs?

  • What are the important points/steps that need to be taken into account in the transition?

  • NA3 – training

    • Found blueprint version 1.0 to be incomplete so have contributed to v1.2

  • NA4 – application support

    • Found blueprint version 1.0 to be incomplete so have contributed to v1.2

    • Many points already covered in Patricia’s talk

EGEE to EGI transition - Bob Jones - EGI workshop - 30 June 2008


Operations l.jpg

Operations

  • EGEE is already a distributed operational model

  • EGEE-III will further develop the operational tools during its 1st and 2nd year

  • The transition plan will be documented in October’08 (DNA.14)

    • This plan will detail the steps needed to migrate EGEE’s operation to EGI, identify major risks and shortcomings and develop stop gap strategies in case a full transition seems unlikely in the remaining lifetime of EGEE-III. This plan may result in a modified Description of Work for EGEE-III updated for the second year.

EGEE to EGI transition - Bob Jones - EGI workshop - 30 June 2008


Users and resources distribution l.jpg

Users and resources distribution

EGEE to EGI transition - Bob Jones - EGI workshop - 30 June 2008


Grid middleware l.jpg

Grid Middleware

Applications

  • Applications access both Higher-level Grid Services and Foundation Grid Middleware

  • VOs complement gLite with other high-level services via the RESPECT programme

    • Rec. External Software Pkgs. for the EGEE Community

    • Identify useful, 3rd-party software that works with gLite

    • Make users aware of that software to avoid duplicated efforts

Higher-Level Grid Services

Workload Management

Replica Management

Visualization

Workflow

Grid Economies

...

Foundation Grid Middleware

Security model and infrastructure

Compute (CE) and Storage Elements (SE)

Accounting

Information and Monitoring

EGEE to EGI transition - Bob Jones - EGI workshop - 30 June 2008


E infrastructure policy group l.jpg

e-Infrastructure Policy Group

  • Creation of the e-Infrastructure Policy Group

    • EGEE (EU)

    • DEISA (EU)

    • NAREGI (Japan)

    • TeraGrid (US)

    • OSG (US)

  • First meeting at OGF22 (Boston, Feb’08)

  • Authentication, Authorization, Accounting, and Auditing (AAAA) are seen as the areas of highest priority for aligning policies across the Infrastructures

  • Next meeting at OGF24 (Singapore, Sept’08)

EGEE to EGI transition - Bob Jones - EGI workshop - 30 June 2008


Quality assurance l.jpg

Quality Assurance

  • There is no material about how the quality of service provided by EGI will be measured

    • NGIs and user communities need to agree on a set of basic metrics that can be easily measured and which give a good indication on quality of the services provided by EGI

  • “The EGI must undergo a review on a 3-5 year cycle of its funding model and required budget, based on the actual usage of the EGI, available commercial technologies, and the innovation required ”

    • EGEE’s annual reviews have been very useful, why not continue them in EGI?

EGEE to EGI transition - Bob Jones - EGI workshop - 30 June 2008


Business relations l.jpg

Business relations

  • “Business usage is then limited, and primarily in form of research collaborations with European and national research institutes, universities and other educational institutions………EGI.org should act positively towards such initiatives and establish policies allowing emerging companies and other initiatives a fair competition in providing services for the EGI.”

    • Are companies allowed to connect resources to EGI?

    • Can commercial providers contribute to UMT?

EGEE to EGI transition - Bob Jones - EGI workshop - 30 June 2008


Grids and cloud computing l.jpg

Grids and Cloud Computing

  • Objective:

    • As cloud computing gains popularity and traction, need to position grid computing with respect to cloud computing

    • https://edms.cern.ch/file/925013/3/EGEE-Grid-Cloud.pdf

    • Compare real implementations and production offerings

      • EGEE/gLite grid production service

      • Amazon Web Services, with focus on EC2 and S3

  • EGEE report produced

    • “An EGEE Comparative study: Grids and Clouds-evolution or revolution?”

    • Presented at OGF23 (Barcelona, June’08) and covered in the press

  • Outcome:

    • Identified convergence paths and

    • Recommendations for managing convergence going forward

  • Future:

    • Investigate the possibility of gateways between EGEE and commercial cloud systems to offer a migration path for under-resourced applications (no national support or mature commercial applications)

EGEE to EGI transition - Bob Jones - EGI workshop - 30 June 2008


Egee 08 conference l.jpg

EGEE’08 conference

  • Opening (Monday, AM) – EC position on funding opportunities through to 2012?

  • EGI plenary (Monday, AM) – present updated blueprint

  • EGI sessions (Monday, PM) – discuss the transition from EGEE & collaborating projects

  • Business track (Monday, PM) – get feedback from business community

  • Exhibition (Monday - Wednesday) – NGIs & collaborating projects can reserve booths

    prospectus http://egee08.eu-egee.org/index.php?id=343

EGEE to EGI transition - Bob Jones - EGI workshop - 30 June 2008


Future plans l.jpg

Future plans

  • Provide written feedback

    • 1 week between the distribution of the EGI blueprint and this workshop did not permit enough time for a wide and detailed analysis

  • Discuss final blueprint at EGEE08 (Sept’08)

  • Identify transition steps during Q4 2008

    • All the steps necessary to migrate from EGEE to EGI

  • Determine practical steps that EGEE-III can make (Q1 2009)

    • Determine which steps can be implemented during the 2nd year of EGEE-III without negatively impacting the services provided to EGEE’s user communities

  • Q2 2009

    • Integrate agreed transition steps into programme of work

      • With agreement of EGEE-III beneficiaries and the European Commission

EGEE is a production infrastructure and its highest priority will always be toprovide continuous support to its user communities

EGEE to EGI transition - Bob Jones - EGI workshop - 30 June 2008


Recommendations for blueprint 1 3 l.jpg

Recommendations for blueprint (1/3)

  • Middleware

    • List the essential services to better define the scope

    • Introduce the concepts of foundation and higher-level services and acknowledge that EGI cannot provide all possible services

    • Approach UMT in a step-wise manner - start with closer integration of gLite and ARC

    • Formalise support arrangements with USA for VDT (Globus & Condor etc.)

    • Review the effort ratio between middleware producers and integration/testing

    • Do not exclude external development teams

    • Emphasize the priorities of stability, scalability, portability, ease-of-use, ease-of-operation in any middleware development

  • Formalise agreements with DEISA/PRACE concerning sharing/access to resources

EGEE to EGI transition - Bob Jones - EGI workshop - 30 June 2008


Recommendations for blueprint 2 3 l.jpg

Recommendations for blueprint (2/3)

  • Clearly separate development required for operational tools (configuration database, trouble-ticketing, operational portal etc.) from middleware itself

  • Pre-production & pilot services should be considered as a ‘service’ not a testbed and associated with operation function

  • A clearly defined working relationship between grids (EGI.org/NGIs) and the network providers (NRENS/GEANT etc.) must be maintained (trouble ticket standardisation, Service Level Agreements, monitoring etc.)

    • Must maintain expertise in networking domain

EGEE to EGI transition - Bob Jones - EGI workshop - 30 June 2008


Recommendations for blueprint 3 3 l.jpg

Recommendations for blueprint (3/3)

  • Acknowledge independence of NGIs but put mechanisms in place to ensure NGI cooperation

    • Cooperation is essential for operations, dissemination, training, application support and dissemination since the ‘core’ EGI.org teams have limited effort

  • Develop use cases for life sciences, high-energy-physics and one other discipline showing how these user communities would interact with EGI

  • Further develop business relations to explain how EGI can engage commercial service and software providers

    • Consider EGEE’s Business Associate programme, industry forum etc.

    • Define relationship to business-focused projects such as RESERVOIR

  • Explore links with other European Commission structures

    • Other directorates, ERC, COST, ESOF, etc.

  • Make the final blueprint available by 1st September

    • To give all the stakeholders and groups involved sufficient time to study the contents and consult with partners

EGEE to EGI transition - Bob Jones - EGI workshop - 30 June 2008


  • Login