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 Verifier Guideline QC5"
| Line 5: | Line 5: | ||
The main objective of this guideline is to aid new SA2 verifiers to complete Verification process successfully. This guideline includes these topics: | 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 | *How to request and manage a new SA2 testbed machine. | ||
*How to handle | *How to handle product 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. | ||
| Line 18: | Line 18: | ||
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: | 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.'' | *Subject: ''SA2 Verification Tesbed request.'' | ||
*Body: | *Body: | ||
** ''Verifier Name.'' | **''Verifier Name.'' | ||
** ''Product name to verify.'' | **''Product name to verify.'' | ||
** ''Verifier SSH public key (generated id_dsa.pub)'' | **''OS and hardware requirements (if necessary)'' | ||
**''Verifier SSH public key (generated id_dsa.pub)'' | |||
Verification team will submit | Verification team will submit a confirmation email to connect to the new machine (public IP, hostname, etc). | ||
== Middlaware Installation == | |||
Verifiers should be able to connect new created VM machines to start verification process, these machines include: | |||
* NTP configuration. | |||
* EPEL and EGI-trustanchors repositories. | |||
* Host certificate (hostcert.pem and hostkey.pem) | |||
Revision as of 18:44, 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 testbed machine.
- How to handle product 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.
- OS and hardware requirements (if necessary)
- Verifier SSH public key (generated id_dsa.pub)
Verification team will submit a confirmation email to connect to the new machine (public IP, hostname, etc).
Middlaware Installation
Verifiers should be able to connect new created VM machines to start verification process, these machines include:
- NTP configuration.
- EPEL and EGI-trustanchors repositories.
- Host certificate (hostcert.pem and hostkey.pem)