Alert.png The wiki is deprecated and due to be decommissioned by the end of September 2022.
The content is being migrated to other supports, new updates will be ignored and lost.
If needed you can get in touch with EGI SDIS team using operations @ egi.eu.

Difference between revisions of "EGI-InSPIRE:WP5 Provisioning the Software Infrastructure (SA2)"

From EGIWiki
Jump to navigation Jump to search
Line 134: Line 134:
| align="center" | 1
| align="center" | 1
| May 2010
| May 2010
|-
|- style="background:lightgray;"
! [https://documents.egi.eu/secure/ShowDocument?docid=69 MS502]
! [https://documents.egi.eu/secure/ShowDocument?docid=69 MS502]
| Deployed Middleware Support Unit Operations Procedures  
| Deployed Middleware Support Unit Operations Procedures  
Line 144: Line 144:
| TSA2.3
| TSA2.3
| align="center" | 2
| align="center" | 2
|-
|- style="background:lightgray;"
! [https://documents.egi.eu/secure/ShowDocument?docid=89 MS504]
! [https://documents.egi.eu/secure/ShowDocument?docid=89 MS504]
| EGI Software Repository – Architecture and Plans
| EGI Software Repository – Architecture and Plans
Line 154: Line 154:
| TSA2.2
| TSA2.2
| align="center" | 4
| align="center" | 4
|-
|- style="background:lightgray;"
! MS506
! MS506
| EGI Software Repository – Architecture and Plans
| EGI Software Repository – Architecture and Plans
Line 164: Line 164:
| TSA2.5
| TSA2.5
| align="center" | 14
| align="center" | 14
|-
|- style="background:lightgray;"
! MS508
! MS508
| Software Provisioning Process
| Software Provisioning Process
Line 174: Line 174:
| TSA2.2
| TSA2.2
| align="center" | 16
| align="center" | 16
|-
|- style="background:lightgray;"
! MS510
! MS510
| EGI Software Repository – Architecture and Plans  
| EGI Software Repository – Architecture and Plans  
Line 184: Line 184:
| TSA2.5
| TSA2.5
| align="center" | 26
| align="center" | 26
|-
|- style="background:lightgray;"
! MS512
! MS512
| Software Provisioning Process
| Software Provisioning Process
Line 194: Line 194:
| TSA2.2
| TSA2.2
| align="center" | 28
| align="center" | 28
|-
|- style="background:lightgray;"
! MS514
! MS514
| EGI Software Repository – Architecture and Plans
| EGI Software Repository – Architecture and Plans
Line 204: Line 204:
| TSA2.5
| TSA2.5
| align="center" | 38
| align="center" | 38
|-
|- style="background:lightgray;"
! MS516
! MS516
| Software Provisioning Process
| Software Provisioning Process

Revision as of 18:31, 18 November 2010

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 PM Calendary Month
D5.1 UMD Roadmap 3 July 2010
D5.2 UMD Roadmap 9 January 2011
D5.3 Annual Report on the status of Software Provisioning activity and the work of DMSU 11 March 2011
D5.4 UMD Roadmap 15 July 2011
D5.5 UMD Roadmap 21 January 2012
D5.6 Annual Report on the status of Software Provisioning activity and the work of DMSU 23 March 2012
D5.7 UMD Roadmap 27 July 2012
D5.8 UMD Roadmap 33 January 2013
D5.9 Annual Report on the status of Software Provisioning activity and the work of DMSU 35 March 2013
D5.10 UMD Roadmap 39 July 2013
D5.11 UMD Roadmap 45 January 2014
D5.12 UMD Roadmap 47 March 2014

Milestones

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