EGI-InSPIRE:WP5 Provisioning the Software Infrastructure (SA2)

From EGIWiki
Revision as of 20:07, 7 September 2010 by Michel (talk | contribs) (Deliverables)
Jump to: navigation, search

Wiki page for EGI InSPIRE SA2 activities

WP5-SA2

This activity will coordinate the external provision of software required by EGI to form the production infrastructure. It will:

  • Establish agreements with key software providers
  • Maintain the UMD Roadmap
  • Define general and component specific quality criteria to be applied to software components
  • Verify the software components against these criteria
  • Provide a repository for the software components within UMD and the related support tools
  • Provided a distributed "support unit" within the EGI Helpdesk infrastructure with expertise on the deployed middleware in production use.

Task Leaders

To contact all task leaders (see below), send mail to inspire-sa2@mailman.egi.eu[1].

Involved partners

EGI.eu - Netherlands
CESNET - Czech Republic
KIT-G - Germany
CSIC - Spain
GRNET - Greece
INFN - Italy
LIP - Portigal
UCPH - Denmark
VR-SNIC - Sweden
NORDUNET A/S - Denmark


TSA2.1 Activity Management (CTO, EGI.eu)

This task focuses on the management of the activity and the relationship with EGI’s software providers. Prioritised requirements from elsewhere in EGI are collated and distributed to the current software providers and published for the whole community. The functional roadmaps and release dates from individual software providers are assembled into an integrated UMD Roadmap. The projected UMD Roadmap is monitored and the effectiveness of software providers to deliver components to the required schedule and quality will be reported to the TCB. This work will be managed by the Technology Manager who reports to the Project Director and will hold regular meetings of the team to ensure effective coordination of its activities. Additional meetings will be held with the external providers to provide a forum for conflict resolution.

TSA2.2: Definition of the UMD quality criteria (Enol Fernandez, CSIC)

The generic component acceptance criteria will be provided and updated according to evolving needs. Specific criteria will be developed for components on the UMD Roadmap.

TSA2.3: Verification of conformance criteria (Carlos Fernandez, CESGA)

The components contributed to the repository will be validated against the generic and component specific conformance criteria. SA2 will be involved in pre-release component testing. Verification of each component will be summarised in an acceptance report, available with the component in the repository.

TSA2.4: Provision of a software repository and support tools (Kostas Koumantaros, GRNET)

Necessary services to deliver the functionality of the repository and its surrounding process (FTP server, web server, issue tracker, version control system, etc.) will be provided and maintained.

TSA2.5: Deployed Middleware Support Unit (Michael Gronager, NDGF)

Expertise is needed in the production infrastructure to debug problems and then to propose workarounds or solutions with the software used in production. This group will be deployed as a support unit (second line support) as part of the EGI Helpdesk and it will work closely with other EGI operations functions and the external software providers.

Deliverables

Code Title Delivery Date
D5.1 UMD Roadmap 3
D5.2 UMD Roadmap 9
D5.3 Annual Report on the status of Software Provisioning activity and the work of DMSU 11
D5.4 UMD Roadmap 15
D5.5 UMD Roadmap 21
D5.6 Annual Report on the status of Software Provisioning activity and the work of DMSU 23
D5.7 UMD Roadmap 27
D5.8 UMD Roadmap 33
D5.9 Annual Report on the status of Software Provisioning activity and the work of DMSU 35
D5.10 UMD Roadmap 39
D5.11 UMD Roadmap 45
D5.12 UMD Roadmap 47

Milestones

Code Title Delivery Date
MS501 Establishment of the EGI Software Repository and associated support tools 1
MS502 Deployed Middleware Support Unit Operations Procedures 2
MS503 Software Provisioning Process 2
MS504 EGI Software Repository – Architecture and Plans 3
MS505 Service Level Agreement with a Software Provider 4
MS506 EGI Software Repository – Architecture and Plans 13
MS507 Deployed Middleware Support Unit Operations Procedures 14
MS508 Software Provisioning Process 14
MS509 Service Level Agreement with a Software Provider 16
MS510 EGI Software Repository – Architecture and Plans 25
MS511 Deployed Middleware Support Unit Operations Procedures 26
MS512 Software Provisioning Process 26
MS513 Service Level Agreement with a Software Provider 28
MS514 EGI Software Repository – Architecture and Plans 37
MS515 Deployed Middleware Support Unit Operations Procedures 38
MS516 Software Provisioning Process 38
MS517 Service Level Agreement with a Software Provider 40