hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
64de3eb8c583b99a379b2b2ae4727979 | 102 874-6 | 4.3.3 Hold-up Time | The hold-up time shall be a minimum of 10 ms at maximum load and both 110 Vac/60 Hz and 220 Vac/50 Hz. The measurement shall be made following AC voltage interrupt from the moment at which the input current ceases, to the moment the output voltage drops below the rated voltage minus 5 %. |
64de3eb8c583b99a379b2b2ae4727979 | 102 874-6 | 4.3.4 Brown-out and recovery | Figure 2: Input voltage brown-out and recovery CPS must have clean ON/OFF and OFF/ON transition, maintaining the compliance to specification and without any permanent damage after the application of different voltages as described in figure 2. Input voltage will be reduced from 90 V to 0 Vac in 30 s, then immediately i... |
64de3eb8c583b99a379b2b2ae4727979 | 102 874-6 | 4.3.5 Dynamic Load | The CPS must be capable of a higher output current than the rated output current during a time interval as given below: • High Load: 250 %/30 ms of the rated load. • Low Load: 100 %/1 s of the rated load. • Slew Rate: 0,1 A/μs. time - s Vac 90 or 200 0 0 40 30 70 ETSI ETSI TS 102 874-6 V1.1.1 (2012-02) 15 |
64de3eb8c583b99a379b2b2ae4727979 | 102 874-6 | 4.3.6 Max Open Circuit Voltage | When the circuit of over voltage protection is invalidated, the output voltage must be 16 V maximum. |
64de3eb8c583b99a379b2b2ae4727979 | 102 874-6 | 4.3.7 Overshoot at turn on/Turn off | The overshoot at turn on and turn off shall not exceed 10 % of the nominal voltage value. |
64de3eb8c583b99a379b2b2ae4727979 | 102 874-6 | 4.3.8 Output transient response/Transient load slew | With an input voltage, output load, ambient temperature and slew rate as given below, the undershoot or overshoot of output shall be not less than 5 % of the output voltage. • Input voltage: 90 V ~ 264 Vac/47 ~ 63Hz. • Output Load: 20 % to 80 %, 80 % to 20 %. • Ambient temperature: 25 ºC ± 3 ºC. • Slew rate: 1,0 A/μs. ... |
64de3eb8c583b99a379b2b2ae4727979 | 102 874-6 | 4.3.9 Rise time | Rise time shall be less than 50 ms when measured from 10 % to 90 % of the output voltage at normal input voltage. 5 Operational, Storage and Transportation Requirements |
64de3eb8c583b99a379b2b2ae4727979 | 102 874-6 | 5.1 Temperature And Humidity | The CPS shall be able to operate in the following environmental conditions: • Temperature: 5 °C to +40 °C. • Relative humidity: 5 % to 95 %. This corresponds to Class 3.1 "Temperature-controlled locations" of EN 300 019-1-3 [16]. The CPS shall be withstand the storage conditions defined in EN 300 019-1-1 [15].and relat... |
64de3eb8c583b99a379b2b2ae4727979 | 102 874-6 | 6 EMC, safety and Environmental requirements | |
64de3eb8c583b99a379b2b2ae4727979 | 102 874-6 | 6.1 Product EMC | As this CPS is intended to be used for Information Technology Equipment (ITE), they should be tested with the associated telecommunication equipment according to the following EMC standards for ITEs: • CISPR 22 [3], or EN 55022 [2], for the emission requirements. ETSI ETSI TS 102 874-6 V1.1.1 (2012-02) 16 • CISPR 24 [2... |
64de3eb8c583b99a379b2b2ae4727979 | 102 874-6 | 6.1.1 Electrostatic Discharge (ESD) | The CPS shall meet EN 61000-4-2 [5]: ±15 kV Air Discharge, ±8 kV contact discharge. |
64de3eb8c583b99a379b2b2ae4727979 | 102 874-6 | 6.1.2 Harmonic Current | The CPS shall meet the requirements of EN 61000-3-2 [4]. |
64de3eb8c583b99a379b2b2ae4727979 | 102 874-6 | 6.1.3 Voltage fluctuations and flicker | The CPS shall meet the requirements of EN 61000-3-3 [24]. |
64de3eb8c583b99a379b2b2ae4727979 | 102 874-6 | 6.2 Product Safety | The power supply must meet the requirements of IEC 60950-1 [29] or EN 60950-1 [10]. |
64de3eb8c583b99a379b2b2ae4727979 | 102 874-6 | 6.3 Environmental and Eco-Design Requirements | The following Ecodesign rules must be applied when manufacturing the CPS: • The external case of the CPS shall be manufactured using recyclable plastic. • The external case of the CPS should be manufactured using at least 50 % recycled plastic (preferred choice: ABS). The cables of the CPS should be manufactured using ... |
64de3eb8c583b99a379b2b2ae4727979 | 102 874-6 | 7 Reliability | |
64de3eb8c583b99a379b2b2ae4727979 | 102 874-6 | 7.1 Burn-in | All power supplies shall be burned-in for 2 hours under nominal input and 70 % ~ 80 % load at an ambient temperature of 40 ºC. |
64de3eb8c583b99a379b2b2ae4727979 | 102 874-6 | 7.2 MTBF Calculation | The MTBF, Mean-Time-Between-Failures, shall be calculated and reported for each quality class offered. The provisional model adopted is referring to the "bathtub curve" defining the behaviour of the failure rate as function of the time. While in the first part of the useful life the failure rate is higher, then it decr... |
64de3eb8c583b99a379b2b2ae4727979 | 102 874-6 | 8 Mechanical Specification | |
64de3eb8c583b99a379b2b2ae4727979 | 102 874-6 | 8.1 AC plug | The 230 Vac plug must form part of the main housing of the CPS or be part of a fixed cord of the main housing of the CPS. The AC plug of the CPS shall comply with EN 50075 [11], but without the cord. |
64de3eb8c583b99a379b2b2ae4727979 | 102 874-6 | 8.2 DC cord | The DC cord must comply with the data below with typical cord length of 2 meters. NOTE 1: Cable: UL 2 468 style: 80 ºC, 300 V, 2 conductors. NOTE 2: Plug: Ø 1,98 x 6,00 x 9,5 mm (tuning fork cannelure entire insulation) black. Figure 3: DC cord |
64de3eb8c583b99a379b2b2ae4727979 | 102 874-6 | 8.3 Label specification | The CPS shall be affixed with a label, with appropriate wording in the language specific for the intended country for deployment, stating the CPS compliance with the appropriate European regulations. ETSI ETSI TS 102 874-6 V1.1.1 (2012-02) 18 Annex A (informative): Details on Tests Procedures This annex is containing n... |
1665137ae8d16f79f9104f7f927dc5f0 | 102 868-3 | 1 Scope | The present document contains the Abstract Test Suite (ATS) for Cooperative Awareness Basic Service (CA) as defined in ETSI TS 103 900 [1] in compliance with the relevant requirements and in accordance with the relevant guidance given in ISO/IEC 9646-7 [i.7]. The objective of the present document is to provide a basis ... |
1665137ae8d16f79f9104f7f927dc5f0 | 102 868-3 | 2 References | |
1665137ae8d16f79f9104f7f927dc5f0 | 102 868-3 | 2.1 Normative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. Referenced documents which a... |
1665137ae8d16f79f9104f7f927dc5f0 | 102 868-3 | 2.2 Informative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. NOTE: While any hyperlinks i... |
1665137ae8d16f79f9104f7f927dc5f0 | 102 868-3 | 3 Definition of terms, symbols and abbreviations | |
1665137ae8d16f79f9104f7f927dc5f0 | 102 868-3 | 3.1 Terms | For the purposes of the present document, the terms given in ETSI TS 103 900 [1], ISO/IEC 9646-1 [i.4] and ISO/IEC 9646-7 [i.7] apply. |
1665137ae8d16f79f9104f7f927dc5f0 | 102 868-3 | 3.2 Symbols | Void. |
1665137ae8d16f79f9104f7f927dc5f0 | 102 868-3 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: ASN.1 Abstract Syntax Notation One ATM Abstract Test Method ATS Abstract Test Suite BTP Basic Transport Protocol BV Valid test events for Behaviour tests CA Cooperative Awareness Basic Service CAM Cooperative Awareness Messages CRS Crash Statu... |
1665137ae8d16f79f9104f7f927dc5f0 | 102 868-3 | 4 Abstract Test Method (ATM) | |
1665137ae8d16f79f9104f7f927dc5f0 | 102 868-3 | 4.1 Abstract protocol tester | The abstract protocol tester used by this test suite is described in figure 1. The test system will simulate valid and invalid protocol behaviour, and will analyse the reaction of the IUT. Figure 1: Abstract protocol tester - CA |
1665137ae8d16f79f9104f7f927dc5f0 | 102 868-3 | 4.2 Test Configuration | This test suite uses a unique test configuration in order to cover the different test scenarios. In this configuration, the tester simulates one ITS station implementing the CAM protocol. Test System SUT ITS-G5/ LTE V2X IUT CAM ITS-G5/ LTE V2X Lower tester PDUs Upper Tester GeoN GeoN BTP BTP ETSI ETSI TS 102 868-3 V2.1... |
1665137ae8d16f79f9104f7f927dc5f0 | 102 868-3 | 4.3 Test architecture | The present document implements the general TTCN-3 test architecture described in ETSI EG 202 798 [i.1], clauses 6.3.2 and 8.3.1. Figure 2 shows the test architecture used for the CA ATS. The CA test component requires using only the Main Test Component (MTC). The MTC communicates with the CA SUT over the camPort. The ... |
1665137ae8d16f79f9104f7f927dc5f0 | 102 868-3 | 4.4 Ports and ASPs (Abstract Services Primitives) | |
1665137ae8d16f79f9104f7f927dc5f0 | 102 868-3 | 4.4.1 Introduction | Two ports are used by the CA ATS: • The camPort, of type CamPort. • The utPort, of type UpperTesterPort. ETSI ETSI TS 102 868-3 V2.1.1 (2025-07) 10 |
1665137ae8d16f79f9104f7f927dc5f0 | 102 868-3 | 4.4.2 Primitives of the camPort | Two types of primitives are used in the camPort: • The CamInd primitive used to receive messages of type CamPdu. • The CamReq primitive used to send messages of type CamPdu. These two primitives use the CamPdu type, which is declared in the CAM.asn ASN.1 module, following the ASN.1 definition from ETSI TS 103 900 [1]. ... |
1665137ae8d16f79f9104f7f927dc5f0 | 102 868-3 | 4.4.3 Primitives of the utPort | This port uses two types of primitives: • The UtInitialize primitive used to initialize IUT. • The UtTrigger primitive used trigger upper layer events in IUT. |
1665137ae8d16f79f9104f7f927dc5f0 | 102 868-3 | 4.5 Executing CA tests in secured mode | All the CA tests, with the exception of the SSP tests, can be executed with security enabled or with security disabled. The choice of running the CA tests in secured or non-secured mode has no impact on the result of the CA tests because the test verdicts assess CA protocol behaviour only. The SSP tests can only be exe... |
1665137ae8d16f79f9104f7f927dc5f0 | 102 868-3 | 4.6 ETSI test adapter | All information of the ETSI test adapter is described in ETSI TR 103 099 [i.3]. ETSI ETSI TS 102 868-3 V2.1.1 (2025-07) 11 |
1665137ae8d16f79f9104f7f927dc5f0 | 102 868-3 | 5 Untestable Test Purposes | Table 1 gives a list of TPs, which are not implemented in the ATS due to the chosen ATM or other restrictions. Table 1: Untestable TPs Test purpose Reason None |
1665137ae8d16f79f9104f7f927dc5f0 | 102 868-3 | 6 ATS conventions | |
1665137ae8d16f79f9104f7f927dc5f0 | 102 868-3 | 6.1 Introduction | The ATS conventions are intended to give a better understanding of the ATS but they also describe the conventions made for the development of the ATS. These conventions shall be considered during any later maintenance or further development of the ATS. The ATS conventions contain two clauses, the testing conventions an... |
1665137ae8d16f79f9104f7f927dc5f0 | 102 868-3 | 6.2 Testing conventions | |
1665137ae8d16f79f9104f7f927dc5f0 | 102 868-3 | 6.2.1 Testing states | |
1665137ae8d16f79f9104f7f927dc5f0 | 102 868-3 | 6.2.1.1 Initial state | All test cases start with the function f_prInitialState. This function brings the IUT in an "initialized" state by invoking the upper tester primitive UtInitialize. |
1665137ae8d16f79f9104f7f927dc5f0 | 102 868-3 | 6.2.1.2 Final state | All test cases end with the function f_poDefault. This function brings the IUT back in an "idle" state. As no specific actions are required for the idle state in ETSI TS 103 900 [1], the function f_ poDefault does not invoke any action. As necessary, further actions may be included in the f_poDefault function. |
1665137ae8d16f79f9104f7f927dc5f0 | 102 868-3 | 6.2.2 Message types - ASN.1 definitions | ASN.1 definitions from ETSI TS 103 900 [1] are directly imported in TTCN-3 using the ASN.1 import method specified in ETSI ES 201 873-7 [i.10]. The following example shows the TTCN-3 import statement used to import ASN.1 definitions in the TTCN-3 modules: import from CAM_PDU_Descriptions language "ASN.1:1997" all; ETSI... |
1665137ae8d16f79f9104f7f927dc5f0 | 102 868-3 | 6.3 Naming conventions | |
1665137ae8d16f79f9104f7f927dc5f0 | 102 868-3 | 6.3.1 Introduction | This test suite follows the naming convention guidelines provided in the ETSI EG 202 798 [i.1]. |
1665137ae8d16f79f9104f7f927dc5f0 | 102 868-3 | 6.3.2 General guidelines | The naming convention is based on the following underlying principles: • in most cases, identifiers should be prefixed with a short alphabetic string (specified in table 2) indicating the type of TTCN-3 element it represents; • suffixes should not be used except in those specific cases identified in table 2; • prefixes... |
1665137ae8d16f79f9104f7f927dc5f0 | 102 868-3 | 6.3.3 ITS specific TTCN-3 naming conventions | Next to such general naming conventions, table 3 shows specific naming conventions that apply to the ITS TTCN-3 test suite. Table 3: ITS specific TTCN-3 naming conventions Language element Naming convention Prefix Example identifier ITS Module Use upper-case initial letter Its"IUTname"_ ItsCam_ Module containing types ... |
1665137ae8d16f79f9104f7f927dc5f0 | 102 868-3 | 6.3.4 Usage of Log statements | All TTCN-3 log statements use the following format using the same order: • Three asterisks. • The TTCN-3 test case or function identifier in which the log statement is defined. • One of the categories of log: INFO, WARNING, ERROR, PASS, FAIL, INCONC, TIMEOUT. • Free text. • three asterisks. EXAMPLE 1: log("*** TC_CAM_M... |
1665137ae8d16f79f9104f7f927dc5f0 | 102 868-3 | 6.3.5 Test Case (TC) identifier | Table 4 shows the test case naming convention, which follows the same naming convention as the test purposes. Table 4: TC naming convention Identifier TC_<root>_<gr>_<sgr>_<x>_<nn> or TP_<root>_<gr>_<x>_<nn> when no <sgr> Abbreviation Description <root> = root CAM <gr> = group MSD Message Dissemination MSP Message Proc... |
1ae034a75bbe7d46c2fae998c5f3b869 | 102 827 | 1 Scope | The present document describes an XML schema for describing resources to be used in distributed and parallel infrastructures like enterprise and scientific grids and job schedulers. The standard will help enterprises and laboratories to manage large-scale computer and telecom infrastructures with the necessary virtuali... |
1ae034a75bbe7d46c2fae998c5f3b869 | 102 827 | 2 References | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. • For a specific reference, subsequent revisions do not apply. • Non-specific reference may be made only to a complete document or a part thereof and only in the following cases: - if it is accept... |
1ae034a75bbe7d46c2fae998c5f3b869 | 102 827 | 2.1 Normative references | The following referenced documents are indispensable for the application of the present document. For dated references, only the edition cited applies. For non-specific references, the latest edition of the referenced document (including any amendments) applies. [1] ETSI TS 102 828: "GRID; Grid Component Model (GCM); G... |
1ae034a75bbe7d46c2fae998c5f3b869 | 102 827 | 2.2 Informative references | The following referenced documents are not essential to the use of the present document but they assist the user with regard to a particular subject area. For non-specific references, the latest version of the referenced document (including any amendments) applies. [i.1] ARC / Nordugrid: "middleware for grid computing"... |
1ae034a75bbe7d46c2fae998c5f3b869 | 102 827 | 3 Definitions and abbreviations | |
1ae034a75bbe7d46c2fae998c5f3b869 | 102 827 | 3.1 Definitions | For the purposes of the present document, the following terms and definitions apply: bridge: GCM Deployment concept that represents a machine through which multiple machines are accessed NOTE: A typical example is a cluster frontend (see frontend). certificate: electronic document which incorporates a digital signature... |
1ae034a75bbe7d46c2fae998c5f3b869 | 102 827 | 3.2 Abbreviations | For the purposes of the present document, the following abbreviations apply: CA Certification Authority CPU Central Processing Unit GCM Grid Component Model HC Host Capacity JVM Java Virtual Machine OS Operating System RSH Remote Shell SOA Service Oriented Architecture SSH Secure Shell VM Virtual Machine VMC Virtual Ma... |
1ae034a75bbe7d46c2fae998c5f3b869 | 102 827 | 4 Overall resource specification | The purpose of the following clauses is to explain the "model toolkit" that the GCM Deployment offers to describe a grid. As explained in the introduction, a grid can be almost any kind of machines networked together. We detail here how to represent any given setup through the GCM Deployment standard. |
1ae034a75bbe7d46c2fae998c5f3b869 | 102 827 | 4.1 Principles | A deployment descriptor is written in XML. The XML document must conform to the GCM Deployment schema (specified in the present document). A deployment descriptor is meant to be referenced by an application descriptor, which is the description of the application that will be run, and its resource requirements (GCM Appl... |
1ae034a75bbe7d46c2fae998c5f3b869 | 102 827 | 4.2 Overall structure of a descriptor | A deployment descriptor has the following XML structure: <environment> <descriptorVariable …/> … </environment> <resources> <bridge …/> <group> <host …/> <host …/> … </group> ETSI ETSI TS 102 827 V1.1.1 (2008-08) 12 … </resources> <acquisition> <lookup …/> <p2p …/> … </acquisition> <infrastructure> <hosts> <host…/> </h... |
1ae034a75bbe7d46c2fae998c5f3b869 | 102 827 | 4.2.1 Environment element | To allow for a bit of flexibility, it is possible to define variables in a descriptor. The variables can be used in any XML value element. They cannot be used in an XML element name. The <environment> element is where the variables are defined. It is a simple list of <descriptorVariable> elements. There is no limitatio... |
1ae034a75bbe7d46c2fae998c5f3b869 | 102 827 | 4.2.2 Resources element | The <resource> element describes the hierarchical structure of the available grid resources. This can be seen as the topology of the grid: which hosts are part of a group, which group is behind a bridge, etc. All the grid resources which are listed in it are fully defined in the <infrastructure> element. However it doe... |
1ae034a75bbe7d46c2fae998c5f3b869 | 102 827 | 4.2.3 Acquisition element and desktop grid | The <acquisition> element describes how resources which are already running can be acquired. It can be used or extended towards standards for managing resources from desktop grids. It contains a simple sequence of two types of elements: <lookup> and <p2p>, in this order. Each element can either have a single occurrence... |
1ae034a75bbe7d46c2fae998c5f3b869 | 102 827 | 4.2.4 Infrastructure element | The <infrastructure> tag holds the list of grid resources on which the deployment can take place, in no particular order. Its purpose is to describe how these resources are deployed (i.e. through which protocols). It can have a single child element of each of the following types: <hosts>, <bridges>, <groups>. <bridges>... |
1ae034a75bbe7d46c2fae998c5f3b869 | 102 827 | 5 Infrastructure specification | |
1ae034a75bbe7d46c2fae998c5f3b869 | 102 827 | 5.1 Common types | The following data types are used by many different elements defining the various grid and job scheduler protocols. |
1ae034a75bbe7d46c2fae998c5f3b869 | 102 827 | 5.1.1 Host list | The format of a host list is a whitespace-separated list of name patterns or hostnames. A name pattern describes a set of hostnames with a common root. The format is as follows: <root name><interval> with root name being an alphanumeric string (only letters and digits, no spaces or punctuation signs), and interval defi... |
1ae034a75bbe7d46c2fae998c5f3b869 | 102 827 | 5.1.2 ID | An ID is an string of alphanumeric characters (no spaces nor punctuation signs). Each ID must be unique in the descriptor. |
1ae034a75bbe7d46c2fae998c5f3b869 | 102 827 | 5.1.3 Path element and path string | A path element has two attributes: 'base' and 'relpath'. 'base' defines what the path is relative to. The following values are defined: • root: the 'relpath' will be interpreted as an absolute path; • home: the home directory of the user under which the job is run. A path string is simply a text element which value rep... |
1ae034a75bbe7d46c2fae998c5f3b869 | 102 827 | 5.1.4 Argument list | An argument list is a simple list of <arg> elements, each holding a string value. |
1ae034a75bbe7d46c2fae998c5f3b869 | 102 827 | 5.2 Elements of the infrastructure | This clause presents the concepts within the <infrastructure> tag, which describes the actual deployment of resources on the grid infrastructure. Deployment is the process through which a machine becomes part of the grid (this generally involves starting the appropriate program on the machine). There are three types of... |
1ae034a75bbe7d46c2fae998c5f3b869 | 102 827 | 5.2.1 Host description | The HostInfo data structure describes a single machine and the environment it provides, with the following information: • userName: (string) the name of the user under which this host can be accessed; • homeDirectory: (absolute path) the home directory of the user; ETSI ETSI TS 102 827 V1.1.1 (2008-08) 16 • os: (one of... |
1ae034a75bbe7d46c2fae998c5f3b869 | 102 827 | 5.2.2 Bridge description | A bridge is meant to represent a frontend to a computing resource. Many grid architectures have such a feature: each physical machine is not accessible directly, the user must instead go through a single machine called a front-end. In a deployment descriptor, a bridge is a gateway toward either: • a host; • a set of gr... |
1ae034a75bbe7d46c2fae998c5f3b869 | 102 827 | 5.2.3 Group description | A Group is a data structure defining a set of machines with identical configuration (like a cluster). It is meant as a base structure which can be derived in an Object-Oriented manner to implement any kind of group. There currently are two kinds of groups: 1) "direct" groups; 2) job schedulers. It is therefore possible... |
1ae034a75bbe7d46c2fae998c5f3b869 | 102 827 | 6 Instances of bridge protocols (one to one) | A bridge starts from one machine to go to a single other machine. It can be used to contact a resource through an SSH gateway for example. |
1ae034a75bbe7d46c2fae998c5f3b869 | 102 827 | 6.1 rsh | An RSH bridge element can have the following attributes: • id (string): the id of the bridge connector corresponding to this definition; • hostname (string): the network hostname of the physical machine which acts as the bridge; • username (string, optional): the user name under which the machine can be accessed; • com... |
1ae034a75bbe7d46c2fae998c5f3b869 | 102 827 | 6.2 ssh | An SSH bridge element can have the following child element: • privateKey (path string): the file of the private ssh key needed to access the bridge. An SSH bridge element can have the following attributes: • id (string): the id of the bridge connector corresponding to this definition; • hostname (string): the network h... |
1ae034a75bbe7d46c2fae998c5f3b869 | 102 827 | 6.3 oarsh | An OARSH bridge element has the same parameters as an SSH bridge element, plus a 'jobId' (positive integer) mandatory attribute, which holds the OAR ID of the job. Figure 8 |
1ae034a75bbe7d46c2fae998c5f3b869 | 102 827 | 6.4 gsissh | A gsissh bridge element has the same parameters as an ssh bridge element, plus two optional attributes: a 'port' (positive integer) which holds the port used by the gsissh server and 'certificate' that indicate the path of a valid p12 certificate delivered by a Certification Authority (CA). By default, these values fol... |
1ae034a75bbe7d46c2fae998c5f3b869 | 102 827 | 7 Instances of group protocols (One to N) | In the following clauses, elements and attribute names which are underlined mean that the item is mandatory. |
1ae034a75bbe7d46c2fae998c5f3b869 | 102 827 | 7.1 Direct groups | The following groups are simply sets of machines with a common configuration. To make the distinction with job schedulers, they are named "direct groups", since the deployment process directly accesses the machines in the group. ETSI ETSI TS 102 827 V1.1.1 (2008-08) 20 |
1ae034a75bbe7d46c2fae998c5f3b869 | 102 827 | 7.1.1 GroupSSH | The SSH Group has the following child elements: • hostList (host list): the list of hosts to connect to. • privateKey (path string): the file of the private ssh key needed to access the host. • commandOptions (string): the list of options which will be passed to the ssh command. Figure 10 |
1ae034a75bbe7d46c2fae998c5f3b869 | 102 827 | 7.1.2 GroupRSH | The rsh Group has the following child elements: • hostList (host list): the list of hosts to connect to. Figure 11 |
1ae034a75bbe7d46c2fae998c5f3b869 | 102 827 | 7.1.3 GroupOARSH | An oarsh group element has the same parameters as an ssh group element, plus a 'jobId' (positive integer) mandatory attribute, which holds the OAR ID of the job. Figure 12 The following examples are group scheduling protocols. A scheduling protocol defines a way to communicate with a grid framework to submit job reques... |
1ae034a75bbe7d46c2fae998c5f3b869 | 102 827 | 7.1.4 ARC (NorduGrid) | Group definition for the NorduGrid's Advanced Resource Connector [i.1]. The NorduGrid group definition has the following child elements: • count (positive integer): amount of sub-jobs to be submitted for parallel tasks; • arguments (argument list): list of arguments passed to the job executable; • inputFiles (sequence ... |
1ae034a75bbe7d46c2fae998c5f3b869 | 102 827 | 7.1.5 CGSP China Grid | Group definition for the ChinaGrid middleware [i.2]. The CGSP group definition has the following child elements: • count (positive integer): number of executions of the executable; • directory (path string): the working directory of the job script; • stdout (path string): path of the file where the standard output of t... |
1ae034a75bbe7d46c2fae998c5f3b869 | 102 827 | 7.1.6 EGEE gLITE | Group definition for the EGEE gLite grid framework [i.3]. The gLite group definition has the following child elements: • stdout (path string): path of the file where the standard output of the job will be stored; • stderr (path string): path of the file where the standard error of the job will be stored; • stdin (path ... |
1ae034a75bbe7d46c2fae998c5f3b869 | 102 827 | 7.1.7 Fura/InnerGrid | Group definition for the Fura grid programming environment [i.4]. The Fura group definition has the following child elements: • description (string): a simple textual description of the job; • stdout (path string): path of the file where the standard output of the job will be stored; • stderr (path string): path of the... |
1ae034a75bbe7d46c2fae998c5f3b869 | 102 827 | 7.1.8 GLOBUS | Group definition for the Globus toolkit [i.5]. The GLOBUS group definition has the following child elements: • count (positive integer): number of executions of the executable; • maxTime (time): maximum amount of time the job is allowed to run; ETSI ETSI TS 102 827 V1.1.1 (2008-08) 24 • directory (path string): the wor... |
1ae034a75bbe7d46c2fae998c5f3b869 | 102 827 | 7.1.9 GridBus | Group definition for the GridBus middleware [i.6]. The GridBus element has a single child element: • arguments (argument list): list of arguments passed to the job executable. Figure 18 |
1ae034a75bbe7d46c2fae998c5f3b869 | 102 827 | 7.1.10 IBM Load Leveler | Group definition for IBM's Load Leveler job scheduler [i.7]. The Load Leveler group definition has the following child elements: • directory (path string): the working directory of the job script; • stdout (path string): path of the file where the standard output of the job will be stored; • stderr (path string) path o... |
1ae034a75bbe7d46c2fae998c5f3b869 | 102 827 | 7.1.11 LSF | Group definition for the LSF scheduler [i.8]. The LSF group definition has the following child elements: • resource (string): this element has the following attributes: - processorNumber (positive integer): number of processors requested; - walltime (time): maximum time allowed for the job. ETSI ETSI TS 102 827 V1.1.1 ... |
1ae034a75bbe7d46c2fae998c5f3b869 | 102 827 | 7.1.12 Microsoft CCS | Group Definition for Microsoft's Compute Cluster Server [i.13]. The CCS group definition has the following child elements: • resources: the resources that will be allowed to the job. This element can have two children: - cpus (positive integer): the number of CPUs allocated for the job; - runtime (time): the maximum ru... |
1ae034a75bbe7d46c2fae998c5f3b869 | 102 827 | 7.1.13 OAR | Group definition for the OAR job scheduler [i.9]. The OAR group definition has the following child elements: • resource (string): this element has the following attributes: ETSI ETSI TS 102 827 V1.1.1 (2008-08) 27 - nodes (positive integer): number of nodes requested; - cpu (positive integer): number of CPUs requested;... |
1ae034a75bbe7d46c2fae998c5f3b869 | 102 827 | 7.1.14 PBS / Torque | Group definition for the Torque job scheduler [i.10]. The PBS/Torque group definition has the following child elements: • resource (string): this element has the following attributes: - nodes (positive integer): number of nodes requested; - ppn (positive integer): number of CPUs requested; - walltime (time): maximum ti... |
1ae034a75bbe7d46c2fae998c5f3b869 | 102 827 | 7.1.15 PRUN | Group definition for the PRUN run server [i.11]. The PRUN group definition has the following child elements: • resource (string): this element has the following attributes: - nodes (positive integer): number of nodes requested; - ppn (positive integer): number of CPUs requested; - walltime (time): maximum time allowed ... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.