DOCSLIB.ORG

System X Virtualization Strategies

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text

Load more

Front cover System x Virtualization Strategies Enterprise class virtualization solutions eX4 hardware architectural features Software virtualization platforms Ben Archer Martin Ausilio William Bauman Francesco Ferri Chuck Kuhlmann Manikandar Madduri Matthew Mariani Ronald Mente Jonathan Patterson ibm.com/redbooks Redpaper International Technical Support Organization System x Virtualization Strategies February 2010 REDP-4480-00 Note: Before using this information and the product it supports, read the information in “Notices” on page v. First edition (February 2010) This edition applies to Model eX4 of IBM System x. © Copyright International Business Machines Corporation 2010. 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 . .v Trademarks . vi Preface . vii The team who wrote this paper . vii Now you can become a published author, too! . viii Comments welcome. viii Chapter 1. System x virtualization strategies. 1 1.1 What is virtualization . 2 1.2 Applying virtualization to your needs. 2 1.3 Desktops . 2 Chapter 2. The IBM Enterprise X Architectures . 5 2.1 The Enterprise X4 architecture . 6 2.1.1 x3850 M2 at a glance . 7 2.1.2 Scalability options with the x3950 M2 . 8 2.1.3 Advantages of a scale-up strategy . 8 Chapter 3. Virtualization strategies architectural overview . 11 3.1 Background . 12 3.2 Operating system virtualization: containers . 13 3.3 Type 2 hypervisors . 14 3.4 Type 1 hypervisors . 14 3.5 Type 1 stand-alone: VMware vSphere . 15 3.6 Type 1 hybrid: Citrix XenServer, Microsoft Hyper-V, OracleVM . 16 3.7 Type 1 mixed: Linux-based Kernel Virtual Machines . 17 Chapter 4. VMware vSphere. 19 4.1 VMware product ecosystem . 20 4.2 VMware vSphere scalability . 22 4.3 Considerations . 23 Chapter 5. Microsoft Hyper-V R2 and System Center . 25 5.1 The Microsoft virtualization ecosystem . 26 5.2 Hyper-V architecture overview . 26 5.3 Hyper-V scalability . 27 Chapter 6. Red Hat Enterprise Virtualization (KVM) . 29 6.1 Product ecosystem . 30 6.2 Scalability . 31 6.3 Considerations . 31 Chapter 7. Citrix XenServer . 33 7.1 Introduction . 34 7.2 Technical. 34 7.3 Citrix XenServer 5.5 . 35 7.4 Licensing . 35 7.5 Citrix XenServer versions . 36 7.6 The Citrix Xen product stack . 36 © Copyright IBM Corp. 2010. All rights reserved. iii 7.7 XenCenter . 39 Chapter 8. IBM Systems Director VMControl . 41 8.1 Overview . 42 8.2 IBM Systems Director VMControl 2.1 Express Edition . 42 8.3 IBM Systems Director VMControl 2.1 Standard Edition . 43 Chapter 9. Conclusion . 45 Related publications . 47 Online resources . 47 How to get Redbooks. 48 Help from IBM . 48 iv System x Virtualization Strategies Notices This information was developed for products and services offered in the U.S.A. IBM may not offer the products, services, or features discussed in this document in other countries. Consult your local IBM representative for information on the products and services currently available in your area. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any IBM intellectual property right may be used instead. However, it is the user's responsibility to evaluate and verify the operation of any non-IBM product, program, or service. IBM may have patents or pending patent applications covering subject matter described in this document. The furnishing of this document does not give you any license to these patents. You can send license inquiries, in writing, to: IBM Director of Licensing, IBM Corporation, North Castle Drive, Armonk, NY 10504-1785 U.S.A. The following paragraph does not apply to the United Kingdom or any other country where such provisions are inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement may not apply to you. This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice. Any references in this information to non-IBM Web sites are provided for convenience only and do not in any manner serve as an endorsement of those Web sites. The materials at those Web sites are not part of the materials for this IBM product and use of those Web sites is at your own risk. IBM may use or distribute any of the information you supply in any way it believes appropriate without incurring any obligation to you. Information concerning non-IBM products was obtained from the suppliers of those products, their published announcements or other publicly available sources. IBM has not tested those products and cannot confirm the accuracy of performance, compatibility or any other claims related to non-IBM products. Questions on the capabilities of non-IBM products should be addressed to the suppliers of those products. This information contains examples of data and reports used in daily business operations. To illustrate them as completely as possible, the examples include the names of individuals, companies, brands, and products. All of these names are fictitious and any similarity to the names and addresses used by an actual business enterprise is entirely coincidental. COPYRIGHT LICENSE: This information contains sample application programs in source language, which illustrate programming techniques on various operating platforms. You may copy, modify, and distribute these sample programs in any form without payment to IBM, for the purposes of developing, using, marketing or distributing application programs conforming to the application programming interface for the operating platform for which the sample programs are written. These examples have not been thoroughly tested under all conditions. IBM, therefore, cannot guarantee or imply reliability, serviceability, or function of these programs. © Copyright IBM Corp. 2010. All rights reserved. v Trademarks IBM, the IBM logo, and ibm.com are trademarks or registered trademarks of International Business Machines Corporation in the United States, other countries, or both. These and other IBM trademarked terms are marked on their first occurrence in this information with the appropriate symbol (® or ™), indicating US registered or common law trademarks owned by IBM at the time this information was published. Such trademarks may also be registered or common law trademarks in other countries. A current list of IBM trademarks is available on the Web at http://www.ibm.com/legal/copytrade.shtml The following terms are trademarks of the International Business Machines Corporation in the United States, other countries, or both: Active Memory™ iDataPlex™ System x® BladeCenter® Redbooks® X-Architecture® DS4000® Redpaper™ IBM® Redbooks (logo) ® The following terms are trademarks of other companies: Microsoft, Windows, and the Windows logo are trademarks of Microsoft Corporation in the United States, other countries, or both. Intel Xeon, Intel, Intel logo, Intel Inside logo, and Intel Centrino logo are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries. Linux is a trademark of Linus Torvalds in the United States, other countries, or both. Other company, product, or service names may be trademarks or service marks of others. vi System x Virtualization Strategies Preface IBM® is the global leader in enterprise class virtualization solutions. IBM offers a full range of virtualization hardware, including the.
Recommended publications
  • Para-Virtualization

    Para-Virtualization

    Large-Scale Data & Systems Group Virtualization Jana Giceva [email protected] PeterDepartment R. Pietzuch of Computing Imperial College London [email protected]://lsds.doc.ic.ac.uk Fall 2018 Intro to Virtualization 2 Why do we need virtualizaton? • Recall previous lecture… 3 What is virtualization? • Broadly speaking… Virtualization: simulate or emulate a function of a resource (object) in software, identical to that of the physical one. Abstraction to make software look and behave like hardware. • Recall – virtual memory • Computer software gains access to more memory than it is physically installed, via the background swapping of data to disk storage. • Similarly, virtualization techniques can be applied to other IT infrastructure layers, including networks, storage, laptop or server hardware, OSs and applications. 4 Virtual infrastructure • Allows multiple VMs with different OSs and applications to run in isolation, side by side on the same physical machine. • VMs can be provisioned to any system. • Machine independence of OS and applications. • Can manage an application and its OS as a unit, encapsulating them in a single VM. src: VMWare whitepaper -- Virtualization 5 Properties of Virtual Machines • Key properties of VMs: • 1. Partitioning – Run multiple OS on one physical machine – Divide system resources between VMs • 2. Isolation – Provide fault and security isolation at the hardware level – Preserve performance with advanced resource controls • 3. Encapsulation – Save the entire state of a VM to files – Move and copy VMs as easily as copying and moving files • 4. Hardware independence – Provision or migrate any VM to any physical server 6 Virtualization – Definitions and Terms Virtual Machine (VM): a tightly isolated software container with an operating system (OS) and an application inside.
  • Network Virtualization for Open Cloud

    Network Virtualization for Open Cloud

    Πανεπιστήμιο Δυτικής Αττικής Τμήμα Μηχανικών Πληροφορικής και Υπολογιστών ΠΤΥΧΙΑΚΗ ΕΡΓΑΣΙΑ της ΣΟΥΒΑΛΙΩΤΗ ΜΑΡΙΑΣ Επιβλέπων Καθηγητής: Ξυδάς Ιωάννης Επίκουρος Καθηγητής ΠΑ.Δ.Α. Αθήνα, Σεπτέμβριος, 2018 Περιεχόμενα Περίληψη ...............................................................................................................................................9 Αbstract...................................................................................................................................................9 Ευχαριστίες.............................................................................................................................................10 ΚΕΦΑΛΑΙΟ 1 – Εισαγωγή ..................................................................................................................11 1.1. Περίληψη Κεφαλαίου..................................................................................................................11 1.2. Virtualization ...............................................................................................................................11 1.2.1. Hypervisor – Virtual Machine Manager................................................................................12 1.2.1.1. Ενσωματωμένοι Hypervisors.........................................................................................13 1.2.2. Network Virtualization..........................................................................................................13 1.2.2.1. Συνδυασμοί Network Virtualization...............................................................................14
  • Understanding Full Virtualization, Paravirtualization, and Hardware Assist

    Understanding Full Virtualization, Paravirtualization, and Hardware Assist

    VMware Understanding Full Virtualization, Paravirtualization, and Hardware Assist Contents Introduction .................................................................................................................1 Overview of x86 Virtualization..................................................................................2 CPU Virtualization .......................................................................................................3 The Challenges of x86 Hardware Virtualization ...........................................................................................................3 Technique 1 - Full Virtualization using Binary Translation......................................................................................4 Technique 2 - OS Assisted Virtualization or Paravirtualization.............................................................................5 Technique 3 - Hardware Assisted Virtualization ..........................................................................................................6 Memory Virtualization................................................................................................6 Device and I/O Virtualization.....................................................................................7 Summarizing the Current State of x86 Virtualization Techniques......................8 Full Virtualization with Binary Translation is the Most Established Technology Today..........................8 Hardware Assist is the Future of Virtualization, but the Real Gains Have
  • Manage Your Virtual Environments with Virtual Machine Manager 2008

    Manage Your Virtual Environments with Virtual Machine Manager 2008

    Virtualisation In this article, I will examine VMM 2008 The red box on the upper-left represents At a glance: and the new features it brings to IT adminis- the Virtual Machine Manager 2008 server Support for VMware VMs trators. I’ll then look at the requirements and service. Above it are the different interfaces Windows PowerShell- based scripting and the steps involved with a VMM installation. into the service: the Administrator Console, automation Finally, I’ll take a closer look at how to use the Windows PowerShell interface, and the Consolidated, centralised some of the new features of VMM 2008. management Installation procedures An introduction to Virtual Machine There are significantly Manager 2008 System Center Virtual Machine Manager more interfaces to 2008 is a standalone application that provides centralised, enterprise-class management of the VMM system in virtual machines running under Microsoft Virtual Server 2005 R2 SP1, Windows Serv- VMM 2008 er 2008 Hyper-V, Microsoft Hyper-V Server Manage your virtual 2008 and VMware Infrastructure 3 (ESX/ ESXi) servers. Together with other System Self-Service Web Portal with delegated user Center products, VMM provides end-to-end access. Windows PowerShell forms the basis physical and virtual infrastructure manage- for all access to the VMM server. The VMM environments with ment. Figure 1 shows the architectural lay- Admin Console is built entirely on Win- out of Virtual Machine Manager. dows PowerShell, so you can simply create As those familiar with VMM 2007 will Windows PowerShell scripts that the VMM note, there are significantly more interfaces server service runs. Thus, the public API for Virtual Machine to the VMM system in VMM 2008 (see Fig- VMM 2008 is Windows PowerShell, and any ure 1).
  • Deliverable No. 5.3 Techniques to Build the Cloud Infrastructure Available to the Community

    Deliverable No. 5.3 Techniques to Build the Cloud Infrastructure Available to the Community

    Deliverable No. 5.3 Techniques to build the cloud infrastructure available to the community Grant Agreement No.: 600841 Deliverable No.: D5.3 Deliverable Name: Techniques to build the cloud infrastructure available to the community Contractual Submission Date: 31/03/2015 Actual Submission Date: 31/03/2015 Dissemination Level PU Public X PP Restricted to other programme participants (including the Commission Services) RE Restricted to a group specified by the consortium (including the Commission Services) CO Confidential, only for members of the consortium (including the Commission Services) Grant Agreement no. 600841 D5.3 – Techniques to build the cloud infrastructure available to the community COVER AND CONTROL PAGE OF DOCUMENT Project Acronym: CHIC Project Full Name: Computational Horizons In Cancer (CHIC): Developing Meta- and Hyper-Multiscale Models and Repositories for In Silico Oncology Deliverable No.: D5.3 Document name: Techniques to build the cloud infrastructure available to the community Nature (R, P, D, O)1 R Dissemination Level (PU, PP, PU RE, CO)2 Version: 1.0 Actual Submission Date: 31/03/2015 Editor: Manolis Tsiknakis Institution: FORTH E-Mail: [email protected] ABSTRACT: This deliverable reports on the technologies, techniques and configuration needed to install, configure, maintain and run a private cloud infrastructure for productive usage. KEYWORD LIST: Cloud infrastructure, OpenStack, Eucalyptus, CloudStack, VMware vSphere, virtualization, computation, storage, security, architecture. The research leading to these results has received funding from the European Community's Seventh Framework Programme (FP7/2007-2013) under grant agreement no 600841. The author is solely responsible for its content, it does not represent the opinion of the European Community and the Community is not responsible for any use that might be made of data appearing therein.
  • Vmware Converter Enterprise-Class Migration Tool for Converting Physical Machines, Virtual Machines Or Other Third-Party Image Formats to Vmware Virtual Machines

    Vmware Converter Enterprise-Class Migration Tool for Converting Physical Machines, Virtual Machines Or Other Third-Party Image Formats to Vmware Virtual Machines

    PRODUCT DATASHEET VMware Converter Enterprise-class migration tool for converting physical machines, virtual machines or other third-party image formats to VMware virtual machines What Is VMware Converter? How Does VMware Converter Work? VMware® Converter is a highly robust and scalable enterprise-class VMware Converter is managed through a simple, task based UI that migration tool that reduces the time that IT managers spend convert- enables customers to convert physical machines, other VMware ing physical machines to VMware virtual machines. Using a snapshot- product formats or other third-party formats to VMware virtual based cloning mechanism that is extremely fast and reliable, VMware machines in three easy steps: Converter enables remote conversions without disrupting the source • Step 1: Specify the source physical server, virtual machine or third- server during the conversion process. party format to convert. VMware Converter provides a full range of physical-to-virtual and • Step 2: Specify the destination format, virtual machine name, and virtual-to-virtual conversions, allowing users to: location for the new virtual machine to be created. • Convert physical machines running Windows operating systems 1 to • Step 3: Automate the virtual machine creation and conversion pro- VMware virtual machines cess with VMware Converter. • Import older VMware virtual machine formats to new VMware virtual machine formats What are Benefits and Applications of VMware • Convert third-party formats such as Symantec Backup Exec System Converter? Recovery (formerly Symantec LiveState Recovery) and Microsoft Vir- tual Server/Virtual PC to VMware virtual machines Customers often want to convert a large number of physical servers to VMware virtual machines, for example, during a server consoli- • Populate new virtual machine environments quickly from large direc- dation project.
  • A Lightweight Virtualization Layer with Hardware-Assistance for Embedded Systems

    A Lightweight Virtualization Layer with Hardware-Assistance for Embedded Systems

    PONTIFICAL CATHOLIC UNIVERSITY OF RIO GRANDE DO SUL FACULTY OF INFORMATICS COMPUTER SCIENCE GRADUATE PROGRAM A LIGHTWEIGHT VIRTUALIZATION LAYER WITH HARDWARE-ASSISTANCE FOR EMBEDDED SYSTEMS CARLOS ROBERTO MORATELLI Dissertation submitted to the Pontifical Catholic University of Rio Grande do Sul in partial fullfillment of the requirements for the degree of Ph. D. in Computer Science. Advisor: Prof. Fabiano Hessel Porto Alegre 2016 To my family and friends. “I’m doing a (free) operating system (just a hobby, won’t be big and professional like gnu) for 386(486) AT clones.” (Linus Torvalds) ACKNOWLEDGMENTS I would like to express my sincere gratitude to those who helped me throughout all my Ph.D. years and made this dissertation possible. First of all, I would like to thank my advisor, Prof. Fabiano Passuelo Hessel, who has given me the opportunity to undertake a Ph.D. and provided me invaluable guidance and support in my Ph.D. and in my academic life in general. Thank you to all the Ph.D. committee members – Prof. Carlos Eduardo Pereira (dissertation proposal), Prof. Rodolfo Jardim de Azevedo, Prof. Rômulo Silva de Oliveira and Prof. Tiago Ferreto - for the time invested and for the valuable feedback provided.Thank you Dr. Luca Carloni and the other SLD team members at the Columbia University in the City of New York for receiving me and giving me the opportunity to work with them during my ‘sandwich’ research internship. Eu gostaria de agraceder minha esposa, Ana Claudia, por ter estado ao meu lado durante todo o meu período de doutorado. O seu apoio e compreensão foram e continuam sendo muito importantes para mim.
  • Vmware Converter User's Manual: Vmware Converter 3

    Vmware Converter User's Manual: Vmware Converter 3

    VMware Converter User’s Manual VMware Converter 3 VMware Converter User’s Manual VMware Converter User’s Manual Version: 3.0.2 Revision: 20071018 Item: VMC-ENG-Q407-281 You can find the most up-to-date technical documentation on our Web site at http://www.vmware.com/support/ The VMware Web site also provides the latest product updates. If you have comments about this documentation, submit your feedback to: [email protected] © 2006-2007 VMware, Inc. All rights reserved. Protected by one or more of U.S. Patent Nos. 6,397,242, 6,496,847, 6,704,925, 6,711,672, 6,725,289, 6,735,601, 6,785,886, 6,789,156, 6,795,966, 6,880,022, 6,944,699, 6,961,806, 6,961,941, 7,069,413, 7,082,598, 7,089,377, 7,111,086, 7,111,145, 7,117,481, 7,149,843, 7,155,558, 7,222,221, 7,260,815, 7,260,820, and 7,269,683; patents pending. 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. All other marks and names mentioned herein may be trademarks of their respective companies. VMware, Inc. 3401 Hillview Ave. Palo Alto, CA 94304 www.vmware.com 2 VMware, Inc. Contents Preface 7 1 Introduction to VMware Converter 9 Migration with VMware Converter 9 VMware Converter Editions 10 Cloning and System Reconfiguration of Physical Machines 10 Hot and Cold Cloning 11 Local and Remote Cloning 11 Example of Remote Hot Cloning 11 Example of Local Cold Cloning 13 Cloning Modes 14 Volume‐Based Cloning 14 Disk‐Based Cloning 15 Migrating Existing Virtual Machines
  • VIRTUAL DESKTOP INFRASTRUCTURE an Rcpsolution Spotlight on a Joint Effort by Microsoft and Citrix to Bring a VDI Solution to the Market

    VIRTUAL DESKTOP INFRASTRUCTURE an Rcpsolution Spotlight on a Joint Effort by Microsoft and Citrix to Bring a VDI Solution to the Market

    0309rcp_Supp.v5 2/10/09 4:53 PM Page C1 SPECIAL PULLOUT SECTION Partner’s Guide to VIRTUAL DESKTOP INFRASTRUCTURE An RCPSolution Spotlight on a joint effort by Microsoft and Citrix to bring a VDI solution to the market. By Scott Bekker ChannelRedmond Partner Project15 2/4/09 3:07 PM Page 1 Project15 2/4/09 3:08 PM Page 1 0309rcp_Supp.v5 2/10/09 4:53 PM Page 2 VIRTUAL DESKTOP INFRASTRUCTURE icrosoft and Citrix Systems Inc. are working together on a joint go-to-market strategy for partners to take Virtual MDesktop Infrastructure (VDI) solutions to the market. VDI is a special subset of desktop virtualization, itself a subset of virtualization in general. While virtualization separates hardware from workers, for users who need access to their work software, Microsoft’s overall virtualization environment from anywhere, including from a non- approaches fit into four broad buckets—server virtu- company-owned PC, as well as enterprise customers alization, desktop virtualization, presentation virtu- with a centralized desktop strategy for office work- alization and application virtualization. ers,” the Microsoft materials explain. That’s not to The biggest part of the virtualization market to date say everyone is appropriate for VDI, even when a fat has been consolidating multiple software servers client isn’t the answer for some reason. onto comparatively fewer hardware servers. “Terminal Services, which has been widely Such server consolidation is still a growth adopted for virtualizing the presentation of entire industry, especially in a down economy, in which desktops or individual applications, is an alternative there are savings to be gained by reducing hardware centralized desktop delivery solution from and power expenses.
  • Full Virtualization on Low-End Hardware: a Case Study

    Full Virtualization on Low-End Hardware: a Case Study

    Full Virtualization on Low-End Hardware: a Case Study Adriano Carvalho∗, Vitor Silva∗, Francisco Afonsoy, Paulo Cardoso∗, Jorge Cabral∗, Mongkol Ekpanyapongz, Sergio Montenegrox and Adriano Tavares∗ ∗Embedded Systems Research Group Universidade do Minho, 4800–058 Guimaraes˜ — Portugal yInstituto Politecnico´ de Coimbra (ESTGOH), 3400–124 Oliveira do Hospital — Portugal zAsian Institute of Technology, Pathumthani 12120 — Thailand xUniversitat¨ Wurzburg,¨ 97074 Wurzburg¨ — Germany Abstract—Most hypervisors today rely either on (1) full virtua- a hypervisor-specific, often proprietary, interface. Full virtua- lization on high-end hardware (i.e., hardware with virtualization lization on low-end hardware, on the other end, has none of extensions), (2) paravirtualization, or (3) both. These, however, those disadvantages. do not fulfill embedded systems’ requirements, or require legacy software to be modified. Full virtualization on low-end hardware Full virtualization on low-end hardware (i.e., hardware with- (i.e., hardware without virtualization extensions), on the other out dedicated support for virtualization) must be accomplished end, has none of those disadvantages. However, it is often using mechanisms which were not originally designed for it. claimed that it is not feasible due to an unacceptably high Therefore, full virtualization on low-end hardware is not al- virtualization overhead. We were, nevertheless, unable to find ways possible because the hardware may not fulfill the neces- real-world quantitative results supporting those claims. In this paper, performance and footprint measurements from a sary requirements (i.e., “the set of sensitive instructions for that case study on low-end hardware full virtualization for embedded computer is a subset of the set of privileged instructions” [1]).
  • Vmware Security Briefing

    Vmware Security Briefing

    VMware Security Briefing Steven Boesel, CISSP Senior Systems Engineer Hosted Virtualization vs. Bare Metal Virtualization Hosted Virtualization Bare-Metal Virtualization VMware Workstation VMware ESX Server VMware Server VMware Player Host OS Changes Security Profile Greatly VMware Confidential/Proprietary Copyright © 2006 VMware, Inc. All rights reserved. 2 VMware Architecture: Isolation and Containment VMM VMM Security Design Highlights Production Use Proof Points • Privileged instructions within a VM are • CC EAL 4+ certification “de-privileged” and run within an isolated virtual memory space • ESX 3.0.2 and VC 2.0.2 • VMs have no direct access to • Passed security audit and put into hardware, only have visibility to virtual production by the largest devices Financial Institutions • VMs can only communicate with each • Passed Defense and Security other through Virtual Switches Agencies scrutiny and audit (NetTop and HAP) • Resource reservations and limits guarantees performance isolation • Large number of customers run mission critical and transaction • OS and applications within a VM run as processing applications is with no modification (hence no recertification required) 3 Are there any Hypervisor Attack Vectors? There are currently no known hypervisor attack vectors to date that have lead to “VM Escape” • Architectural Vulnerability • Designed specifically with Isolation in Mind • Software Vulnerability • Possible like with any code written by humans • Small Code Footprint of Hypervisor (~32MB) Makes it Easier to Audit • Depends
  • Opennebula 5.7 Deployment Guide Release 5.7.80

    Opennebula 5.7 Deployment Guide Release 5.7.80

    OpenNebula 5.7 Deployment guide Release 5.7.80 OpenNebula Systems Jan 16, 2019 This document is being provided by OpenNebula Systems under the Creative Commons Attribution-NonCommercial- Share Alike License. THE DOCUMENT IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IM- PLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE DOCUMENT. i CONTENTS 1 Cloud Design 1 1.1 Overview.................................................1 1.2 Open Cloud Architecture.........................................2 1.3 VMware Cloud Architecture.......................................7 1.4 OpenNebula Provisioning Model.................................... 13 2 OpenNebula Installation 19 2.1 Overview................................................. 19 2.2 Front-end Installation.......................................... 19 2.3 MySQL Setup.............................................. 25 3 Node Installation 27 3.1 Overview................................................. 27 3.2 KVM Node Installation......................................... 28 3.3 LXD Node Installation.......................................... 35 3.4 vCenter Node Installation........................................ 37 3.5 Verify your Installation.......................................... 45 4 Authentication Setup 52