A maintenance report will be produced on a 6-month basis.
Overall SW performances will be monitored, and TM(5,4), TM(5,3) relevant TM(5,2) events will be tracked indicating the Jira entry number.
Any software reconfiguration apart from the DPU-ASW defaults should be traced, including the HW reconfiguration.
Git repository https://baltig.infn.it/euclid/DPU-ASW
Public git-page https://euclid.baltig-pages.infn.it/DPU-ASW/index.html
Jira tracking https://issues.infn.it/jira/projects/EUNIDPUASW/summary
...
...
...
Management
DPU-ASW manager statement
...
nominal
...
Events, Issues, Bugs
List of events, issues
- none
- Issue link to Jira
Jira server INFN Jira Software serverId 8087fedc-8816-3706-9e66-78f987f39e0c key EUNIDPUASW-175
...
SW/HW Reconfiguration
List of changes with respect to the ASW defaults
...
- any
...
Value and metrics
Results from the trend, or other analysis on all metrics
...
- processing time
- compression factor
- link reports ...
...
Proposed solution for issues/bugs
Conclusion of NRBs related to SW/HW issues
...
Monitor requests
Add any parameter that should be included in the monitoring, to be analyzed in the next report
...
- temperature
- any bias
- etc
...
Management dependencies
Add actions requested to system team management
...
- System NRB to be defined
- etc
- none
...
To Do
Add the list of actions to be conducted in the next period
...
- solve issue
- dedicated test
- SW release
- etc
Notes, actions, and due dates:
...
Learn more: https://www.atlassian.com/team-playbook/health-monitor/project-teams
Copyright © 2016 Atlassian
This work is licensed under a Creative Commons Attribution-Non Commercial-Share Alike 4.0 International License.