INFSOM-RI Project Overview Alberto Di Meglio Project Manager 2

INFSOM-RI Summary ETICS 2 in a nutshellETICS 2 in a nutshell The ETICS 2 PartnersThe ETICS 2 Partners ETICS 2 OrganizationETICS 2 Organization Major ObjectivesMajor Objectives Work Packages GoalsWork Packages Goals RelationshipsRelationships The ETICS SystemThe ETICS System Deliverables, reporting, timelineDeliverables, reporting, timeline

INFSOM-RI ETICS 2 in a Nutshell ETICS 2 stands for e-Infrastructure for Testing, Integration and Configuration of Software – Phase 2ETICS 2 stands for e-Infrastructure for Testing, Integration and Configuration of Software – Phase 2 It’s a CCP/CSA (I3) projectIt’s a CCP/CSA (I3) project It has been granted a contribution of ~2.7 M€It has been granted a contribution of ~2.7 M€ It has a duration of two yearsIt has a duration of two years The project has started on March 1 st, 2008The project has started on March 1 st, 2008

INFSOM-RI The ETICS 2 Partners

INFSOM-RI ETICS 2 Organization Project Manager NA1 Project administrative and technical management (CERN) NA2 Dissemination, training and certification (ENG) SA1 Service Management (CERN) SA2 Infrastructures Support (INFN) Advisory Board PMBTechnical Committee Management and Coordination Service (Other) Joint Research

INFSOM-RI Major Objectives Objective 1: Extension of the ETICS services to new infrastructuresObjective 1: Extension of the ETICS services to new infrastructures Objective 2: Enhancement of the services, federation and customization of resourcesObjective 2: Enhancement of the services, federation and customization of resources Objective 3: International collaborations, procedures and standardsObjective 3: International collaborations, procedures and standards Objective 4: Commercial exploitation and business strategiesObjective 4: Commercial exploitation and business strategies

INFSOM-RI NA1 – Administrative and Technical Coordination Coordinator: CERNCoordinator: CERN Participants: all partnersParticipants: all partners Objectives:Objectives: –Ensure the consistency of the overall resources used and the work performed. –Control the progress of the work so that the results of the project adhere to the grant agreement. –Organise and co-ordinate the production of deliverables, meetings, workshops. –Resolve any project internal conflicts and build accountability into the project's work. –Report on project progress to the EC and to potential project sponsors. –Represent the project vision and mission in European and International events

INFSOM-RI NA2 - Dissemination, Training and Certification Coordinator: EngineeringCoordinator: Engineering Participants: CERN, INFN, 4DSOFT, VEGAParticipants: CERN, INFN, 4DSOFT, VEGA Objectives:Objectives: –Increase awareness and knowledge about the ETICS system and its service by delivering dissemination and training events –Make the ETICS Grid Quality Certification Model known and accepted by wide audiences of users by promoting it and integrating it with other established quality assurance procedures –Speed up the creation on business activities by analysing business cases, charging models and service level agreements and possibly implementing one case study example in collaboration with commercial enterprises within or outside the consortium

INFSOM-RI SA1 – Service Management Coordinator: CERNCoordinator: CERN Participants: INFN, ENG, 4DSOFT, Wisconsin, SZTAKIParticipants: INFN, ENG, 4DSOFT, Wisconsin, SZTAKI Objectives:Objectives: –Maintain and extend existing ETICS core functionality, including documentation –Improve security of core services, such that sites autonomy and security is preserved, while the integrity of the overall eInfrastructure is ensured –Delivery of federated and secure software repositories and release management tools –Automation of the core service monitoring system (e.g. alerts should be triggered when monitored parameters exceed expected thresholds) –Provide second level user support including systematic tracking of support tickets –Regularly review and integrate extensions from SA2 and community contributions and results from JRA activities –Assessment and implementation of scalability strategies to ensure high availability of core services and infrastructure –Apply ETICS Certification Process to ETICS core services. The core services should pass the certification level 2 at the end of year 1 and level 3 at the end of year 2

INFSOM-RI SA2 – Infrastructures Support Coordinator: INFNCoordinator: INFN Participants: 4DSOFT, SZTAKI, FZJ, VEGAParticipants: 4DSOFT, SZTAKI, FZJ, VEGA Objectives:Objectives: –Speed up the extension of the ETICS build, test and certification services to new infrastructures, starting with the DEISA and the Aerospace Engineering community –Assist ETICS infrastructure providers in deploying and using the ETICS services efficiently to provide software development services to their users by providing first- level user support, escalation procedures and an on-line knowledge base of frequently asked questions and answers –Improve the functionality and efficiency of the ETICS system by collecting and organizing user requirements, implementing methods and tools to satisfy them, assisting in the integration of ETICS within existing services, analysing the ETICS performance and usability ‘on the field’ with respect to efficiency, scalability and fault- tolerance and defining possible improvement strategies and prototype implementations –Produce a set of guidelines for new infrastructures to facilitate the migration to ETICS and lower the initial learning curve

INFSOM-RI JRA1 – Testbed Management Technologies Coordinator: WISCONSINCoordinator: WISCONSIN Participants: ENG?Participants: ENG? Objectives:Objectives: –Develop technologies to allow efficient and secure federation of resource sites –Develop or integrate virtualization technologies in the job management middleware and in the system management tools to lower the local site maintenance costs, increase security and enable new operational models, such as the sharing or pre- configured virtual images or the off-line analysis of build and test failures –Modify the job submission middleware and the ETICS system management tools to run on IPv6 networks

INFSOM-RI JRA2 – Test Management Tools Coordinator: 4D SoftCoordinator: 4D Soft Participants: CERN, SZTAKIParticipants: CERN, SZTAKI Objectives:Objectives: –Develop the necessary test interface standards for proper collaboration of testing and static analysis tools –Develop a tool by which the testing tools providers can register their tools as Web Services to be integrated into the ETICS testing infrastructure –Develop an interface for the users to construct their testing process in a convenient way –Develop a test execution system to validate the test sequence and generate a specification for the ETICS Execution Engine –Provide the means for users to visualise their test results

INFSOM-RI Internal Relationships

INFSOM-RI External Relationships Infrastructures:Infrastructures: –EGEE –DEISA ProjectsProjects –EGEE/gLite –D4Science –Aerospace Community –LCG/Physics experiments (CERN) Collaboration and Standardization BodiesCollaboration and Standardization Bodies –OGF (US and Europe) –ETSI –ISO

INFSOM-RI Deliverables Each WP has a number of deliverables to produce, mainly under the form of written reportsEach WP has a number of deliverables to produce, mainly under the form of written reports Each deliverable has an associated contractual submission date indicated on the DoW in terms of Project Months (PM)  no more 45 days periodEach deliverable has an associated contractual submission date indicated on the DoW in terms of Project Months (PM)  no more 45 days period The deliverable submission process is described in detail in the Project QA Plan. In summary:The deliverable submission process is described in detail in the Project QA Plan. In summary: –At PM-15: WP leader submit deliverable to technical committee –At PM-7: Appointed reviewers revise and provide comments –At PM-2: WP leaders submit final version to Project Manager All deliverables must follow the same project templateAll deliverables must follow the same project template

INFSOM-RI Reporting Three types of reporting:Three types of reporting: –Quarterly Reports –Describe the achievements and progress of the projects every three months –Follow an EC template –Prepared by the Project Manager based on contributions from the WP leaders –Similar preparation schedule as deliverables: –PM-15: WP send contributions to PM –PM-7: PM send QR to PMB and Technical Committee –PM-2: Comments to PM for final version –Periodic Report: within 60 days from end of Period 1, using EC template –Final Report: within 60 days from end of project, using EC template

INFSOM-RI Project Timeline Mar 08Sep 08Mar 09Sep 09Mar 10 Kick-off I Review II Review All-hands meeting Two projects are issued with a Grid-QCM certificate (gLite, UNICORE) Four projects are issued with a Grid-QCM certificate First new infrastructure applications built and tested with ETICS ETICS runs on different infrastructures