...
| Action | Description | Status | Due Date | Assigned to | Comment |
|---|---|---|---|---|---|
Service Architecture Documented | Make a reference drawing of service architecture | done | Marina | ||
| Update the requirements for service operations | To reflect the service architecture that was documented | Marina, consult with Leif | |||
| Deploy beta service | Maria, Leif | ||||
| Prepare the OLA | First draft till 10th October | Marina (consult with Jonny) | |||
| Pen testing of the beta service | Marina via DFN cert (consult Leif, inform Jonny of results) | ||||
| Code testing of code that is running as web app | Marina via Marcin (consult Leif, inform Jonny of results) | ||||
| Get budget for the monitoring, and clean up the ops budget | status.io, pingdom.com | WP5 leaders approved the 10k budget, need to make the CR | First week October | Marina | |
| Configure monitoring | Leif, Maria, Marina | ||||
| Set the public status pages | Leif, Maria, Marina | ||||
| Check the GDPR | User never touches any of the nodes that are maintained by seamless access.org. The only interaction point is the CDN. Their privacy policy and DPA should be checked!!! | Marina via GEANT project GDPR | |||
| Check the IPR? | Marina to consult with Klaas | ||||
| Configuration change process | Define the configuration change process. Should be reflected in the OLA. | Marina (consult with Jonny) | |||
| Support process | Define who the support process flow, the actors etc. Should be reflected in the SLA | Marina (consult with Jonny) and take up with Heather | |||
| Formulate the L3 support | Leif + certain members from the Technical Sterring group | Marina to take up with Heather | |||
| Service operations definition | Prepare a definition of the service ops baseline for additional operators of the service | Marina, consult with Leif, Tech Steerting group for approval. |
Examples for status codes:
...