| 14 | | We walk through the documentation, and Sander resolves any issues live. This makes sure that they are addressed immediately without back-and-forth over e-mail, and satisfactorily. Only if issues are very major and hard to resolve at once, will the task be postponed, but then Trac tickets should be made to specify and track each such task. |
| | 14 | We walk through [SystemAdministration/Monitoring/Icinga the documentation], and Sander resolves any issues live. This makes sure that they are addressed immediately without back-and-forth over e-mail, and satisfactorily. Only if issues are very major and hard to resolve at once, will the task be postponed, but then Trac tickets should be made to specify and track each such task. |
| | 15 | |
| | 16 | ## Workflow ## |
| | 17 | |
| | 18 | Benedikt will clarify the workflow insofar needed, including the GitHub <-> monitoring host configuration management script, described here [https://github.com/clarin-eric/monitoring/blob/master/README.md]. |
| | 19 | |
| | 20 | ## Shibboleth SP configuration ## |
| | 21 | |
| | 22 | The DNS name `monitoring.clarin.eu` is now in place for [wiki:SystemAdministration/Hosts/fsd-cloud22.zam.kfa-juelich.de the monitoring host]. The SAML metadata about the Shibboleth SP needs to be updated. A valid TLS certificate needs to be put in place. We will discuss the issue insofar needed, and assign tasks. |
