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

From EGIWiki
Jump to: navigation, search
(Deliverables)
 
(68 intermediate revisions by 5 users not shown)
Line 1: Line 1:
Wiki page for EGI InSPIRE SA2 activities
+
{{EGI-Inspire_menubar}}
 +
{{TOC_right}}
  
=WP5-SA2=
+
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:  
 
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==
+
*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-taskleaders@mailman.egi.eu[mailto:inspire-sa2-taskleaders@mailman.egi.eu].
 +
 
 +
{| cellspacing="0" cellpadding="5" class="wikitable" style="border:1px solid black;"
 +
|- style="background-color:darkgray;"
 +
! style="border-bottom:1px solid black; text-align:left;" | Task
 +
! style="border-bottom:1px solid black; text-align:left;" | Name
 +
! style="border-bottom:1px solid black; text-align:left;" | Task Leader
 +
! style="border-bottom:1px solid black; text-align:left;" | Deputy
 +
|-
 +
! TSA2.1
 +
| Activity Management
 +
| [https://www.egi.eu/sso/userDetail/michel Michel Drescher]
 +
| [https://www.egi.eu/sso/userDetail/snewhouse Steven Newhouse]
 +
|- style="background:lightgray;"
 +
! TSA2.2
 +
| Definition of the UMD Quality Criteria
 +
| [https://www.egi.eu/sso/userDetail/enolfc Enol Fernandez del Castillo]
 +
| [https://www.egi.eu/sso/userDetail/carlosf Carlos Fernandez Sanchez] (temporary)
 +
|-
 +
! TSA2.3
 +
| Verification of conformance criteria
 +
| [https://www.egi.eu/sso/userDetail/asimon Alvaro Simon]
 +
| [https://www.egi.eu/sso/userDetail/ivandiaz Ivan Diaz]
 +
|- style="background:lightgray;"
 +
! TSA2.4
 +
| Provision of a software repository and support tools
 +
| [https://www.egi.eu/sso/userDetail/kkoum Kostas Koumantaros]
 +
| [https://www.egi.eu/sso/userDetail/mhaggel Marios Chatziangelou]
 +
|-
 +
! TSA2.5
 +
| Deployed Middleware Support Unit
 +
| [https://www.egi.eu/sso/userDetail/ljocha Ales Krenek]
 +
| [https://www.egi.eu/sso/userDetail/zsustr Zdenek Sustr]
 +
|}
  
To contact all task leaders (see below), send mail to inspire-sa2@mailman.egi.eu[mailto:inspire-sa2@mailman.egi.eu].
+
== Involved partners  ==
  
==Involved partners==
+
EGI.eu - Netherlands <br> CESNET - Czech Republic <br> KIT-G - Germany <br> CSIC - Spain <br> GRNET - Greece <br> INFN - Italy <br> LIP - Portugal <br> UCPH - Denmark <br> VR-SNIC - Sweden <br> NORDUNET A/S - Denmark <br>
  
EGI.eu - Netherlands <br>
+
<br>
CESNET - Czech Republic <br>
 
KIT-G - Germany <br>
 
CSIC - Spain <br>
 
GRNET - Greece <br>
 
INFN - Italy <br>
 
LIP - Portigal <br>
 
UCPH - Denmark <br>
 
VR-SNIC - Sweden <br>
 
NORDUNET A/S - Denmark <br>
 
  
 +
== [[Task 1: Activity Management|TSA2.1 Activity Management]]  ==
  
== 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.  
  
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  ==
  
== 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.
  
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|TSA2.3: Verification of conformance criteria]]  ==
  
== 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.
  
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.
+
== [[Task 4: Provision of a Software Repository and Support Tools|TSA2.4: Provision of a software repository and support tools]]  ==
  
== 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.
  
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|TSA2.5: Deployed Middleware Support Unit]]  ==
  
== 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.
  
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  ==
  
== Deliverables ==
+
The following gives an overview of deliverables scheduled and published by EGI-InSPIRE SA2. For convenience, they are also available in the [http://www.google.com/calendar/ical/egi.eu_kh77lqphl6hs97lagduhp1c2qs%40group.calendar.google.com/public/basic.ics EGI-InSPIRE SA2 calendar].
  
{| border="1"
+
{| cellspacing="0" cellpadding="5" class="wikitable" style="border: 1px solid black;"
 +
|- style="background-color: darkgray;"
 +
! style="border-bottom: 1px solid black;" | Code
 +
! style="border-bottom: 1px solid black;" | Title
 +
! style="border-bottom: 1px solid black;" | Delivery PM
 +
! style="border-bottom: 1px solid black;" | Delivery CM
 +
! style="border-bottom: 1px solid black;" | Delivered
 +
! style="border-bottom: 1px solid black;" | Status
 
|-
 
|-
! Code
+
! [https://documents.egi.eu/document/100 D5.1]
! Title
+
| UMD Roadmap
! Relative Delivery Date
+
| align="center" | 3
 +
| July 2010
 +
| November 2010
 +
| align="center" | [[Image:Green tick.png]]
 +
|- style="background: none repeat scroll 0% 0% lightgray;"
 +
! [https://documents.egi.eu/document/272 D5.2]
 +
| UMD Roadmap
 +
| align="center" | 9
 +
| January 2011
 +
| March 2011
 +
| align="center" | [[Image:Green tick.png]]
 
|-
 
|-
| D5.1
+
! [https://documents.egi.eu/document/375 D5.3]
| UMD Roadmap
+
| Annual Report on the status of Software Provisioning activity and the work of DMSU
| align="center" | 3
+
| align="center" | 11
 +
| March 2011
 +
| May 2011
 +
| align="center" | [[Image:Green tick.png]]
 +
|- style="background: none repeat scroll 0% 0% lightgray;"
 +
! [https://documents.egi.eu/document/612 D5.4]
 +
| UMD Roadmap  
 +
| align="center" | 15
 +
| July 2011
 +
| Sep 2011
 +
| align="center" | [[Image:Green tick.png]]
 
|-
 
|-
| D5.2
+
! [https://documents.egi.eu/document/1015 D5.6]
| UMD Roadmap
+
| Annual Report on the status of Software Provisioning activity and the work of DMSU
| align="center" | 9
+
| align="center" | 23
 +
| March 2012
 +
| April 2012
 +
| align="center" | [[Image:Green tick.png]]
 +
|- style="background: none repeat scroll 0% 0% lightgray;"
 +
! D5.9
 +
| Annual Report on the status of Software Provisioning activity and the work of DMSU
 +
| align="center" | 35
 +
| March 2013
 +
|  
 +
| align="center" |  
 
|-
 
|-
| D5.3
+
! D5.12
| Annual Report on the status of Software Provisioning activity and the work of DMSU
+
| Annual Report on the status of Software Provisioning activity and the work of DMSU  
| align="center" | 11
+
| align="center" | 47
 +
| March 2014
 +
|
 +
| align="center" |
 +
|}
 +
 
 +
== Milestones  ==
 +
 
 +
The following gives an overview of milestones scheduled and published by EGI-InSPIRE SA2. For convenience, they are also available in the [http://www.google.com/calendar/ical/egi.eu_kh77lqphl6hs97lagduhp1c2qs%40group.calendar.google.com/public/basic.ics EGI-InSPIRE SA2 calendar].
 +
 
 +
{| cellspacing="0" cellpadding="5" class="wikitable" style="border: 1px solid black;"
 +
|- style="background-color: darkgray;"
 +
! style="border-bottom: 1px solid black;" | Milestone
 +
! style="border-bottom: 1px solid black;" | Title
 +
! style="border-bottom: 1px solid black;" | Lead-Task
 +
! style="border-bottom: 1px solid black;" | Delivery PM
 +
! style="border-bottom: 1px solid black;" | Delivery CM
 +
! style="border-bottom: 1px solid black;" | Delivered
 +
! style="border-bottom: 1px solid black;" | Status
 
|-
 
|-
| D5.4
+
! [https://documents.egi.eu/secure/ShowDocument?docid=46 MS501]
| UMD Roadmap
+
| Establishment of the EGI Software Repository and associated support tools
| align="center" | 15
+
| TSA2.4  
 +
| align="center" | 1
 +
| May 2010
 +
| November 2010
 +
| align="center" | [[Image:Green tick.png]]
 +
|- style="background: none repeat scroll 0% 0% lightgray;"
 +
! [https://documents.egi.eu/secure/ShowDocument?docid=69 MS502]
 +
| Deployed Middleware Support Unit Operations Procedures
 +
| TSA2.5
 +
| align="center" | 2
 +
| June 2010
 +
| December 2010
 +
| align="center" | [[Image:Green tick.png]]
 
|-
 
|-
| D5.5
+
! [https://documents.egi.eu/secure/ShowDocument?docid=68 MS503]
| UMD Roadmap
+
| Software Provisioning Process
| align="center" | 21
+
| TSA2.2,<br>TSA2.3
 +
| align="center" | 2
 +
| June 2010
 +
| November 2010
 +
| align="center" | [[Image:Green tick.png]]
 +
|- style="background: none repeat scroll 0% 0% lightgray;"
 +
! [https://documents.egi.eu/secure/ShowDocument?docid=89 MS504]
 +
| EGI Software Repository – Architecture and Plans
 +
| TSA2.4
 +
| align="center" | 3
 +
| July 2010
 +
| November 2010
 +
| align="center" | [[Image:Green tick.png]]
 
|-
 
|-
| D5.6
+
! [https://documents.egi.eu/document/212 MS505]
| Annual Report on the status of Software Provisioning activity and the work of DMSU
+
| Service Level Agreement with a Software Provider
| align="center" | 23
+
| TSA2.1
 +
| align="center" | 4
 +
| August 2010
 +
| November 2010
 +
| align="center" | [[Image:Green tick.png]]
 +
|- style="background: none repeat scroll 0% 0% lightgray;"
 +
! [https://documents.egi.eu/document/503 MS506]
 +
| EGI Software Repository – Architecture and Plans
 +
| TSA2.4
 +
| align="center" | 13
 +
| May 2011
 +
| June 2011
 +
| align="center" | [[Image:Green tick.png]]
 
|-
 
|-
| D5.7
+
! [https://documents.egi.eu/document/504 MS507]
| UMD Roadmap
+
| Deployed Middleware Support Unit Operations Procedures
| align="center" | 27
+
| TSA2.5
 +
| align="center" | 14
 +
| June 2011
 +
| July 2011
 +
| align="center" | [[Image:Green tick.png]]
 +
|- style="background: none repeat scroll 0% 0% lightgray;"
 +
! [https://documents.egi.eu/document/505 MS508]
 +
| Software Provisioning Process
 +
| TSA2.2,<br>TSA2.3
 +
| align="center" | 14
 +
| June 2011
 +
| July 2011
 +
| align="center" | [[Image:Green tick.png]]
 
|-
 
|-
| D5.8
+
! [https://documents.egi.eu/document/615 MS509]
| UMD Roadmap
+
| Service Level Agreement with a Software Provider
| align="center" | 33
+
| TSA2.1
 +
| align="center" | 16
 +
| August 2011
 +
| August 2011
 +
| align="center" | [[Image:Green tick.png]]
 +
|- style="background: none repeat scroll 0% 0% lightgray;"
 +
! [https://documents.egi.eu/document/970 MS510]
 +
| EGI Platform Roadmap  
 +
| TSA2.4
 +
| align="center" | 22
 +
| February 2012
 +
| April 2012
 +
| align="center" | [[Image:Green tick.png]]
 
|-
 
|-
| D5.9
+
! [https://documents.egi.eu/document/1110 MS513]
| Annual Report on the status of Software Provisioning activity and the work of DMSU
+
| Service Level Agreement with a Software Provider
| align="center" | 35
+
| TSA2.1
 +
| align="center" | 24
 +
| April 2012
 +
| June 2012
 +
| align="center" | [[Image:Green tick.png]]
 +
|- style="background: none repeat scroll 0% 0% lightgray;"
 +
! [https://documents.egi.eu/document/1134 MS511]
 +
| Deployed Middleware Support Unit Operations Procedures
 +
| TSA2.5
 +
| align="center" | 26
 +
| June 2012
 +
| August 2012
 +
| align="center" | [[Image:Green tick.png]]
 
|-
 
|-
| D5.10
+
! [https://documents.egi.eu/document/1135 MS512]
| UMD Roadmap
+
| Software Provisioning Process
| align="center" | 39
+
| TSA2.2,<br>TSA2.3
 +
| align="center" | 26
 +
| June 2012
 +
| July 2012
 +
| align="center" | [[Image:Green tick.png]]
 +
|- style="background: none repeat scroll 0% 0% lightgray;"
 +
! MS514
 +
| EGI Platform Roadmap
 +
| TSA2.4
 +
| align="center" | 34
 +
| February 2013
 +
|
 +
| align="center" |  
 
|-
 
|-
| D5.11
+
! MS515
| UMD Roadmap
+
| Deployed Middleware Support Unit Operations Procedures
| align="center" | 45
+
| TSA2.5
 +
| align="center" | 38
 +
| June 2013
 +
|
 +
| align="center" |
 +
|- style="background: none repeat scroll 0% 0% lightgray;"
 +
! MS516
 +
| Software Provisioning Process
 +
| TSA2.2,<br>TSA2.3
 +
| align="center" | 38
 +
| June 2013
 +
|  
 +
| align="center" |  
 
|-
 
|-
| D5.12
+
! MS518
| UMD Roadmap
+
| EGI Platform Roadmap
| align="center" | 47
+
| TSA2.4
 +
| align="center" | 46
 +
| February 2014
 +
|
 +
| align="center" |
 +
|- style="background: none repeat scroll 0% 0% lightgray;"
 +
! MS517
 +
| Service Level Agreement with a Software Provider
 +
| TSA2.1
 +
| align="center" | 48
 +
| April 2014
 +
|  
 +
| align="center" |  
 
|}
 
|}
 
== Milestones ==
 
 
MS501 Establishment of the EGI Software Repository and associated support tools [PM1] <br>
 
MS502 Deployed Middleware Support Unit Operations Procedures [PM2] <br>
 
MS503 Software Provisioning Process [PM2] <br>
 
MS504 EGI Software Repository – Architecture and Plans [PM3] <br>
 
MS505 Service Level Agreement with a Software Provider [PM4] <br>
 
MS506 EGI Software Repository – Architecture and Plans [PM13] <br>
 
MS507 Deployed Middleware Support Unit Operations Procedures [PM14] <br>
 
MS508 Software Provisioning Process [PM14] <br>
 
MS509 Service Level Agreement with a Software Provider [PM16] <br>
 
MS510 EGI Software Repository – Architecture and Plans [PM25] <br>
 
MS511 Deployed Middleware Support Unit Operations Procedures [PM26] <br>
 
MS512 Software Provisioning Process [PM26] <br>
 
MS513 Service Level Agreement with a Software Provider [PM28] <br>
 
MS514 EGI Software Repository – Architecture and Plans [PM37] <br>
 
MS515 Deployed Middleware Support Unit Operations Procedures [PM38] <br>
 
MS516 Software Provisioning Process [PM38] <br>
 
MS517Service Level Agreement with a Software Provider [PM40] <br>
 

Latest revision as of 23:25, 24 December 2014

EGI Inspire Main page



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-taskleaders@mailman.egi.eu[1].

Task Name Task Leader Deputy
TSA2.1 Activity Management Michel Drescher Steven Newhouse
TSA2.2 Definition of the UMD Quality Criteria Enol Fernandez del Castillo Carlos Fernandez Sanchez (temporary)
TSA2.3 Verification of conformance criteria Alvaro Simon Ivan Diaz
TSA2.4 Provision of a software repository and support tools Kostas Koumantaros Marios Chatziangelou
TSA2.5 Deployed Middleware Support Unit Ales Krenek Zdenek Sustr

Involved partners

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


TSA2.1 Activity Management

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

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

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

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

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

The following gives an overview of deliverables scheduled and published by EGI-InSPIRE SA2. For convenience, they are also available in the EGI-InSPIRE SA2 calendar.

Code Title Delivery PM Delivery CM Delivered Status
D5.1 UMD Roadmap 3 July 2010 November 2010 Green tick.png
D5.2 UMD Roadmap 9 January 2011 March 2011 Green tick.png
D5.3 Annual Report on the status of Software Provisioning activity and the work of DMSU 11 March 2011 May 2011 Green tick.png
D5.4 UMD Roadmap 15 July 2011 Sep 2011 Green tick.png
D5.6 Annual Report on the status of Software Provisioning activity and the work of DMSU 23 March 2012 April 2012 Green tick.png
D5.9 Annual Report on the status of Software Provisioning activity and the work of DMSU 35 March 2013
D5.12 Annual Report on the status of Software Provisioning activity and the work of DMSU 47 March 2014

Milestones

The following gives an overview of milestones scheduled and published by EGI-InSPIRE SA2. For convenience, they are also available in the EGI-InSPIRE SA2 calendar.

Milestone Title Lead-Task Delivery PM Delivery CM Delivered Status
MS501 Establishment of the EGI Software Repository and associated support tools TSA2.4 1 May 2010 November 2010 Green tick.png
MS502 Deployed Middleware Support Unit Operations Procedures TSA2.5 2 June 2010 December 2010 Green tick.png
MS503 Software Provisioning Process TSA2.2,
TSA2.3
2 June 2010 November 2010 Green tick.png
MS504 EGI Software Repository – Architecture and Plans TSA2.4 3 July 2010 November 2010 Green tick.png
MS505 Service Level Agreement with a Software Provider TSA2.1 4 August 2010 November 2010 Green tick.png
MS506 EGI Software Repository – Architecture and Plans TSA2.4 13 May 2011 June 2011 Green tick.png
MS507 Deployed Middleware Support Unit Operations Procedures TSA2.5 14 June 2011 July 2011 Green tick.png
MS508 Software Provisioning Process TSA2.2,
TSA2.3
14 June 2011 July 2011 Green tick.png
MS509 Service Level Agreement with a Software Provider TSA2.1 16 August 2011 August 2011 Green tick.png
MS510 EGI Platform Roadmap TSA2.4 22 February 2012 April 2012 Green tick.png
MS513 Service Level Agreement with a Software Provider TSA2.1 24 April 2012 June 2012 Green tick.png
MS511 Deployed Middleware Support Unit Operations Procedures TSA2.5 26 June 2012 August 2012 Green tick.png
MS512 Software Provisioning Process TSA2.2,
TSA2.3
26 June 2012 July 2012 Green tick.png
MS514 EGI Platform Roadmap TSA2.4 34 February 2013
MS515 Deployed Middleware Support Unit Operations Procedures TSA2.5 38 June 2013
MS516 Software Provisioning Process TSA2.2,
TSA2.3
38 June 2013
MS518 EGI Platform Roadmap TSA2.4 46 February 2014
MS517 Service Level Agreement with a Software Provider TSA2.1 48 April 2014