...
No | Work item | Responsible | Comment | Status | Start date | End date | ||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 | Preparation of documentation | |||||||||||
| Service Description | -Development team prepares -SO signs off | Need to prepare high level service description | DONE | |||||||||
Service policy (Terms of use, SLA) | -Development team prepares -SO signs off | Write at the UI that this is pilot and there is no SLA guaranteed. |
| |||||||||
| Branding and Visibility | -Development team prepares -SO signs off | we still need to think a branding - for production |
| |||||||||
| Operational Requirements | -Development team prepares -SO signs off | We should document what are ops requirements for running pilot (see eduroam managed SP Operational Requirements) | DONE | |||||||||
| OLA | -Development team prepares -SO and GEANT T&I operation support/Core team sign off | not relevant for pilot (example for production later eduroam Managed IdP OLA) |
| |||||||||
| Operational documentation | -Development team prepares -SM signs off, test team can validate | Tomasz and Maja through eduroam-OT are the ops team. Documentation not relevant for pilot ( example for production later Dev team prepared this in the corresponding Wiki page) |
| |||||||||
| Operational processes | -Development team prepares -SM signs off, test team can validate | not relevant Service order is done through the UI Service support is the same like for eduroam supporting services. |
| |||||||||
| User documentation | -Development team prepares -SM signs off, test team can validate | DONE | ||||||||||
| User support | -Development team prepares -SM signs off, test team can validate | We dont need anything special for pilot as we will work with a defined group of pilot participants directly |
| |||||||||
| GDPR - data inventory, privacy notice, DPA | -Development team prepares -SO and T&I service portfolio reviews -GDPR accountable signs off | eduroam privacy notice was updated to reflect the changes of eduroam managed SP, and was approved by GEANT DPO eduroam Privacy Notice - Changes for Managed SP | | |||||||||
| 2 | Test and validation | |||||||||||
| Make a test plan | Development team and Test team prepares | We dont need to do code review for the pilot, but it is a good idea to do test the code during the pilot, as preparation for production Stefan Winter initiated the scans with Marcin Wolski . It was agreed to do the code scan in second half of 2021 | DONE | |||||||||
| 3 | IPR compliance checking | |||||||||||
| IPR compliance | IPR accountable Route the request through GEANT T&I operation support/Core team We can provide source php files for IPR check done by white source Should we do this with entire CAT - check with Miroslav Milinovic Marina Adomeit to check the approach with Miro and then send mail request IPR responsible Stefan Winter initiated WhiteSource review with Marcin Wolski | White source review was done by the WP9 team Results are available to WP9 team, WP5 lead and eduroam team and to GEANT IPR person https://app-eu.whitesourcesoftware.com/Wss/WSS.html#!product;id=78288 Based on the results, GEANT IPR has signed off the IPR compliance check. |
| |||||||||
| 4 | GDPR compliance checking | GDPR accountable | ||||||||||
| Data inventory and mapping | Data inventory and mapping were updated | DONE | ||||||||||
| Update the privacy notice and DPA | eduroam privacy notice was updated to reflect the changes of eduroam managed SP, and was approved by GEANT DPO eduroam Privacy Notice - Changes for Managed SP | DONE | ||||||||||
| 5 | Operational team establishment | |||||||||||
| Appoint service manager | Operations accountable | It comes under the eduroam service family and existing service owner. |
| |||||||||
| Define roles, skills, manpower needed | Development team | pilot will be supported by the eduroam-OT and dev team |
| |||||||||
Appoint operational team members | SM | For production we may need some additional manpower for opserations |
| |||||||||
| 6 | Operational team training | |||||||||||
| Training the operational team | Development team prepares eduroam-OT is trained | Not needed. |
| |||||||||
| 7 | Support team establishment | |||||||||||
| Establish the support team | Pilot doesn't need dedicated support team - dev team will work with limited pilot participants |
| ||||||||||
| 8 | Support team training | |||||||||||
| Training of the support team | Development team prepares eduroam-OT is trained | Not needed. |
| |||||||||
| 9 | Deployment in pilot | |||||||||||
| Monitoring set up | eduroam-OT | not necessary for the pilot, but there are monitoring end points ready to be used for production |
| |||||||||
| Back-up and restore | eduroam-OT | not necessary for the pilot |
| |||||||||
| VM provision | GEANT T&I operation support/Core team | DONE | ||||||||||
| Installation of the components | eduroam-OT | Stefan, Tomasz, Maja Radius servers will need to be deployed | DONE | |||||||||
| 10 | Service Promotion | |||||||||||
| Web site update | not relevant for pilot |
| ||||||||||
| Add the service to the partner services portfolio | not relevant for pilot |
| ||||||||||
| Contact the people/NRENs who took part in the infoshare to update them on service availability | not relevant for pilot |
| ||||||||||
| Update eduroam flyer with the managed service element | not relevant for pilot |
| ||||||||||
| Slide deck for Partner Relations | SO | update the slide deck |
| |||||||||
| Article for CONNECT | not relevant for pilot |
| ||||||||||
| Launch announcement in Tryfon's weekly email when reached | SO/Development team | we will want to do this |
| |||||||||
| Write géant blog | SO/Development team | we will want to do this |
| |||||||||
| Webinar / infoshare | we don't want to do it before pilot, but perhaps when the pilot starts |
| ||||||||||
| Promotion via the eduroam-SG, by the service manager | SO | yes |
| |||||||||
| 11 | PLM Documentation | |||||||||||
CBA | Development team and T&I service portfolio guardians | Marina Adomeit to check if there is template | DONE |
...