This document investigates the steps still needed to transition the discovery service (from the GN42 eduTEAMS pilot / GN43 Incubator) to move to WP5 T1 eduGAIN
The transition should finish all the necessery steps to meet the PLM gate for service to enter production.
The transition generally consist of the following areas of work:
- Documentation preparation and signoff
- Test and Validation
- GDPR compliance checking
- IPR compliance checking
- Operational team establishment
- Operational team training
- Support team establishment
- Support team training
- Operational deployment
- Service promotion
Teams/people:
- Operations accountable:
- Development accountable:
- Service Owner/Manager (SO):
- GEANT T&I operation support/Core team:
- eduTEAMS Devops Team:
- Test team:
- PLM assistance:
- IPR accountable:
- GDPR accountable:
Table below DOES NOT yet reflect work in progress or current status - NiDi
ON HOLD
IN PROGRESS
DONE
No | Work item | Responsible | Comment | Status |
|---|---|---|---|---|
| 1 | Preparation of documentation - based on the SA2 Service Template | |||
| Service Description | Development team prepares SO and Marina signs off | eduTEAMS - Service Description Note: when GEANT GitLab is federated and the continuous integration available, the code can be transferred there. At the moment, the NIIFI GitLab instance is being used. | ||
Service policy (AUP) | Development team prepares GEANT T&I operation support/Core team signs off | DONE | ||
| Branding and Visibility | Development team prepares SO signs off | eduTEAMS - Branding and Visibility After the production gate, a dedicated website should be prepared, either as a dedicated website or as part of the eduTEAMs central portal. . | DONE | |
| Operational Requirements | Development team prepares SO, Marina and core team sign off | eduTEAMS - Operational Requirements | DONE | |
| OLA | Development team prepares SO and Marina GEANT T&I operation support/Core team sign off | The last bit is to put the OLAs in place. This will be mediated by the GEANT T&I operations team, agreement will be made by email confirmation which will be for future reference be saved by the GEANT T&I ops team The OLA with CESNET and SZTAKI were accepted on 4th January 2019 and 10th January 2019 respectively. The OLAs are available at Service Status Dashboard |
| |
| Operational documentation | Development team prepares SO and Marina signs off | DONE | ||
| Operational processes | Development team prepares SO and Marina signs off | eduTEAMS - Operational Processes | DONE | |
| User documentation | Development team prepares SO and Marina signs off | DONE | ||
| User support | Development team prepares SO and Marina signs off, test team can validate | eduTEAMS - User Support | DONE | |
| GDPR - data inventory, privacy notice, DPA | Development team prepares GDPR accountable and SO signs off | DONE | ||
| Roadmap | eduTEAMS - Roadmap | DONE | ||
| 2 | Test and validation | |||
| Make a test plan | Development team and Test team prepares | Done: UI testing and pen testing | DONE | |
| 3 | IPR compliance checking | |||
| IPR compliance | IPR accountable Route the request through GEANT T&I operation support/Core team | eduTEAMS - IPR | DONE | |
| 4 | GDPR compliance checking | GDPR accountable | ||
| Data inventory and mapping/ or Data flows | eduTEAMS Data Processing | DONE | ||
| Privacy notice | DONE | |||
| Prepare the data processing agreement | DONE | |||
| 5 | Operational team establishment | |||
| Appoint service manager i.e Service Owner in GN4-3 | Operations & Service accountable | Christos Kanellopoulos appointed as Service Owner | DONE | |
| Define roles, skills, manpower needed | Development team | Defined during the budget and people allocations for the GN-3. Initial requirements are documented at https://docs.google.com/spreadsheets/d/1cBhD3nIwsXmXzbJrsbXWCnklLhD7mnNfVEjrWg1KTBI/edit#gid=0 | DONE | |
Appoint devops team members | SM | GN4-2
GN4-3
| DONE | |
| 6 | Operational team training | |||
| Training the operational team | Development team prepares | The operational team was involved during the development process. As new members are/will be joining the team, training on case by case will be done. The f2f meeting of the eduTEAMS was held on 17-19 December. | DONE | |
| 7 | Support team establishment | |||
| Establish the support team | The support team was involved during the development process. As new members are/will be joining the team, the support team will be changing its structure. Involvement of the GEANT helpdesk will be done when ready for production | DONE | ||
| 8 | Support team training | |||
| Training of the support team | Development team prepares | Training for the eduTEAMS team members who are providing support to eduTEAMS customers was held on 17-19 December. | DONE | |
| 9 | Deployment in production environment | |||
| Central monitoring set up | GEANT T&I operation support/Core team | Nagios monitoring service is arleady configured and monitors the service. Working with the SA2 core team to transition to the new Zabbix monitoring service when it is ready | DONE | |
| Back-up and restore | eduTEAMS Devops Team | The backup and restore of the MMS systems is part of the service delivered by the partners, for which there is OLA with them defining the backup and restore that they are responsible for. The central components of the service are stateless and completely redeploy-able by using automatic scripts and therefor do not need backup. There is only one component that requires back and that is the database of the consent management service, which contains non-critical data and this is being backed up. | DONE | |
| Resource inventory configured | core team | when available by the core team, not a requirement for production | DONE | |
| VM provision | eduTEAMS Devops Team | AWS offer is used. This needs to be put under the IaaS infrastructure agreement. | DONE | |
| Installation of the components | eduTEAMS Devops Team | Done by the eduTEAMS DevOps team | DONE | |
| Penetration testing | Test team | Done by SA2/T1 | DONE | |
| Functional testing | Test Team | Done by SA2/T1 | DONE | |
| 10 | Service Promotion | |||
| Promotion plan | Christos and engagement team | The initial plans are already set with the NA engagement team and WP5 enabling communities task | ON HOLD After the production gate | |
| Web site update | Christos and Karl | Already mentioned under 1. branding and visibility | DONE | |
| Slide deck from the infoshares that can be used by the Research Engagement and support | Christos | Available | DONE | |
| Article for CONNECT | Christos and Karl | In preparation with connect people | DONE | |
| Launch announcement in Tryfon's weekly email when reached | Christos and Tryfon | After production gate | ON HOLD After the production gate | |
| 11 | PLM Documentation | |||
| CBA update | Documents are updated for the service production and available at JRA3 PLM Staging Area | DONE |