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.
Glossary
Jump to navigation
Jump to search
EGI Glossary
This page contains the latest version of EGI glossary terms (DRAFT PAGE).
The Glossary is designed to be general. Terms in Italics should be instantiated to the attaining infrastructure. In the context of EGI, the following substitutions should be considered:
- e-infrastructure = EGI
- IT capabilities = UMD Capabilities
| Term | Abbr. | Definition |
|---|---|---|
| All of the hardware, software, networks, facilities, etc. that are required to develop, test, deliver, monitor, control or support IT Services. The term IT Infrastructure includes all of the information technology but not the associated people, Processes and documentation (source: ITIL V3) | ||
| AUP | A set of terms and conditions applicable to the Users of an IT Infrastructure. | |
| An IT Infrastructure for instant access to data, remote instruments, "in silico" experimentation, as well as the setup of Virtual Research Communities. | ||
| Means of delivering value to Users by facilitating outcomes they want to achieve withouth the ownership of specific costs and risks (adapted from ITIL V3) | ||
| A Service provided to one or more Users by a Resource Centre or a Resource Infrastructure Provider. An IT Service is based on the use of Information Technology and supports the User Business Processses. An IT Service is made up from a combination of people, Processes and technology and should be defined in a Service Level Agreement. An IT Service provides one or more IT capabilities (adapted from ITIL V3) | ||
| A physical or virtual entity that is consumed from an e-Infrastructure through IT Services | ||
| A person who uses the IT Service on day-to-day basis (source: ITIL V3) | ||
| RC | The smallest resource administration domain in an e-infrastructure. It can be either localised or geographically distributed. It provides a minimum set of local or remote IT services compliant to well-defined IT capabilities necessary to make resources accessible to users. Access is granted by exposing common interfaces to users. | |
| Site | See Resource Centre | |
| A centre offering operations services on behalf of the Resource Infrastructure Provider. | ||
| RI | A Resource Infrastructure is a federation of Resource Centres. | |
| An individual who leads the Resource Centre operations, and is the official technical contact person in the connected organisation. He/she is locally supported by a team of Resource Centre administrators. | ||
| An individual who is responsible for installing, operating, maintaining and supporting one or more resources or IT services in a Resource Centre. | ||
| A Resource Centre that conforms to the requirements specified in the "Resource Centre Registration and Certification Procedure" | ||
| RP | The legal organisation responsible for any matter that concerns the respective Resource Infrastructure. It provides, manages and operates (directly or indirectly) all the operational services required to an agreed level of quality as required by the Resource Centres and their user community. It holds the responsibility of integrating these operational services into EGI in order to enable uniform resource access and sharing for the benefit of their users. The Resource Infrastructure Provider liaises locally with the Resource Centre Operations Managers, and represents the Resource Centres at an international level. Examples of a Resource Infrastructure Provider are the European Intergovernmental Research Institutes (EIRO) and the National Grid Initiatives (NGIs) | |
| VRC | A group of large-scale research collaborations, or a number of separate VOs grouped according to research domain or computational technique. The group shares information and experience in achieveing their goals through the usage of an e-Infrastructure (e.g., best practies, applications, training material). The group also interact with e-infrastructure providers through defined points of contact. | |
| VO |
A group of people (e.g. scientists, researchers) with common interests and requirements, who need to work collaboratively and/or share resources (e.g. data, software, expertise, CPU, storage space) regardless of geographical location. They join a VO in order to access resources to meet these needs, after agreeing to a set of rules and policies that govern their access and security rights (to users, resources and data) | |
| UMD | The integrated set of software components contributed by technology providers and packaged for deployment as production-quality services in EGI. | |
|
The ability of an IT Service to carry out an activity. A capability may be 1) functional if providing an Activity for the direct benefit of the User; 2) operational if providing an Activity for supporting the Operations of an IT Infrastructure; 3) security if related to security aspects. A Capability may depend on others Capabilities. A Capability is defined and delivered by one or more Interfaces supported by one or more technology providers | ||
| See <meta charset="utf-8"></meta>Capability | ||
| An IT Capability defined in the UMD Roadmap. | ||
| NGI | ||
| EIRO | European Intergovernmental scientific Research Organisation that have extensive expertise in the areas of basic research and the management of large, international infrastructures, facilities and research programmes. | |
| 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. | ||
| 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. | ||
| 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. | ||
| 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. | ||
| 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.) | ||
| Step by step written and approved specification of how to complete a specific task or process. | ||
| Clear, formal and mandatory statement and position of general nature adopted by the IT Infrastructure governance bodies. | ||
| SLA | An Agreement between an IT Service Provider and a Customer. THe SLA describes the IT Service, documents Service Level Targets and specifies the responsibilities of the IT Service Provider and the Customer. A single SLA may cover multiple IT Services or multiple Customers. | |
| OLA | An Agreement between an IT Service Provider and another part of the same Organization. An OLA supports the IT Service Provider’s delivery of IT Services to Customers. The OLA defines the goods or Services to be provided and the responsibilities of both parties. | |
| MoU | An agreement that clarifies the relationships, responsibilities and communication channels between two or more parties that may share services, clients, and resources. The MoU is used when both parties do not want to pursue a contract that is legally binding (generally). Formal contracts can be intimidating therefore MoUs are the better option for some communities. However, it can also be used to regulate the relationship between parties. |
