Wait for results of service dashboard then use that to create this
Participants
Name | Organisation |
---|---|
Lukas Hämmerle | SWITCH |
#Enter the persons who are participating in the team that works on this Activity - delete this line after using the template#
Name | Organisation | Role |
---|---|---|
#Enter the persons who are internal projects or external stakeholders of this Activity - delete this line after using the template#
Name | Organisation | Role |
---|---|---|
Davide Vaghetti | GARR | eduGAIN service owner |
PSNC | eduGAIN OPS | |
multiple | various | eduTEAMS support team |
Activity overview
There are currently already several eduGAIN checking tools that examine the quality of an eduGAIN federation’s metadata, the connection status of their IdPs or the attribute release status of their IdPs. The results of these checks are public but only few federation operators seem to regularly consult the results.
The eduGAIN Support team plays a pivotal role in trying to make federation operators and sometimes also entities aware of some of these issues, but as this is done manually and it is tedious work, they typically only act in case of complaints, which means not not all entities are engaged with and it is done so only irregularly.
It would be an improvement if all federation operators would receive a monthly email summarizing the state of their federation. Therefor this activity proposes to create a tool that aggregates the combined result of all these checks into 1 comprehensive infographic per entity. This infographic should also show how well the entity is doing in relation to its peers. At the same time it should provide pointers to documentation on how to actually improve. A second infographic will generate an overview for federation operators, summarizing the per entity findings. This page should also compare their own federation with their peers.
The tool will put this information readily into the hands of the federation operators allowing them to decide if and how to pass it on towards the entities in their federation.
In addition, there is work ongoing to check for status of various entity categories, like CoCo, R&S and SIRTFI. This is currently happening in separate teams. Rather then reinvent the wheel and create yet another tool, we should investigate joining efforts.
Example infographic (not on entity status, but just for reference https://www.surf.nl/files/2019-03/gebruik_surfconext_2018.pdf)
- Collect the well know issues that need checking an reporting on w/ Lukas and members of eduGAIN support team and fedOPS generically
- Collect the various information sources (existing checking tools) we have for creating these informational pages
- Design a layout for the two infographics
- Create a tool (and possible required backed checks) to produce the infographic (Note
- enable periodic emailing of infographics to fedOPS
Activity Details
- We may need to add some new checks
- we should discuss if such tools can be closely integrated with the existing eduGAIN technical pages)
- we should collaborate with e.g. the team working on SIrtfi checking
- we should engage with some people form e.g. marcoms to help us work on the layout and presentation of the infographics
- Overall this would increase the awareness of which issues a federation has, it would increase the motivation to fix them and it thus would increase the overall eduGAIN service quality.
- By automating some of these task, we relieve the burden of the eduGAIN support team
- Check tools too difficult to integrate with
- FedOps would still not act/care
THis activity is done when:
We have collected a list of things to include in the reporting and the sources for this information are understood
We created a comprehensive design for the infographics
#How are the results of the Activity intended to be used? If this requires further engagement, can you describe how you intent to sustain it? - delete this line after using the template#
<Enter here>
Activity Results
Meetings
Date | Activity | Owner | Minutes |
---|---|---|---|
January 1, 2017 | Kickoff meeting | ||
Documents