Common use of December 2017 Clause in Contracts

December 2017. The Agreement was discussed and approved by the Customer and the Provider [date]. The Agreement extends the Corporate-level EGI Operational Level Agreement1 with following information: 1The Services The Services are defined by the following properties: Technical All the products released in UMD must be verified against the relevant acceptance criteria. Products must be deployed in a controlled environment. Every product in UMD must have a verification report associated, with the results of the verification process. The verifiers must be familiar with the core products used in EGI, the most common site configurations and third parties components such as DBMS and LRMS. The software to be verified involves user facing services, HTC services, storage services, cloud services, and all the products that are critical for EGI communities and are part of UMD. This task will also test the release candidates to check the dependencies and installability of the packages before the official release. UMD releases are expected to be 6-10 minor releases per year, distributed in two major releases, and supporting three operating system platforms. Staged Rollout is performed by Early Adopter (EA) sites who volunteer to deploy products fulfilling the acceptance criteria in the production infrastructure, exposing them to real users and real use cases. Coordination The task must coordinate the verifications when the process is outsourced to developers or user communities, this means: overview to advancements in the process and collect the reports produced during verification, making sure that the relevant information (GGUS tickets opened, known issues) are properly propagated to the UMD release. During staged rollout this task is responsible for the coordination of the Early Adopters activity, namely assign and monitor the progress of each individual product and corresponding EA teams, collect and analyze the reports provided by the EA team and in case of issues found make sure that relevant information is properly handled. Operation This task will operate a cloud infrastructure to be used as a testbed for the verification of the UMD products. The size of the infrastructure should allow the deployment of several VM in parallel to test also for service interoperability. Verification of products should be outsourced only when the effort required would be too high (for example for lack of expertise), or for technical limitations that prevent to deploy the service in the testbed. UMD Release candidates must be tested for the installation of all the components, new and already available in the repositories. The test, possibly automated, must be able to generate a report in few hours (less than one working day, possibly 2-4 hours). This task is also responsible for producing and maintaining the UMD release notes and known issues wiki pages. The task leader must participate the periodic EGI Operations meetings and report about the status of the UMD releases. Together with those activities it also includes: maintenance of the EA tables contribute in handling the PPAs advancement in the software provisioning process Maintenance The task should also review the set of quality criteria and add/remove criteria based on the requirements of the final users and service providers. This activity is on-request. 2Service hours and exceptions As defined in Corporate-level EGI Operational Level Agreement. 3Support As defined in Corporate-level EGI Operational Level Agreement. Support is provided via EGI Service Desk2 Support Unit: <specify> Support is available between: Monday and Friday 9:00 and 17:00 CET/CEST time This excludes public holidays at the same time in all organizations providing the service.

December 2017. The Agreement was discussed and approved by the Customer and the Provider [date]Provider. The Agreement extends the Corporate-level EGI Operational Level Agreement1 with following information: 1The The Services The Services are defined by the following properties: Technical All the products released in UMD must be verified against the relevant acceptance criteria. Products must be deployed in a controlled environment. Every product in UMD must have a verification report associated, with the results of the verification process. The verifiers must be familiar with the core products used in EGI, the most common site configurations and third parties components such as DBMS and LRMS. The software to be verified involves user facing services, HTC services, storage services, cloud services, and all the products that are critical for EGI communities and are part of UMD. This task will also test the release candidates to check the dependencies and installability of the packages before the official release. UMD releases are expected to be 6-10 minor releases per year, distributed in two major releases, and supporting three operating system platforms. Staged Rollout is performed by Early Adopter (EA) sites who volunteer to deploy products fulfilling the acceptance criteria in the production infrastructure, exposing them to real users and real use cases. Coordination The task must coordinate the verifications when the process is outsourced to developers or user communities, this means: overview to advancements in the process and collect the reports produced during verification, making sure that the relevant information (GGUS tickets opened, known issues) are properly propagated to the UMD release. During staged rollout this task is responsible for the coordination of the Early Adopters activity, namely assign and monitor the progress of each individual product and corresponding EA teams, collect and analyze the reports provided by the EA team and in case of issues found make sure that relevant information is properly handled. Operation This task will operate a cloud infrastructure to be used as a testbed for the verification of the UMD products. The size of the infrastructure should allow the deployment of several VM in parallel to test also for service interoperability. Verification of products should be outsourced only when the effort required would be too high (for example for lack of expertise), or for technical limitations that prevent to deploy the service in the testbed. UMD Release candidates must be tested for the installation of all the components, new and already available in the repositories. The test, possibly automated, must be able to generate a report in few hours (less than one working day, possibly 2-4 hours). This task is also responsible for producing and maintaining the UMD release notes and known issues wiki pages. The task leader must participate the periodic EGI Operations meetings and report about the status of the UMD releases. Together with those activities it also includes: maintenance of the EA tables contribute in handling the PPAs advancement in the software provisioning process Maintenance The task should also review the set of quality criteria and add/remove criteria based on the requirements of the final users and service providers. This activity is on-request. 2Service Service hours and exceptions As defined in Corporate-level EGI Operational Level Agreement. 3Support Support As defined in Corporate-level EGI Operational Level Agreement. Support is provided via EGI Service Desk2 Support Unit: <specify> UMD Quality Assurance Support is available between: Monday and Friday 9:00 and 17:00 CET/CEST time This excludes public holidays at the same time in all organizations providing the service. Incident handling As defined in Corporate-level EGI Operational Level Agreement. Service requests As defined in Corporate-level EGI Operational Level Agreement. Service level targets Estimated number of products to verify in one year is 200 PPA Medium (Section 3) Limitations and constraints As defined in Corporate-level EGI Operational Level Agreement. Communication, reporting and escalation General communication The following contacts will be generally used for communications related to the service in the scope of this Agreement. Customer contact for the Provider ▇▇▇▇▇ ▇▇▇▇▇▇▇ ▇▇▇▇▇▇▇▇▇▇@▇▇▇.▇▇ Provider contact for the Customer ▇▇▇▇ ▇▇▇▇ ▇▇▇▇▇@▇▇▇.▇▇ ▇▇▇▇▇ ▇▇▇▇▇ ▇▇▇▇▇@▇▇▇▇.▇▇▇▇▇▇.▇▇ Service Support contact See Section 3 Regular reporting As part of the fulfilment of this Agreement and provisioning of the service, the following reports will be provided:

December 2017. The Agreement was discussed and approved by the Customer and the Provider [date]. The Agreement extends the Corporate-level EGI Operational Level Agreement1 with following information: 1The Services The Services are defined by the following properties: Technical All the products released in UMD must be verified against the relevant acceptance criteria. Products must be deployed in a controlled environment. Every product in UMD must have a verification report associated, with the results of the verification process. The verifiers must be familiar with the core products used in EGI, the most common site configurations and third parties components such as DBMS and LRMS. The software to be verified involves user facing services, HTC services, storage services, cloud services, and all the products that are critical for EGI communities and are part of UMD. This task will also test the release candidates to check the dependencies and installability of the packages before the official release. UMD releases are expected to be 6-10 minor releases per year, distributed in two major releases, and supporting three operating system platforms. Staged Rollout is performed by Early Adopter (EA) sites who volunteer to deploy products fulfilling the acceptance criteria in the production infrastructure, exposing them to real users and real use cases. Coordination The task must coordinate the verifications when the process is outsourced to developers or user communities, this means: overview to advancements in the process and collect the reports produced during verification, making sure that the relevant information (GGUS tickets opened, known issues) are properly propagated to the UMD release. During staged rollout this task is responsible for the coordination of the Early Adopters activity, namely assign and monitor the progress of each individual product and corresponding EA teams, collect and analyze the reports provided by the EA team and in case of issues found make sure that relevant information is properly handled. Operation This task will operate a cloud infrastructure to be used as a testbed for the verification of the UMD products. The size of the infrastructure should allow the deployment of several VM in parallel to test also for service interoperability. Verification of products should be outsourced only when the effort required would be too high (for example for lack of expertise), or for technical limitations that prevent to deploy the service in the testbed. UMD Release candidates must be tested for the installation of all the components, new and already available in the repositories. The test, possibly automated, must be able to generate a report in few hours (less than one working day, possibly 2-4 hours). This task is also responsible for producing and maintaining the UMD release notes and known issues wiki pages. The task leader must participate the periodic EGI Operations meetings and report about the status of the UMD releases. Together with those activities it also includes: maintenance of the EA tables contribute in handling the PPAs advancement in the software provisioning process Maintenance The task should also review the set of quality criteria and add/remove criteria based on the requirements of the final users and service providers. This activity is on-request. 2Service hours and exceptions As defined in Corporate-level EGI Operational Level Agreement. 3Support As defined in Corporate-level EGI Operational Level Agreement. Support is provided via EGI Service Desk2 Support Unit: <specify> Support is available between: Monday and Friday 9:00 and 17:00 CET/CEST time This excludes public holidays at the same time in all organizations providing the service.Friday

December 2017. The Agreement was discussed and approved by the Customer and the Provider [date]. The Agreement extends the Corporate-level EGI Operational Level Lever Agreement1 with following information: 1The Services The Services are defined by the following properties: Technical All the products released in UMD must be verified against the relevant acceptance criteria. Products must be deployed in a controlled environment. Every product in UMD must have a verification report associated, with the results of the verification process. The verifiers must be familiar with the core products used in EGI, the most common site configurations and third parties components such as DBMS and LRMS. The software to be verified involves user facing services, HTC services, storage services, cloud services, and all the products that are critical for EGI communities and are part of UMD. This task will also test the release candidates to check the dependencies and installability of the packages before the official release. UMD releases are expected to be 6-10 minor releases per year, distributed in two major releases, and supporting three operating system platforms. Staged Rollout is performed by Early Adopter (EA) sites who volunteer to deploy products fulfilling the acceptance criteria in the production infrastructure, exposing them to real users and real use cases. Coordination The task must coordinate the verifications when the process is outsourced to developers or user communities, this means: overview to advancements in the process and collect the reports produced during verification, making sure that the relevant information (GGUS tickets opened, known issues) are properly propagated to the UMD release. During staged rollout this task is responsible for the coordination of the Early Adopters activity, namely assign and monitor the progress of each individual product and corresponding EA teams, collect and analyze the reports provided by the EA team and in case of issues found make sure that relevant information is properly handled. Operation This task will operate a cloud infrastructure to be used as a testbed for the verification of the UMD products. The size of the infrastructure should allow the deployment of several VM in parallel to test also for service interoperability. Verification of products should be outsourced only when the effort required would be too high (for example for lack of expertise), or for technical limitations that prevent to deploy the service in the testbed. UMD Release candidates must be tested for the installation of all the components, new and already available in the repositories. The test, possibly automated, must be able to generate a report in few hours (less than one working day, possibly 2-4 hours). This task is also responsible for producing and maintaining the UMD release notes and known issues wiki pages. The task leader must participate the periodic EGI Operations meetings and report about the status of the UMD releases. Together with those activities it also includes: maintenance of the EA tables contribute in handling the PPAs advancement in the software provisioning process Maintenance The task should also review the set of quality criteria and add/remove criteria based on the requirements of the final users and service providers. This activity is on-request. 2Service hours and exceptions As defined in Corporate-level EGI Operational Level Lever Agreement. 3Support As defined in Corporate-level EGI Operational Level Lever Agreement. Support is provided via EGI Service Desk2 Support Unit: <specify> Support is available between: Monday and Friday 9:00 and 17:00 CET/CEST time This excludes public holidays at the same time in all organizations providing the service.