DOCSLIB.ORG

Implementing the IBM Storwize V7000 Unified Disk System

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Implementing the IBM Storwize V7000 Unified Disk System Front cover Implementing the IBM Storwize V7000 Unified Disk System Consolidates storage and file serving workloads into an integrated system Simplifies management and reduces cost Integrates support for IBM Real-time Compression Jure Arzensek Nancy Kinney Daniel Owen Jorge Quintal Jon Tate ibm.com/redbooks International Technical Support Organization Implementing the IBM Storwize V7000 Unified Disk System April 2014 SG24-8010-01 Note: Before using this information and the product it supports, read the information in “Notices” on page xi. Second Edition (April 2014) This edition applies to Version 7.1.0.5 of the IBM Storwize V7000 code and Version v1.4.2.0-27-2273 of the IBM Storwize V7000 File Module code. © Copyright International Business Machines Corporation 2013, 2014. All rights reserved. Note to U.S. Government Users Restricted Rights -- Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Contents Notices . xi Trademarks . xii Preface . xiii Authors. xiii Now you can become a published author, too! . .xv Comments welcome. xvi Stay connected to IBM Redbooks . xvi Chapter 1. Introduction. 1 1.1 A short history lesson . 2 1.2 About the rest of this book . 3 1.3 Latest release highlights . 4 1.3.1 USB Access Recovery . 4 1.3.2 Call-home installation enhancement. 4 1.3.3 SSH tunnel from the IFS Management Node to the Storwize V7000 Node . 4 Chapter 2. Terminology and file serving concepts . 5 2.1 Terminology for storage and file services . 6 2.1.1 Terminology for random access mass storage . 6 2.1.2 Terminology for file systems and file sharing, file access, and file transfer . 7 2.2 File serving with file sharing and file transfer protocols. 10 2.2.1 The Network File System protocol . 11 2.2.2 The Server Message Block protocol . 13 2.2.3 File Transfer Protocol . 16 2.2.4 Hypertext Transfer Protocol . 17 2.2.5 Secure Copy Protocol . 18 2.2.6 Secure Shell File Transfer Protocol . 18 Chapter 3. Architecture and functions . 19 3.1 High-level overview of Storwize V7000 Unified system . 20 3.1.1 Storwize V7000 Unified storage subsystem: the Storwize V7000 . 20 3.1.2 Storwize V7000 Unified system file server subsystem: The file modules . 20 3.2 Storwize V7000 Unified system configuration. 21 3.2.1 Storwize V7000 Unified storage subsystem configuration . 21 3.2.2 Storwize V7000 Unified system file server subsystem configuration . 22 3.3 Storwize V7000 Unified system storage functions . 23 3.4 Storwize V7000 Unified system file serving functions. 24 3.4.1 Storwize V7000 Unified system file sharing and file transfer protocols. 26 3.4.2 Storwize V7000 Unified system NFS protocol support . 26 3.4.3 Storwize V7000 Unified system SMB and CIFS protocol support. 27 3.4.4 Storwize V7000 Unified system cluster manager . 31 3.4.5 Storwize V7000 Unified system product limits . 33 Chapter 4. Access control for file serving clients . 37 4.1 Authentication and authorization overview . 38 4.1.1 UNIX authentication and authorization . 38 4.1.2 Windows authentication and authorization . 39 4.1.3 UNIX and Windows authentication and authorization. 39 © Copyright IBM Corp. 2013, 2014. All rights reserved. iii 4.2 Methods used for access control . 39 4.2.1 Kerberos . 39 4.2.2 User names and user IDs . 40 4.2.3 Group names and group identifiers in UNIX . 40 4.2.4 Resource names and security identifiers in Windows. 40 4.2.5 UID, GID, and SID mapping in the Storwize V7000 Unified system . 40 4.2.6 Directory services in general. 41 4.2.7 Windows NT 4.0 domain controller and Samba primary domain controller . 41 4.2.8 Lightweight Directory Access Protocol . 41 4.2.9 Microsoft Active Directory . 41 4.2.10 Services for UNIX and Identity Management for UNIX . 42 4.2.11 Network Information Service. 42 4.2.12 Access control list in general. 42 4.2.13 GPFS NFSv4 ACLs . 42 4.2.14 POSIX bits . 42 4.2.15 ACL mapping . 43 4.3 Access control with Storwize V7000 Unified system. 43 4.3.1 Authentication methods supported . 43 4.3.2 Active Directory authentication . 44 4.3.3 Active Directory with Services for UNIX or Identity Management for UNIX . 44 4.3.4 Samba primary domain controller authentication . 45 4.3.5 LDAP authentication . 45 4.3.6 Network Information Service. 45 4.4 Access control limitations and considerations. 46 4.4.1 Authentication limitations . 46 4.4.2 Authorization limitations . 47 Chapter 5. Storage virtualization . 49 5.1 User requirements that storage virtualization can meet . 50 5.2 Storage virtualization terminology . 50 5.2.1 Realizing the benefits of Storwize V7000 Unified storage virtualization . 53 5.2.2 Using internal physical disk drives in the Storwize V7000 Unified system . 53 5.2.3 Using external physical disk drives in the Storwize V7000 Unified system. 55 5.3 Summary. 56 Chapter 6. NAS use cases and differences: SONAS and Storwize Unified. 57 6.1 Use cases for the Storwize V7000 Unified system . 58 6.1.1 Unified storage with both file and block access . 58 6.1.2 Multi-user file sharing with centralized snapshots and backup . 59 6.1.3 Availability and data protection . 60 6.1.4 Information lifecycle management (ILM), hierarchical storage management (HSM), and archiving . 60 6.2 Storwize V7000 Unified system and SONAS . 61 6.2.1 SONAS brief overview . 61 6.2.2 Implementation differences between Storwize V7000 Unified and SONAS . 63 Chapter 7. IBM General Parallel File System ..
Load more

Recommended publications
  • Elastic Storage for Linux on System Z IBM Research & Development Germany
    Peter Münch T/L Test and Development – Elastic Storage for Linux on System z IBM Research & Development Germany Elastic Storage for Linux on IBM System z © Copyright IBM Corporation 2014 9.0 Elastic Storage for Linux on System z Session objectives • This presentation introduces the Elastic Storage, based on General Parallel File System technology that will be available for Linux on IBM System z. Understand the concepts of Elastic Storage and which functions will be available for Linux on System z. Learn how you can integrate and benefit from the Elastic Storage in a Linux on System z environment. Finally, get your first impression in a live demo of Elastic Storage. 2 © Copyright IBM Corporation 2014 Elastic Storage for Linux on System z Trademarks The following are trademarks of the International Business Machines Corporation in the United States and/or other countries. AIX* FlashSystem Storwize* Tivoli* DB2* IBM* System p* WebSphere* DS8000* IBM (logo)* System x* XIV* ECKD MQSeries* System z* z/VM* * Registered trademarks of IBM Corporation The following are trademarks or registered trademarks of other companies. Adobe, the Adobe logo, PostScript, and the PostScript logo are either registered trademarks or trademarks of Adobe Systems Incorporated in the United States, and/or other countries. Cell Broadband Engine is a trademark of Sony Computer Entertainment, Inc. in the United States, other countries, or both and is used under license therefrom. Intel, Intel logo, Intel Inside, Intel Inside logo, Intel Centrino, Intel Centrino logo, Celeron, Intel Xeon, Intel SpeedStep, Itanium, and Pentium are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries.
    [Show full text]
  • CISCO-CONFIG-COPY-MIB: Secure Copy Support
    CISCO-CONFIG-COPY-MIB: Secure Copy Support The CISCO-CONFIG-COPY-MIB: Secure Copy Support feature enhances the CISCO-CONFIG-COPY-MIB by adding support for the copy Cisco IOS EXEC command, and implementing file transfers between a router and server using the secure copy protocol (scp). Feature Specifications for CISCO-CONFIG-COPY-MIB: Secure Copy Support Feature History Release Modification 12.3(2)T This feature was introduced. Supported Platforms Cisco 1710, Cisco 3600 series, Cisco 3725, Cisco 3745, Cisco 6400-NRP series, Cisco 7200, Cisco 7400, Cisco 7500, Cisco AS5300, Cisco AS5350, Cisco AS5400, Cisco AS5850, Cisco CVA 120, Cisco ICS 7750, Cisco ONS 15104, Cisco uBR 7200, Cisco uBR 925 Finding Support Information for Platforms and Cisco IOS Software Images Use Cisco Feature Navigator to find information about platform support and Cisco IOS software image support. Access Cisco Feature Navigator at http://www.cisco.com/go/fn. You must have an account on Cisco.com. If you do not have an account or have forgotten your username or password, click Cancel the login dialog box and follow the instructions that appear. Contents • , page 2 • How to Use Secure Copy Support, page 2 Configuration Examples for Secure Copy Support, page 3 Additional References, page 4 Command Reference, page 5 Americas Headquarters: Cisco Systems, Inc., 170 West Tasman Drive, San Jose, CA 95134-1706 USA © 2007 Cisco Systems, Inc. All rights reserved. CISCO-CONFIG-COPY-MIB: Secure Copy Support Information About CISCO-CONFIG-COPY-MIB Secure Copy Support Information About CISCO-CONFIG-COPY-MIB Secure Copy Support • • CISCO-CONFIG-COPY-MIB Secure Copy Implementation CISCO-CONFIG-COPY-MIB is platform-independent and provides objects to allow the copy functionality.
    [Show full text]
  • IBM Spectrum Scale CSI Driver for Container Persistent Storage
    Front cover IBM Spectrum Scale CSI Driver for Container Persistent Storage Abhishek Jain Andrew Beattie Daniel de Souza Casali Deepak Ghuge Harald Seipp Kedar Karmarkar Muthu Muthiah Pravin P. Kudav Sandeep R. Patil Smita Raut Yadavendra Yadav Redpaper IBM Redbooks IBM Spectrum Scale CSI Driver for Container Persistent Storage April 2020 REDP-5589-00 Note: Before using this information and the product it supports, read the information in “Notices” on page ix. First Edition (April 2020) This edition applies to Version 5, Release 0, Modification 4 of IBM Spectrum Scale. © Copyright International Business Machines Corporation 2020. Note to U.S. Government Users Restricted Rights -- Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. iii iv IBM Spectrum Scale CSI Driver for Container Persistent Storage Contents Notices . vii Trademarks . viii Preface . ix Authors. ix Now you can become a published author, too . xi Comments welcome. xii Stay connected to IBM Redbooks . xii Chapter 1. IBM Spectrum Scale and Containers Introduction . 1 1.1 Abstract . 2 1.2 Assumptions . 2 1.3 Key concepts and terminology . 3 1.3.1 IBM Spectrum Scale . 3 1.3.2 Container runtime . 3 1.3.3 Container Orchestration System. 4 1.4 Introduction to persistent storage for containers Flex volumes. 4 1.4.1 Static provisioning. 4 1.4.2 Dynamic provisioning . 4 1.4.3 Container Storage Interface (CSI). 5 1.4.4 Advantages of using IBM Spectrum Scale storage for containers . 5 Chapter 2. Architecture of IBM Spectrum Scale CSI Driver . 7 2.1 CSI Component Overview. 8 2.2 IBM Spectrum Scale CSI driver architecture.
    [Show full text]
  • Install a VCS Release Key Via the Web Interface and CLI Configuration Example
    Install a VCS Release Key via the Web Interface and CLI Configuration Example Contents Introduction Prerequisites Requirements Components Used Configure Web Interface Release Key Installation Example CLI Release Key Installation Example Verify Web interface Verification of Release Key Installation CLI Interface Verification of Release Key Installation Troubleshoot Introduction This document describes the installation of a release key to a Cisco Video Communication Server (VCS) via the web interface and the Command Line Interface (CLI). Prerequisites Requirements Cisco recommends that you have knowledge of these topics: VCS Installation Have Installed successfully the VCS and applied a valid IP address that is reachable via web interface and or CLI. Have applied for and received a release key valid for the VCS serial number. Have access to the VCS with both root (by CLI) and the admin account by web interface or CLI. Have downloaded a VCS software upgrade image from Cisco.com. Note: Installation guides can be found here: http://www.cisco.com/c/en/us/support/unified- communications/telepresence-video-communication-server-vcs/products-installation-guides- list.html Components Used The information in this document is based on these software versions: VCS Version x8.6.1 and x8.7.3 VCS Control x7.X and x8.X releases VCS Expressway x7.X and x8.X releases PuTTY (terminal emulation software) ---Alternatively, you could use any terminal emulation software that supports SSH such as Secure CRT, TeraTerm and so on. PSCP (PuTTY Secure Copy Protocol client) ---You can use any client that supports SCP. Licensing email with a Release Key or Upgrade Key.
    [Show full text]
  • Pcoip Management Console 20.01 Administrators Guide
    Installing the PCoIP Management Console and Configuring Your System Installing the PCoIP Management Console and Configuring Your System The topics in this section contain information to help you get up and running quickly. Topics that refer to specific versions of PCoIP Management Console will be identified by the release number. Migrating, upgrading, or downgrading from other versions If you are migrating to a new PCoIP Management Console version see Migrating to a Newer Version. If you need to downgrade endpoints from firmware 5.0 or later to 4.8, see Downgrading Endpoints to Firmware 4.x. © 2020 Teradici 1 Installing PCoIP Management Console using vSphere Installing PCoIP Management Console using vSphere Once you have downloaded PCoIP Management Console, deploy it as an Open Virtual Appliance (OVA) using vSphere Client. To install PCoIP Management Console using vSphere Client: 1. Download the latest PCoIP Management Console OVA file to a location accessible from your vSphere Client. 2. Log in to your vSphere Client. 3. If you have more than one ESXi host, select the desired ESXi node; otherwise, there is no need to select a node. 4. From the vSphere client’s File menu, select Deploy OVF Template. 5. In the Source window, click Browse, select the PCoIP Management Console’s OVA file, click Open and Next. 6. In the OVF Template Details window, view the information and click Next. 7. In the End User License Agreement window, read the EULA information, click Accept and then Next. 8. In the Name and Location window, enter the name for your PCoIP Management Console and click Next.
    [Show full text]
  • OSI Model and Network Protocols
    CHAPTER4 FOUR OSI Model and Network Protocols Objectives 1.1 Explain the function of common networking protocols . TCP . FTP . UDP . TCP/IP suite . DHCP . TFTP . DNS . HTTP(S) . ARP . SIP (VoIP) . RTP (VoIP) . SSH . POP3 . NTP . IMAP4 . Telnet . SMTP . SNMP2/3 . ICMP . IGMP . TLS 134 Chapter 4: OSI Model and Network Protocols 4.1 Explain the function of each layer of the OSI model . Layer 1 – physical . Layer 2 – data link . Layer 3 – network . Layer 4 – transport . Layer 5 – session . Layer 6 – presentation . Layer 7 – application What You Need To Know . Identify the seven layers of the OSI model. Identify the function of each layer of the OSI model. Identify the layer at which networking devices function. Identify the function of various networking protocols. Introduction One of the most important networking concepts to understand is the Open Systems Interconnect (OSI) reference model. This conceptual model, created by the International Organization for Standardization (ISO) in 1978 and revised in 1984, describes a network architecture that allows data to be passed between computer systems. This chapter looks at the OSI model and describes how it relates to real-world networking. It also examines how common network devices relate to the OSI model. Even though the OSI model is conceptual, an appreciation of its purpose and function can help you better understand how protocol suites and network architectures work in practical applications. The OSI Seven-Layer Model As shown in Figure 4.1, the OSI reference model is built, bottom to top, in the following order: physical, data link, network, transport, session, presentation, and application.
    [Show full text]
  • Policy and Procedures
    Policy and Procedures PEER FORUM I: DISK IMAGING December 7-8, 2017 at The Museum of Modern Art The following notes came out of Peer Forum I: Disk Imaging, a discussion as part of the Media Conservation Initiative ​ at MoMA. These notes represent the views of the speakers and participants who attended this meeting. The following notes came out of Peer Forum I: Disk Imaging, a discussion as part of the Media Conservation Initiative ​ at MoMA. These notes represent the views of the speakers and participants who attended this meeting. Contributors Reinhard Bek, Conservator of Contemporary Art, Bek & Frohnert LLC ​ Amy Brost, Assistant Media Conservator, The Museum of Modern Art ​ Euan Cochrane (Speaker), Digital Preservation Manager, Yale University Library ​ ​ Eddy Colloton, Assistant Conservator specializing in Electronic Media, Denver Art Museum ​ Deena Engel (Moderator), Clinical Professor, Director of the Program in Digital Humanities and Social ​ ​ ​ Science; Department of Computer Science, Courant Institute of Mathematical Sciences, New York University Dragan Espenschied (Speaker), Preservation Director, Rhizome ​ ​ Patricia Falcão, Time-Based Media Conservator, Tate ​ Jonathan Farbowitz, Fellow in the Conservation of Computer-Based Art, The Solomon R. Guggenheim ​ Museum Briana Feston-Brunet, Variable Media Conservator, Hirshhorn Museum & Sculpture Garden ​ Dan Finn, Media Conservator, Smithsonian American Art Museum ​ Ben Fino-Radin, Founder, Small Data Industries ​ Flaminia Fortunato, Andrew W. Mellon Fellow in Media Conservation,
    [Show full text]
  • File Systems and Storage
    FILE SYSTEMS AND STORAGE On Making GPFS Truly General DEAN HILDEBRAND AND FRANK SCHMUCK Dean Hildebrand manages the PFS (also called IBM Spectrum Scale) began as a research project Cloud Storage Software team that quickly found its groove supporting high performance comput- at the IBM Almaden Research ing (HPC) applications [1, 2]. Over the last 15 years, GPFS branched Center and is a recognized G expert in the field of distributed out to embrace general file-serving workloads while maintaining its original and parallel file systems. He pioneered pNFS, distributed design. This article gives a brief overview of the origins of numer- demonstrating the feasibility of providing ous features that we and many others at IBM have implemented to make standard and scalable access to any file GPFS a truly general file system. system. He received a BSc degree in computer science from the University of British Columbia Early Days in 1998 and a PhD in computer science from Following its origins as a project focused on high-performance lossless streaming of multi- the University of Michigan in 2007. media video files, GPFS was soon enhanced to support high performance computing (HPC) [email protected] applications, to become the “General Parallel File System.” One of its first large deployments was on ASCI White in 2002—at the time, the fastest supercomputer in the world. This HPC- Frank Schmuck joined IBM focused architecture is described in more detail in a 2002 FAST paper [3], but from the outset Research in 1988 after receiving an important design goal was to support general workloads through a standard POSIX inter- a PhD in computer science face—and live up to the “General” term in the name.
    [Show full text]
  • Symantec Web Security Service Policy Guide
    Web Security Service Policy Guide Version 6.10.4.1/OCT.12.2018 Symantec Web Security Service/Page 2 Policy Guide/Page 3 Copyrights Copyright © 2018 Symantec Corp. All rights reserved. Symantec, the Symantec Logo, the Checkmark Logo, Blue Coat, and the Blue Coat logo are trademarks or registered trademarks of Symantec Corp. or its affiliates in the U.S. and other coun- tries. Other names may be trademarks of their respective owners. This document is provided for informational purposes only and is not intended as advertising. All warranties relating to the information in this document, either express or implied, are disclaimed to the maximum extent allowed by law. The information in this document is subject to change without notice. THE DOCUMENTATION IS PROVIDED "AS IS" AND ALL EXPRESS OR IMPLIED CONDITIONS, REPRESENTATIONS AND WARRANTIES, INCLUDING ANY IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NON-INFRINGEMENT, ARE DISCLAIMED, EXCEPT TO THE EXTENT THAT SUCH DISCLAIMERS ARE HELD TO BE LEGALLY INVALID. SYMANTEC CORPORATION SHALL NOT BE LIABLE FOR INCIDENTAL OR CONSEQUENTIAL DAMAGES IN CONNECTION WITH THE FURNISHING, PERFORMANCE, OR USE OF THIS DOCUMENTATION. THE INFORMATION CONTAINED IN THIS DOCUMENTATION IS SUBJECT TO CHANGE WITHOUT NOTICE. Symantec Corporation 350 Ellis Street Mountain View, CA 94043 www.symantec.com Policy Guide/Page 4 Symantec Web Security Service Policy Guide The Symantec Web Security Service solutions provide real-time protection against web-borne threats. As a cloud-based product, the Web Security Service leverages Symantec's proven security technology as well as the WebPulse™ cloud com- munity of over 75 million users.
    [Show full text]
  • Symantec Web Security Service Policy Guide
    Web Security Service Policy Guide Revision: NOV.07.2020 Symantec Web Security Service/Page 2 Policy Guide/Page 3 Copyrights Broadcom, the pulse logo, Connecting everything, and Symantec are among the trademarks of Broadcom. The term “Broadcom” refers to Broadcom Inc. and/or its subsidiaries. Copyright © 2020 Broadcom. All Rights Reserved. The term “Broadcom” refers to Broadcom Inc. and/or its subsidiaries. For more information, please visit www.broadcom.com. Broadcom reserves the right to make changes without further notice to any products or data herein to improve reliability, function, or design. Information furnished by Broadcom is believed to be accurate and reliable. However, Broadcom does not assume any liability arising out of the application or use of this information, nor the application or use of any product or circuit described herein, neither does it convey any license under its patent rights nor the rights of others. Policy Guide/Page 4 Symantec WSS Policy Guide The Symantec Web Security Service solutions provide real-time protection against web-borne threats. As a cloud-based product, the Web Security Service leverages Symantec's proven security technology, including the WebPulse™ cloud community. With extensive web application controls and detailed reporting features, IT administrators can use the Web Security Service to create and enforce granular policies that are applied to all covered users, including fixed locations and roaming users. If the WSS is the body, then the policy engine is the brain. While the WSS by default provides malware protection (blocks four categories: Phishing, Proxy Avoidance, Spyware Effects/Privacy Concerns, and Spyware/Malware Sources), the additional policy rules and options you create dictate exactly what content your employees can and cannot access—from global allows/denials to individual users at specific times from specific locations.
    [Show full text]
  • Langley Aerospace Test Highlights 1990
    Langley Aerospace 4" Test Highlights I _ r-4 r_ i-j S_ L_ .Z: i:" 7 >- t,/ ,. 1990 Langley Research Center NASA Technical Memorandum 104090 ORIGINAL PAGE AND Wt-fTTE _:"-_TO_PAPH Langley Aerospace Test Highlights 1990 National Aeronautics and Space Administration Langley Research Center Langley Research Center NASA Technical Memorandum 104090 Hampton, Virginia 23665-5225 k ¸ Foreword The role of the NASA Langley Research Center is to perform basic and applied research necessary for the advancement of aeronautics and spaceflight, to generate new and advanced concepts for the accomplishment of related national goals, and to provide research advice, technological support, and assistance to other NASA installations, other government agencies, and industry. This report highlights some of the significant tests that were performed during calendar year 1990 in the NASA Langley Research Center test facilities, a number of which are unique in the world. The report illustrates both the broad range of the research and technology activities at the NASA Langley Research Center and the contributions of this work toward maintaining United States leadership in aeronautics and space research. Other highlights of Langley research and technology for 1990 are described in Research and Technology 1990-- Lan,gley Research Center. Further information concerning both reports is available from the Office of the Chief Scientist, Mail Stop l OS-A, NASA Langley Research Center, Hampton, Virginia 23665 (804-864-6062). Richard H. Petersen Director °o° PRECEDING PAGE BLANK NOT FILMED 111 Availability Information For additional information on any highlight, contact one of the individuals identified with the highlight. This individual is either a member or a leader of the research group.
    [Show full text]
  • The Open Virtual Machine Format Whitepaper for OVF Specification
    The Open Virtual Machine Format Whitepaper for OVF Specification version 0.9 OVF Whitepaper 0.9 VMware, Inc. 3401 Hillview Ave., Palo Alto CA, 94304 USA Tel 877-486-9273 Fax 650-427-5001 www.vmware.com XenSource, Inc. 2300 Geng Road, Suite 2500, Palo Alto, CA 94303 www.xensource.com Copyright © VMware, Inc. and XenSource, Inc. All rights reserved. VMware, the VMware “boxes” logo and design, Virtual SMP and VMotion are registered trademarks or trademarks of VMware, Inc. in the United States and/or other jurisdictions. Xen, XenSource, the “Circle Xen” logo and derivatives thereof are registered trademarks or trademarks of XenSource, Inc. in the United States and other countries. Microsoft, Windows and Windows NT are registered trademarks of Microsoft Corporation. Linux is a registered trademark of Linus Torvalds. All other marks and names mentioned herein may be trademarks of their respective companies. No part of this specification (whether in hardcopy or electronic form) may be reproduced, stored in a retrieval system, or transmitted, in any form or by any means, electronic, mechanical, photocopying, recording, or otherwise, without the prior written permission of VMware, Inc. (VMware), and XenSource, Inc. (XenSource) except as otherwise permitted under copyright law or the terms of that certain Teaming and Non-Disclosure Agreement between VMware and XenSource dated March 23, 2007, as amended from time to time. Please note that the content in this specification is protected under copyright law even if it is not distributed with software
    [Show full text]