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 @ egi.eu.

Difference between revisions of "EGI Technology"

From EGIWiki
Jump to navigation Jump to search
(Replaced content with '#redirect EGI_Software_Provisioning')
 
(One intermediate revision by the same user not shown)
Line 1: Line 1:
{{TOC_right}}
#redirect [[EGI_Software_Provisioning]]
 
== Quality Assurance ==
 
The Quality Assurance unit in EGI defines and executes the processes of
* structuring, defining and assurance of technical accuracy of Quality Criteria
* evolving Quality Criteria from a current set to a future set of criteria valid for assurance and control by Technology Providers
 
=== Structure and Definition of Quality Criteria ===
 
EGI's Quality Critera are organised in a set of documents. The organisation of Quality Criteria follows the layout of the UMD Roadmap version for which the Quality Criteria [[https://wiki.egi.eu/wiki/EGI_Technology#Evolution_of_Quality_Criteria are valid]].
 
One document in any given set of Quality Criteria defines ''Generic Quality Criteria'', whereas the remaining documents define the ''Specific Quality Criteria''.
 
**Generic Quality Criteria** apply to all Products delivered to EGI by a Technology Provider. However, some Generic Quality Criteria may not apply to a specific Product because the scope of the Product falls out of the coverage of the pertinent Generic Quality Criteria. The Quality Control team in EGI advises Technology Providers which Generic Quality Criteria apply to Products they wish to make available to EGI.
 
**Specific Quality Criteria** apply to all Products delivered to EGI that implement a specific UMD Capability. Conversely, if a Product implements more than one Capability at once, then ''all'' Specific Quality Criteria of all implemented Capabilities apply to the given Product.
 
=== Evolution of Quality Criteria ===
 
It is a well-proven fact in Software Engineering that user requirements for any given piece of software change over time. So, as requirements change, so must the software designed to satisfy these requirements. Consequently, Quality Criteria by which the quality of the software is assessed that is verified for production infrastructure availability, must evolve over time, too.
 
With change of Quality Criteria come multiple sets of Quality Criteria. To deliver software that matches EGI's quality demand, Technology Providers must know well in advance which set of Quality Criteria are in effect at any given point in time.
 
 
The following rules define the process of Quality Criteria validity:
* A set of Quality Criteria covers the complete UMD Capabilities.
* A set of Quality Criteria are valid for 6 calendar months, following the [[https://wiki.egi.eu/wiki/WP5:_Provisioning_the_Software_Infrastructure_(SA2)#Deliverables UMD Roadmap publication schedule]] with an offset of one month.
* A set of Quality Criteria is stored in EGI's document database as a set of documents grouped in one storage location.
* A set of Quality Criteria has a shared version, e.g. "QC-1"
* At most one set of Quality Criteria is valid at any given point in time marked "FINAL" in EGI's document database.
* There may be more than one set of Quality Criteria in "DRAFT" status, marked as such in the document database.
* As time passes, FINAL sets of Quality Criteria may become "DEPRECATED" by the next version of Quality Criteria.
* All DEPRECATED sets of Quality Criteria are kept publicly available for reference.
 
 
Quality Criteria may evolve to reflect changing user requirements. The process of evolution is captured as follows:
# Anyone interested in the Quality Criteria definition may review the documents, at any given point in time.
# Feedback and requests for change must be given through the appropriate channels associated with the reviewer's affiliation
## Reviews and comments from the resource operation communities must be given through the OMB
## Reviews and comments from the end user communities must be given, via the VRCs, to the UCB
# UCB and OMB are collating and prioritising the reviews and comments, and discuss them at regular TCB meetings.
# The TCB decides upon the changes, and in which DRAFT version of the Quality Criteria they shall be reflected.
 
== Quality Control ==
 
== Software Provisioning ==
 
== 2nd line support: Distributed Middleware Support Unit ==
 
== Glossary ==
 
{| class="sortable" style="border:1px solid black;" cellpadding="5" cellspacing="0"
|-style="background: lightgray;"
! style="border-bottom:1px solid black;" | Term
! style="border-bottom:1px solid black;" | Description
|-
|style="border-bottom:1px solid black;" | (UMD) Capability
|style="border-bottom:1px solid black;" | A Capability is scoped around well known and well-defined activities that are sufficiently disparate, independent, and fulfil a discrete task in a higher-level orchestrated sequence of actions taken by the user (manually or automated) in order to reach the aspired goal. Capabilities may depend on the presence of another Capability. Appliances, however, SHOULD NOT depend on each other to avoid technical dependencies and vendor lock-in.
|-
|style="border-bottom:1px solid black;" | Appliance
|style="border-bottom:1px solid black;" | An Appliance is the technical implementation of a Capability. An Appliance may be delivered in a single, monolithic Package, or it may be delivered as a set of components that are grouped into a set of Packages. In the latter case all packages must be installed to provide the complete Appliance.
|-
|style="border-bottom:1px solid black;" | Package
|style="border-bottom:1px solid black;" | A Package is a structured software unit suitable for automated installation on a computer. A Package may specify dependencies on other packages, so that either a specific version of that package, or a minimum version of that package may satisfy that dependency.
|-
|style="border-bottom:1px solid black;" | Product
|style="border-bottom:1px solid black;" | A Product is a solution delivered by Technology Providers to EGI and provides the functionality for one, sometimes more Capabilities ''as one single, undividable unit''. Consequently, a Product may comprise of one or more Appliances.
|-
|style="border-bottom:1px solid black;" | Primary Package
|style="border-bottom:1px solid black;" | A Product consists of a well-defined set of specific packages, each in a specific version. Different versions (whether major, minor, or revision) of the same Product may share a subset of packages of the same version, that do not change between the compared versions.
|-
|style="border-bottom:1px solid black;" | Secondary Package
|style="border-bottom:1px solid black;" | A Secondary Package is a Package that is resolved from dependency declarations within a Package, that sources either from the Technology Provider's own Repository, or from any additional repository except OS distribution repositories. (Note: EPEL is an example of such a repository that is not an OS repository.)
|}

Latest revision as of 17:42, 7 February 2011