Difference between revisions of "UMDQualityCriteria"

From EGIWiki
Jump to: navigation, search
m (UMD Quality Criteria)
 
(12 intermediate revisions by 2 users not shown)
Line 3: Line 3:
 
All the software included in the Unified Middleware Distribution (UMD) must meet a set of Quality Criteria defined by EGI. The Quality Criteria can be classified into generic criteria, i.e. criteria which sould hold for any component of the UMD, and specific criteria, i.e. criteria valid for a particular component only.
 
All the software included in the Unified Middleware Distribution (UMD) must meet a set of Quality Criteria defined by EGI. The Quality Criteria can be classified into generic criteria, i.e. criteria which sould hold for any component of the UMD, and specific criteria, i.e. criteria valid for a particular component only.
  
The current Quality Criteria (QC) can be found in the EGI DocDB: [https://documents.egi.eu/secure/ShowDocument?docid=240 UMD Quality Criteria]. There are several documents that cover the different capabilities defined in the [https://documents.egi.eu/secure/ShowDocument?docid=100 UMD RoadMap]:
+
Any Technology Provider (TP) willing to have their software verified by the SA2 team should carefully read them.
* Generic QC, for all software
 
* Functional Capabilities QC
 
* Security Capabilities QC
 
* Operational Capabilities QC
 
  
TP willing to have their software audited by the SA2 team should carefully read them.
+
=== QC Documents ===
  
== QC drafts ==
+
The Quality Criteria (QC) is written following the classification of capabilities defined in can the [https://documents.egi.eu/secure/ShowDocument?docid=272 UMD RoadMap], one document for each type of capability. Take into account that a software component may cover QC specified in more than one of those documents.
  
This page is now used as a placeholder for drafting new criteria for components.
+
=== QC Roadmap ===
  
=== Identified Capabilities ===
+
QC definition is a continuous process driven by the requirements of users and operations communities, however the verification of new software releases will be done against fixed releases of the QC documents. At least every 6 months a new major version of the QC will be released, although more frequent releases may occur if necessary.
These capabilities are identified in the [https://documents.egi.eu/secure/ShowDocument?docid=100 UMD RoadMap] but still waiting for EGI Community input for definition:
 
  
==== Functional Capabilities ====
+
Each new release of the QC will be announced in this page and the TCB mailing list. Along with the announcement of each release of QC specification, a date for its use in verification will be specified. It is expected that verification will use new releases of the QC within 2 to 4 weeks from the release date.
* File Encryption/Decryption
 
  
: Sensitive data needs to be stored securely. Before being stored in a remote file store the file may need to be encrypted and then on retrieval de-encrypted before use. The capability should also provide solutions relating to the storage of the keys needed to perform these tasks.
+
Each QC release will contain documentation with:
 +
* major changes introduced in the version.
 +
* criteria to be deprecated in next release of the QC, if any.
  
* Metadata Catalogue
+
As soon as a major update of the QC is released, the next version will be made available as draft in the DocDB. This draft will allow the TP to plan their testing efforts.  
: The metadata catalogue is used to store and query information relating to the data (files, databases, etc.) stored within the production infrastructure.  
 
  
* Database Access
+
==== Current QC Specification ====
: Many communities are moving to the use of structured data stored in relational databases. These need to be accessible for controlled use by remote users as any other e-Infrastructure resource.
 
  
* File Transfer Scheduling
+
Current QC Specification can be found at the [https://documents.egi.eu/public/ShowDocument?docid=240 QC document] in EGI DocDB.
: The bandwidth linking resource sites is a resource that needs to be managed in the same way compute resources at a site are accessed through a job scheduler. By being able to schedule wide area data transfers, requests can be prioritised and managed. This would include the capability to monitor and restart transfers as required.
+
Check the [[EGI-InSPIRE:UMDQualityCriteria:QC1 | release notes]].
  
* Remote Instrumentation
+
==== Future Releases ====
: Instruments are data sources frequently encountered within e-Infrastructures. As part of a distributed computing architecture providing remote access to manage and monitor these instruments is becoming increasingly important within some communities.
 
  
* Workflow
+
{| class="wikitable sortable"  style="border:1px solid black" cellspacing="0" cellpadding="3" border="1"
: The ability to define, initiate, manage and monitor a workflow is a key capability across many user communities. It is also a capability that can be deployed by a user or a user community (i.e. it does not need to be a service provided as part of the core infrastructure) but the various workflow systems may have requirements that need to be supported within the core infrastructure.
+
|- style="background:Lightgray"  align="left"
 +
! DocDB link
 +
! Expected Release Date
 +
! Expected Verification Date
 +
! More information
 +
|-
 +
| [https://documents.egi.eu/public/ShowDocument?docid=240 240]
 +
| 10. 02. 2011
 +
| 10. 02. 2011
 +
| [[EGI-InSPIRE:UMDQualityCriteria:QC1 | release notes]]
 +
|-
 +
| -
 +
| 01. 08. 2011
 +
| 15. 08. 2011
 +
| -
 +
|}
  
==== Operational Capabilities ====
+
==== Past QC releases ====
* Virtual Image Management
 
: As virtual machine images become the default approach to providing the environment for both jobs and services, increased effort is needed on building the trust model around the distribution of images. Resource providers will need a mechanism for images to be distributed, cached and trusted for execution on their sites.
 
  
* Virtual Machine Management
+
There are no past QC releases.
: The core functionality is for authorized users to manage the virtual machine life-cycle and configuration on a remote site (i.e. start, stop, pause, etc.) Machine images would be selected from a trusted repository at the site that would be configured according to site policy. Together this would allow site managers to determine both who could control the virtual machines running on their sites and who generated the images used on their site.
 
 
 
* Messaging
 
: Within distributed systems, a message ‘bus’ provides a reliable mechanism for data items to be sent between producers and (multiple) consumers. Such a capability, once established, can be reused by many different software services.
 
 
 
[[Category:WP5-SA2]]
 

Latest revision as of 22:11, 24 December 2014

UMD Quality Criteria

All the software included in the Unified Middleware Distribution (UMD) must meet a set of Quality Criteria defined by EGI. The Quality Criteria can be classified into generic criteria, i.e. criteria which sould hold for any component of the UMD, and specific criteria, i.e. criteria valid for a particular component only.

Any Technology Provider (TP) willing to have their software verified by the SA2 team should carefully read them.

QC Documents

The Quality Criteria (QC) is written following the classification of capabilities defined in can the UMD RoadMap, one document for each type of capability. Take into account that a software component may cover QC specified in more than one of those documents.

QC Roadmap

QC definition is a continuous process driven by the requirements of users and operations communities, however the verification of new software releases will be done against fixed releases of the QC documents. At least every 6 months a new major version of the QC will be released, although more frequent releases may occur if necessary.

Each new release of the QC will be announced in this page and the TCB mailing list. Along with the announcement of each release of QC specification, a date for its use in verification will be specified. It is expected that verification will use new releases of the QC within 2 to 4 weeks from the release date.

Each QC release will contain documentation with:

  • major changes introduced in the version.
  • criteria to be deprecated in next release of the QC, if any.

As soon as a major update of the QC is released, the next version will be made available as draft in the DocDB. This draft will allow the TP to plan their testing efforts.

Current QC Specification

Current QC Specification can be found at the QC document in EGI DocDB. Check the release notes.

Future Releases

DocDB link Expected Release Date Expected Verification Date More information
240 10. 02. 2011 10. 02. 2011 release notes
- 01. 08. 2011 15. 08. 2011 -

Past QC releases

There are no past QC releases.