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 "GCG:Glossary Draft"
Jump to navigation
Jump to search
| Line 23: | Line 23: | ||
|An entity that stores both local and non-local accounting data | |An entity that stores both local and non-local accounting data | ||
| | | | ||
| | |Draft | ||
|- | |- | ||
|SPG | |SPG | ||
| Line 30: | Line 30: | ||
|An individual entry in an accounting database relating to one Grid job | |An individual entry in an accounting database relating to one Grid job | ||
| | | | ||
| | |Draft | ||
|- | |- | ||
|SPG | |SPG | ||
| Line 37: | Line 37: | ||
|A Web User who does not provide unique credentials to the Portal when invoking functionality | |A Web User who does not provide unique credentials to the Portal when invoking functionality | ||
| | | | ||
| | |Draft | ||
|- | |- | ||
|SPG | |SPG | ||
| Line 44: | Line 44: | ||
|A community of users connected by a shared discipline or project | |A community of users connected by a shared discipline or project | ||
| | | | ||
| | |Draft | ||
|- | |- | ||
|SPG | |SPG | ||
| Line 51: | Line 51: | ||
|A Certification Authority accredited by the IGTF according to the "Classic" Authentication Profile (URL) | |A Certification Authority accredited by the IGTF according to the "Classic" Authentication Profile (URL) | ||
| | | | ||
| | |Draft | ||
|- | |- | ||
|SPG | |SPG | ||
| Line 58: | Line 58: | ||
|The privacy aspects of any data relating to personal information | |The privacy aspects of any data relating to personal information | ||
| | | | ||
| | |Draft | ||
|- | |- | ||
|SPG | |SPG | ||
| Line 65: | Line 65: | ||
|The name of the subject to which a public key is bound in a certificate | |The name of the subject to which a public key is bound in a certificate | ||
| | | | ||
| | |Draft | ||
|- | |- | ||
|SPG | |SPG | ||
| Line 72: | Line 72: | ||
|Any project or operational infrastructure which uses grid technologies and decides to adopt a policy to which this glossary pertains | |Any project or operational infrastructure which uses grid technologies and decides to adopt a policy to which this glossary pertains | ||
| | | | ||
| | |Draft | ||
|- | |- | ||
|SPG | |SPG | ||
| Line 79: | Line 79: | ||
|The AUP applying to all Grid users, not to be confused with the VO AUP | |The AUP applying to all Grid users, not to be confused with the VO AUP | ||
| | | | ||
| | |Draft | ||
|- | |- | ||
|SPG | |SPG | ||
| Line 86: | Line 86: | ||
|An entity responsible for Grid operations | |An entity responsible for Grid operations | ||
| | | | ||
| | |Draft | ||
|- | |- | ||
|SPG | |SPG | ||
| Line 93: | Line 93: | ||
|A service containing information about Grid resources | |A service containing information about Grid resources | ||
| | | | ||
| | |Draft | ||
|- | |- | ||
|SPG | |SPG | ||
| Line 100: | Line 100: | ||
|A named individual responsible for operational security of the Grid | |A named individual responsible for operational security of the Grid | ||
| | | | ||
| | |Draft | ||
|- | |- | ||
|SPG | |SPG | ||
| Line 107: | Line 107: | ||
|The team providing the operational security capability for the Grid | |The team providing the operational security capability for the Grid | ||
| | | | ||
| | |Draft | ||
|- | |- | ||
|SPG | |SPG | ||
| Line 114: | Line 114: | ||
|A Web User that provides authenticated personal identification to the Portal when invoking functionality, but whose credentials and way of authentication are not necessarily compatible or equivalent with Grid authentication. | |A Web User that provides authenticated personal identification to the Portal when invoking functionality, but whose credentials and way of authentication are not necessarily compatible or equivalent with Grid authentication. | ||
| | | | ||
| | |Draft | ||
|- | |- | ||
|SPG | |SPG | ||
| Line 121: | Line 121: | ||
|The process of responding to a security incident | |The process of responding to a security incident | ||
| | | | ||
| | |Draft | ||
|- | |- | ||
|SPG | |SPG | ||
| Line 128: | Line 128: | ||
|The organisation responsible for the coordination of the Grid trust fabric (URL). | |The organisation responsible for the coordination of the Grid trust fabric (URL). | ||
| | | | ||
| | |Draft | ||
|- | |- | ||
|SPG | |SPG | ||
| Line 135: | Line 135: | ||
|A Certification Authority accredited by the IGTF according to the Member Integrated Credential Services Authentication Profile (URL) | |A Certification Authority accredited by the IGTF according to the Member Integrated Credential Services Authentication Profile (URL) | ||
| | | | ||
| | |Draft | ||
|- | |- | ||
|SPG | |SPG | ||
| Line 142: | Line 142: | ||
|A pilot job which pulls down workload belonging to a different user than the owner of the pilot job | |A pilot job which pulls down workload belonging to a different user than the owner of the pilot job | ||
| | | | ||
| | |Draft | ||
|- | |- | ||
|SPG | |SPG | ||
| Line 149: | Line 149: | ||
|A place-holder Grid job which pulls down the real workload at execution time | |A place-holder Grid job which pulls down the real workload at execution time | ||
| | | | ||
| | |Draft | ||
|- | |- | ||
|SPG | |SPG | ||
| Line 156: | Line 156: | ||
|A web site or web-based service that provides functionality to Web Users via web-specific applications | |A web site or web-based service that provides functionality to Web Users via web-specific applications | ||
| | | | ||
| | |Draft | ||
|- | |- | ||
|SPG | |SPG | ||
| Line 163: | Line 163: | ||
|A verifiably-human Web User that provides authenticated non-identifying information to the Portal when invoking functionality. | |A verifiably-human Web User that provides authenticated non-identifying information to the Portal when invoking functionality. | ||
| | | | ||
| | |Draft | ||
|- | |- | ||
|SPG | |SPG | ||
| Line 170: | Line 170: | ||
|An individual responsible for collecting and maintaining information about a person registering as a Grid user | |An individual responsible for collecting and maintaining information about a person registering as a Grid user | ||
| | | | ||
| | |Draft | ||
|- | |- | ||
|SPG | |SPG | ||
| Line 177: | Line 177: | ||
|The equipment and software required to run a service on the Grid, and any data held on the service | |The equipment and software required to run a service on the Grid, and any data held on the service | ||
| | | | ||
| | |Draft | ||
|- | |- | ||
|SPG | |SPG | ||
| Line 184: | Line 184: | ||
|The person responsible for installing, operating, maintaining and supporting one or more resource(s) at a site | |The person responsible for installing, operating, maintaining and supporting one or more resource(s) at a site | ||
| | | | ||
| | |Draft | ||
|- | |- | ||
|SPG | |SPG | ||
| Line 191: | Line 191: | ||
|A software agent that performs automatic functions | |A software agent that performs automatic functions | ||
| | | | ||
| | |Draft | ||
|- | |- | ||
|SPG | |SPG | ||
| Line 198: | Line 198: | ||
|The actual or suspected violation of an explicit or implied security policy | |The actual or suspected violation of an explicit or implied security policy | ||
| | | | ||
| | |Draft | ||
|- | |- | ||
|SPG | |SPG | ||
| Line 205: | Line 205: | ||
|Any computing or software system, based on grid technologies, which provides access to, information about or controls resources | |Any computing or software system, based on grid technologies, which provides access to, information about or controls resources | ||
| | | | ||
| | |Draft | ||
|- | |- | ||
|SPG | |SPG | ||
| Line 212: | Line 212: | ||
|An entity having administrative control of resources provided to the Grid. This may be at one physical location or spread across multiple physical locations | |An entity having administrative control of resources provided to the Grid. This may be at one physical location or spread across multiple physical locations | ||
| | | | ||
| | |Draft | ||
|- | |- | ||
|SPG | |SPG | ||
| Line 219: | Line 219: | ||
|An individual responsible for Grid operations at a Site | |An individual responsible for Grid operations at a Site | ||
| | | | ||
| | |Draft | ||
|- | |- | ||
|SPG | |SPG | ||
| Line 226: | Line 226: | ||
|A Certification Authority accredited by the IGTF according to the Short Lived Credential Services Authentication Profile (URL) | |A Certification Authority accredited by the IGTF according to the Short Lived Credential Services Authentication Profile (URL) | ||
| | | | ||
| | |Draft | ||
|- | |- | ||
|SPG | |SPG | ||
| Line 233: | Line 233: | ||
|A Grid User that provides authenticated identification to the Portal when invoking functionality, that allows the portal to authenticate to the Grid Resources with valid Grid credentials specific to the Grid User. | |A Grid User that provides authenticated identification to the Portal when invoking functionality, that allows the portal to authenticate to the Grid Resources with valid Grid credentials specific to the Grid User. | ||
| | | | ||
| | |Draft | ||
|- | |- | ||
|SPG | |SPG | ||
| Line 240: | Line 240: | ||
|An individual who has been given authority to access and use Grid resources | |An individual who has been given authority to access and use Grid resources | ||
| | | | ||
| | |Draft | ||
|- | |- | ||
|SPG | |SPG | ||
| Line 247: | Line 247: | ||
|A grouping of users and optionally resources, often not bound to a single institution, who, by reason of their common membership and in sharing a common goal, are given authority to use a set of resources | |A grouping of users and optionally resources, often not bound to a single institution, who, by reason of their common membership and in sharing a common goal, are given authority to use a set of resources | ||
| | | | ||
| | |Draft | ||
|- | |- | ||
|SPG | |SPG | ||
| Line 254: | Line 254: | ||
|The policy document describing the goals of the VO thereby defining the expected and acceptable use of the Grid by the users of the VO | |The policy document describing the goals of the VO thereby defining the expected and acceptable use of the Grid by the users of the VO | ||
| | | | ||
| | |Draft | ||
|- | |- | ||
|SPG | |SPG | ||
| Line 261: | Line 261: | ||
|An individual responsible for the membership registry of the VO including its accuracy and integrity. | |An individual responsible for the membership registry of the VO including its accuracy and integrity. | ||
| | | | ||
| | |Draft | ||
|- | |- | ||
|SPG | |SPG | ||
| Line 268: | Line 268: | ||
|The operational interface to the VO membership registry | |The operational interface to the VO membership registry | ||
| | | | ||
| | |Draft | ||
|- | |- | ||
|SPG | |SPG | ||
| Line 275: | Line 275: | ||
|A named individual within a VO with authority to inspect resource usage at the individual VO user level | |A named individual within a VO with authority to inspect resource usage at the individual VO user level | ||
| | | | ||
| | |Draft | ||
|- | |- | ||
|SPG | |SPG | ||
| Line 282: | Line 282: | ||
|A human individual that accesses Grid resources through a Portal | |A human individual that accesses Grid resources through a Portal | ||
| | | | ||
| | |Draft | ||
|- | |- | ||
|TCB | |TCB | ||
| Line 289: | Line 289: | ||
|A Capability is scoped around well known and well-defined activities that are sufficiently disparate, independent, and fulfill 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. | |A Capability is scoped around well known and well-defined activities that are sufficiently disparate, independent, and fulfill 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. | ||
| | | | ||
| | |Draft | ||
|- | |- | ||
|TCB | |TCB | ||
| Line 296: | Line 296: | ||
|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. | |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. | ||
| | | | ||
| | |Draft | ||
|- | |- | ||
|TCB | |TCB | ||
| Line 303: | Line 303: | ||
|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. | |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. | ||
| | | | ||
| | |Draft | ||
|- | |- | ||
|TCB | |TCB | ||
| Line 310: | Line 310: | ||
|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. | |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. | ||
| | | | ||
| | |Draft | ||
|- | |- | ||
|TCB | |TCB | ||
| Line 317: | Line 317: | ||
|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 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. | ||
| | | | ||
| | |Draft | ||
|- | |- | ||
|TCB | |TCB | ||
| Line 324: | Line 324: | ||
|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.) | |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.) | ||
| | | | ||
| | |Draft | ||
|} | |} | ||
Revision as of 15:44, 25 February 2011
Status: Draft, Review and Approved
| From | Term | Abbr. | Definition | Notes | Status |
|---|---|---|---|---|---|
| SPG | Acceptable Use Policy | AUP | A policy describing the terms and conditions applicable to use of the Grid. | ||
| SPG | Accounting Data Centre | ADC | An entity that stores both local and non-local accounting data | Draft | |
| SPG | Accounting record | An individual entry in an accounting database relating to one Grid job | Draft | ||
| SPG | Anonymous web user | A Web User who does not provide unique credentials to the Portal when invoking functionality | Draft | ||
| SPG | Application Community | A community of users connected by a shared discipline or project | Draft | ||
| SPG | Classic CA | A Certification Authority accredited by the IGTF according to the "Classic" Authentication Profile (URL) | Draft | ||
| SPG | Data Privacy | The privacy aspects of any data relating to personal information | Draft | ||
| SPG | Distinguished Name | DN | The name of the subject to which a public key is bound in a certificate | Draft | |
| SPG | Grid | Any project or operational infrastructure which uses grid technologies and decides to adopt a policy to which this glossary pertains | Draft | ||
| SPG | Grid AUP | The AUP applying to all Grid users, not to be confused with the VO AUP | Draft | ||
| SPG | Grid Deployment Team | An entity responsible for Grid operations | Draft | ||
| SPG | Grid resource information system | A service containing information about Grid resources | Draft | ||
| SPG | Grid Security Officer | A named individual responsible for operational security of the Grid | Draft | ||
| SPG | Grid Security Operations | The team providing the operational security capability for the Grid | Draft | ||
| SPG | Identified web user | A Web User that provides authenticated personal identification to the Portal when invoking functionality, but whose credentials and way of authentication are not necessarily compatible or equivalent with Grid authentication. | Draft | ||
| SPG | Incident response | The process of responding to a security incident | Draft | ||
| SPG | International Grid Trust Federation | IGTF | The organisation responsible for the coordination of the Grid trust fabric (URL). | Draft | |
| SPG | MICS CA | A Certification Authority accredited by the IGTF according to the Member Integrated Credential Services Authentication Profile (URL) | Draft | ||
| SPG | Multi User Pilot Job | MUPJ | A pilot job which pulls down workload belonging to a different user than the owner of the pilot job | Draft | |
| SPG | Pilot Job | A place-holder Grid job which pulls down the real workload at execution time | Draft | ||
| SPG | Portal | A web site or web-based service that provides functionality to Web Users via web-specific applications | Draft | ||
| SPG | Pseudonymous web user | A verifiably-human Web User that provides authenticated non-identifying information to the Portal when invoking functionality. | Draft | ||
| SPG | Registrar | An individual responsible for collecting and maintaining information about a person registering as a Grid user | Draft | ||
| SPG | Resource | The equipment and software required to run a service on the Grid, and any data held on the service | Draft | ||
| SPG | Resource Administrator | The person responsible for installing, operating, maintaining and supporting one or more resource(s) at a site | Draft | ||
| SPG | Robot | A software agent that performs automatic functions | Draft | ||
| SPG | Security Incident | The actual or suspected violation of an explicit or implied security policy | Draft | ||
| SPG | Service | Any computing or software system, based on grid technologies, which provides access to, information about or controls resources | Draft | ||
| SPG | Site | An entity having administrative control of resources provided to the Grid. This may be at one physical location or spread across multiple physical locations | Draft | ||
| SPG | Site Manager | An individual responsible for Grid operations at a Site | Draft | ||
| SPG | SLCS CA | A Certification Authority accredited by the IGTF according to the Short Lived Credential Services Authentication Profile (URL) | Draft | ||
| SPG | Strongly identified web user | A Grid User that provides authenticated identification to the Portal when invoking functionality, that allows the portal to authenticate to the Grid Resources with valid Grid credentials specific to the Grid User. | Draft | ||
| SPG | User | An individual who has been given authority to access and use Grid resources | Draft | ||
| SPG | Virtual Organisation | A grouping of users and optionally resources, often not bound to a single institution, who, by reason of their common membership and in sharing a common goal, are given authority to use a set of resources | Draft | ||
| SPG | VO AUP | The policy document describing the goals of the VO thereby defining the expected and acceptable use of the Grid by the users of the VO | Draft | ||
| SPG | VO Manager | An individual responsible for the membership registry of the VO including its accuracy and integrity. | Draft | ||
| SPG | VO Membership Service | The operational interface to the VO membership registry | Draft | ||
| SPG | VO Resource Manager | A named individual within a VO with authority to inspect resource usage at the individual VO user level | Draft | ||
| SPG | Web user | A human individual that accesses Grid resources through a Portal | Draft | ||
| TCB | (UMD) Capability | A Capability is scoped around well known and well-defined activities that are sufficiently disparate, independent, and fulfill 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. | Draft | ||
| TCB | Appliance | 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. | Draft | ||
| TCB | Package | 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. | Draft | ||
| TCB | Product | 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. | Draft | ||
| TCB | Primary Package | 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. | Draft | ||
| TCB | Secondary Package | 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.) | Draft |