Work in progress!!!!
Provide some context and plan for the transitionservice. What is in place now, what is rough timeline for service: for example reach pilot by time a, run pilot for period p and based on results run the service in production by time c. Give some view on what happens with the technical infrastructure through this - i.e the installation will remain ... Example from managed idp transition bellow:delivery. Current plan is that the service beta becomes available from 1 July and runs for one year.
The transition generally consist of the following areas of work:
...
- Service Owner and member of the Technical Steering committee: Christos Kanellopoulos
- Member of the Governance Steering Committee: Klaas Wierenga
- Lead Architect and member of the Technical Steering Committee: Leif Johanson
- Development team: Fresia Perez Arriagada, Elena Rakhimova
- Operations team: Erik Bergstörm, Maria Haide (Sunet)
- GEANT T&I operation support/Core team: Nicole Harris
- Test team: WP9 - Marcin Wolski (ask what testing can be done)
- IPR: Magdalena Rzaca
- GDPR: Magdalena Rzaca GEANT GDPR team
- WP5 leaders ultimately responsible for the T&I service portfolio delivered through the GEANT project: Licia Florio, Marina Adomeit
| Status | ||||
|---|---|---|---|---|
|
IN PROGRESS
...
No | Work item | Responsible | Comment | Status |
|---|---|---|---|---|
| 1 | Preparation of documentation | |||
| Service Description | -Development team prepares -SO signs off | RA21 Discovery Service Description | ||
Service policy (Terms of use, SLA) | -Development team prepares -SO signs off | Terms of use are out of scope for service delivered by GEANT. It is responisbility of seamlessaccess.org SLA should be defined between seamlesaccess.org and GEANT. | ||
| Branding and Visibility | -Development team prepares -SO signs off | This is probably not relevant to the part of the service delivered by GEANT. It is responisbility of seamlessaccess.org | ||
| Operational Requirements | -Development team prepares -SO signs off | RA21 Discovery Operational Requirements | ||
| OLA | -Development team prepares -SO and GEANT T&I operation support/Core team sign off | RA21 RA21 Discovery Operational Level Agreements (OLA) This is between SUNET and GEANT | ||
| Operational documentation | -Development team prepares -SO signs off | RA21 RA21 Discovery Operational Documentation | ||
| Operational processes | -Development team prepares -SO signs off | RA21 RA21 Discovery Operational Processes Change management, Incident response, ... | ||
| User documentation | Who is responsible for this? | |||
| User support | Who is responsible for this? | |||
| GDPR - data inventory, privacy notice, DPA | -GDPR team +SO + technical architect -GDPR accountable and SO signs off | We should clarify the roles regarding the GDPR. We thing that GEANT and SUNET are data controller, and then probably no DPA is needed. CDNs are data processors. But we would to provide the privacy notice. | ||
| 2 | Test and validation | |||
| Make a test plan | Development team and Test team prepares | Talk to Marcin and understand the requirements for testing first | ||
| 3 | IPR compliance checking | |||
| IPR compliance | IPR accountable + SO + technical architect Route the request through GEANT T&I operation support/Core team | To whoom the IPR belongs to ? Needs discussion. | ||
| 4 | GDPR compliance checking | GDPR accountable | ||
| Data inventory and mapping | -GDPR team +SO + technical architect -GDPR accountable and SO signs off | |||
| Privacy notice and DPA | -GDPR team +SO + technical architect -GDPR accountable and SO signs off | |||
| 5 | Operational team establishment | |||
| Appoint service owner | WP5 leaders | Done. The service owner is responsible for service as delivered via GEANT project. | ||
| Define roles, skills, manpower needed | Development team | We need to check this with what seamlessaccess.org, but if we deliver a service then it is our internal matter. | ||
Appoint operational team members | Service Owner | Done | ||
| 6 | Operational team training | |||
| Training the operational team | Not needed | |||
| 7 | Support team establishment | |||
| Establish the support team | We need to understand who provides support | |||
| 8 | Support team training | |||
| Training of the support team | We need to understand who provides support | |||
| 9 | Deployment in production environment | |||
| Monitoring set up | Operations team based on the requirements from the technical lead and SO SO signs off when implemented | |||
| Back-up and restore | Operations team based on the requirements from the technical lead and SO SO signs off when implemented | |||
| VMs | Operations team based on the requirements from the technical lead and SO SO signs off when implemented | One PoP is provided by SUNET. Second PoP will be deployed on AWS, in two different regions. | ||
| Deployment | Operations team based on the requirements from the technical lead and SO SO signs off when implemented | |||
| CDN | ? | ? | ||
| 10 | Service Promotion | |||
| NA, responsibility of the seamless access | ||||
| 11 | PLM Documentation | |||
| TBD if applicable |
...