Alert.png 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 @

Difference between revisions of "UMDQualityCriteria"

From EGIWiki
Jump to navigation Jump to search
Line 10: Line 10:

TP willing to have their software audited by the SA2 team should carefully read them.
TP willing to have their software audited by the SA2 team should carefully read them.

== QC drafts ==
== QC drafts ==

Revision as of 17:17, 16 November 2010

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.

The current Quality Criteria (QC) can be found in the EGI DocDB: UMD Quality Criteria. There are several documents that cover the different capabilities defined in the UMD RoadMap:

  • 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 drafts

This page is now used as a placeholder for drafting new criteria for components.

Identified Capabilities

These capabilities are identified in the UMD RoadMap but still waiting for EGI Community input for definition:

Functional Capabilities

  • 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.
  • Metadata Catalogue
The metadata catalogue is used to store and query information relating to the data (files, databases, etc.) stored within the production infrastructure.
  • Database Access
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
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.
  • Remote Instrumentation
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
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.

Operational Capabilities

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