1、 ETSI TS 102 786 V1.1.1 (2009-10)Technical Specification GRID;ICT Grid Interoperability Testing FrameworkETSI ETSI TS 102 786 V1.1.1 (2009-10)2Reference DTS/GRID-0007 Keywords ICT, interoperability, testing ETSI 650 Route des Lucioles F-06921 Sophia Antipolis Cedex - FRANCE Tel.: +33 4 92 94 42 00 F
2、ax: +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 may be made available in more than
3、 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 version kept on a specific network
4、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.asp If you find errors in the prese
5、nt 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 to reproduction in all media. Europe
6、an Telecommunications Standards Institute 2009. 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 benefit of its Members and of the 3GPP Or
7、ganizational 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 786 V1.1.1 (2009-10)3Contents Intellectual Property
8、 Rights 4g3Foreword . 4g31 Scope 5g32 References 5g32.1 Normative references . 5g32.2 Informative references 5g33 Definitions and abbreviations . 6g33.1 Definitions 6g33.2 Abbreviations . 6g34 Testing framework for the Grid Component Model . 7g34.1 Introduction 7g34.2 Grid Component Model 7g34.3 Goa
9、ls 8g34.4 Test architecture . 9g34.5 Test suite structure and test purposes . 10g34.5.1 Test suite structure 10g34.5.2 Test purposes 10g34.5.3 Test descriptions . 10g34.5.4 Test execution . 11g3History 12g3ETSI ETSI TS 102 786 V1.1.1 (2009-10)4Intellectual Property Rights IPRs essential or potential
10、ly essential 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, IPR
11、s notified to 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 guaran
12、tee can be given 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). E
13、TSI ETSI TS 102 786 V1.1.1 (2009-10)51 Scope The present document defines a grid testing framework based on existing testing and validation methodologies, best practices and tools used, in IT and Telecom sectors to obtain ICT Interoperability. 2 References References are either specific (identified
14、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 accepted that it will be possible
15、 to use all future changes of the referenced document for the purposes of the referring document; - 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 inc
16、luded in this clause were valid at the time of publication ETSI cannot guarantee their long term 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
17、 references, the latest edition of the referenced document (including any amendments) applies. Not applicable. 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
18、-specific references, the latest version of the referenced document (including any amendments) applies. i.1 ETSI EG 202 237 (V1.1.2): “Methods for Testing and Specification (MTS); Internet Protocol Testing (IPT); Generic approach to interoperability testing“. i.2 ETSI TS 102 828 (V1.1.1): “GRID; Gri
19、d Component Model (GCM); GCM Application Description“. i.3 ETSI TS 102 827 (V1.1.1): “GRID; Grid Component Model (GCM); GCM Interoperability Deployment“. i.4 ETSI TS 102 829 (V1.1.1): “GRID; Grid Component Model (GCM);GCM Fractal Architecture Description Language (ADL)“. i.5 IBM, Workload Management
20、 with LoadLeveler, IBM Redbooks. NOTE: Available at http:/ i.6 Platform, Manage and accelerate compute- or data-intensive workload on HPC clusters and grids. NOTE: Available at http:/ ETSI ETSI TS 102 786 V1.1.1 (2009-10)6i.7 Microsoft, Microsoft Windows Compute Cluster Server 2003 (CCS). NOTE: Avai
21、lable at http:/ i.8 PBS Gridworks, OpenPBS. NOTE: Available at: http:/ TPLan: A notation for expressing Test Purposes“. 3 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the following terms and definitions apply: deployment manager: entity which converts deplo
22、yment information into infrastructure specific service calls or commands to perform resource reservation and application deployment 3.2 Abbreviations For the purposes of the present document, the following abbreviations apply: AD GCM Application Descriptor ADL Architecture Description Language CCS C
23、ompute Cluster Server DD GCM Deployment Descriptor GCM Grid Component Model ICS Implementation Conformance Statement IPT Internet Protocol Testing LSF Load Sharing Facility PBS Portable Batch SystemSGE Sun Grid Engine SUT System Under Test ETSI ETSI TS 102 786 V1.1.1 (2009-10)7TP Test Purpose VN Vir
24、tual Node XML Extensible Markup Language 4 Testing framework for the Grid Component Model 4.1 Introduction EG 202 237 i.1 describes a generic approach to interoperability testing for Internet Protocol Testing (IPT). In this guide, interoperability testing is defined as the “activity of proving that
25、end-to-end functionality between (at least) two communicating systems is as required by the base standard(s) on which those systems are based“. The document introduces the interoperability testing process that includes descriptions of basic interoperability concepts, interoperability test architectu
26、res, and interoperability test models. In addition, the process for the development of interoperability test specification and execution are presented. In the present document, the development of an interoperability grid testing framework is described which has been derived from the generic approach
27、 to interoperability testing i.1. This grid interoperability testing framework is based on the ETSI GCM standards i.2, i.3 and i.4. The GCM standards were not meant to standardize interfaces but to abstract a common set of properties from existing interfaces. In addition, it standardizes the use of
28、these proprietary interfaces towards the respective platforms. This approach has been chosen to allow infrastructure providers not to change their interfaces for a deployment of applications. The main focus of the testing framework is to validate that properties described in the GCM DD and AD are im
29、plemented by the equipment under test. This equipment includes one or more infrastructures as well as a GCM deployment manager as shown in the abstract architecture shown in figure 1. Example test purposes and test descriptions are presented which have been developed based on this framework. Due to
30、the proprietary nature of deployment interfaces the testing framework is currently envisioned to primarily serve as the basis for development of informal test descriptions suitable for manual execution of tests, e.g. at interoperability events such as ETSI Plugtests. However, test descriptions may a
31、lso be used as a basis for test case development, i.e. an automated testing framework. 4.2 Grid Component Model The Grid Component Model (GCM) standard contains three parts: the GCM Application Description i.2, GCM Interoperability Deployment i.3, and GCM Fractal Architecture Description Language (A
32、DL) i.4. A generic GCM test architecture which focuses on the GCM Application Descriptor (AD) and Deployment Descriptor (DD) has been developed as shown in figure 1. Here, the user is assumed to provide a (test) application, a GCM DD XML file, as well as optionally a GCM AD XML file. The GCM DD desc
33、ribes resources requested from one or more different infrastructures for an application. The GCM DD is converted by the deployment manager into the invocation of specific infrastructure services or commands. This conversion process should be done in an automated manner by a deployment manager but ma
34、y need to be performed manually if the use of the infrastructure interface has not yet been standardized in i.3. The GCM DD is mapped to resources of the specified infrastructure(s), and then used to deploy and establish a communication layer, called the GCM infrastructure, which is used for applica
35、tion deployment and execution. Input and output data servers can be used to store input and/or output data of GCM applications independent of the infrastructure on which it runs. Data can be accessed remotely or locally. ETSI ETSI TS 102 786 V1.1.1 (2009-10)8Figure 1: GCM Architecture A GCM AD descr
36、ibes the requirements of an application from an underlying infrastructure, e.g. how Virtual Nodes (VNs) required by the application are mapped to resources defined in the GCM DD it references. In addition, an application may access data servers to read input data and write output data from locations
37、 specified in the GCM AD. A GCM DD describes resources that are expected to be available and provided by one or more infrastructures. Note that the resources requested in a GCM DD are often only a subset of all resources available in one or more infrastructures. The resources have to be accessible e
38、ither in a direct or indirect manner. While infrastructures with indirect resource access offer a service that contacts a job scheduler and grants access to resources, infrastructures with direct resource access perform the deployment on the resources without any manager. Examples of infrastructures
39、 with indirect resource access include clusters and/or grid middleware. Examples of infrastructures with direct resource access include desktop computers and cloud computing systems. A set of desktop computers may also be collected to form a group infrastructure. The GCM DD standard contains already
40、 a number of standardized mappings to a number of different commercial as well as open source infrastructures: Infrastructures with indirect resource access: - Local resources manager including IBM LoadLeveler i.5, Platform Load Sharing Facility (LSF) i.6, Microsoft Compute Cluster Server (CCS) i.7,
41、 Portable Batch System (PBS) i.8 and Sun Grid Engine (SGE) i.9. - Grid infrastructure including gLite i.10, Fura i.11, Globus i.12 and Unicore i.13. Infrastructures with direct resource access: - Desktop computer including MS Windows and Linux. - Cloud computing system including Amazon EC2. Input an
42、d output data servers are used to store input and/or output data of GCM applications independent of the infrastructure on which it runs. 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 da
43、ta is accessed remotely or locally. 4.3 Goals The main purpose of the tests is the assessment of the standardized GCM Deployment Descriptor (DD) and Application Descriptor (AD). The general test objective is to check that applications can be deployed and executed on a given infrastructure based on t
44、he information provided in GCM DD and AD. An infrastructure can either provide direct or indirect resource access. To access an infrastructure, its protocol need to be followed as specified in i.3. ETSI ETSI TS 102 786 V1.1.1 (2009-10)9For a classification of functionalities that may be provided by
45、a System Under Test (SUT), we define compliance levels as follows: Compliance by the infrastructure: 1) An infrastructure does not support properties described in GCM AD and DD. 2) An infrastructure supports properties described in GCM AD and DD but are converted in a manual manner. 3) An infrastruc
46、ture supports properties described in GCM AD and DD and are converted in an automated manner. Compliance by the deployment manager: 4) Multiple infrastructures support fulfill level 1. 5) Multiple infrastructures support fulfill either level 1 or level 2. 6) Multiple infrastructures support fulfill
47、level 2. 4.4 Test architecture Figure 2: A test architecture for GCM-based deployment An example test architecture is shown in figure 2. The System Under Test (SUT) consists of the Deployment Manager and one or more infrastructures. The different types of entities that compose the means of testing h
48、andle provision of GCM DD and AD files to the deployment manager associated with the infrastructure to be tested, the evaluation of responses from the deployment manager, analysis of the output produced by the application, monitoring of the processing ongoing in the infrastructure during the executi
49、on of tests, e.g. the number of processors involved in a computation, the interface(s) between deployment manager, each infrastructure and the input/output servers. NOTE 1: The interfaces for supplying GCM DD and AD to a deployment manager have not yet been standardized. NOTE 2: This testing architecture can also be us
