Difference between revisions of "EGI Quality Criteria Release 3"
(Created page with '{Tech menubar}} {{Tech QA submenu}} {{TOC_right}} These release notes describe the third release of the Quality Criteria for UMD software with expected deliver date in early Feb…') |
|||
Line 24: | Line 24: | ||
== Covered Capabilities == | == Covered Capabilities == | ||
From all capabilities identified in | From all capabilities identified in [[EGI_Roadmap_and_Technology]], the following are covered: | ||
=== Security Capabilities === | === Security Capabilities === | ||
* Authentication | * Authentication |
Revision as of 10:53, 6 October 2011
{Tech menubar}}
Quality Assurance | | Quality Criteria Definition | | Quality Criteria Dissemination | | Quality Criteria Verification | | Verifier Guideline | | Verification Testbed | | Glossary |
These release notes describe the third release of the Quality Criteria for UMD software with expected deliver date in early February 2011.
The documents can be found at DocDB #718, current status is DRAFT.
What's New
Documents
The Quality Criteria (QC) can be found in the DocDB #718, there is one document for each type of capability:
- Generic QC, for all software
- Security Capabilities QC
- Information Capabilities QC
- Storage Capabilities QC
- Data Capabilities QC
- Compute Capabilities QC
- Operations Capabilities QC
- Virtualisation Capabilities QC
Take into account that a software product may cover QC specified in more than one of those documents.
Covered Capabilities
From all capabilities identified in EGI_Roadmap_and_Technology, the following are covered:
Security Capabilities
- Authentication
- Attribute Authority (using VOMS as reference implementation)
- Authorization (using Argus as reference implementation)
- Credential Management (using MyProxy as reference implementation)
Information Capabilities
- Information Model
- Information Discovery
- Messaging
Storage Capabilities
- File Encryption/Decryption (using Hydra as reference implementation)
- File Access
- File Transfer
- File Transfer Scheduling (using FTS as reference implementation)
- Storage Management
Data Capabilities
- Data Access (using OGSA-DAI as reference implementation)
- Metadata Catalogue (using AMGA and LFC as reference implementations)
Compute Capabilities
- Job Execution
- Parallel Job
- Interactive Job Management
- Job Scheduling (using WMS as reference implementation)
Client API Capability
- Client API
- Client Tools
Remote Instrumentation
- Remote Instrumentation
Operations Capabilities
- Monitoring
- Accounting (using APEL as reference implementation)
Virtualisation Capabilities
- Virtual Machine Management
- Virtual Machine Image Format
- Image Distribution
Non Covered Capabilities
Some capabilities identified in the UMD Roadmap are still missing the Quality Criteria due to lack of a clear reference implementation or missing requirements from the EGI community. Most of the missing capabilities are introduced in the last UMD roadmap version.
- Workflow
The Quality Criteria Task will continue the process of defining the missing capabilities for the next releases of the QC.
Detailed Changelog
- Requirements from User Community
- Requirements from Operations Community (especially software incidents found in production)
- Deficiencies in criteria found in Verification or Stage Rollout
- Recommendations and issues found by the Software Vulnerability Group
- Analysis of reference implementations of UMD Capabilities defined in the Roadmap:
- Review and analysis of feedback from Technology Providers