DOCSLIB.ORG

ETSI TR 102 659-1 V1.2.1 (2009-10) Technical Report

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
ETSI TR 102 659-1 V1.2.1 (2009-10) Technical Report ETSI TR 102 659-1 V1.2.1 (2009-10) Technical Report GRID; Study of ICT Grid interoperability gaps; Part 1: Inventory of ICT Stakeholders 2 ETSI TR 102 659-1 V1.2.1 (2009-10) Reference RTR/GRID-0001-1[2] Keywords analysis, directory, ICT, interoperability, testing ETSI 650 Route des Lucioles F-06921 Sophia Antipolis Cedex - 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 enregistrée à la Sous-Préfecture 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 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 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 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 to reproduction in all media. © European 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 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 3 ETSI TR 102 659-1 V1.2.1 (2009-10) Contents Foreword ............................................................................................................................................................. 6 Introduction ........................................................................................................................................................ 6 1 Scope ........................................................................................................................................................ 7 2 References ................................................................................................................................................ 7 2.1 Normative references ......................................................................................................................................... 7 2.2 Informative references ........................................................................................................................................ 8 3 Definitions and abbreviations ................................................................................................................. 13 3.1 Definitions ........................................................................................................................................................ 13 3.2 Abbreviations ................................................................................................................................................... 14 4 Grid Introduction .................................................................................................................................... 18 4.1 The idea and characteristics of Grids ............................................................................................................... 19 4.2 Diverse Grid systems - both in scope and use .................................................................................................. 19 4.3 Service Oriented Architecture (SOA) ............................................................................................................... 20 4.4 Next Generation Grid (NGG) ........................................................................................................................... 20 4.5 Next Generation Network (NGN) .................................................................................................................... 22 4.6 Grids and Clouds .............................................................................................................................................. 23 4.6.1 The growth of Clouds ................................................................................................................................. 23 4.6.2 Standardization and interoperability ........................................................................................................... 25 5 Grid requirements ................................................................................................................................... 25 6 Grid Architecture .................................................................................................................................... 26 6.1 Grid Software Architectures ............................................................................................................................. 27 6.2 Grid Infrastructure Architectures ..................................................................................................................... 28 6.3 Conceptual model of a grid and associated roles .............................................................................................. 28 7 Telcos in the Grid/cloud market ............................................................................................................. 29 7.1 Eurescom .......................................................................................................................................................... 29 7.2 An Analyst's View ............................................................................................................................................ 30 7.3 An IT Industry Vendors View .......................................................................................................................... 30 7.4 AT&T ............................................................................................................................................................... 30 7.5 BT ..................................................................................................................................................................... 31 7.5.1 NGN............................................................................................................................................................ 31 7.5.2 Grid/Cloud computing Services .................................................................................................................. 32 7.5.2.1 Virtual data centres ............................................................................................................................... 32 7.5.2.2 Software-As-A-Service (SAAS) ........................................................................................................... 32 7.5.2.3 Ribbit for Salesforce ............................................................................................................................. 32 7.6 DT .................................................................................................................................................................... 33 7.6.1 NGN............................................................................................................................................................ 33 7.6.2 Grid/Cloud computing Services .................................................................................................................. 33 7.7 France Telecom ................................................................................................................................................ 34 7.7.1 Background ................................................................................................................................................. 34 7.7.2 Test Overview ............................................................................................................................................. 34 7.7.3 Developments ............................................................................................................................................. 35 7.8 Telefónica ......................................................................................................................................................... 35 7.8.1 Background ................................................................................................................................................. 35 7.8.2 Cloud Vision ............................................................................................................................................... 35 7.8.3 Open Telefónica .......................................................................................................................................... 36 7.8.4 Open Cloud ................................................................................................................................................
Load more

Recommended publications
  • Job Peer Group Controller Job Peer Group Host „ a PG for Each Job
    Korea-Japan Grid Symposium, Seoul December 1-2, 2004 P3: Personal Power Plant Makes over your PCs into power generator on the Grid Kazuyuki Shudo <[email protected]>, Yoshio Tanaka, Satoshi Sekiguchi Grid Technology Research Center, AIST, Japan P3: Personal Power Plant Middleware for distributed computation utilizing JXTA. Traditional goals Cycle scavenging Harvest compute power of existing PCs in an organization. Conventional dist. computing Internet-wide distributed computing E.g. distributed.net, SETI@home Challenging goals Aggregate PCs and expose them as an integrated Grid resource. Integrate P3 with Grid middleware ? cf. Community Scheduler Framework Dealings and circulation of computational resources Transfer individual resources (C2C, C2B) and also aggregated resources (B2B). Transfer and aggregation of Other resources than processing power. individual resources Commercial dealings need a market and a system supporting it. P2P way of interaction between PCs P3 uses JXTA for all communications JXTA is a widely accepted P2P protocol, project and library, that provides common functions P2P software requires. P2P concepts supported by JXTA efficiently support P3: Ad-hoc self-organization PCs can discover and communicate with each other without pre-configuration. Discovery PCs dynamically discover each other and jobs without a central server. Peer Group PCs are grouped into job groups, in which PCs carry out code distribution, job control, and collective communication for parallel computation. Overlay Network Peer ID in JXTA is independent from physical IDs like IP addresses and MAC addresses. JXTA enables end-to-end bidirectional communication over NA(P)T and firewall (even if the FW allows only unidirectional HTTP). This function supports parallel processing in the message-passing model, not only master-worker model.
    [Show full text]
  • Bringing the Openbmc for Platform Manage- Ment System in Telco Cloud
    Rongqiang Zhang Bringing the OpenBMC for Platform Manage- ment System in Telco Cloud Helsinki Metropolia University of Applied Sciences Master of Engineering Information Technology Master’s Thesis 30 Apr 2019 Abstract Rongqiang Zhang Author(s) Bringing the OpenBMC for Platform Man-agement System in Title Telco Cloud Number of Pages 88 pages + 0 appendices Date 30 Apr 2019 Degree Master of Engineering Degree Programme Information Technology Specialisation option Networking and Services Ville Jääskeläinen, Head of Degree Program Instructor(s) Zinaida Grabovskaia, PhL, Senior Lecturer Antti Koivumäki, Senior Lecturer Ari Helminen, Business Manager The current platform management system in Telco cloud infrastructure is based on closed firmware stack. With the upcoming 5G, this closed firmware stack has created several tech- nology and business problems. The major problems are hardware-software vendor lock-in, long lead time for feature development and bug fixing, and security risks. The objective of this study is to evaluate the possibility to bring an Open Source software stack for platform management system and baseboard management controller in Telco cloud. The study was divided into 3 parts. First part is to analyse the current state and project specification. Second part is to introduce and evaluate the OpenBMC, an open source soft- ware stack for the objective of this study. Third part is Proof of Concept to run OpenBMC on Telco. Keywords BMC, 5G, NFV, Redfish, Security Table of Contents Abstract List of Abbreviations 1 Introduction
    [Show full text]
  • Web Services and PC Grid
    Web Services and PC Grid ONG Guan Sin <[email protected]> Grid Evangelist Singapore Computer Systems Ltd APBioNet/APAN 18 Jul 2006 Tera-scale Campus Grid @ NUS LATEST: CIO Award 2006 winner Harnessing existing computation capacity campus-wide, creating large-scale supercomputing capability Computers are aggregated through its gigabit network into a virtual supercomputing platform using United Devices Grid MP middleware Community grid by voluntary participation from depts Two-year collaboration project between NUS and SCS to develop applications and support community Number of Nodes Theoretical# Practical^ 1,042 (Sep 20, 2005) 4.5 TFlops 2.5 TFlops 3,000 (Planned - 2007) 13 TFlops 7.2 TFlops * Accumulated average CPU speed of 2.456GHz as at Sep 20, 2005 # Assuming 90% capacity effectively harnessed ^ Assuming 50% capacity effectively harnessed Copyright 2006 Singapore Computer Systems Limited 2 UD Grid MP Architecture Managed Grid Services Interface (MGSI) ± Web Services API 3 Command-line Interface Application Service 4 Simple Web Interface 5 Application Service Overview Application Service . Is a job submission and result retrieval program which provides users with a simple interface for performing work on the Grid . It is responsible for Splitting and Merging Application Data Features . Control the Grid MP Sever with SOAP or XML-RPC communications . SOAP and XML-RPC Communications are protected with SSL encryption . SOAP and XML-RPC are language and platform independent with many publicly available toolkits and libraries. User interface can be command-line, web-based, GUI, etc. Can be written to run on various operating systems MP Grid Services Interface (MGSI) . All Objects in the Grid MP platform can be controlled through the MGSI .
    [Show full text]
  • Good Practice Guide No. 17 Distributed Computing for Metrology
    NPL REPORT DEM-ES 006 Software Support for Metrology - Good Practice Guide No. 17 Distributed computing for metrology applications T J Esward, N J McCormick, K M Lawrence and M J Stevens NOT RESTRICTED March 2007 National Physical Laboratory | Hampton Road | Teddington | Middlesex | United Kingdom | TW11 0LW Switchboard 020 8977 3222 | NPL Helpline 020 8943 6880 | Fax 020 8943 6458 | www.npl.co.uk Software Support for Metrology Good Practice Guide No. 17 Distributed computing for metrology applications T J Esward, N J McCormick, K M Lawrence and M J Stevens Mathematics and Scientific Computing Group March 2007 ABSTRACT This guide aims to facilitate the effective use of distributed computing methods and techniques by other National Measurement System (NMS) programmes and by metrologists in general. It focuses on the needs of those developing applications for distributed computing systems, and on PC desktop grids in particular, and seeks to ensure that application developers are given enough knowledge of system issues to be able to appreciate what is needed for the optimum performance of their own applications. Within metrology, the use of more comprehensive and realistic mathematical models that require extensive computing resources for their solution is increasing. The motivation for the guide is that in several areas of metrology the computational requirements of such models are so demanding that there is a strong requirement for distributed processing using parallel computing on PC networks. Those who need to use such technology can benefit from guidance on how best to structure the models and software to allow the effective use of distributed computing.
    [Show full text]
  • Print This Article
    L{{b b Volume 1, No. 3, Sept-Oct 2010 International Journal of Advanced Research in Computer Science RESEARCH PAPER Available Online at www.ijarcs.info A Simplified Network manager for Grid and Presenting the Grid as a Computation Providing Cloud M.Sudha* M.Monica Assistant Professor (Senior) Assistant Professor, School of Information Technology and Engineering, VIT School of Computer Science and Engineering, University INDIA VIT University INDIA [email protected] [email protected] Abstract: One of the common forms of distributed computing is grid computing. A grid uses the resources of many separate computers, loosely connected by a network, to solve large-scale computation problems. Our approach was as follows first computationally large data is split into a number of smaller, more manageable, working units secondly each work-unit is then sent to one member of the grid ,That member completes processing of that work-unit in its own and sends back the result. In this architecture, there needs to be at least one host that performs the task of assigning work-units, and then sending them, to a remote processor, as well as receive the results from remote processors. We call this unit as the Network Manager. In addition to this assigning, sending and receiving the work-units and results, there also is the need for a host that splits tasks into work-units and assimilates the received work units. We call this unit as the Task Broker, which we propose to design. On the server end, there is a program for processing module, splitter and assimilator (broker).
    [Show full text]
  • Oracle ILOM Web Interface
    ® Oracle ILOM User's Guide for System Monitoring and Diagnostics Firmware Release 4.0.x Part No: E86150-06 September 2018 Oracle ILOM User's Guide for System Monitoring and Diagnostics Firmware Release 4.0.x Part No: E86150-06 Copyright © 2018, Oracle and/or its affiliates. All rights reserved. This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited. The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing. If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable: U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs.
    [Show full text]
  • Implementing IBM Director 5.20
    Front cover Implementing IBM Director 5.20 Describes how to plan and implement an IBM Director solution Includes many advanced scenarios of use Companion to IBM Director product publications David Watts Robert J Brenneman David Feisthammel Tim Sutherland ibm.com/redbooks International Technical Support Organization Implementing IBM Director 5.20 April 2007 SG24-6188-03 Note: Before using this information and the product it supports, read the information in “Notices” on page xv. Fourth Edition (April 2007) This edition applies to Version 5.20 of IBM Director. © Copyright International Business Machines Corporation 2001, 2003, 2006, 2007. All rights reserved. Note to U.S. Government Users Restricted Rights -- Use, duplication or disclosure restricted by GSA ADP Contents Notices . xv Trademarks . xvi Preface . xvii The team that wrote this book . xvii Become a published author . xx Comments welcome. xxi Chapter 1. Introduction. 1 1.1 Overview . 2 1.2 Other platforms . 2 1.3 IBM Systems Director . 3 1.4 Industry standards. 3 1.4.1 Common Information Model . 4 1.4.2 Intelligent Platform Management Interface . 4 1.4.3 Platform Event Trap . 5 1.4.4 Predictive Failure Analysis . 6 1.4.5 Service Location Protocol . 7 1.4.6 Simple Network Management Protocol. 7 1.4.7 System Management Bus . 7 1.4.8 Storage Management Initiative Specification . 8 1.4.9 System Management BIOS. 8 1.4.10 Systems Management Architecture for Server Hardware. 9 1.5 IBM Director overview . 9 1.5.1 IBM Director components . 10 1.5.2 IBM Director Extensions . 14 1.6 IBM Director licensing .
    [Show full text]
  • PMCI) 4 Architecture 5 6 White Paper 7
    1 2 3 Platform Management Component Intercommunications (PMCI) 4 Architecture 5 6 White Paper 7 8 Version 1.0.0a 9 Status: Informational 10 Publication Date: July, 2007 11 DSP2015 Page 1 of 16 12 Copyright © 2007 Distributed Management Task Force, Inc. (DMTF). All rights reserved. 13 DMTF is a not-for-profit association of industry members dedicated to promoting enterprise and systems manage- 14 ment and interoperability. Members and non-members may reproduce DMTF specifications and documents for uses 15 consistent with this purpose, provided that correct attribution is given. As DMTF specifications may be revised 16 from time to time, the particular version and release date should always be noted. 17 Implementation of certain elements of this standard or proposed standard may be subject to third party patent rights, 18 including provisional patent rights (herein "patent rights"). DMTF makes no representations to users of the standard 19 as to the existence of such rights, and is not responsible to recognize, disclose, or identify any or all such third party 20 patent right, owners or claimants, nor for any incomplete or inaccurate identification or disclosure of such rights, 21 owners or claimants. DMTF shall have no liability to any party, in any manner or circumstance, under any legal the- 22 ory whatsoever, for failure to recognize, disclose, or identify any such third party patent rights, or for such party’s 23 reliance on the standard or incorporation thereof in its product, protocols or testing procedures. DMTF shall have no 24 liability to any party implementing such standard, whether such implementation is foreseeable or not, nor to any 25 patent owner or claimant, and shall have no liability or responsibility for costs or losses incurred if a standard is 26 withdrawn or modified after publication, and shall be indemnified and held harmless by any party implementing the 27 standard from any and all claims of infringement by a patent owner for such implementations.
    [Show full text]
  • History of Manageability
    Chapter 2 History of Manageability Civilizations in decline are consistently characterized by a tendency to- wards standardization and uniformity — Arnold Toynbee (1889–1975) anageability, as a unique discipline, has historically evolved from the M growing need to configure and maintain the computer systems, applications, and networks. As more and more of these entities provided capabilities that could be adapted, changed, and optimized for a particular use or preference, the need for manageability grew. With a low number of systems, it was possible to have system administrators individually log into the system locally and manage each system independently. However, as these systems grew in number and became more and more complex, administrators needed to manage a large number of resources from a central management site. The use of remote management tools became important. This led to development of several protocols for remote management. In the beginning, most of these were proprietary in nature, which meant that a system from one manufacturer could only be managed with a manage- ment console from the same manufacturer. This led the industry to work on interoperable standards that allow the systems from multiple manufactures to be managed with common tools. 15 16 Active Platform Management Demystified Chapter 2: History of Manageability 17 Protocol and Data Model Remote management interfaces can be logically viewed as a combination of a communication protocol and the payload that is exchanged via that communication protocol. Historically, this separation has not always been very clear or emphasized, and some standards have treated them with a very tight binding. However, making this logical separation has clear advantages as illustrated in Figure 2.1.
    [Show full text]
  • Resume Ivo Janssen
    Ivo J. Janssen 13266 Kerrville Folkway Austin, TX 78729 (512) 750-9455 / [email protected] Objective To be part of a successful professional services team in a pre-sales and post-sales architecture and deployment role. Summary I'm an experienced, enthusiastic and skilled professional services consultant with experience in architecting and supporting large-scale enterprise software, with extensive experience in designing and implementing custom solutions as part of pre- and post sales support activities in diverse industry verticals across five continents. I'm as comfortable in designing and coding in an engineering role as I am in on-site planning, executing and troubleshooting customer deployments in a professional services role, as well as in participating in sales calls and drafting proposals in a sales engineering role. I'm able to adapt to new environments quickly and rapidly become proficient with new systems, tools and skills. I'm a good team player who thinks beyond the problem at hand instead of following the established paths in order to find a better solution that meets both current and future needs. Professional experience • Virtual Bridges , Austin, TX, USA (Nov 2010 – present) Senior Solution Architect o Solution architect for VDI product line. • Initiate Systems / IBM , Austin, TX, USA (Sep 2008 – Nov 2010) Senior Consultant o Senior implementation engineer for Healthcare sector of Master Data Management product line. o Responsibilities include requirements gathering, product installation and configuration, custom coding, connectivity scripting on Windows and Unix, database performance tuning, customer training workshops, pre/post-sales support. o Successfully architected, implemented and brought live custom implementation projects for major hospital systems and labs in the US, including customers with up to 250 million records (1TB database) connected to 20 auxiliary systems.
    [Show full text]
  • Desktop Grids for Escience
    Produced by the IDGF-SP project for the International Desktop Grid Federation A Road Map Desktop Grids for eScience Technical part – December 2013 IDGF/IDGF-SP International Desktop Grid federation http://desktopgridfederation.org Edited by Ad Emmen Leslie Versweyveld Contributions Robert Lovas Bernhard Schott Erika Swiderski Peter Hannape Graphics are produced by the projects. version 4.2 2013-12-27 © 2013 IDGF-SP Consortium: http://idgf-sp.eu IDGF-SP is supported by the FP7 Capacities Programme under contract nr RI-312297. Copyright (c) 2013. Members of IDGF-SP consortium, see http://degisco.eu/partners for details on the copyright holders. You are permitted to copy and distribute verbatim copies of this document containing this copyright notice but modifying this document is not allowed. You are permitted to copy this document in whole or in part into other documents if you attach the following reference to the copied elements: ‘Copyright (c) 2013. Members of IDGF-SP consortium - http://idgf-sp.eu’. The commercial use of any information contained in this document may require a license from the proprietor of that information. The IDGF-SP consortium members do not warrant that the information contained in the deliverable is capable of use, or that use of the information is free from risk, and accept no liability for loss or damage suffered by any person and organisation using this information. – 2 – Preface This document is produced by the IDGF-SP project for the International Desktop Grid Fe- deration. Please note that there are some links in this document pointing to the Desktop Grid Federation portal, that requires you to be signed in first.
    [Show full text]
  • Distributed Computing with the Berkeley Open Infrastructure for Network Computing BOINC
    Distributed Computing with the Berkeley Open Infrastructure for Network Computing BOINC Eric Myers 1 September 2010 Mid-Hudson Linux Users Group 2 How BOINC Works BOINC Client BOINC is the software BOINC Server Windows framework that makes Linux Mac OS this all work. Linux 50+ separate projects (& Solaris, AIX, HP-UX, etc…) 1 September 2010 Mid-Hudson Valley Linux Users Group 3 BOINC Dataflow 1 September 2010 Mid-Hudson Valley Linux Users Group 4 Early History SETI@home . May 1999 to Dec 2005 (“Classic”) . 2003 (BOINC) World Community Grid (IBM) . Nov 2004 to mid 2008 (Grid MP) Climatepredition.net . Nov 2007 (BOINC) . Sept 2003 (“Classic”) . August 2004 (BOINC) Einstein@Home . February 2005 Predictor@Home . (Pirates@Home – June 2004 :-) . June 2004 - Scripps . October 2008 – U. Michigan Rosetta@Home (University of Washington) . June 2005 LHC@Home . Sept 2004 - CERN PrimeGrid (Lithuania) . October 2007 - QMC . July 2005 With 50+ to follow… 1 September 2010 Mid-Hudson Valley Linux Users Group 5 http://setiathome.berkeley.edu SETI@home http:/climateprediction.net/ 1 September 2010 Mid-Hudson Valley Linux Users Group 7 http://www.worldcommunitygrid.org/ World Community Grid Active The Clean Energy Project - Phase 2 Help Cure Muscular Dystrophy – Phase 2 Funded and operated by IBM Help Fight Childhood Cancer Help Conquer Cancer Human Proteome Folding - Phase 2 Completed FightAIDS@Home Nutritious Rice for the World Intermittent AfricanClimate@Home Discovering Dengue Drugs - Together - Phase 2 Help Cure Muscular Dystrophy Influenza Antiviral Drug Search Genome Comparison The Clean Energy Project Help Defeat Cancer Discovering Dengue Drugs - Together Human Proteome Folding 1 September 2010 Mid-Hudson Valley Linux Users Group 8 http://einstein.phys.uwm.edu/ or http://einsteinathome.org Einstein@Home 9 Rules and Policies Run BOINC only on authorized computers Run BOINC only on computers that you own, or for which you have obtained the owner’s permission.
    [Show full text]