This page contains information about roadmap for devops, but may include description to actual issues and developments. RESPONSIBLE: Content is defined and maintained by devops team. |
| 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 |
|
| Deploy beta service |
|
|
| Maria, Leif |
|
| Prepare the OLA |
|
|
| 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 | status.io, pingdom.com | WP5 leaders approved the 10k budget, need to make the CR |
| Marina |
|
| Configure monitoring |
|
|
| Leif, Maria, Marina |
|
| Set the public status pages |
|
|
| Leif, Maria, Marina |
|
| Check the GDPR |
|
|
| Marina via GEANT project GDPR |
|
| Check the IPR? |
|
|
| Marina to consult with Klaas |
|
| Define the procedure for configuration changes |
|
|
|
|
|
Examples for status codes:
| Status |
|---|
| colour | Grey |
|---|
| title | nOT STARTED |
|---|
|
| Status |
|---|
| colour | Yellow |
|---|
| title | iN pROGRESS |
|---|
|
