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)"
| Line 139: | Line 139: | ||
| TSA2.5 | | TSA2.5 | ||
| align="center" | 2 | | align="center" | 2 | ||
| June 2010 | |||
|- | |- | ||
! [https://documents.egi.eu/secure/ShowDocument?docid=68 MS503] | ! [https://documents.egi.eu/secure/ShowDocument?docid=68 MS503] | ||
| Line 144: | Line 145: | ||
| TSA2.3 | | TSA2.3 | ||
| align="center" | 2 | | align="center" | 2 | ||
| June 2010 | |||
|- style="background:lightgray;" | |- style="background:lightgray;" | ||
! [https://documents.egi.eu/secure/ShowDocument?docid=89 MS504] | ! [https://documents.egi.eu/secure/ShowDocument?docid=89 MS504] | ||
| Line 149: | Line 151: | ||
| TSA2.4 | | TSA2.4 | ||
| align="center" | 3 | | align="center" | 3 | ||
| July 2010 | |||
|- | |- | ||
! [https://documents.egi.eu/secure/ShowDocument?docid=212 MS505] | ! [https://documents.egi.eu/secure/ShowDocument?docid=212 MS505] | ||
| Line 154: | Line 157: | ||
| TSA2.2 | | TSA2.2 | ||
| align="center" | 4 | | align="center" | 4 | ||
| August 2010 | |||
|- style="background:lightgray;" | |- style="background:lightgray;" | ||
! MS506 | ! MS506 | ||
| Line 159: | Line 163: | ||
| TSA2.4 | | TSA2.4 | ||
| align="center" | 13 | | align="center" | 13 | ||
| May 2011 | |||
|- | |- | ||
! MS507 | ! MS507 | ||
| Line 164: | Line 169: | ||
| TSA2.5 | | TSA2.5 | ||
| align="center" | 14 | | align="center" | 14 | ||
| June 2011 | |||
|- style="background:lightgray;" | |- style="background:lightgray;" | ||
! MS508 | ! MS508 | ||
| Line 169: | Line 175: | ||
| TSA2.3 | | TSA2.3 | ||
| align="center" | 14 | | align="center" | 14 | ||
| June 2011 | |||
|- | |- | ||
! MS509 | ! MS509 | ||
| Line 174: | Line 181: | ||
| TSA2.2 | | TSA2.2 | ||
| align="center" | 16 | | align="center" | 16 | ||
| August 2011 | |||
|- style="background:lightgray;" | |- style="background:lightgray;" | ||
! MS510 | ! MS510 | ||
| Line 179: | Line 187: | ||
| TSA2.4 | | TSA2.4 | ||
| align="center" | 25 | | align="center" | 25 | ||
| May 2012 | |||
|- | |- | ||
! MS511 | ! MS511 | ||
| Line 184: | Line 193: | ||
| TSA2.5 | | TSA2.5 | ||
| align="center" | 26 | | align="center" | 26 | ||
| June 2012 | |||
|- style="background:lightgray;" | |- style="background:lightgray;" | ||
! MS512 | ! MS512 | ||
| Line 189: | Line 199: | ||
| TSA2.3 | | TSA2.3 | ||
| align="center" | 26 | | align="center" | 26 | ||
| June 2012 | |||
|- | |- | ||
! MS513 | ! MS513 | ||
| Line 194: | Line 205: | ||
| TSA2.2 | | TSA2.2 | ||
| align="center" | 28 | | align="center" | 28 | ||
| August 2012 | |||
|- style="background:lightgray;" | |- style="background:lightgray;" | ||
! MS514 | ! MS514 | ||
| Line 199: | Line 211: | ||
| TSA2.4 | | TSA2.4 | ||
| align="center" | 37 | | align="center" | 37 | ||
| May 2013 | |||
|- | |- | ||
! MS515 | ! MS515 | ||
| Line 204: | Line 217: | ||
| TSA2.5 | | TSA2.5 | ||
| align="center" | 38 | | align="center" | 38 | ||
| June 2013 | |||
|- style="background:lightgray;" | |- style="background:lightgray;" | ||
! MS516 | ! MS516 | ||
| Line 209: | Line 223: | ||
| TSA2.3 | | TSA2.3 | ||
| align="center" | 38 | | align="center" | 38 | ||
| June 2013 | |||
|- | |- | ||
! MS517 | ! MS517 | ||
| Line 214: | Line 229: | ||
| TSA2.2 | | TSA2.2 | ||
| align="center" | 40 | | align="center" | 40 | ||
| August 2013 | |||
|} | |} | ||
[[Category:WP5-SA2]] | [[Category:WP5-SA2]] | ||
Revision as of 19:36, 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 | June 2010 |
| MS503 | Software Provisioning Process | TSA2.3 | 2 | June 2010 |
| MS504 | EGI Software Repository – Architecture and Plans | TSA2.4 | 3 | July 2010 |
| MS505 | Service Level Agreement with a Software Provider | TSA2.2 | 4 | August 2010 |
| MS506 | EGI Software Repository – Architecture and Plans | TSA2.4 | 13 | May 2011 |
| MS507 | Deployed Middleware Support Unit Operations Procedures | TSA2.5 | 14 | June 2011 |
| MS508 | Software Provisioning Process | TSA2.3 | 14 | June 2011 |
| MS509 | Service Level Agreement with a Software Provider | TSA2.2 | 16 | August 2011 |
| MS510 | EGI Software Repository – Architecture and Plans | TSA2.4 | 25 | May 2012 |
| MS511 | Deployed Middleware Support Unit Operations Procedures | TSA2.5 | 26 | June 2012 |
| MS512 | Software Provisioning Process | TSA2.3 | 26 | June 2012 |
| MS513 | Service Level Agreement with a Software Provider | TSA2.2 | 28 | August 2012 |
| MS514 | EGI Software Repository – Architecture and Plans | TSA2.4 | 37 | May 2013 |
| MS515 | Deployed Middleware Support Unit Operations Procedures | TSA2.5 | 38 | June 2013 |
| MS516 | Software Provisioning Process | TSA2.3 | 38 | June 2013 |
| MS517 | Service Level Agreement with a Software Provider | TSA2.2 | 40 | August 2013 |