DOCSLIB.ORG

Architecture and Design

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Architecture and Design Architecture and Design 17 JUL 2018 VMware Validated Design 4.3 VMware Validated Design for Management and Workload Consolidation 4.3 Architecture and Design You can find the most up-to-date technical documentation on the VMware website at: https://docs.vmware.com/ If you have comments about this documentation, submit your feedback to [email protected] VMware, Inc. 3401 Hillview Ave. Palo Alto, CA 94304 www.vmware.com Copyright © 2017–2018 VMware, Inc. All rights reserved. Copyright and trademark information. VMware, Inc. 2 Contents About Architecture and Design for Consolidated SDDC 5 1 Architecture Overview for Consolidated SDDC 6 Infrastructure Architecture for Consolidated SDDC 8 Workload Domain Architecture for Consolidated SDDC 9 Cluster Types for Consolidated SDDC 10 Physical Network Architecture for Consolidated SDDC 11 Availability Zones and Regions for Consolidated SDDC 16 Virtual Infrastructure Architecture for Consolidated SDDC 17 Virtual Infrastructure Overview for Consolidated SDDC 18 Network Virtualization Components for Consolidated SDDC 19 Network Virtualization Services for Consolidated SDDC 20 Operations Management Architecture for Consolidated SDDC 23 ESXi Patching and Upgrade Architecture for Consolidated SDDC 23 vRealize Suite Lifecycle Management Architecture for Consolidated SDDC 26 Monitoring Architecture for Consolidated SDDC 29 Logging Architecture for Consolidated SDDC 33 Cloud Management Architecture for Consolidated SDDC 39 vRealize Automation Architecture for Consolidated SDDC 40 vRealize Business for Cloud Architecture for Consolidated SDDC 44 Business Continuity Architecture for Consolidated SDDC 46 Data Protection and Backup Architecture for Consolidated SDDC 46 2 Detailed Design for Consolidated SDDC 48 Physical Infrastructure Design for Consolidated SDDC 49 Physical Design Fundamentals for Consolidated SDDC 49 Physical Networking Design for Consolidated SDDC 53 Physical Storage Design for Consolidated SDDC 57 Virtual Infrastructure Design for Consolidated SDDC 67 ESXi Design for Consolidated SDDC 69 vCenter Server Design for Consolidated SDDC 71 Virtualization Network Design for Consolidated SDDC 81 NSX Design for Consolidated SDDC 92 Shared Storage Design for Consolidated SDDC 114 Operations Management Design for Consolidated SDDC 133 vSphere Update Manager Design for Consolidated SDDC 133 vRealize Suite Lifecycle Manager Design for Consolidated SDDC 141 vRealize Operations Manager Design for Consolidated SDDC 160 VMware, Inc. 3 Architecture and Design vRealize Log Insight Design for Consolidated SDDC 176 Cloud Management Design for Consolidated SDDC 195 vRealize Automation Design for Consolidated SDDC 196 vRealize Business Design for Consolidated SDDC 227 vRealize Orchestrator Design for Consolidated SDDC 228 Business Continuity Design for Consolidated SDDC 234 Data Protection and Backup Design for Consolidated SDDC 234 VMware, Inc. 4 About Architecture and Design for Consolidated SDDC The Architecture and Design document for the VMware Validated Design for Management and Workload Consolidation contains a validated model of a consolidated cluster implementation of a VMware Validated Design, and provides a detailed design of each management component of the data center stack. Chapter 1 Architecture Overview for Consolidated SDDC discusses the building blocks and the main principles of each SDDC management layer. Chapter 2 Detailed Design for Consolidated SDDC provides the available design options according to the design objective, and a set of design decisions to justify selecting the path for building each SDDC component. This document refers to the VMware Validated Design for Management and Workload Consolidation as the Consolidated SDDC. Intended Audience VMware Validated Design Architecture and Design is intended for cloud architects, infrastructure administrators, and cloud administrators who are familiar with and want to use VMware software to deploy in a short time and manage an SDDC that meets the requirements for capacity, scalability, backup and restore, and extensibility for disaster recovery support. Required VMware Software VMware Validated Design Architecture and Design is compliant and validated with certain product versions. See VMware Validated Design Release Notes for more information about supported product versions. VMware, Inc. 5 Architecture Overview for Consolidated SDDC 1 VMware Validated Design for Consolidated Software-Defined Data Center (Consolidated SDDC) enables an IT organization to automate the provisioning of common repeatable requests and to respond to business needs with agility and predictability. Usually, this use case is referred to as Infrastructure as a Service (IaaS). However, VMware Validated Design for Software-Defined Data Center extends the typical IaaS solution to provide an IT solution with features across many areas such as IaaS, operations management, business continuity and security. The VMware Validated Design architecture is based on layers and modules. You can replace components to implement the end solution or outcome such as the SDDC. If a particular component design does not fit a business or technical requirement for some reason, you can swap it out for a similar one. A VMware Validated Design is one way of assembling an architecture. It is tested for stability, scalability and compatibility. The design of the system ensures achieving best IT outcomes. Figure 1‑1. Architecture Overview Service Cloud Service Catalog Business Security Management Management Continuity Layer Self-Service Portal Orchestration Virtual Hypervisor Infrastructure Backup & Governance Layer Pools of Resources Restore Virtualization Control Portfolio Risk Management Physical Compute Layer Storage Operations Compliance Management Network VMware, Inc. 6 Architecture and Design Physical Layer The lowest layer of the solution is the physical layer which consists of the compute, network and storage components. The compute component contains the x86-based servers that run the management, edge and tenant workloads. This design provides some guidance about the physical capabilities that are required to run this architecture. However, you select a specific type or brand of hardware according to VMware Compatibility Guide. Virtual Infrastructure Layer The virtual infrastructure layer is on top of the physical layer components. The virtual infrastructure layer controls the access to the underlying physical infrastructure, and controls and allocates resources to the management and tenant workloads. The management workloads consist of elements in the virtual infrastructure layer itself, together with elements in the cloud management, service management, business continuity and security layers. Cloud Management Layer The cloud management layer is the top layer of the stack. Service consumption occurs at this layer. This layer requests resources and orchestrates the actions of the lower layers from a user interface or application programming interface (API). Service Management Layer When building any type of IT infrastructure, you use portfolio and operations management for continuous day-to-day service delivery. The service management area of this architecture focuses on operations management, in particular lifecycle management, monitoring, alerting, and log management. Operations Management Layer The architecture of the operations management layer includes management components that provide support for the main types of operations in an SDDC. In the operations management layer, you monitor the underlying physical infrastructure and the virtual management and tenant workloads in real-time. Information is collected in the form of structured data (metrics) and unstructured data (logs). The operations management layer also retrieves the SDDC topology, that is physical and virtual compute, networking, and storage resources, which are key in intelligent and dynamic operational management. The operations management layer consists primarily of monitoring and logging functionality. VMware, Inc. 7 Architecture and Design Business Continuity Layer A consolidated SDDC must contain elements to support business continuity by providing data backup and restore. If data loss occurs, the right elements must be in place to prevent permanent loss of business critical data. This design provides guidance on how to operate backup and restore functions. Security Layer All systems must be secure by design. A secure design reduces risk and increases compliance while providing a governance structure. The security layer outlines the operations and setup that you must provide to implement an SDDC that is resilient to both internal and external threats. This chapter includes the following topics: n Infrastructure Architecture for Consolidated SDDC n Virtual Infrastructure Architecture for Consolidated SDDC n Operations Management Architecture for Consolidated SDDC n Cloud Management Architecture for Consolidated SDDC n Business Continuity Architecture for Consolidated SDDC Infrastructure Architecture for Consolidated SDDC The architecture of the data center physical layer is based on logical hardware domains and the physical network topology. Figure 1‑2. Physical Infrastructure Design in the SDDC Service Cloud Service Catalog Business Security Management Management Continuity Layer Self-Service Portal Orchestration Virtual Hypervisor Infrastructure Backup & Governance Layer Pools of Resources Restore Virtualization Control Portfolio Risk Management Physical Compute Layer Storage Operations Compliance
Load more

Recommended publications
  • Tree-Like Distributed Computation Environment with Shapp Library
    information Article Tree-Like Distributed Computation Environment with Shapp Library Tomasz Gałecki and Wiktor Bohdan Daszczuk * Institute of Computer Science, Warsaw University of Technology, 00-665 Warsaw, Poland; [email protected] * Correspondence: [email protected]; Tel.: +48-22-234-78-12 Received: 30 January 2020; Accepted: 1 March 2020; Published: 3 March 2020 Abstract: Despite the rapidly growing computing power of computers, it is often insufficient to perform mass calculations in a short time, for example, simulation of systems for various sets of parameters, the searching of huge state spaces, optimization using ant or genetic algorithms, machine learning, etc. One can solve the problem of a lack of computing power through workload management systems used in local networks in order to use the free computing power of servers and workstations. This article proposes raising such a system to a higher level of abstraction: The use in the .NET environment of a new Shapp library that allows remote task execution using fork-like operations from Portable Operating System Interface for UNIX (POSIX) systems. The library distributes the task code, sending static data on which task force is working, and individualizing tasks. In addition, a convenient way of communicating distributed tasks running hierarchically in the Shapp library was proposed to better manage the execution of these tasks. Many different task group architectures are possible; we focus on tree-like calculations that are suitable for many problems where the range of possible parallelism increases as the calculations progress. Keywords: workload management; remote fork; distributed computations; task group communication 1.
    [Show full text]
  • Administration Guide Administration Guide SUSE Linux Enterprise High Availability Extension 15 SP1 by Tanja Roth and Thomas Schraitle
    SUSE Linux Enterprise High Availability Extension 15 SP1 Administration Guide Administration Guide SUSE Linux Enterprise High Availability Extension 15 SP1 by Tanja Roth and Thomas Schraitle This guide is intended for administrators who need to set up, congure, and maintain clusters with SUSE® Linux Enterprise High Availability Extension. For quick and ecient conguration and administration, the product includes both a graphical user interface and a command line interface (CLI). For performing key tasks, both approaches are covered in this guide. Thus, you can choose the appropriate tool that matches your needs. 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 http://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
    [Show full text]
  • Introduction to Linux Virtual Server and High Availability
    Outlines Introduction to Linux Virtual Server and High Availability Chen Kaiwang [email protected] December 5, 2011 Chen Kaiwang [email protected] LVS-DR and Keepalived Outlines If you don't know the theory, you don't have a way to be rigorous. Robert J. Shiller http://www.econ.yale.edu/~shiller/ Chen Kaiwang [email protected] LVS-DR and Keepalived Outlines Misery stories I Jul 2011 Too many connections at zongheng.com I Aug 2011 Realserver maintenance at 173.com quiescent persistent connections I Nov 2011 Health check at 173.com I Nov 2011 Virtual service configuration at 173.com persistent session data Chen Kaiwang [email protected] LVS-DR and Keepalived Outlines Outline of Part I Introduction to Linux Virtual Server Configuration Overview Netfilter Architecture Job Scheduling Scheduling Basics Scheduling Algorithms Connection Affinity Persistence Template Persistence Granularity Quirks Chen Kaiwang [email protected] LVS-DR and Keepalived Outlines Outline of Part II HA Basics LVS High Avaliablity Realserver Failover Director Failover Solutions Heartbeat Keepalived Chen Kaiwang [email protected] LVS-DR and Keepalived LVS Intro Job Scheduling Connection Affinity Quirks Part I Introduction to Linux Virtual Server Chen Kaiwang [email protected] LVS-DR and Keepalived LVS Intro Job Scheduling Configuration Overview Connection Affinity Netfilter Architecture Quirks Introduction to Linux Virtual Server Configuration Overview Netfilter Architecture Job Scheduling Scheduling Basics Scheduling Algorithms Connection Affinity Persistence Template Persistence Granularity Quirks Chen Kaiwang [email protected] LVS-DR and Keepalived LVS Intro Job Scheduling Configuration Overview Connection Affinity Netfilter Architecture Quirks A Linux Virtual Serverr (LVS) is a group of servers that appear to the client as one large, fast, reliable (highly available) server.
    [Show full text]
  • Keepalived User Guide Release 1.4.3
    Keepalived User Guide Release 1.4.3 Alexandre Cassen and Contributors March 06, 2021 Contents 1 Introduction 1 2 Software Design 3 3 Load Balancing Techniques 11 4 Installing Keepalived 13 5 Keepalived configuration synopsis 17 6 Keepalived programs synopsis 23 7 IPVS Scheduling Algorithms 27 8 IPVS Protocol Support 31 9 Configuring SNMP Support 33 10 Case Study: Healthcheck 37 11 Case Study: Failover using VRRP 43 12 Case Study: Mixing Healthcheck & Failover 47 13 Terminology 51 14 License 53 15 About These Documents 55 16 TODO List 57 Index 59 i ii CHAPTER 1 Introduction Load balancing is a method of distributing IP traffic across a cluster of real servers, providing one or more highly available virtual services. When designing load-balanced topologies, it is important to account for the availability of the load balancer itself as well as the real servers behind it. Keepalived provides frameworks for both load balancing and high availability. The load balancing framework relies on the well-known and widely used Linux Virtual Server (IPVS) kernel module, which provides Layer 4 load balancing. Keepalived implements a set of health checkers to dynamically and adaptively maintain and manage load balanced server pools according to their health. High availability is achieved by the Virtual Redundancy Routing Protocol (VRRP). VRRP is a fundamental brick for router failover. In addition, keepalived implements a set of hooks to the VRRP finite state machine providing low-level and high-speed protocol interactions. Each Keepalived framework can be used independently or together to provide resilient infrastructures. In this context, load balancer may also be referred to as a director or an LVS router.
    [Show full text]
  • Ubuntu Server Guide Basic Installation Preparing to Install
    Ubuntu Server Guide Welcome to the Ubuntu Server Guide! This site includes information on using Ubuntu Server for the latest LTS release, Ubuntu 20.04 LTS (Focal Fossa). For an offline version as well as versions for previous releases see below. Improving the Documentation If you find any errors or have suggestions for improvements to pages, please use the link at thebottomof each topic titled: “Help improve this document in the forum.” This link will take you to the Server Discourse forum for the specific page you are viewing. There you can share your comments or let us know aboutbugs with any page. PDFs and Previous Releases Below are links to the previous Ubuntu Server release server guides as well as an offline copy of the current version of this site: Ubuntu 20.04 LTS (Focal Fossa): PDF Ubuntu 18.04 LTS (Bionic Beaver): Web and PDF Ubuntu 16.04 LTS (Xenial Xerus): Web and PDF Support There are a couple of different ways that the Ubuntu Server edition is supported: commercial support and community support. The main commercial support (and development funding) is available from Canonical, Ltd. They supply reasonably- priced support contracts on a per desktop or per-server basis. For more information see the Ubuntu Advantage page. Community support is also provided by dedicated individuals and companies that wish to make Ubuntu the best distribution possible. Support is provided through multiple mailing lists, IRC channels, forums, blogs, wikis, etc. The large amount of information available can be overwhelming, but a good search engine query can usually provide an answer to your questions.
    [Show full text]
  • HP/ISV Confidential
    Advanced Cluster Software for Meteorology Betty van Houten 1 Frederic Ciesielski / Gavin Brebner / Ghislain de Jacquelot 2 Michael Riedmann 3 Henry Strauss 4 1 HPC Division Richardson 2 HPC Competency Centre Grenoble 3 EPC Boeblingen 4 HPC PreSales Munich ECMWF workshop “Use of HPC in Meteorology” -- Reading/UK, November 2nd, 2006 © 2006 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice 2 Nov 2, 2006 Advanced Cluster Software for Meteorology Outline • requirements in met • HP‘s ways to address those − XC – a cluster environment for real-world applications − HP-MPI – a universal approach − some thoughts on checkpoint/restart and alternatives − future work • LM on HP – status & results • conclusions 3 Nov 2, 2006 Advanced Cluster Software for Meteorology Requirements • both capability and capacity • reliability & turn-around times • data management! • visualization? 4 Nov 2, 2006 Advanced Cluster Software for Meteorology Cluster Implementation Challenges • Manageability • Scalability • Integration of Data Mgmt & Visualization • Interconnect/Network Complexity • Version Control • Application Availability 5 Nov 2, 2006 Advanced Cluster Software for Meteorology XC Cluster: HP’s Linux-Based Production Cluster for HPC • A production computing environment for HPC built on Linux/Industry standard clusters − Industrial-hardened, scalable, supported − Integrates leading technologies from open source and partners • Simple and complete product for real world usage − Turn-key, with single
    [Show full text]
  • Protectv Installation Guide (AWS)
    ProtectV Installation Guide (AWS) Technical Manual Template 1 Release 1.0, PN: 000-000000-000, Rev. A, March 2013, Copyright © 2013 SafeNet, Inc. All rights reserved. Document Information Product Version 1.7 Document Part Number 007-011532-001, Rev R Release Date March 2014 Trademarks All intellectual property is protected by copyright. All trademarks and product names used or referred to are the copyright of their respective owners. No part of this document may be reproduced, stored in a retrieval system or transmitted in any form or by any means, electronic, mechanical, chemical, photocopy, recording, or otherwise, without the prior written permission of SafeNet, Inc. • Linux® is a registered trademark of Linus Torvalds. Linux Foundation, Linux Standard Base, LSB, LSB Certified, IAccessible2, MeeGo are registered trademarks of the Linux Foundation. Copyright © 2010 Linux Foundation. All rights reserved. • Windows is a registered trademark of Microsoft Corporation in the United States and other countries. • Amazon Web Services™ and AWS™ are registered trademarks of Amazon.com, Inc. or its affiliates in the United States and other countries. • Red Hat® Linux® is a registered trademark of Red Hat, Inc. in the United States and other countries. • Ubuntu™ is a registered trademark of Canonical Ltd. Disclaimer SafeNet makes no representations or warranties with respect to the contents of this document and specifically disclaims any implied warranties of merchantability or fitness for any particular purpose. Furthermore, SafeNet reserves the right to revise this publication and to make changes from time to time in the content hereof without the obligation upon SafeNet to notify any person or organization of any such revisions or changes.
    [Show full text]
  • Virtually Linux Virtualization Techniques in Linux
    Virtually Linux Virtualization Techniques in Linux Chris Wright OSDL [email protected] Abstract ware1 or software [16, 21, 19], may include any subset of a machine’s resources, and has Virtualization provides an abstraction layer a wide variety of applications. Such usages mapping a virtual resource to a real resource. include machine emulation, hardware consol- Such an abstraction allows one machine to be idation, resource isolation, quality of service carved into many virtual machines as well as resource allocation, and transparent resource allowing a cluster of machines to be viewed redirection. Applications of these usage mod- as one. Linux provides a wealth of virtual- els include virtual hosting, security, high avail- ization offerings. The technologies range in ability, high throughput, testing, and ease of the problems they solve, the models they are administration. useful in, and their respective maturity. This It is interesting to note that differing virtual- paper surveys some of the current virtualiza- ization models may have inversely correlated tion techniques available to Linux users, and proportions of virtual to physical resources. it reviews ways to leverage these technologies. For example, the method of carving up a sin- Virtualization can be used to provide things gle machine into multiple machines—useful such as quality of service resource allocation, in hardware consolidation or virtual hosting— resource isolation for security or sandboxing, looks quite different from a single system im- transparent resource redirection for availability age (SSI) [15]—useful in clustering. This pa- and throughput, and simulation environments per primarily focuses on providing multiple for testing and debugging. virtual instances of a single physical resource, however, it does cover some examples of a sin- 1 Introduction gle virtual resource mapping to multiple phys- ical resources.
    [Show full text]
  • Abkürzungs-Liste ABKLEX
    Abkürzungs-Liste ABKLEX (Informatik, Telekommunikation) W. Alex 1. Juli 2021 Karlsruhe Copyright W. Alex, Karlsruhe, 1994 – 2018. Die Liste darf unentgeltlich benutzt und weitergegeben werden. The list may be used or copied free of any charge. Original Point of Distribution: http://www.abklex.de/abklex/ An authorized Czechian version is published on: http://www.sochorek.cz/archiv/slovniky/abklex.htm Author’s Email address: [email protected] 2 Kapitel 1 Abkürzungen Gehen wir von 30 Zeichen aus, aus denen Abkürzungen gebildet werden, und nehmen wir eine größte Länge von 5 Zeichen an, so lassen sich 25.137.930 verschiedene Abkür- zungen bilden (Kombinationen mit Wiederholung und Berücksichtigung der Reihenfol- ge). Es folgt eine Auswahl von rund 16000 Abkürzungen aus den Bereichen Informatik und Telekommunikation. Die Abkürzungen werden hier durchgehend groß geschrieben, Akzente, Bindestriche und dergleichen wurden weggelassen. Einige Abkürzungen sind geschützte Namen; diese sind nicht gekennzeichnet. Die Liste beschreibt nur den Ge- brauch, sie legt nicht eine Definition fest. 100GE 100 GBit/s Ethernet 16CIF 16 times Common Intermediate Format (Picture Format) 16QAM 16-state Quadrature Amplitude Modulation 1GFC 1 Gigabaud Fiber Channel (2, 4, 8, 10, 20GFC) 1GL 1st Generation Language (Maschinencode) 1TBS One True Brace Style (C) 1TR6 (ISDN-Protokoll D-Kanal, national) 247 24/7: 24 hours per day, 7 days per week 2D 2-dimensional 2FA Zwei-Faktor-Authentifizierung 2GL 2nd Generation Language (Assembler) 2L8 Too Late (Slang) 2MS Strukturierte
    [Show full text]
  • Detail of Department Programs Supplement to the 2005-06 Proposed Budget 2005-06
    CITY OF LOS ANGELES Detail of Department Programs Supplement to the 2005-06 Proposed Budget 2005-06 Prepared by the City Administrative Officer - April 2005 TABLE OF CONTENTS INTRODUCTION Page Foreword The Blue Book Summary of Changes in Appropriations SECTION 1 - REGULAR DEPARTMENTAL PROGRAM COSTS Aging............................................................................................................................................ ............1 Animal Services........................................................................................................................... ..........11 Building and Safety...................................................................................................................... ..........25 City Administrative Officer ........................................................................................................... ..........39 City Attorney ................................................................................................................................ ..........53 City Clerk..................................................................................................................................... ..........69 Commission for Children, Youth and Their Families................................................................... ..........81 Commission on the Status of Women ......................................................................................... ..........89 Community Development ...........................................................................................................
    [Show full text]
  • Applying MLS To
    Applying a Multi-level Security Mechanism to a Network Address Translation Scheduler Arthur McDonald1 and Haklin Kimm1 Haesun Lee2 and Ilhyun Lee2 1Computer Science Department 2Department of Science and Mathematics East Stroudsburg University of Pennsylvania University of Texas of the Permian Basin East Stroudsburg PA 18301 4901 E. University Blvd. Odessa, TX 79762 E-mail: [email protected] E-mail: [email protected] Abstract - In this paper, we consider a scheduling on their security levels. Using the algorithm that we algorithm being applied with multi-level security that present in this paper, information can be kept at allows two or more hierarchical classification levels of several levels of security on separate server machines, information to be processed simultaneously. There are which will only grant access to the data if the security various load scheduling algorithms pre-built into the Linux level of the client machine is identifiable and has Virtual Server system that have been tested and proven effective for distributing the load among the real servers. been given the proper security clearance. The While these algorithms may work effectively, there is no security levels are statically assigned by the security current scheduling algorithm that considers a multi-level administrator of the LVS and as of this writing there security protocol to determine which clients have access is no way to bypass the scheduler. rights among the servers. 1. Introduction 2. Linux Virtual Servers One of the main concepts in a Linux Virtual In the late 1990s, several open source developers Server is the ability for the director to forward data created a software package for Linux to take packets sent by the client to the appropriate real advantage of scalability and cluster computing.
    [Show full text]
  • Research Report XEN Based HA Backup Environment
    Research Report XEN based HA backup environment Research Report for RP1 University of Amsterdam MSc in System and Network Engineering Class of 2006-2007 Peter Ruissen, Marju jalloh {pruissen,mjalloh}@os3.nl February 5, 2007 RP1: XEN based HA backup environment Abstract In this paper we will investigate the possibilities for High Availability (HA) failover mecha- nisms using the XEN virtualization technology and the requirements necessary for implementation on technical level. Virtualization technology is becoming increasingly popular in server environ- ments because it adds a layer of transparency and flexibility on top of a hardware layer, reduces recovery time and utilizes hardware resources more efficiently. Back in the 1960s, IBM developed virtualization support on a mainframe. Since then, many virtualization projects have become available for UNIX/Linux and other operating systems. The XEN project offers a novel technique known as paravirtualisation which brings a whole new range of possibilities to the table. Our tests showed that it is possible to use XEN in combination with Hearbeat to provide a HA environment. Even though combining XEN virtualization technology and High Availability software is still in the beginning stages at this moment, our research showed that XEN can be used with Heartbeat to realize a flexible, reliable and efficient HA environment.5.1 2 Contents 1 Project information 5 1.1 Assignment formulation . 5 1.2 Project Description . 5 1.3 Scope .............................................. 5 2 Virtualization technology 7 2.1 Forms of VT . 7 3 High availability concepts 9 3.1 Service availability . 10 3.2 Linux High Availability projects . 10 3.3 High Available Storage .
    [Show full text]