1、 ETSI TS 102 811 V1.1.1 (2010-03)Technical Specification GRID; Grid Component Model (GCM);Interoperability test specificationfloppy3ETSI ETSI TS 102 811 V1.1.1 (2010-03)2Reference DTS/GRID-0008 GCM_IOP_Test Keywords interoperability, testing ETSI 650 Route des Lucioles F-06921 Sophia Antipolis Cedex
2、 - FRANCE Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 Siret N 348 623 562 00017 - NAF 742 C Association but non lucratif enregistre la Sous-Prfecture de Grasse (06) N 7803/88 Important notice Individual copies of the present document can be downloaded from: http:/www.etsi.org The present document
3、 may be made available in more than one electronic version or in print. In any case of existing or perceived difference in contents between such versions, the reference version is the Portable Document Format (PDF). In case of dispute, the reference shall be the printing on ETSI printers of the PDF
4、version kept on a specific network drive within ETSI Secretariat. Users of the present document should be aware that the document may be subject to revision or change of status. Information on the current status of this and other ETSI documents is available at http:/portal.etsi.org/tb/status/status.
5、asp If you find errors in the present document, please send your comment to one of the following services: http:/portal.etsi.org/chaircor/ETSI_support.asp Copyright Notification No part may be reproduced except as authorized by written permission. The copyright and the foregoing restriction extend t
6、o reproduction in all media. European Telecommunications Standards Institute 2010. All rights reserved. DECTTM, PLUGTESTSTM, UMTSTM, TIPHONTM, the TIPHON logo and the ETSI logo are Trade Marks of ETSI registered for the benefit of its Members. 3GPPTM is a Trade Mark of ETSI registered for the benefi
7、t of its Members and of the 3GPP Organizational Partners. LTE is a Trade Mark of ETSI currently being registered for the benefit of its Members and of the 3GPP Organizational Partners. GSM and the GSM logo are Trade Marks registered and owned by the GSM Association. ETSI ETSI TS 102 811 V1.1.1 (2010
8、-03)3Contents Intellectual Property Rights 5g3Foreword . 5g31 Scope 6g32 References 6g32.1 Normative references . 6g32.2 Informative references 6g33 Definitions and abbreviations . 7g33.1 Definitions 7g33.2 Abbreviations . 7g34 About GCM Interoperability testing 7g35 Test Configurations 8g35.1 Entit
9、ies 8g35.1.1 Infrastructure including frontend 8g35.1.2 Deployment Manager . 8g35.1.3 Input and output data server(s) . 8g35.2 Single Infrastructure . 8g35.3 Single Infrastructure with a bridge . 9g35.4 Two Infrastructures and bridges . 10g35.5 Single Infrastructure with input and output data server
10、(s) . 10g36 Test Applications 11g36.1 Single process batch job . 11g36.2 Parallel job 12g36.3 Virtual Node GCM Application . 12g36.4 Data Manipulation GCM Application 12g37 GCM Test Descriptions 13g37.1 GCM Deployment Descriptor 13g37.1.1 Direct access . 13g37.1.1.1 Processor allocation 13g37.1.1.1.
11、1 Single processor with direct resource access . 13g37.1.1.1.2 Single processor with multiple threads with direct resource access 14g37.1.1.1.3 Multiple processors on a single host with direct resource access 14g37.1.1.1.4 Multiple processors on multiple hosts with direct resource access . 15g37.1.1
12、.1.5 Multiple processors in two infrastructures with direct resource access . 15g37.1.2 Indirect access . 16g37.1.2.1 Processor allocation 16g37.1.2.1.1 Single processor with indirect resource access 16g37.1.2.1.2 Multiple processors with indirect resource access . 16g37.1.2.1.3 Multiple processors
13、in two infrastructures with indirect resource access 17g37.1.2.2 Infrastructure properties 17g37.1.2.2.1 Termination before the maximum execution time . 17g37.1.2.2.2 Exceeding the maximum execution time . 18g37.1.2.2.3 Job queues . 18g37.1.2.2.4 Redirection of standard output 19g37.1.2.2.5 Memory s
14、pecification 19g37.1.2.2.6 Specified memory exceeds maximum amount of memory 20g37.1.2.2.7 Memory limitation . 20g37.1.3 Direct and indirect access . 21g37.1.3.1 Processor allocation 21g37.1.3.1.1 Multiple processors in an infrastructures with indirect and direct resource access . 21g37.2 GCM Applic
15、ation Descriptor . 21g37.2.1 Virtual node 21g37.2.1.1 Specific capacity of a single virtual node 21g3ETSI ETSI TS 102 811 V1.1.1 (2010-03)47.2.1.2 Maximum capacity of a single virtual node 22g37.2.1.3 Specific capacities of two virtual nodes 22g37.2.1.4 Maximum capacities of two virtual nodes 23g37.
16、2.1.5 Maximum and specific capacities of two virtual nodes 23g37.2.2 Data location . 24g37.2.2.1 Default input and output data 24g3Annex A (informative): Electronic attachments 25g3History 26g3ETSI ETSI TS 102 811 V1.1.1 (2010-03)5Intellectual Property Rights IPRs essential or potentially essential
17、to the present document may have been declared to ETSI. The information pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found in ETSI SR 000 314: “Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to
18、 ETSI in respect of ETSI standards“, which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web server (http:/webapp.etsi.org/IPR/home.asp). Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee can be gi
19、ven as to the existence of other IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web server) which are, or may be, or may become, essential to the present document. Foreword This Technical Specification (TS) has been produced by ETSI Technical Committee GRID (GRID). ETSI ETSI TS 1
20、02 811 V1.1.1 (2010-03)61 Scope The present document specifies interoperability tests for ETSI GCM deployment and application descriptor standards. 2 References References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For a specific
21、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 accepted that it will be possible to use all future changes of the referenced document for the purposes of the referring document
22、; - for informative references. Referenced documents which are not found to be publicly available in the expected location might be found at http:/docbox.etsi.org/Reference. NOTE: While any hyperlinks included in this clause were valid at the time of publication ETSI cannot guarantee their long term
23、 validity. 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
24、 ETSI TS 102 827 (V1.1.1): “GRID; Grid Component Model (GCM); GCM Interoperability Deployment“. 2 ETSI TS 102 828: “GRID; Grid Component Model (GCM); GCM Application Description“. 3 ETSI TR 102 766: “GRID; ICT Grid Interoperability Testing Framework and survey of existing ICT Grid interoperability s
25、olutions“. 4 ETSI EG 202 237: “Methods for Testing and Specification (MTS); Internet Protocol Testing (IPT); Generic approach to interoperability testing“. 2.2 Informative references The following referenced documents are not essential to the use of the present document but they assist the user with
26、 regard to a particular subject area. For non-specific references, the latest version of the referenced document (including any amendments) applies Not applicable. ETSI ETSI TS 102 811 V1.1.1 (2010-03)73 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the foll
27、owing terms and definitions apply: direct resource access: resources of an infrastructure are accessed directly, e.g. via logging into a machine, for the purpose of deploying applications frontend: in a physical network, single machine acting as a gateway for a set of machines NOTE: See 1. indirect
28、resource access: resources of an infrastructure are accessed via a frontend including a job scheduler for the purpose of deploying applications 3.2 Abbreviations For the purposes of the present document, the following abbreviations apply: AD Application Descriptor DD Deployment Descriptor EUT Equipm
29、ent Under Test GCM Grid Component Model MET Maximum Execution Time MiB MebiByte VN Virtual NodeXML eXtensible Markup Language 4 About GCM Interoperability testing The present document describes interoperability tests for the Grid Component Model (GCM) standards. The main purpose of the tests is the
30、assessment of the standardized GCM Deployment Descriptor (DD) 1 and Application Descriptor (AD) 2. The method and criteria how these tests have been derived is explained in detail in the grid interoperability testing framework 3. The generic approach to interoperability testing described in 4 has be
31、en adapted for developing the interoperability tests including the test architecture and tests configurations for the GCM standards. The GCM DD describes resources requested from one or more different infrastructures for an application. The GCM DD is converted into deployment information. This conve
32、rsion process should be done in an automated manner by a GCM implementation but may be performed manually in case the use of the interface has not yet been standardized in 1. The GCM DD is mapped on resources of specified infrastructure(s) and is then used to deploy and establish a communication lay
33、er, in the following called GCM infrastructure, needed by an application. The GCM AD describes the requirements of an application from an underlying infrastructure, e.g. virtual nodes (VNs) required by the application are mapped to resources. An application can utilize the resources specified by the
34、 GCM DD it references. In the present document, the GCM interoperability tests are described with Test Descriptions (TD). TDs are mainly intended for a manual test execution. However, they can also be used as a basis for the development of automated GCM interoperability tests. The tests assess both
35、mandatory as well as optional features of GCM DD and GCM AD. In each test, a test application is used to assess that GCM information is provided as expected. The test application used in a test is referenced in the TD. Properties of test applications, e.g. their execution time, can be customized via
36、 input parameters. Test applications are described in more detail in clause 6. ETSI ETSI TS 102 811 V1.1.1 (2010-03)8Prior any test execution, all of the tests pre-conditions should be checked to identify if it is applicable for the equipment participating in the test. Common types of pre-conditions
37、 are: 1) GCM descriptor: GCM DD and/or GCM AD specifications must fulfil requirements. 2) Infrastructure requirements: include type of resource access, functionality to be fulfilled, and available amount of resources. 3) Test application parameterization: the parameters provided to the application m
38、ust fulfil requirements. A test should be recorded as being not applicable if any of its pre-conditions are not met by the one (or more) equipment used in the test. A test can be executed after its pre-test conditions have been ensured. NOTE: The TDs assume that basic conditions such as the existenc
39、e of a user account for the test operator have been fulfilled. 5 Test Configurations This clause introduces the GCM test configurations used in the TDs described in clause 7. The test configurations include the entities infrastructure, deployment manager and input/output data servers. 5.1 Entities I
40、n this clause, the entities used in the test configurations are explained. 5.1.1 Infrastructure including frontend In the GCM DD, resources of infrastructures can be requested for deploying the GCM infrastructure. These resources of an infrastructure have to be accessible either in a direct or indir
41、ect manner. While infrastructures with indirect resource access offer a frontend that contacts a job scheduler and grants access to resources, infrastructures with direct resource access perform the deployment on the resources without any frontend or manager. Infrastructures with indirect resource a
42、ccess are mainly clusters and grid middlewares. Examples of infrastructures with direct resource access include a desktop computer and a cloud computing system. A set of desktop computers may also be collected to form a group infrastructure. More information and examples of different types of infras
43、tructures can be found in 3. 5.1.2 Deployment Manager The deployment manager (which can also be a human being) establishes the GCM infrastructure by converting GCM DD information into specific service calls or commands which are supported by the underlying infrastructure. After that, the test applic
44、ation with its parameters and infrastructure parameters can be submitted, e.g. as a job, using the specific protocol provided by the infrastructure. 5.1.3 Input and output data server(s) Input and output data servers are used to store input and/or output data of GCM applications independent of the i
45、nfrastructure on which it runs on. Input and output data servers can be access independently using a supported file access protocol such as http, ftp, sftp, or file. Depending on the protocol, the data is accessed remotely or locally. The file access protocol, the input and/or the output data direct
46、ories (or files) are defined in the GCM AD. 5.2 Single Infrastructure In the test configuration depicted in Figure 1, the Equipment Under Test (EUT) 4 contains a single infrastructure and the deployment manager. Access to the deployment manager, the infrastructure, the application, the GCM DD, and t
47、he GCM AD are available from one single physical machine. The user uses the deployment manager to load the GCM DD and, in case the test application is a GCM application, also the GCM AD as input. The user is logged into the infrastructure to establish the GCM infrastructure and submit jobs related t
48、o the application and the infrastructure. ETSI ETSI TS 102 811 V1.1.1 (2010-03)9Depending on the type of the resource access provided by the infrastructure, a frontend may or may not be used to access resources. Figure 1: Single Infrastructure 5.3 Single Infrastructure with a bridge The test configu
49、ration depicted in Figure 2 extends the test configuration described in clause 5.2 with a bridge. This test configuration has two EUTs, whereas EUT A contains the deployment manager and EUT B contains a single infrastructure. The deployment manager is only able to access the infrastructure via a bridge. Here, the user submits jobs from a remote machine which is connected to the infrastructure via a bridge. Depending on the type of the resource access provided by the infrastructure, a frontend may or may not be used to access resources. Figure 2: S
