Difference between revisions of "EGI Verifier Guideline QC5"
Jump to navigation
Jump to search
Line 7: | Line 7: | ||
*How to request and manage a new SA2 tesbed machine. | *How to request and manage a new SA2 tesbed machine. | ||
*How to handle pruduct RT information and install new middleware. | *How to handle pruduct RT information and install new middleware. | ||
*How to use QC verification reports: | *How to use QC verification reports: | ||
**Which QC tests must be checked. | **Which QC tests must be checked. | ||
**How to fill QC reports and Executive Summaries. | **How to fill QC reports and Executive Summaries. | ||
*When and how a product is rejected or accepted. | *When and how a product is rejected or accepted. | ||
**Differences between critical and non critical bugs. | **Differences between critical and non critical bugs. | ||
**Mandatory and Optional QCs. | **Mandatory and Optional QCs. | ||
== SA2 | == SA2 Verification Testbed == | ||
Each released product | Each released product '''MUST''' be installed in different machines. SA2 Verifiers should request a new virtual machine for verification test submitting an email to grid-admin(at)cesga.es. This email should include: | ||
*Subject: ''SA2 Verification Tesbed request.'' | |||
*Body: | |||
** ''Verifier Name.'' | |||
** ''Product name to verify.'' | |||
** ''Verifier SSH public key (generated id_dsa.pub)'' | |||
Verification team will submit an confirmation email to connect to the new machine: |
Revision as of 18:33, 19 April 2011
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 this guideline is to aid new SA2 verifiers to complete Verification process successfully. This guideline includes these topics:
- How to request and manage a new SA2 tesbed machine.
- How to handle pruduct RT information and install new middleware.
- How to use QC verification reports:
- Which QC tests must be checked.
- How to fill QC reports and Executive Summaries.
- When and how a product is rejected or accepted.
- Differences between critical and non critical bugs.
- Mandatory and Optional QCs.
SA2 Verification Testbed
Each released product MUST be installed in different machines. SA2 Verifiers should request a new virtual machine for verification test submitting an email to grid-admin(at)cesga.es. This email should include:
- Subject: SA2 Verification Tesbed request.
- Body:
- Verifier Name.
- Product name to verify.
- Verifier SSH public key (generated id_dsa.pub)
Verification team will submit an confirmation email to connect to the new machine: