The development of managed eduroam SP started in January 2019 under GN4-3 project, by eduroam development team in WP5. During the course of the project, the eduroam development team was working closely with NRO community and has developed the service prototype. By the end of 2020, it is planned to prepare for running service pilot and completing the PLM gate to transition to pilot. The information in this page is meant to capture all aspects of preparing for the pilot and needed for making the decision.
What kind of pilot are we running:
It will be limited audience - up to 10 participants that we will invite and manage.
Technically we need to run this on stabile IP address. Two locations in Europe would be preffered. - for HA of the service. We can ask for 2 locations from GEANT IT
Logging usage information: we will now how many institutions are using, we cannot know who much wifi hotspots are connected. There is possibility to collect stats for number of auths.
We want to have it as "at no additional cost" service, and NROs that want to rely on it at a greater scale and have tighter control can deploy national solutions.
Think about global model - operators at regional level. - think about this for production.
The transition of the service to pilot generally consist of the subset of the following areas of work (the full list here is relating to production operations):
- 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:
- T&I service portfolio guardians: Licia Florio Marina Adomeit
- Service owner: Miroslav Milinovic
- Development team: Stefan Winter
- GEANT T&I operation support/Core team: Nicole Harris
- PLM product manager: Alan Lewis
- Test team: Marcin Wolski
- IPR and GDPR accountable: GEANT DPO gdpr@geant.org
NOT RELEVANT FOR PILOT
IN PROGRESS
DONE
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. | NOT RELEVANT FOR PILOT | |||
| Branding and Visibility | -Development team prepares -SO signs off | we still need to think a branding - for production | NOT RELEVANT FOR PILOT | |||
| 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) | NOT RELEVANT FOR PILOT | |||
| 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) | NOT RELEVANT FOR PILOT | |||
| 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. | NOT RELEVANT FOR PILOT | |||
| 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 | NOT RELEVANT FOR PILOT | |||
| 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 | IN PROGRESS | |||
| 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. | NOT RELEVANT FOR PILOT | |||
| Define roles, skills, manpower needed | Development team | pilot will be supported by the eduroam-OT and dev team | NOT RELEVANT FOR PILOT | |||
Appoint operational team members | SM | For production we may need some additional manpower for opserations | NOT RELEVANT FOR PILOT | |||
| 6 | Operational team training | |||||
| Training the operational team | Development team prepares eduroam-OT is trained | Not needed. | NOT RELEVANT FOR PILOT | |||
| 7 | Support team establishment | |||||
| Establish the support team | Pilot doesn't need dedicated support team - dev team will work with limited pilot participants | NOT RELEVANT FOR PILOT | ||||
| 8 | Support team training | |||||
| Training of the support team | Development team prepares eduroam-OT is trained | Not needed. | NOT RELEVANT FOR PILOT | |||
| 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 | NOT RELEVANT FOR PILOT | |||
| Back-up and restore | eduroam-OT | not necessary for the pilot | NOT RELEVANT FOR 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 | TO DO To do after pilot is approved | ||||
| Add the service to the partner services portfolio | not relevant for pilot | NOT RELEVANT FOR PILOT | ||||
| Contact the people/NRENs who took part in the infoshare to update them on service availability | not relevant for pilot | NOT RELEVANT FOR PILOT | ||||
| Update eduroam flyer with the managed service element | not relevant for pilot | NOT RELEVANT FOR PILOT | ||||
| Slide deck for Partner Relations | SO | update the slide deck | TO DO To do after pilot is approved | |||
| Article for CONNECT | not relevant for pilot | NOT RELEVANT FOR PILOT | ||||
| Launch announcement in Tryfon's weekly email when reached | SO/Development team | we will want to do this | TO DO To do after pilot is approved | |||
| Write géant blog | SO/Development team | we will want to do this | TO DO To do after pilot is approved | |||
| Webinar / infoshare | we don't want to do it before pilot, but perhaps when the pilot starts | NOT RELEVANT FOR PILOT | ||||
| Promotion via the eduroam-SG, by the service manager | SO | yes | TO DO To do after pilot is approved | |||
| 11 | PLM Documentation | |||||
CBA | Development team and T&I service portfolio guardians | Marina Adomeit to check if there is template | DONE |