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:the service 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:
...
Define the people involved:
Teams/people:
- Service Owner: Marina Adomeit
- Member 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 Haider (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 Marina to give a try to document - talk to Outreach person for SPs Laura Paglione. She will be working to adapt the documentation from the github into docs that SPs can use. Marina to peer with her, and give her direct feedback - include Heather in this conversation as well. |
| |||||||||||
| don | Service policy (Terms of use, SLA) | -Development team prepares -SO signs off | RA21 Discovery Service Seamless Access Policy Terms of use are out of scope for service delivered by GEANT. It is responisbility responsibility of seamlessaccess.org. Example from InAcademia https://inacademia.org/service-policy/, and eduroam https://www.eduroam.org/wp-content/uploads/2016/05/GN3-12-192_eduroam-policy-service-definition_ver28_26072012.pdf Marina can check if there is something additional in the contract - especially about who responsibility it is to support the end-users. SLA should be defined between seamlesaccess.org and GEANT. The beta service should be best effort (there could be some tension with the publishers though ) For the beta service, there is an MoU which is being signed. (update from 16 July - orcid the last one to sign, it should be done this week) |
This should be done for the production service. The beta service is to test this out. | ||||||||||
| 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 responsibility of seamlessaccess.org Info from July 2019 from Heather: There will be a website soon - we now have a UX person contracted (Sean, Chicago), and that’s one of the things on his plate |
| |||||||||||
| Operational Requirements | -Development team prepares -SO signs off | RA21 Discovery Seamless Access Operational Requirements Marina to check if anything needs to be updated or what is missing. |
| |||||||||||
| OLA | -Development team prepares -SO and GEANT T&I operation support/Core team sign off | RA21 RA21 Discovery Seamless Access Operational Level Agreements (- OLA) This is between SUNET and GEANT Operational documentation. Draft OLA was defined and is within SUNET NOC for approval |
| |||||||||||
| Deployment architecture | -Development team prepares -SO signs off | Seamless Access Deployment Architecture Marina to set this up based on the OLA. |
| |||||||||||
| Operational documentation and | RA21 RA21 Discovery Operational Documentation | Operational processes | -Development team prepares -SO signs off |
| ||||||||||
| User documentation | Who is responsible for this? |
| ||||||||||||
| User support | Who is responsible for this? | In scope for seamless access. |
| |||||||||||
| GDPR - data inventory, privacy notice, DPA | -GDPR team +SO + technical architect -GDPR accountable and SO signs offWe 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. | GDPR evaluation was done and conclusion is that Seamless Access does not process any personal data. |
| |||||||||||
| 2 | Test and validation | |||||||||||||
| Make a test plan | Development team and Test team preparesTalk to Marcin and understand the requirements for testing first | Pen/Security done by DFN cert. Additional testing could be done as well if skilled javascript testers can be found. |
| |||||||||||
| 3 | IPR compliance checking | |||||||||||||
| IPR compliance | IPR accountable + SO + technical architect Route the request through GEANT T&I operation support/Core team | GEANT IPR coordinator has signed off the IPR. Note that was given on 6th December 2019: "Update regarding the scanning of the code provided https://github.com/TheIdentitySelector in most of the files no source/binary files were detected, consequently no licence/vulnerabilities were detected…In the js-storage-master file there were 3 licences detected (MIT licences) – as this is permissive licence, there are no further issues with it." |
| |||||||||||
| 4 | GDPR compliance checking | GDPR accountable | ||||||||||||
| Data inventory and mapping | -GDPR team +SO + technical architect -GDPR accountable and SO signs off | Seamless Access Data Processing Conclusion is that SA doesn't process any personal data, so Data Inventory and Mapping are not needed. |
| |||||||||||
| Privacy notice and DPA | -GDPR team +SO + technical architect -GDPR accountable and SO signs off | Not needed. |
| |||||||||||
| 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 teamWe need to understand who provides support | Will be provided by seamless access, out of scope for GEANT |
| ||||||||||||
| 8 | Support team training | |||||||||||||
| Training of the support teamWe need to understand who provides support | Will be provided by seamless access, out of scope for GEANT |
| ||||||||||||
| 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 | Not needed |
| |||||||||||
| VMs | Operations team based on the requirements from the technical lead and SO SO signs off when implemented | One PoP is Two nodes are provided by SUNET. Second PoP will be deployed Two nodes are operated on AWS, in two different regions. . |
| |||||||||||
| Deployment | Operations team based on the requirements from the technical lead and SO SO signs off when implemented | Deployment is completed on SUNET nodes. In progress is deployment on AWS nodes. |
| |||||||||||
| CDN | ? | Provided by Fastly. The bill is currently picked up by SUNET, but this should move to GEANT. |
| |||||||||||
| 10 | Service Promotion | |||||||||||||
| NA, responsibility of the seamless access | Will be provided by seamless access, out of scope for GEANT. Outreach person for SPs Laura Paglione (laura@seamlessaccess.org). Feel free to reach out to her if you have questions or ideas. |
| ||||||||||||
| 11 | PLM Documentation | |||||||||||||
| TBD if applicable |
|
Other notes: the success criteria - what do we consider to be the success criteria for the project, from the GEANT side.