DOCSLIB.ORG

Server Virtualization with Vmware Vsphere 4

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Server Virtualization with Vmware Vsphere 4 Server Virtualization with VMware vSphere 4 Masaaki Nishikiori The server virtualization market is expanding rapidly as customers seek savings in both space and energy through efficient use of hardware resources, an increase in business agility through prompt addition and removal of servers, and a reduction in the total cost of ownership (TCO) by separating hardware and business-system life cycles. The virtualization solution offered by Fujitsu and used by a large number of its customers in Japan combines Fujitsu’s high-reliability servers and middleware products, which optimize data center operations, with vSphere 4, VMware’s virtual infrastructure. This paper describes the transition of VMware’s server virtualization products over the years, the functions and features of the vSphere 4 virtual infrastructure, its relation to cloud environments, and examples of using Fujitsu middleware with vSphere 4. 1. Introduction of data center operations. These solutions are The server virtualization market is deployed by more than 1200 customers (as of expanding rapidly as customers seek space and November 2010). Fujitsu has abundant customer energy saving through more efficient usage of experience with these virtualization solutions hardware resources, greater business agility and has released three case studies regarding through prompt addition and removal of servers, cloud systems, which are currently attracting and lower total cost of ownership (TCO) through considerable attention. separation of hardware and business-system life • In-house Case Study 1: “Deployment of cycles. VMware vSphere 4 and Enhancement of VMware, Inc.,1) headquartered in Palo Alto, On-Demand Virtual Environment Hosting California, is a virtualization software vendor for SaaS Providers”2) with approximately 190 000 customers worldwide • In-house Case Study 2: “Putting the and about 6000 customers in Japan (as of Cloud Into Practice: Numazu Software October 2010). Its most recent product offerings Development Cloud Center”3) for building and operating server virtualization • Oita Prefecture Case Study: “Virtualization environments are VMware vSphere 4 and of Mission-critical Systems by VMware vCenter Server (respectively referred to PRIMEQUEST, PRIMERGY, and VMware as “vSphere 4” and “vCenter” hereafter). vSphere 4 toward Creation of a Public Fujitsu started providing VMware products Sector Cloud”4) in 2006 and has since been providing its customers Fujitsu’s server virtualization solutions with virtualization solutions by combining these are based on a number of server virtualization products with its own high-reliability servers as products (such as VMware, Hyper-V, RHEL-Xen, well as its middleware products for optimization RHEL-KVM, and XenServer). From among 356 FUJITSU Sci. Tech. J., Vol. 47, No. 3, pp. 356–361 (July 2011) M. Nishikiori: Server Virtualization with VMware vSphere 4 these, this paper describes the transition of metal,” i.e., hardware—which is currently the VMware server virtualization products over the most popular form [2) in Figure 1]. It features years and introduces the functions of VMware’s higher performance than GSX and has a console latest product, vSphere 4. OS (COS) for hypervisor management. Client management is done by vSphere Client, and 2. Transition of VMware server adding vCenter simplifies management of virtualization multiple ESX hypervisors. Since COS is Linux- This section introduces how VMware’s based, it must be frequently patched, thus server virtualization has changed, focusing on two security is one challenge that it presents. aspects—the “hypervisor” and the “virtualization 3) VMware ESXi (ESXi) product.” The hypervisor, occasionally referred ESXi, the latest hypervisor of VMware, does to as “VM monitor,” is a control program not have a COS [3) in Figure 1]. As with ESX, designed to enable the creation and control of vSphere Client is used to perform management virtual machines (VMs). As shown in Figure 1, tasks. While maintaining the same capabilities VMware’s hypervisor product (shaded boxes as ESX, ESXi is more compact since it has no in the figure) has evolved through three main COS, is easy to install and configure, and does phases. not require COS patches (which reduces security 1) VMware GSX (GSX) risks). The GSX hypervisor runs as an application As summarized above, VMware’s hypervisor on a general purpose OS (the “host OS”) on has evolved into a compact and high-performance hardware [1) in Figure 1]. In this setup, the product with easy-to-install features. host OS is in charge of I/O processing, which Figure 2 shows the evolution of VMware’s enables the hypervisor itself to have a compact virtualization products. configuration. However, this type of hypervisor 1) VMware ESX Server 2.x suffers from overhead and extensibility problems. This product enables resources on an ESX- Like VMware Workstation, it is optimal for PC installed server (ESX server) to be shared among virtualization. VMs. Centralized management of multiple ESX 2) VMware ESX (ESX) servers is provided by vCenter. The ESX hypervisor runs directly on “bare Manager Manager Manager vSphere Client vSphere Client vCenter vCenter VM VM VMware GSX COS VM VM VM VM Host OS VMware ESX VMware ESXi Hardware Hardware Hardware 1) GSX 2) ESX 3) ESXi Figure 1 Evolution of VMware’s hypervisor server virtualization product. FUJITSU Sci. Tech. J., Vol. 47, No. 3 (July 2011) 357 M. Nishikiori: Server Virtualization with VMware vSphere 4 VMware vSphere 4.x VMware Infrastructure 3.x Achievement of a virtual VMware ESX Server 2.x infrastructure including shared resources and support of dynamic changes Transformation of server virtualization environment into a resource pool Centralized management of server virtualization environment 2004 2006 2008 Figure 2 Changes in VMware’s server virtualization environment. 2) VMware Infrastructure 3.x (VI3) functionalities and features of vSphere 4. Adding the concept of resource pooling to vSphere 4 enables users to chose either ESX VMware ESX Server 2.x, VI3 has enhanced or ESXi as the hypervisor and to create a virtual overall capabilities. The CPU and memory infrastructure having the following features. resources of multiple ESX servers can be 1) Wide management scope managed as a resource pool, enabling them to be In general, this kind of infrastructure handled as a single resource pool. virtualizes and pools together physical resources 3) VMware vSphere 4.x and provides VMs with virtualized CPUs, This product has significantly enhanced virtualized memory, virtualized networks, and functionalities compared to those of VI3. It virtualized disks. On top of that, vSphere 4 broadens the management scope to include enables dynamic and detailed management, network resources and shared storage and including resource allocation, configuration enables management of server, network, change, priority control, and access control. and storage resources as a single virtual 2) Flexibility infrastructure. It is better able to deal with vSphere 4 provides a variety of dynamic hardware changes and enables agile functionalities such as dynamic addition of modification of the ESX/VM configuration in virtualized CPUs and virtualized memory (Hot accordance with resource requirement changes. Add), dynamic reconfiguration of virtualized As described above, vSphere 4 represents disks and networks (Hot Plug), dynamic the evolution of VMware’s server virtualization extension of virtualized disks (Hot Extend of products in two major streams: a) more compact, Virtual Disks), and dynamic load balancing of high-performing, and easy-to-install hypervisor network I/O. These functions enable elastic and b) strengthened adaptability to system business operations—responding flexibly to changes. In other words, vSphere 4 is suitable service requirements and hardware changes for environments such as the cloud, where agile without disrupting services provided by VMs. creation and operation of systems is required. 3) Benefits for applications vSphere 4 also provides advanced functions 3. Functions and features such as ones for ensuring business continuity of vSphere 4 virtual (vMotion and Storage vMotion enable the infrastructure moving of resources point-to-point [P2P] without In this chapter, we will dive into the disrupting the operation of VMs), automatic 358 FUJITSU Sci. Tech. J., Vol. 47, No. 3 (July 2011) M. Nishikiori: Server Virtualization with VMware vSphere 4 load balancing (DRS: Distributed Resource individual functionalities, and descriptions for Scheduler), and automatic VM reboot upon vSphere 4. For further details, please check server failure (HA: VMware High Availability). VMware’s public web page.1) Since these functions are part of the virtual The virtual infrastructure is integrally infrastructure, there is no need to reconfigure the managed by vCenter. This enables system OS or applications running on the VMs—they managers to manage almost all management can be used as is. tasks through the vSphere Client graphical user 4) Integrated management interface (GUI), which displays each management vSphere 4 provides useful features and function in icon form for easy operation, enabling extensive function groups for creating and the entire virtual infrastructure to be managed operating virtual infrastructures. With these as a single environment, just like Windows functionalities, vSphere 4 has always been a step control panels (Figure 3). ahead of other hypervisors. Fujitsu provides middleware products that Table 1 lists the major function
Load more

Recommended publications
  • 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
    [Show full text]
  • 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.
    [Show full text]
  • 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.
    [Show full text]
  • 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
    [Show full text]
  • 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
    [Show full text]
  • Dell EMC Host Connectivity Guide for Vmware Esxi Server
    Dell EMC Host Connectivity Guide for VMware ESXi Server P/N 300-002-304 REV 52 May 2020 Copyright © 2016-2020 Dell Inc. or its subsidiaries. All rights reserved. Dell believes the information in this publication is accurate as of its publication date. The information is subject to change without notice. THE INFORMATION IN THIS PUBLICATION IS PROVIDED “AS-IS.” DELL MAKES NO REPRESENTATIONS OR WARRANTIES OF ANY KIND WITH RESPECT TO THE INFORMATION IN THIS PUBLICATION, AND SPECIFICALLY DISCLAIMS IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. USE, COPYING, AND DISTRIBUTION OF ANY DELL SOFTWARE DESCRIBED IN THIS PUBLICATION REQUIRES AN APPLICABLE SOFTWARE LICENSE. Dell Technologies, Dell, EMC, Dell EMC and other trademarks are trademarks of Dell Inc. or its subsidiaries. Other trademarks may be the property of their respective owners. Published in the USA. Dell EMC Hopkinton, Massachusetts 01748-9103 1-508-435-1000 In North America 1-866-464-7381 www.DellEMC.com 2 Dell EMC Host Connectivity Guide for VMware ESXi Server CONTENTS PREFACE 7 Chapter 1 Introduction to VMware Infrastructure 9 VMware vSphere...............................................................................................10 vSphere 6.0..........................................................................................10 vSphere 6.5..........................................................................................10 vSphere 6.7.......................................................................................... 10 VMware ESXi
    [Show full text]
  • Vmware Infrastructure
    Sales Reference Card VMware Infrastructure 3.5 http://www.vmware.com/ October 2008 Vendor and Solution Overview VMware Infrastructure 3.5 is a server virtualization suite that includes the ESX hypervisor and associated management tools. Quick Facts VMware has the largest market share in server virtualization, and enjoys strong brand Corporate Profile: awareness as a virtualization provider. Founded 1998 VMware offers free versions of some of its software (e.g. VMware Server, ESXi) to broaden adoption Ownership Public (VMW) VMware was first to create bare-metal x86 virtualization solutions, and has built up its 2007 Revenue $1.33B leading market share while facing limited competition. Given that its solution was built prior to the availability of virtualization-aware processors Employees 6,000+ and operating systems, VMware’s solution features a first-generation architecture that Office Headquarters Palo Alto, CA USA employs a “binary translation” approach to virtualization that tricks an OS into thinking it is running on physical hardware. Regional Offices Worldwide Recent innovations such as hardware virtualization assist (Intel VT and AMD-V) and Market Share 86% (2007) paravirtualization have cut into VMware’s technology lead. Paravirtualization enables full cooperation between the OS and the hypervisor to deliver the best performance. Hardware-virtualization assist refers to virtualization-aware processors which eliminate Related Products VMware Server the need to perform binary instruction translation in the hypervisor’s software stack. VMware Workstation These developments are more and more disruptive to VMware given its reliance on an VMware VDI older architecture, similar to the “Innovator’s Dilemma” effect chronicled in the book by Harvard professor Clayton Christensen.
    [Show full text]
  • Vmware Virtual Infrastructure Solutions for the Responsive Enterprise
    PRODUCT INFORMATION SHEET VMware Virtual Infrastructure Solutions for the Responsive Enterprise Fast. Flexible. Connected. Changing the Way Your Data Center Conducts Business What if you could snap your fingers and get the IT services you need right away? And pay only for what you use? VMware® VirtualCenter management software is designed to optimize your data center and APPLICATIONS pave the way for utility computing on x86–based servers. By provid- OPERATING SYSTEM ing the ability to view, manage, and quickly deploy enterprise-wide VIRTUAL LAYER data center resources, VMware VirtualCenter enables IT administra- tors to respond to immediate business needs. VMware VirtualCenter software helps administrators manage the many diverse components that make up a virtual infrastructure. VMware’s virtual infrastructure approach to IT management creates virtual services out of the physical IT infrastructure, enabling admin- istrators to allocate these virtual resources quickly to the business STORAGE units that need them most. Administrators can use VMware NETWORK VirtualCenter software to deploy or reallocate resources without all of the configuration changes normally needed in a physical SERVERS environment. Having the right IT assets readily at hand can improve business performance and increase competitive advantage. NETWORK VMware VirtualCenter management software is the vehicle for deliv- SERVERS ering the business benefits of a virtual infrastructure, including: NETWORK • Instant provisioning. Reduce server provisioning time from weeks to minutes, allowing administrators to respond immediately STORAGE to requests for IT services. • Zero-downtime maintenance. Safeguard business continuity 24/7, VMware VirtualCenter manages a virtual infrastructure, including virtual machines running without service interruptions for system maintenance, deployment, on VMware ESX Server™, VMware GSX Server™, virtual storage, and networking.
    [Show full text]
  • Download Vmware P2v Converter
    download vmware p2v converter Welcome the to VMware Converter 3.0 Beta Program! We have received an overwhelming response towards participation in the VMware Converter Beta program. We thank you all for the interest shown and appreciate your patience in waiting for the beta program to be widely available. We are looking forward to your feedback, inputs and suggestions with regards to VMware Converter, as you move forward with testing the next generation migration tool during this beta process. In order to proceed with participation in this beta program, please follow the guided directions for downloading the VMware Converter Beta. Regards, VMware Converter Product Team. Please follow the steps below to get started: Read the supporting documentation. Download product binaries. Install VMware Converter. Launch the VMware Converter application and enjoy the new migration features! Quicklinks. Note: For a faster response and resolution towards the bugs/issues you are reporting, please make sure that you upload the log and core file(s) when applicable. It will usually take us longer to resolve your issue if you do not attach a VMware Converter log file. Zip all your attached files and make sure the total file size is less than 10MB. To export a copy of the log file(s), choose the following from the main menu: File > Export Logs. Recommended logs on Windows 2000 and above: %TEMP%\vmware-p2v-*.log and vmware-p2v-index C:\Windows\Temp\vmware-ufad-*.log and vmware-ufad-index. Recommended logs on Windows NT: %TEMP%\vmware-p2v-*.log and vmware-p2v-index C:\Windows\vmware-ufad-*.log and vmware-ufad-index (note the absence of Temp) Download vmware p2v converter.
    [Show full text]
  • Vmware Infrastructure Architecture Overview Vmware White Paper
    WHITE PAPER VMware Infrastructure Architecture Overview VMWARE WHITE PAPER Table of Contents Physical Topology of the VMware Infrastructure Data Center .............................. .4 Virtual Data Center Architecture . .5 Hosts, Clusters and Resource Pools ..................................................... .6 VMware VMotion, VMware DRS and VMware HA .......................................... .7 Networking Architecture. .8 Storage Architecture .................................................................. .9 VMware Consolidated Backup ......................................................... 10 ESX Server External Interfacing Components ........................................... 10 VirtualCenter Management Server Architecture ......................................... 11 Conclusion .......................................................................... 13 VMWARE WHITE PAPER VMware Infrastructure Architecture Overview VMware® Infrastructure is the industry’s first full infrastruc- ture virtualization suite that allows enterprises and small busi- What is Virtualization and What are Virtual nesses alike to transform, manage and optimize their IT systems Machines? infrastructure through virtualization. VMware Infrastructure delivers comprehensive virtualization, management, resource Virtualization is an abstraction layer that decouples optimization, application availability and operational automa- the physical hardware from the operating system to tion capabilities in an integrated offering. deliver greater IT resource utilization
    [Show full text]
  • Dell EMC SC Series Best Practices with Vmware Vsphere 5.X–6.X
    Best Practices Dell EMC SC Series: Best Practices with VMware vSphere Abstract This document provides best practices for integrating VMware® vSphere® 5.x- 7.x hosts with Dell EMC™ SC Series storage. May 2021 2060-M-BP-V Revisions Revisions Date Description July 2016 Initial release: Combined vSphere 5.x and 6.x best practice documents, added SCOS 7.1 updates September 2016 Minor revisions and corrections October 2016 Changed Disk.AutoremoveOnPDL to reflect current VMware guidance January 2017 Updated for vSphere 6.5 changes; added appendix D summarizing all host settings February 2017 Updated Linux guest disk timeout recommendations in section 4.7.2 April 2017 Updated iSCSI login timeout recommendation July 2017 Updated SAS driver info in 4.2.3, Added auto UNMAP requirements in 16.3.5 April 2018 Updated to provide vSphere 6.7 guidance October 2018 Minor revisions and corrections December 2018 Added SAS front-end lsi_msgpt3 module parameter recommendation in 4.2.3 March 2019 Modified SATP claim rules in section 6.9.1 and appendix D July 2019 Minor revisions and corrections (VMFS3.EnableBlockDelete=1) September 2019 Claim rule syntax corrections April 2020 vSphere 7.0 additions December 2020 Minor clarifications January 2021 Esxcli command syntax change for DelayedAck in appendix D.1 May 2021 Updated section 4.2.3 with additional KB articles for SAS FE connectivity Acknowledgments Author: Darin Schmitz The information in this publication is provided “as is.” Dell Inc. makes no representations or warranties of any kind with respect to the information in this publication, and specifically disclaims implied warranties of merchantability or fitness for a particular purpose.
    [Show full text]
  • Denodo Platform 5.5 Quickstart VM Manual
    Denodo Platform 5.5 QuickStart VM Manual Revision 20150330 NOTE This document is confidential and proprietary of Denodo Technologies. No part of this document may be reproduced in any form by any means without prior written authorization of Denodo Technologies. Copyright © 2015 Denodo Technologies Proprietary and Confidential Denodo Platform 5.5 QuickStart VM Manual 20150330 2 of 11 CONTENTS 1 INTRODUCTION...................................................................3 2 DENODO QUICKSTART VM CONTENTS...................................4 3 DENODO QUICKSTART VM DEPLOYMENT...............................5 3.1 MEMORY CONFIGURATION SETTINGS...............................................5 3.2 NETWORK CONFIGURATION SETTINGS.............................................5 3.3 DEPLOYMENT ON ORACLE VM VIRTUALBOX......................................7 3.4 DEPLOYMENT ON VMWARE..............................................................7 4 POST-INSTALLATION TASKS..................................................9 4.1 INSTALL OS INTEGRATION TOOLS....................................................9 4.2 DENODO PLATFORM CONTROL CENTER STARTUP..............................9 4.3 DENODO LICENSE FILE INSTALLATION..............................................9 4.4 DENODO PLATFORM UPDATES.........................................................9 4.5 DENODO PLATFORM SERVICES STARTUP.........................................10 4.6 DENODO PLATFORM FIRST STEPS..................................................10 5 KNOWN LIMITATIONS........................................................11
    [Show full text]