DOCSLIB.ORG

The X-Bone & Its Virtual Internet Architecture

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
The X-Bone & Its Virtual Internet Architecture The X-Bone & its Virtual Internet Architecture 10 Years Later Joe Touch, Greg Finn, Lars Eggert, Amy Hughes and Yu-Shun Wang Workshop on Overlay and Network Virtualization 16th GI/ITG Conference on Kommunikation in Verteilten Systemen Kassel, Germany March 6, 2009 March 6, 2009 Copyright 2009, USC/ISI. All rights reserved. 1 History X-Bone was a series of research projects at USC/ISI 1997-2005+ initial funding from DARPA, follow-on funding from the NSF http://www.isi.edu/xbone/ key results an architecture (the “Virtual Internet” architecture) a deployment/management system (the “X-Bone”) follow-on work using virtual nets March 6, 2009 Copyright 2009, USC/ISI. All rights reserved. 2 X-Bone Overlay System Web GUI Multiple views IP Base Star Overlay B A C D ring-ovl star-ovl B B A A Ring Overlay C D C D xd GUI Overlay Manager Resource Base IPv4 Resource Daemon Daemon Network Resource Daemon link host router X-Bone system Automated monitoring March 6, 2009 Copyright 2009, USC/ISI. All rights reserved. 3 X-Bone Timeline 1997 – first whitepaper 2001-2003 – NetFS (NSF) 1998-2001 – X-Bone (DARPA) File system configuration of IP overlays with revisitation, network properties recursion (LISP) 2002-2005 – X-Tend (NSF) 2000 – running code (FreeBSD, X-Bone for testbed uses Linux) 2003-2005 – DataRouter (int.) 2000 – application deployment Support for overlay P2P 2001 – TetherNet “NAT-buster” forwarding to support demos 2005-2006 – Agile Tunnels (NSA) 2001-2004 – DynaBone Partial overlays for DDOS safety (DARPA) 2006-2009 – RNA (NSF) 800-way spread-spectrum Extending X-Bone Choices model parallel overlays to general protocol stack 15-level deep overlays architecture March 6, 2009 Copyright 2009, USC/ISI. All rights reserved. 4 Creating a Ring Request sin eql Ring Ovl. udel cos div sec isipc2 bbn Internet March 6, 2009 Copyright 2009, USC/ISI. All rights reserved. 5 Virtual Internet – Why “network equivalent of virtual memory” protection separate topology, optionally secured test + deploy new protocol/service sharing increase utility of infrastructure abstraction adapt topology to application March 6, 2009 Copyright 2009, USC/ISI. All rights reserved. 6 Virtual Internet – What network = hosts + routers + links virtual network = virtual host → packet src/sink + virtual router → packet gateway + virtual link → tunnel X over Y virtual Internet – ”network of networks” use Internet as physical media virtual virtual Internet IP link IP network IP payload create virtual link & network layers header header header strong L2 vs. weak L3 host model a virtual Internet should look exactly like the real thing “if an app can know it runs in a VI, we did it wrong March 6, 2009 Copyright 2009, USC/ISI. All rights reserved. 7 Feature – Recursion virtual Internets on top of virtual Internets our litmus test: system should be able to do recursive VI-in-VI without hacks recursion has real uses cases e.g., allows transparent reconfiguration change outer VI w/o affecting inner fault tolerance, basis for DynaBone also allows VI “embedding” “router is a network inside” March 6, 2009 Copyright 2009, USC/ISI. All rights reserved. 8 Feature – Concurrency one node participates in multiple virtual Internets at the same time basis for isolation & abstraction bind different apps/VMs to different VIs on the same physical node March 6, 2009 Copyright 2009, USC/ISI. All rights reserved. 9 Feature – Revisitation one node participates in the same virtual Internet but multiple times allows creation of VIs larger than physical resources fully decouples virtual from physical topologies March 6, 2009 Copyright 2009, USC/ISI. All rights reserved. 10 Feature – Security security in the Virtual Internet architecture is a virtual link property decoupled from topology transparently coexists with end-to-end security inside the VI transparently coexists with security underneath a VI IPsec tunnel mode IPIP tunnel + IPsec transport mode base IP IPsec VPN IP data base IP IPsec VPN IP data #2 #1 IPIP tunnels + IPsec transport mode modular tunnel mode equivalent huge IETF debate around 2000 (draft-touch-ipsec-vpn-05.txt) March 6, 2009 Copyright 2009, USC/ISI. All rights reserved. 11 The X-Bone System deployment + management system for VIs programs → standardized API humans → web interface virtual network description language high-level: express virtual topology + services XML collaborating, distributed management daemons multicast expanding-ring discovery distributed resource reservation instantiate + manage virtual network non-goals: topology optimization, non-IP VIs, … March 6, 2009 Copyright 2009, USC/ISI. All rights reserved. 12 X-Bone Status current release: 3.2 mature: 10 years of open source availability platforms: FreeBSD, Linux unofficial: NetBSD, Cisco widely used (by 2003): UCL, UPenn, Aerospace, DOD Canada, Sinica Taiwan + more March 6, 2009 Copyright 2009, USC/ISI. All rights reserved. 13 Follow-On Work at USC/ISI March 6, 2009 Copyright 2009, USC/ISI. All rights reserved. 14 DynaBone (~2001-2003) parallel inner virtual networks = algorithmic & protocol diversity spread-spectrum multiplexer, wrapped inside outer virtual network Innerlays Outerlay AES + SHA1 + BGP MUX 3DES + MD5 + RIP MUX MD5CAST128X auth +/ staticstatic Base network March 6, 2009 Copyright 2009, USC/ISI. All rights reserved. 15 TetherNet (~2001-2004) issue: firewalls, NATs, clueless ISPs broken end-to-end connectivity solution: relocate real Internet subnet real = routable IP + DNS + no fw + … tunnel subnet from anchor router totether router at remote site Internet Internet NAT March 6, 2009 Copyright 2009, USC/ISI. All rights reserved. 16 Other Related Projects X-Tend (~2003-2007?) maintain + extend X-Bone as tool for research + education GeoNet (~2000-2002) geographically-addressed overlays NetFS (~2002-2004?) access control for the network stack via a pseudo file system March 6, 2009 Copyright 2009, USC/ISI. All rights reserved. 17 .
Load more

Recommended publications
  • QEMU Version 4.2.0 User Documentation I
    QEMU version 4.2.0 User Documentation i Table of Contents 1 Introduction ::::::::::::::::::::::::::::::::::::: 1 1.1 Features :::::::::::::::::::::::::::::::::::::::::::::::::::::::: 1 2 QEMU PC System emulator ::::::::::::::::::: 2 2.1 Introduction :::::::::::::::::::::::::::::::::::::::::::::::::::: 2 2.2 Quick Start::::::::::::::::::::::::::::::::::::::::::::::::::::: 2 2.3 Invocation :::::::::::::::::::::::::::::::::::::::::::::::::::::: 3 2.3.1 Standard options :::::::::::::::::::::::::::::::::::::::::: 3 2.3.2 Block device options :::::::::::::::::::::::::::::::::::::: 12 2.3.3 USB options:::::::::::::::::::::::::::::::::::::::::::::: 23 2.3.4 Display options ::::::::::::::::::::::::::::::::::::::::::: 23 2.3.5 i386 target only::::::::::::::::::::::::::::::::::::::::::: 30 2.3.6 Network options :::::::::::::::::::::::::::::::::::::::::: 31 2.3.7 Character device options:::::::::::::::::::::::::::::::::: 38 2.3.8 Bluetooth(R) options ::::::::::::::::::::::::::::::::::::: 42 2.3.9 TPM device options :::::::::::::::::::::::::::::::::::::: 43 2.3.10 Linux/Multiboot boot specific ::::::::::::::::::::::::::: 44 2.3.11 Debug/Expert options ::::::::::::::::::::::::::::::::::: 45 2.3.12 Generic object creation :::::::::::::::::::::::::::::::::: 54 2.3.13 Device URL Syntax ::::::::::::::::::::::::::::::::::::: 66 2.4 Keys in the graphical frontends :::::::::::::::::::::::::::::::: 69 2.5 Keys in the character backend multiplexer ::::::::::::::::::::: 69 2.6 QEMU Monitor ::::::::::::::::::::::::::::::::::::::::::::::: 70 2.6.1 Commands :::::::::::::::::::::::::::::::::::::::::::::::
    [Show full text]
  • How to Configure the NFX250
    How to Configure the NFX250 Published 2021-07-12 ii Juniper Networks, Inc. 1133 Innovation Way Sunnyvale, California 94089 USA 408-745-2000 www.juniper.net Juniper Networks, the Juniper Networks logo, Juniper, and Junos are registered trademarks of Juniper Networks, Inc. in the United States and other countries. All other trademarks, service marks, registered marks, or registered service marks are the property of their respective owners. Juniper Networks assumes no responsibility for any inaccuracies in this document. Juniper Networks reserves the right to change, modify, transfer, or otherwise revise this publication without notice. How to Configure the NFX250 Copyright © 2021 Juniper Networks, Inc. All rights reserved. The information in this document is current as of the date on the title page. YEAR 2000 NOTICE Juniper Networks hardware and software products are Year 2000 compliant. Junos OS has no known time-related limitations through the year 2038. However, the NTP application is known to have some difficulty in the year 2036. END USER LICENSE AGREEMENT The Juniper Networks product that is the subject of this technical documentation consists of (or is intended for use with) Juniper Networks software. Use of such software is subject to the terms and conditions of the End User License Agreement ("EULA") posted at https://support.juniper.net/support/eula/. By downloading, installing or using such software, you agree to the terms and conditions of that EULA. iii Table of Contents About This Guide | ix 1 Overview NFX250 Overview | 2 JDM
    [Show full text]
  • Multihoming with ILNP in Freebsd
    MULTIHOMING WITH ILNP IN FREEBSD Bruce Simpson A Thesis Submitted for the Degree of PhD at the University of St Andrews 2016 Full metadata for this item is available in St Andrews Research Repository at: http://research-repository.st-andrews.ac.uk/ Please use this identifier to cite or link to this item: http://hdl.handle.net/10023/8681 This item is protected by original copyright This item is licensed under a Creative Commons Licence Multihoming with ILNP in FreeBSD Thesis by Bruce Simpson In Partial Fulfillment of the Requirements for the Degree of Doctor of Philosophy University of St Andrews School of Computer Science 2016 (Defended 17th December 2015) Declaration I, Bruce Simpson, certify that this thesis, which is approximately 40,000 words in length, has been written by me, that it is the record of work carried out by me, or principally by myself in collaboration with others as acknowledged, and that it has not been submitted in any previous application for a higher degree. I was admitted as a research student in October, 2011 and as a candidate for the degree of Doctor of Philosophy in November, 2014; the higher study for which this is a record was carried out in the University of St Andrews between 2011 and 2015. Date ................ Signature of candidate ............................... I hereby certify that the candidate has fulfilled the conditions of the Resolution and Regulations appropriate for the degree of Doctor of Philosophy in the University of St Andrews and that the candidate is qualified to submit this thesis in application for that degree.
    [Show full text]
  • IP Flow Mobility Support for Proxy Mobile Ipv6 Based Networks
    UNIVERSIT A` DEGLI STUDI DI PADOVA Facolt`adi Ingegneria Corso di Laurea in Ingegneria delle Telecomunicazioni Tesi di Laurea IP Flow Mobility support for Proxy Mobile IPv6 based networks Relatori: Prof. Michele Zorzi Dott. Telemaco Melia Candidato: Fabio Giust Anno accademico 2010-2011 Summary The ability of offloading selected IP data traffic from 3G to WLAN access networks is considered a key feature in the upcoming 3GPP specifications, being the main goal to alleviate data congestion in cellular networks while delivering a positive user experience. Lately, the 3GPP has adopted solutions that enable mobility of IP-based wireless devices relocating mobility functions from the terminal to the network. To this end, the IETF has standardized Proxy Mobile IPv6 (PMIPv6), a protocol capable to hide often complex mobility procedures from the mobile devices. This thesis, in line with the mentioned offload requirement, further extends PMI- Pv6 to support dynamic IP flow mobility management across access wireless net- works according to operator policies. In this work, we assess the feasibility of the proposed solution and provide an experimental analysis based on a prototype net- work setup, implementing the PMIPv6 protocol and the related enhancements for flow mobility support. La capacit`adi spostare flussi IP da una rete di accesso 3G ad una di tipo WLAN `econsiderata una caratteristica chiave nelle specifiche future di 3GPP, essendo il principale metodo per alleviare la congestione nelle reti cellulari mantenendo al contempo una ragionevole qualit`apercepita dall’utente. Recentemente, 3GPP ha adottato soluzioni di mobilit`aper dispositivi con accesso radio basato su IP, tra- slando le funzioni di supporto dal terminale alla rete, e, a questo scopo, IETF ha standardizzato Proxy Mobile IPv6 (PMIPv6), un protocollo studiato per nascondere le procedure di mobilit`aai sistemi mobili.
    [Show full text]
  • Ipv6 for Ipv4 Experts
    IPv6 for IPv4 Experts Yar Tikhiy December 31, 2013 DRAFT License cbnd This draft is licensed under the Creative Commons Attribution-NonCommercial- NoDerivs license. DRAFT 1 Contents Preface 9 1 Defining the Problem 11 2 IPv6 Address 19 2.1 TheIPv6AddressLengthIssue . 19 2.2 TextRepresentationofanIPv6Address . 29 2.3 IPv6AddressTypes ....................... 38 2.4 IPv6AddressScopeandZone . 42 2.5 Well-known Applications of IPv6 Link-local Addresses . 59 2.6 IPv6UnicastAddressStructure . 61 2.7 IPv6InterfaceIDsandEUI-64. 66 2.8 IPv6MulticastAddressStructure . 72 2.9 IPv6 Multicast Addressing Extensions Based on Unicast Ad- dresses . 78 2.10 Site-Local Address Problem and Its Solution . 85 2.11 IPv6AddressesinDNS. 89 3IPv6Packet 92 3.1 IPv6 Packet Layout . 92 3.2 IPv6Header............................ 96 3.3 ExtensionHeaders ........................ 104 3.3.1 A Header That Isn’t There: No Next Header . 104 3.3.2 IPv6DRAFT Options . 105 3.3.3 RoutingHeader ..................... 111 3.3.4 Fragment Header. IPv6 Fragmentation and Reassembly 119 3.3.5 IPSecurityHeaders. 134 3.3.6 ExtensionHeaderOrdering . 142 3.3.7 UnsupportedHeaderHandling. 144 2 CONTENTS 3 4 IPv6 in the Protocol Stack 147 4.1 Link-Level Encapsulation . 147 4.1.1 Ethernet . 148 4.1.2 PPP . 151 4.2 InteractionwithUpper-LayerProtocols . 158 4.3 Control . 162 5 Neighbor Discovery Protocol 172 5.1 Neighbor Discovery and IPv6 Address Resolution . 172 5.2 TheHost,theLink,andtheSubnetinIPv6 . 207 5.3 IPv6AddressingModesRevised. Anycast . 239 5.4 IPv6Autoconfiguration. 247 5.4.1 Interface ID Selection and Duplicate Address Detection 247 5.4.2 Prefix and Router Discovery . 255 6 Advanced IPv6 277 6.1 AnycastingtotheRoutersoftheSubnet . 277 6.2 PrivacyExtensionsforSLAAC .
    [Show full text]
  • Appliance Quick Start Guide V7.0
    Appliance Quick Start Guide v7.0 Copyright © 2002 - 2010 Loadbalancer.org Ltd 1 Table of Contents Loadbalancer.org terminology......................................................................................................................4 What is a virtual IP address?..................................................................................................................4 What is a floating IP address?................................................................................................................4 What are your objectives?...........................................................................................................................5 What is the difference between a one-arm and a two-arm configuration?...................................................5 What are the different load balancing methods supported?.........................................................................6 High-availability configuration of two Loadbalancer.org appliances........................................................8 Network diagram: One-Arm – DR Direct Routing (clustered pair) ..........................................................8 Network diagram: Two-Arm - NAT Network Address Translation (clustered pair)...................................9 Network diagram: One-Arm – DR Direct Routing (single unit)..............................................................10 Network diagram: Two-Arm - NAT Network Address Translation (single unit).......................................11 Un-packing and setting up the
    [Show full text]
  • Virtualization Guide Virtualization Guide SUSE Linux Enterprise Server 15 SP3
    SUSE Linux Enterprise Server 15 SP3 Virtualization Guide Virtualization Guide SUSE Linux Enterprise Server 15 SP3 This guide describes virtualization technology in general. It introduces libvirt—the unied interface to virtualization—and provides detailed information on specic hypervisors. Publication Date: September 24, 2021 SUSE LLC 1800 South Novell Place Provo, UT 84606 USA https://documentation.suse.com Copyright © 2006– 2021 SUSE LLC and contributors. All rights reserved. Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or (at your option) version 1.3; with the Invariant Section being this copyright notice and license. A copy of the license version 1.2 is included in the section entitled “GNU Free Documentation License”. For SUSE trademarks, see https://www.suse.com/company/legal/ . All other third-party trademarks are the property of their respective owners. Trademark symbols (®, ™ etc.) denote trademarks of SUSE and its aliates. Asterisks (*) denote third-party trademarks. All information found in this book has been compiled with utmost attention to detail. However, this does not guarantee complete accuracy. Neither SUSE LLC, its aliates, the authors nor the translators shall be held liable for possible errors or the consequences thereof. Contents Preface xvii 1 Available documentation xvii 2 Improving the documentation xvii 3 Documentation conventions xviii 4 Support xx Support statement for SUSE Linux Enterprise Server xx • Technology previews
    [Show full text]
  • QEMU Version 4.1.0 User Documentation I
    QEMU version 4.1.0 User Documentation i Table of Contents 1 Introduction ::::::::::::::::::::::::::::::::::::: 1 1.1 Features :::::::::::::::::::::::::::::::::::::::::::::::::::::::: 1 2 QEMU PC System emulator ::::::::::::::::::: 2 2.1 Introduction :::::::::::::::::::::::::::::::::::::::::::::::::::: 2 2.2 Quick Start::::::::::::::::::::::::::::::::::::::::::::::::::::: 2 2.3 Invocation :::::::::::::::::::::::::::::::::::::::::::::::::::::: 3 2.3.1 Standard options :::::::::::::::::::::::::::::::::::::::::: 3 2.3.2 Block device options :::::::::::::::::::::::::::::::::::::: 12 2.3.3 USB options:::::::::::::::::::::::::::::::::::::::::::::: 21 2.3.4 Display options ::::::::::::::::::::::::::::::::::::::::::: 22 2.3.5 i386 target only::::::::::::::::::::::::::::::::::::::::::: 28 2.3.6 Network options :::::::::::::::::::::::::::::::::::::::::: 29 2.3.7 Character device options:::::::::::::::::::::::::::::::::: 37 2.3.8 Bluetooth(R) options ::::::::::::::::::::::::::::::::::::: 41 2.3.9 TPM device options :::::::::::::::::::::::::::::::::::::: 42 2.3.10 Linux/Multiboot boot specific ::::::::::::::::::::::::::: 43 2.3.11 Debug/Expert options ::::::::::::::::::::::::::::::::::: 43 2.3.12 Generic object creation :::::::::::::::::::::::::::::::::: 52 2.3.13 Device URL Syntax ::::::::::::::::::::::::::::::::::::: 63 2.4 Keys in the graphical frontends :::::::::::::::::::::::::::::::: 66 2.5 Keys in the character backend multiplexer ::::::::::::::::::::: 67 2.6 QEMU Monitor ::::::::::::::::::::::::::::::::::::::::::::::: 67 2.6.1 Commands :::::::::::::::::::::::::::::::::::::::::::::::
    [Show full text]
  • Appliance Quick Start Guide V7.4
    Appliance Quick Start Guide v7.4 Copyright © 2002 – 2013 Loadbalancer.org, Inc. Table of Contents Loadbalancer.org Terminology.....................................................................................................................4 What is a Virtual IP Address?.................................................................................................................4 What is a Floating IP Address?...............................................................................................................4 What are Your Objectives?.......................................................................................................................... 5 What is the Difference Between a One-Arm and a Two-Arm Configuration?...............................................6 What Load Balancing Methods are Supported?..........................................................................................6 Direct Routing (DR)................................................................................................................................ 8 Network Address Translation (NAT)........................................................................................................9 Source Network Address Translation (SNAT) ......................................................................................10 High-Availability Configuration of two Loadbalancer.org Appliances..........................................................11 Clustered Pair Configuration Methods..................................................................................................11
    [Show full text]
  • High Speed Networks Study Guide
    High-Speed Networks 1 High Speed Networks Study Guide Dr. Wanlei Zhou and Dr. Weijia Jia High-Speed Networks 2 Contents 0. UNIT OUTLINE .................................................................................................9 0.1. Objective 9 0.2. Text Books 9 0.2.1. Main Text Book 9 0.2.2. Reference Books 9 0.3. Assessment 9 1. INTRODUCTION: THE NEED FOR SPEED AND QUALITY OF SERVICE...10 1.1. Study Points 10 1.2. A Brief Networking History 10 1.3. Milestones 11 1.4. The Need for High Speed and Quality of Service (QoS) 12 1.5. Advanced TCP/IP and ATM Networks 12 1.5.1. IP-based Internet 13 1.5.2. ATM Networks 13 1.6. Review Questions 13 2. DATA NETWORKS AND COMMUNICATION PROTOCOLS........................15 2.1. Study Points 15 2.2. Packet-Switch Networks 15 2.2.1. Basic Concepts 15 2.2.2. Switching and Routing Techniques 16 2.2.3. X.25 16 2.3. Frame Relay Networks 17 2.3.1. Why Frame Relay? 17 2.3.2. Frame Relay Architecture 18 2.4. Congestion in Data Network and Internets 18 2.4.1. Effect of Congestion 19 2.4.2. Congestion Control 19 2.4.3. Traffic Management 20 High-Speed Networks 3 2.5. Communication Protocol Architectures 20 2.5.1. The OSI Protocol Architecture 20 2.5.2. Internet Architecture 21 2.5.3. Bridges and Routers 22 2.6. Review Questions 23 3. FAST ETHERNET: IEEE 802.3 100BASE-T ..................................................24 3.1. Study Points 24 3.2. Classical Ethernet 24 3.2.1.
    [Show full text]
  • The X-Bone & Its Virtual Internet Architecture 10 Years Later
    The X-Bone & its Virtual Internet Architecture 10 Years Later Lars Eggert Dagstuhl Seminar on Network Virtualization for the Future Internet Schloss Dagstuhl, Germany September 18-19, 2008 September 18, 2008 Lars Eggert | Nokia © 2008 1 Talk Outline history Virtual Internets why what architecture highlights related projects at ISI (time permitting…) X-Bone, DynaBone, TetherNet September 18, 2008 Lars Eggert | Nokia © 2008 2 History X-Bone was a series of research projects at USC/ISI X-Bone, DynaBone, TetherNet, X-Tend, NetFS, GeoNet, … 1997-2005+ initial funding from DARPA, follow-on funding from the NSF http://www.isi.edu/xbone/ key results an architecture (the “Virtual Internet” architecture) a deployment/management system (the “X-Bone”) follow-on work using virtual nets: DynaBone spread-spectrum virtual networks TetherNet rent real Internet behind firewall + NAT GeoNet geographically-routed virtual networks September 18, 2008 Lars Eggert | Nokia © 2008 3 Prior & Related Work new services & protocols Cronus, M/6/Q/A-Bone multi/other layers Cronus, Supranet, MorphNet, VANs partial solutions VPN, VNS, RON, Detour, PPVPN, SOS virtualization, revisitation, recursion X-Bone, Spawning, Netlab/Emulab OS virtualization VMware, jails, vserver, XEN, PlanetLab September 18, 2008 Lars Eggert | Nokia © 2008 4 Virtual Internet – Why “network equivalent of virtual memory” protection separate topology, optionally secured test + deploy new protocol/service sharing increase utility of infrastructure abstraction adapt topology to application September 18, 2008 Lars Eggert | Nokia © 2008 5 Virtual Internet – What network = hosts + routers + links virtual network = virtual host → packet src/sink + virtual router → packet gateway + virtual link → tunnel X over Y virtual Internet – ”network of networks” use Internet as physical media virtual virtual Internet IP link IP network IP payload create virtual link & network layers header header header strong L2 vs.
    [Show full text]
  • Red Hat Openstack Platform 13 Instances and Images Guide
    Red Hat OpenStack Platform 13 Instances and Images Guide Managing Instances and Images Last Updated: 2021-09-24 Red Hat OpenStack Platform 13 Instances and Images Guide Managing Instances and Images OpenStack Team [email protected] Legal Notice Copyright © 2021 Red Hat, Inc. The text of and illustrations in this document are licensed by Red Hat under a Creative Commons Attribution–Share Alike 3.0 Unported license ("CC-BY-SA"). An explanation of CC-BY-SA is available at http://creativecommons.org/licenses/by-sa/3.0/ . In accordance with CC-BY-SA, if you distribute this document or an adaptation of it, you must provide the URL for the original version. Red Hat, as the licensor of this document, waives the right to enforce, and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent permitted by applicable law. Red Hat, Red Hat Enterprise Linux, the Shadowman logo, the Red Hat logo, JBoss, OpenShift, Fedora, the Infinity logo, and RHCE are trademarks of Red Hat, Inc., registered in the United States and other countries. Linux ® is the registered trademark of Linus Torvalds in the United States and other countries. Java ® is a registered trademark of Oracle and/or its affiliates. XFS ® is a trademark of Silicon Graphics International Corp. or its subsidiaries in the United States and/or other countries. MySQL ® is a registered trademark of MySQL AB in the United States, the European Union and other countries. Node.js ® is an official trademark of Joyent. Red Hat is not formally related to or endorsed by the official Joyent Node.js open source or commercial project.
    [Show full text]