PROC10 Recomputation of SAM results or availability reliability statistics
|Main||EGI.eu operations services||Support||Documentation||Tools||Activities||Performance||Technology||Catch-all Services||Resource Allocation||Security|
|Documentation menu:||Home •||Manuals •||Procedures •||Training •||Other •||Contact ►||For:||VO managers •||Administrators|
|This page is Deprecated; the content has been moved to https://confluence.egi.eu/display/EGIPP/PROC10+Recomputation+of+SAM+results+or+availability+reliability+statistics|
|Title||Recomputation of availability/reliability statistics|
|Policy Group Acronym||OMB|
|Policy Group Name||Operations Management Board|
|Procedure Statement||This procedure documents the steps for requesting a correction in the SAM test results and in the related availability/reliability statistics.|
This procedure documents the steps for requesting a correction in the OPS VO test results and in the related availability/reliability statistics if applicable.
Figures are available trough the web interface : http://egi.ui.argo.grnet.gr/
DISCLAIMER: This procedure is only applicable to EGI OPS test results. Procedures for the computation of VO-specific availability report are VO-specific and are out of this scope.
Please refer to the EGI Glossary for the definitions of the terms used in this procedure.
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", “MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119.
Who can submit a request?
Re-computations can be requested by:
- site administrators
- regional operations staff.
Starting from the 01 May 2012:
- monitoring results can be recomputed only in the case of problems with the monitoring infrastructure itself.
- No re-computations will be performed in case of issues with the deployed middleware (e.g. in case of documented bugs affecting the availability of a production service end-point), which will be consequently reflected in lower availability/reliability.
Some examples of possible issues justifying a re-computation request:
- invalid proxy certificate used for submitting the monitoring probes in a Nagios instance;
- problems with the Storage Element used for replica management tests resulting in errors on CE's metrics.
The deadline: 10 calendar days after the publication and announcement of the monthly Availability/Reliability reports for a given month X (typically the announcement will be distributed on the 1st day of month X+1).
According to the re-computation requests received, A/R reports will be regenerated only once for each month, after the 10th of month X+1.
How to request a re-computation of OPS monitoring results
|1||Site administrator / ROD team||
As soon as the problem is detected, please fill in the form in the following page: https://ui.argo.grnet.gr/recomputation
Provide an explanation for the request.
The submission of the form will inform the ARGO team and your request will be in pending status.
Member of the staff validates the request.
You will be informed about the confirmation / rejection of the request by email .
If the request is accepted - the recomputation will be triggered as soon as possible .
The status of the recomputation will be visible trough a web page (link given in the email of the previous step )
|George Fergadis/AUTH||03/05/2012||updated policy and procedure to reflect the OMB decision of the March 2012 meeting|
|George Fergadis/AUTH||17/01/2012||the text of the procedure is fixed to clarify that both RC administrators and regional operations staff can request a re-computation.|
|George Fergadis/AUTH||16/01/2012||the text of the procedure is fixed to clarify that the recomputation of test results can be requested before the end of the affected month, in which case if sufficient time is allowed for fixing of the test results, no re-computation of availability/reliability statistics will be needed.|
|M. Krakowian||19 August 2014||Change contact group -> Operations support|
Add step2: Note: It is recommended to open a ticket for recomputation as soon as the problems has been detected.
|C. L'Orphelin||28.09.2015||ARGO procedure : no need of a ticket , replacement by a recomputation form|
|Alessandro Paolini||2016-06-08||Changed contact group -> Operations|
|Alessandro Paolini||2019-07-08||the old link for re-computation (http://argo.egi.eu/lavoisier/recomputation) has been removed while waiting for the correspondent page on the new web UI; a ggus ticket should be opened for the re-computation request|
|Alessandro Paolini||2019-09-05||the new link for the re-computation request has been added; removed some old links.|