Alert.png The wiki is deprecated and due to be decommissioned by the end of September 2022.
The content is being migrated to other supports, new updates will be ignored and lost.
If needed you can get in touch with EGI SDIS team using operations @ egi.eu.

Difference between revisions of "EGI Quality Criteria Verification"

From EGIWiki
Jump to navigation Jump to search
m
Line 39: Line 39:
== Reference Documents  ==
== Reference Documents  ==


{| cellspacing="0" cellpadding="3" border="1" style="border: 1px solid black;" class="wikitable sortable"
{| cellspacing="0" cellpadding="3" border="1" class="wikitable sortable" style="border: 1px solid black;"
|- align="left" style="background: none repeat scroll 0% 0% Lightgray;"
|- align="left" style="background: none repeat scroll 0% 0% Lightgray;"
! DocDB link  
! DocDB link  
Line 60: Line 60:
== Metrics  ==
== Metrics  ==


{| cellspacing="0" cellpadding="3" border="1" style="border: 1px solid black;" class="wikitable sortable"
{| cellspacing="0" cellpadding="3" border="1" class="wikitable sortable" style="border: 1px solid black;"
|- align="left" style="background: none repeat scroll 0% 0% Lightgray;"
|- align="left" style="background: none repeat scroll 0% 0% Lightgray;"
! Metric  
! Metric  
Line 83: Line 83:
== Verification engineer skill matrix  ==
== Verification engineer skill matrix  ==


{| border="1" class="wikitable" style="text-align: center;"
{| border="1" style="text-align: center;" class="wikitable"
|+ Verification Cheat Sheet  
|+ Verification Cheat Sheet  
|-
|-
! align="left" width="200" | Product\Institute  
! width="200" align="left" | Product\Institute  
! width="75" | CESGA  
! width="75" | CESGA  
! width="75" | IFCA  
! width="75" | IFCA  
Line 96: Line 96:
! width="75" | BADWB  
! width="75" | BADWB  
! width="75" | UTC-N  
! width="75" | UTC-N  
! width="75" | CSC
! width="75" | CIEMAT
! width="75" | RAL
! width="300" style="background: none repeat scroll 0% 0% Gray;" | COMMENTS
! width="300" style="background: none repeat scroll 0% 0% Gray;" | COMMENTS
|-
|-
Line 109: Line 112:
|  
|  
|  
|  
|
|
|
|-
|-
! align="left" | EMI ARC compute cli  
! align="left" | EMI ARC compute cli  
Line 120: Line 126:
|  
|  
|  
|  
|
|
|
|  
|  
|-
|-
Line 132: Line 141:
|  
|  
|  
|  
|
|
|
|  
|  
|-
|-
Line 145: Line 157:
|  
|  
|  
|  
|
|
|
|-
|-
! align="left" | EMI gLite MPI  
! align="left" | EMI gLite MPI  
Line 156: Line 171:
|  
|  
|  
|  
|
|
|
|  
|  
|-
|-
Line 168: Line 186:
|  
|  
|  
|  
|
|
|
|  
|  
|-
|-
Line 180: Line 201:
|  
|  
|  
|  
|
|
|
|  
|  
|-
|-
Line 192: Line 216:
|  
|  
|  
|  
|
|
|
|  
|  
|-
|-
Line 204: Line 231:
|  
|  
|  
|  
|
|
|
|  
|  
|-
|-
Line 215: Line 245:
|  
|  
|  
|  
|
|
|
|  
|  
| No verifiers available yet.
| No verifiers available yet.
Line 228: Line 261:
|  
|  
|  
|  
|
|
|
|  
|  
|-
|-
Line 240: Line 276:
|  
|  
|  
|  
|
|
|
|  
|  
|-
|-
Line 252: Line 291:
|  
|  
|  
|  
|
|
|
|  
|  
|-
|-
Line 264: Line 306:
|  
|  
|  
|  
|
|
|
|  
|  
|-
|-
Line 276: Line 321:
|  
|  
|  
|  
|
|
|
|  
|  
|-
|-
Line 288: Line 336:
|  
|  
|  
|  
|
|
|
|  
|  
|-
|-
Line 300: Line 351:
|  
|  
|  
|  
|
|
|
|  
|  
|-
|-
Line 312: Line 366:
|  
|  
|  
|  
|
|
|
|  
|  
|-
|-
Line 324: Line 381:
|  
|  
|  
|  
|
|
|
|  
|  
|-
|-
Line 336: Line 396:
|  
|  
|  
|  
|
|
|
|  
|  
|-
|-
! align="left" | EMI EMIR
! align="left" | EMI EMIR  
|  
|  
|  
|  
Line 348: Line 411:
|  
|  
|  
|  
|
|
|
|  
|  
|-
|-
Line 359: Line 425:
|  
|  
|  
|  
|
|
|
|  
|  
| No verifiers available yet. Oracle training required.
| No verifiers available yet. Oracle training required.
Line 371: Line 440:
|  
|  
|  
|  
|
|
|
|  
|  
| No verifiers available yet.
| No verifiers available yet.
Line 383: Line 455:
|  
|  
|  
|  
|
|
|
|  
|  
| No verifiers available yet.
| No verifiers available yet.
Line 395: Line 470:
|  
|  
|  
|  
|
|
|
|  
|  
| No verifiers available yet.
| No verifiers available yet.
Line 407: Line 485:
|  
|  
|  
|  
|
|
|
|  
|  
| No verifiers available yet.
| No verifiers available yet.
Line 420: Line 501:
|  
|  
|  
|  
|
|
|
|  
|  
|-
|-
Line 432: Line 516:
|  
|  
|  
|  
|
|
|
|  
|  
|-
|-
Line 444: Line 531:
|  
|  
|  
|  
|
|
|
|  
|  
|-
|-
Line 456: Line 546:
|  
|  
|  
|  
|
|
|
|  
|  
|-
|-
Line 468: Line 561:
|  
|  
|  
|  
|
|
|
|  
|  
|-
|-
Line 480: Line 576:
|  
|  
|  
|  
|
|
|
|  
|  
|-
|-
Line 492: Line 591:
|  
|  
|  
|  
|
|
|
|  
|  
|-
|-
Line 504: Line 606:
|  
|  
|  
|  
|
|
|
|  
|  
|-
|-
Line 516: Line 621:
|  
|  
|  
|  
|
|
|
|  
|  
|-
|-
Line 528: Line 636:
|  
|  
|  
|  
|
|
|
|  
|  
|-
|-
Line 539: Line 650:
|  
|  
|  
|  
|
|
|
|  
|  
| No verifiers available yet.
| No verifiers available yet.
Line 552: Line 666:
|  
|  
|  
|  
|
|
|
|  
|  
|-
|-
Line 564: Line 681:
|  
|  
|  
|  
|
|
|
|  
|  
|-
|-
Line 576: Line 696:
|  
|  
|  
|  
|
|
|
|  
|  
|-
|-
Line 588: Line 711:
|  
|  
|  
|  
|
|
|
|  
|  
|-
|-
Line 600: Line 726:
|  
|  
|  
|  
|  
|
|
|
|
|-
|-
! align="left" | IGE GridWay  
! align="left" | IGE GridWay  
Line 612: Line 741:
|  
|  
|  
|  
|
|
|
|  
|  
|-
|-
Line 624: Line 756:
|  
|  
| *  
| *  
|
|
|
|  
|  
|-
|-
Line 636: Line 771:
|  
|  
| *  
| *  
|
|
|
|  
|  
|-
|-
Line 648: Line 786:
|  
|  
|  
|  
|
|
|
|  
|  
|-
|-
Line 660: Line 801:
| *  
| *  
|  
|  
|
|
|
|  
|  
|}
|}

Revision as of 10:06, 17 October 2012

Technology Software Component Delivery Software Provisioning UMD Middleware Cloud Middleware Distribution Containers Distribution Technology Glossary


Quality Assurance | Quality Criteria Definition | Quality Criteria Dissemination | Quality Criteria Verification | Verifier Guideline | Verification Testbed | Glossary





Objective

The main objective of the TSA2.3 is to verify the quality of the software provided by the TP before entering the SR phase and going to production. By doing so we prevent that software that might work enters into the SR and even goes into production but that doesn´t follow the quality criteria defined in TSA2.2. Some of the reasons for doing the verification before the software enters the stage rollout are:

- Check that the bugs reported in the previous release of the software have been corrected (work in collaboration with DMSU) by the TP.

- Software can work well in the SR but might not have all the functionalities required

- Software might not be safe, well documented, or have the necessary installation rules or licenses

The Verification Process

When a new product is available, the TP has to follow the NSRW. Once the software is correctly uploaded to the repository, the release enters into the verification phase. The requirements are that the TP has to provide all the necessary information to the verifier (QCV) so that the QCV can assess that the TP has tested in advance the quality of the software. Depending on the type of release, different actions will be taken by the QCV, Verification process is described in detail in the EGI Verifier Guideline.

QC Verification Reports

RT workflow and Verification Templates links are available in this page. First of all verifiers must check QC service mapping to know which test must be verified for each product. This service mapping is available here QC Verification service mapping and Verification/Executive Summary templates are available here: QC Verification Templates.

Verifiers must fill all required fields for each product and write a Verification process summary into Executive Summary, this summary should include:

  • A short summary of the installation and configuration process: Installation and configuration were successful?, If not explain any issue or bug found. If the product was rejected explain why.
  • If its necessary Verifiers should include a comment for StageRollout: Configuration changes or minor issues found verifying the product.
  • If a new QC is necessary and is not included, Verifiers must write a comment to SA2.2 to change current QC.


Verification Work Effort Metrics

Each verification process and change is registered by EGI RT. A complete report is generated on a daily basis each midnight. The XLS file can be downloaded from here SA2 Verification Metrics


Verification Team

Verifiers team is updated for each UMD release and it is available here: SA2.3 Verifiers List. All verifiers are included in the SSO sw-rel-qc group that includes a mailing list and permissions to modify RT tickets related with the verification process.

Reference Documents

DocDB link Release Date Document
QCv3 10. 04. 2012 UMD Quality Criteria
418 11. 08. 2011 UMD Products service mapping
417 11. 08. 2011 QC Verification Templates

Metrics

Metric Description
M.SA2.4 Number of new releases validated against defined criteria: Measures the workload on the validation team.
M.SA2.5 Mean time taken to validate a releas: Indicates how responsive the team is to validating releases.
M.SA2.6 Number of releases failing validation: Indicates the quality assurance process of the software providers.

SLAs

EGI SLAs negotiated with the TPs

EMI-EGI SLA

Verification engineer skill matrix

Verification Cheat Sheet
Product\Institute CESGA IFCA IFIC INFN IN2P3 JÜLICH LIP BADWB UTC-N CSC CIEMAT RAL COMMENTS
EMI ARC CE * *
EMI ARC compute cli * *
EMI ARC Infosys * *
EMI dCache *
EMI gLite MPI * *
EMI CREAM_torque * *
EMI CREAM_lsf *
EMI WMS * *
EMI LB * *
EMI FTS No verifiers available yet.
EMI DPM *
EMI LFC_mySQL *
EMI LFC_Oracle *
EMI StoRM * *
EMI APEL *
EMI DGAS *
EMI BDII *
EMI UI *
EMI PX *
EMI VOMS_mySQL *
EMI EMIR *
EMI VOMS_Oracle No verifiers available yet. Oracle training required.
EMI HYDRA No verifiers available yet.
EMI Wnodes No verifiers available yet.
EMI NAGIOS No verifiers available yet.
EMI Pseudonymity No verifiers available yet.
EMI ARGUS *
EMI UNICORE TSI *
EMI UNICORE WS *
EMI UNICORE Client *
EMI UNICORE Registry *
EMI UNICORE Gateway *
EMI UNICORE Hila *
EMI UNICORE xuudb *
EMI UNICORE Uvos *
EMI AMGA *
IGE SAGA-SD No verifiers available yet.
IGE GRAM5 *
IGE GSISSH *
IGE GridFTP *
IGE myProxy *
IGE RLS *
IGE GridWay *
IGE SAM *
IGE OGSA-DAI *
IGE Security *
IGE Gridsafe *


Early Adopters list

Early Adopters per UMD product