EGI Quality Criteria Release 3

From EGIWiki
Jump to: navigation, search
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

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 FIANL.

What's New


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)
  • Workflow (covered by the WMS Dag execution)

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

Detailed Changelog

  • Requirements from User Community
    • Rephrasing of GENERIC_DOC_4 to avoid inconsistencies (GGUS #73214)
  • Requirements from Operations Community (especially software incidents found in production)
    • New criteria: INFOMODEL_SCHEMA_2 (From RT #1378)
    • Bugs found: JOBSCH_WMS_BUG_1 (for GGUS bug: #73035)
  • Deficiencies in criteria found in Verification or Stage Rollout:
    • Removed non testeable criteria on verification: JOBEXEC_AVAIL_3
  • Recommendations and issues found by the Software Vulnerability Group:
  • Analysis of reference implementations of UMD Capabilities defined in the Roadmap:
    • New capabilities: Client Tools (CLIENT_TOOLS_*), Virtual Machine Management (VIRT_MGMT_*), Virtual Machine Image Format (VIRT_IMG_*), Virtual Image Distribution (VIRT_IMGDIST_*).
  • Review and analysis of feedback from Technology Providers
    • Better wording of several criteria to not require test suites but functionality (FILECRYPT_*, FILETRANSSCHE_*, INSTRUMENT_IE_1, DATAACCESS_*)
    • Added a reference to sample tests in STORAGE_API_2
    • Review of SAGA criteria (CLIENT_API_*)
    • Review of Information capabilities criteria (INFO_*, MSG_*), remove INFO_AVAIL_2 (Redundant with other availability criteria)
    • New criterion for bugfixes and features testing (GENERIC_SOFT_2)
    • Other:
      • better wording in GENERIC_DOC_9
      • review tests in GENERIC_SERVICE_1
      • removed requirement for keeping manual configuration in GENERIC_SERVICE_5
      • removed DRMAA as possible interface in JOBEXEC_IFACE_1
      • configuration conditions for GENERIC_SERVICE_5