Platform9 for Vsphere Vs. Vmware Integrated Openstack: 7 Key Differences WHITE PAPER: Platform9 for Vsphere Vs

Total Page:16

File Type:pdf, Size:1020Kb

Platform9 for Vsphere Vs. Vmware Integrated Openstack: 7 Key Differences WHITE PAPER: Platform9 for Vsphere Vs WHITE PAPER Platform9 for vSphere vs. VMware Integrated OpenStack: 7 Key Differences WHITE PAPER: Platform9 for vSphere vs. VMware Integrated OpenStack: Introduction 7 Key Differences Private clouds provide a valuable opportunity for VMware customers to increase the utility of their existing vSphere infrastructure. Those considering OpenStack to achieve automa- tion, self-service, and programmatic infrastructure access for their users often ask us how Platform9 Managed OpenStack for vSphere (Platform9) compares with VMware Integrated OpenStack (VIO). This brief will explain some of the key features that differentiate these two products, but the primary difference is this: Platform9 Managed OpenStack takes a fundamentally different architectural approach than VMware Integrated OpenStack, enabling a fundamentally better solution for OpenStack-based private clouds for VMware vSphere customers. Why? Because instead of just another repackaging of OpenStack like VIO, Platform9 provides an enterprise-grade private cloud solution that incorporates existing assets and is backed by a 24/7 service level agreement (SLA). Existing Environments Many large enterprises and service providers have massive existing deployments of infrastructure, with proven configurations of compute, storage and network infrastructure, along with well-tested operating system (OS) images and existing VM deployments. When implementing OpenStack, organizations generally don’t want to duplicate these investments; they would rather get started by reusing the applicable portions, saving time and money. The Challenge with VIO VIO requires customers to “reboot the stack” and start with greenfield environments. This means existing investments in pre-configured OS images, running VM workloads and network configurations must be duplicated, increasing the time required to implement OpenStack and adding risk to the process. The Platform9 Difference Platform9 does not require customers to reboot anything. Instead, Platform9 automatically discovers existing compute capacity (from clusters and hosts), storage (from datastores), networks (from host vSwitch mappings), VM templates (from datastores) and VMs (from datastores and clusters). Metadata about these existing resources and workloads is then reconciled with the OpenStack control plane, thus eliminating duplication and saving time. 2 Interoperability Organizations that have been using vSphere for several years often have third-party applications, automation scripts, and (most importantly) IT administrators that regularly perform operations directly via vSphere. Cloud platforms such as OpenStack need to interoperate with vSphere so that operations made directly via vSphere do not conflict with OpenStack’s understanding of the underlying infrastructure. The Challenge with VIO VIO takes exclusive control of the vSphere resources it manages. In other words, VIO assumes that OpenStack has sole authority to perform operations on underlying resources. The result is that other VMware and third-party applications (such as Backup/Restore or Site Recovery Manager), vSphere API-based automation scripts, and maintenance operations performed by admins will all conflict with OpenStack and are therefore unsupported. Examples of such unsupported operations include: • vMotion of VMs across clusters • Storage vMotion of VMs across datastores • VM power operations • VM creation and deletion • Cluster, datastore and network maintenance operations that can reconfigure datastores or clusters The Platform9 Difference Platform9 works by discovering the environment metadata, and refreshing that metadata every few minutes. This updated metadata is then reconciled with the OpenStack control plane, making OpenStack resilient to any changes made via vSphere directly. Therefore, Platform9 fully supports “dual-mode” operation and there are no restrictions on what operations can be performed via vSphere. 3 OpenStack Lifecycle and SLA It is generally understood that running OpenStack at scale and in production can be challenging. Key challenges to consider include: • 24/7 monitoring: OpenStack is a complex distributed system with several services that interact with compute node agents via message queues. Failures can occur at many different sites and if not detected and fixed quickly, small failures can cause “pile-ups” that eventually affect the entire environment. To keep the system running smoothly, the entire stack needs to be monitored 24/7 to detect and address problems immediately. • Patches for urgent issues: Once discovered, problems must be fixed quickly to prevent a pile-up that affects the entire cloud. Often, this requires the development of a patch to OpenStack services and rolling out that patch into production within a few hours. • Upgrades: OpenStack has a major new release every six months with significant bug-fixes and valuable new features. To avoid disruption of production OpenStack deployments, IT teams need visibility on the frequency with which their OpenStack release will be updated and how it will be rolled out. The Challenge with VIO VIO doesn’t include a 24/7 monitoring mechanism that IT can lean on. Instead, IT has to monitor all of OpenStack’s footprint, so when there is a problem, it’s up to IT to catch it and work through VMware’s manual, time-consuming support process to help get a resolution. Patches can take weeks or months to be developed, and VIO’s massive footprint (16-VM appliance) makes rolling out new patches complex and risky. In addition, there is no backup strategy while rolling out patches or upgrades to new releases of OpenStack. In short, VIO doesn’t address critical issues about the OpenStack lifecycle, thereby putting service levels at risk for the VIO cloud. The Platform9 Difference Platform9 is designed with a focus on not only the initial configuration of OpenStack but also managing the ongoing lifecycle. Every Platform9 deployment is monitored 24/7 (controller health, message queue health and compute node agent health), and therefore problems are detected within seconds. Since Platform9 monitors hundreds of OpenStack clouds across the globe, we detect problems that might be latent in a given OpenStack deployment. Such problems are triaged continuously and patches are developed as required. These patches can be rolled out to customers within 4-8 hours, thereby mitigating the risk of pile-ups. New OpenStack releases are tested extensively and rolled out to customers every 12 months (i.e. every two OpenStack releases). In short, Platform9 owns responsibility for OpenStack service levels. Through a contractual service level agreement (SLA), Platform9 continuously manages and tunes the OpenStack environment, insulating customers from the need to think about, much less spend time on, OpenStack service levels. 4 Multi-vCenter / Regions Many larger organizations have multiple vCenter deployments due to vCenter’s scale limitations and/or infrastructure that spans multiple geographies. When using OpenStack to orchestrate vSphere, organizations should pay attention to the operational cost of managing multiple vSphere deployments. The Challenge with VIO VIO is limited in scope to a single vSphere environment. Managing multiple vSphere deployments requires many OpenStack deploy- ments. Moreover, for each vSphere environment, VIO is packaged as an extremely resource-intensive, 16-VM virtual appliance that consumes 200GB of memory just for OpenStack! These factors are problematic from an operational perspective: • Multiple OpenStack deployments dramatically increases management complexity • Resources across multiple vSphere deployments cannot be pooled, managed and consumed via a single OpenStack API. • Different geographies cannot be reflected via OpenStack as independent “regions” • The total resources required just for VIO can be massive (multiple TB of memory) The Platform9 Difference Platform9’s design simplifies managing multiple vSphere deployments: • Each vCenter is managed by a single, lightweight and stateless vSphere gateway appliance. This gateway appliance is small, hardened, and serves as a stateless API proxy between vCenter and OpenStack. Therefore, its resource requirements are just 1-2% of that of VIO. • Managing multiple vCenters is a simple matter of deploying multiple vSphere gateways. • Resources in different geographies can be reflected in Platform9 as distinct “regions”, similar to how Amazon Web Services reflects regions independently. 5 Choice vs. Lock-in OpenStack can serve as an open API “interconnect” between compute, storage and network technologies in the data center, enabling greater freedom of choice in technology investments. However, some OpenStack options are truly open and enable choice, while others are very restricted and fail to deliver the level of interoperability that OpenStack is capable of. The Challenge with VIO VIO has a number of restrictions, and has been criticized by some as VMware’s attempt to prevent customers from making non-VM- ware-friendly technology choices. Its restrictions include: • Hypervisor: vSphere Enterprise Plus is the only supported hypervisor platform. Notable exclusions include: • KVM on CentOS / Ubuntu / RHEL • vSphere Enterprise • Networking: VMware NSX is the only fully Neutron-compatible software-defined network (SDN) platform. Exclusions include: • Linux/OVS • Cisco/APIC • Juniper/Contrail • PlumGrid The Platform9 Difference Unlike VMware, Platform9 does not have a vested interest in any hardware, OS, or virtualization platform and is committed
Recommended publications
  • Oracle Database on AWS October 2013
    Amazon Web Services – RDBMS in the Cloud: Oracle Database on AWS October 2013 RDBMS in the Cloud: Oracle Database on AWS Jean-Pierre Le Goaller, Carlos Conde, and Shakil Langha October 2013 (Please consult http://aws.amazon.com/whitepapers/ for the latest version of this paper) Page 1 of 33 Amazon Web Services – RDBMS in the Cloud: Oracle Database on AWS October 2013 Table of Contents Abstract ................................................................................................................................................................................... 3 Oracle Database Solutions on AWS ........................................................................................................................................ 3 Oracle Database on Amazon RDS ....................................................................................................................................... 3 Oracle Database on Amazon EC2 ........................................................................................................................................ 3 Other Database Scenarios ................................................................................................................................................... 3 Choosing between Amazon RDS and Amazon EC2 for an Oracle Database ........................................................................... 4 Oracle Database Feature Comparison between Amazon RDS and Amazon EC2 ............................................................... 5 Oracle Licensing and
    [Show full text]
  • Website Hosting Amazon Web Services
    Website Hosting Amazon Web Services Arpit Ahuja, Principal Consultant [email protected] Why to host your website on AWS Website on Amazon Web Service Low Scalable Flexible Cost Stable About Amazon Web Services • World’s leading Cloud Computing Platform • Collection of Remote Computing Services (Web Services) • Powered by Amazon.com – World’s leading Ecommerce Portal • Currently have Data Centers in 10 Geographic locations • Multiple Availability Zones in each region • Edge locations for content distribution in many other geographies • Have done 42 Price Reductions in the last 8 years (Launched in 2006) • More than a Use Cases • Public Website • A company’s website is one of its most visible, accessible, and valuable ways of communicating with current and potential customers. Putting your website on the AWS cloud is fast, easy, and low-cost. • Online Application • Connected applications underpin the modern Internet. Amazon Web Services provides the services you need to make your application successful online. • Intranet Site • Internal websites help share information within your organization and aid collaboration while keeping the information protected from those outside your organization. • Connected Mobile Application • Many mobile applications rely on servers behind the scenes to deliver the information that makes them useful. Many of the world’s biggest sites uses AWS Capabilities • AWS is a flexible cloud computing solution. You can use whatever platform you like. AWS even provides SDKs for many popular platforms like Java, Ruby, PHP, Node.js, .Net, and more. Use Your Favorite Tools • Your content management system (CMS) may be the core of your website. No matter which system you choose; it can run on AWS Let your website grow and shrink with demand • Website traffic can fluctuate a lot.
    [Show full text]
  • Creating Smart Virtual Appliances with IBM Image Construction and Composition Tool
    Front cover Creating Smart Virtual Appliances with IBM Image Construction and Composition Tool Create smart appliances that are cloud-ready Develop PowerVM, KVM, and ESX customized virtual appliances Learn from experts how to cloudify your applications Jarek Miszczyk Greg Hurlebaus Pat Nickel Rashed Ferdous David Peraza John Jacobson Moises Romo Li-Fang Lee Kerry Staples ibm.com/redbooks International Technical Support Organization Creating Smart Virtual Appliances with IBM Image Construction and Composition Tool July 2013 SG24-8042-01 Note: Before using this information and the product it supports, read the information in “Notices” on page ix. Second Edition (July 2013) This edition applies to Version 2, Release 2, Modification 1.1 of the IBM Image Construction and Composition Tool. © Copyright International Business Machines Corporation 2012, 2013. 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 . ix Trademarks . .x Preface . xi Authors. xi Now you can become a published author, too! . xiii Comments welcome. xiii Stay connected to IBM Redbooks . xiv Chapter 1. Introduction to virtual appliance construction . 1 1.1 Deploying your applications into the cloud . 2 1.2 Solving the terminology puzzle . 3 1.3 Why implement software virtual appliances . 4 1.4 A need for a virtual appliance construction tool . 5 1.4.1 Application packaging options . 5 1.4.2 Supported deployment options . 5 1.5 Putting the Image Construction and Composition Tool into context . 7 1.5.1 Image Construction and Composition Tool and the IBM PureSystems . 7 1.5.2 Image Construction and Composition Tool and the IBM Workload Deployer.
    [Show full text]
  • Best Practices for Building Virtual Appliances Vmware White Paper
    WHITE PAPER Best Practices for Building Virtual Appliances VMWARE WHITE PAPER Table of Contents Objectives. 3 Design Principles . 3 Completely Encapsulated. 3 Optimized Virtual Disk and Operating System. 4 Initial Configuration. 4 ‘Standard’ Components. 5 Command Line Interface . 5 SSH Support. 5 Web Management Interface . 5 External Management . 5 Virtual Machine Configuration. 6 Updates and Ongoing Maintenance. 6 Packaging and Publishing . 6 2 VMWARE WHITE PAPER Best Practices for Building Virtual Appliances A virtual appliance is a pre-installed, pre-configured operating system and software solution delivered inside a virtual machine. 60-70% of support calls relate to initial installation and Deploying a software solution as a virtual appliance enables you configuration of a software application to build a complete turnkey package that customers are able to download and immediately deploy. Thus, customers skip the time-consuming and often support-intensive task of installing and configuring the appliance. This lets customers focus all their energies on trying or using your solution rather than struggling Design Principles to get it to run. Completely Encapsulated This document describes the best practices for building a virtual A virtual appliance contains all of the components required to appliance. It covers high level design principles as well as low run your solution on top of a virtualization layer. Since virtual level details for building virtual appliances ready for certification appliances are designed to run a specific solution, customers under the VMware Certified Virtual Appliance program. In turn, should not need root access to the operating system inside virtual appliances built according to these standards will allow your appliance.
    [Show full text]
  • Reproducibility, Virtual Appliances, and Cloud Computing
    1 Reproducibility, Virtual Appliances, and Cloud Computing Bill Howe University of Washington CONTENTS 1.1 Introduction ...................................................... 1 1.2 Background on Cloud Computing and Virtualization ........... 2 1.3 Related Approaches and Examples .............................. 3 1.3.1 Other Uses of Virtual Machines ......................... 5 1.3.2 Towards Services Instead of Artifacts ................... 6 1.4 How Cloud Computing can Improve Reproducibility ........... 6 1.4.1 Capturing More Variables ............................... 6 1.4.2 Fewer constraints on research methods ................. 6 1.4.3 On-Demand Backups .................................... 7 1.4.4 Virtual Machines as Citable Publications ............... 7 1.4.5 Code, Data, Environment, plus Resources .............. 7 1.4.6 Automatic Upgrades ..................................... 8 1.4.7 Competitive, Elastic Pricing ............................ 8 1.4.8 Reproducibility for Complex Architectures. ............. 8 1.4.9 Unfettered Collaborative Experiments .................. 8 1.4.10 Data-intensive Computing ............................... 9 1.4.11 Cost Sharing ............................................. 9 1.4.12 A Foundation for Single-Payer Funding ................. 9 1.4.13 Compatibility with Other Approaches .................. 9 1.5 Remaining Challenges ............................................ 10 1.5.1 Cost ...................................................... 10 1.5.2 Culture ..................................................
    [Show full text]
  • Amazon Elastic Compute Cloud User Guide for Linux API Version 2015-04-15 Amazon Elastic Compute Cloud User Guide for Linux
    Amazon Elastic Compute Cloud User Guide for Linux API Version 2015-04-15 Amazon Elastic Compute Cloud User Guide for Linux Amazon Elastic Compute Cloud: User Guide for Linux Copyright © 2015 Amazon Web Services, Inc. and/or its affiliates. All rights reserved. The following are trademarks of Amazon Web Services, Inc.: Amazon, Amazon Web Services Design, AWS, Amazon CloudFront, AWS CloudTrail, AWS CodeDeploy, Amazon Cognito, Amazon DevPay, DynamoDB, ElastiCache, Amazon EC2, Amazon Elastic Compute Cloud, Amazon Glacier, Amazon Kinesis, Kindle, Kindle Fire, AWS Marketplace Design, Mechanical Turk, Amazon Redshift, Amazon Route 53, Amazon S3, Amazon VPC, and Amazon WorkDocs. In addition, Amazon.com graphics, logos, page headers, button icons, scripts, and service names are trademarks, or trade dress of Amazon in the U.S. and/or other countries. Amazon©s trademarks and trade dress may not be used in connection with any product or service that is not Amazon©s, in any manner that is likely to cause confusion among customers, or in any manner that disparages or discredits Amazon. All other trademarks not owned by Amazon are the property of their respective owners, who may or may not be affiliated with, connected to, or sponsored by Amazon. Amazon Elastic Compute Cloud User Guide for Linux Table of Contents What Is Amazon EC2? ................................................................................................................... 1 Features of Amazon EC2 .......................................................................................................
    [Show full text]
  • Virtual Scanner Appliance User Guide
    Virtual Scanner Appliance User Guide April 22, 2021 Verity Confidential Copyright 2012-2021 by Qualys, Inc. All Rights Reserved. Qualys and the Qualys logo are registered trademarks of Qualys, Inc. All other trademarks are the property of their respective owners. Qualys, Inc. 919 E Hillsdale Blvd 4th Floor Foster City, CA 94404 1 (650) 801 6100 Table of Contents About this guide............................................................................................... 3 About Qualys ........................................................................................................................... 3 Qualys Support ........................................................................................................................ 3 Get Started ........................................................................................................ 4 It’s easy to add a virtual scanner........................................................................................... 4 Add Your Virtual Scanner ...................................................................................................... 5 We recommend one more thing.......................................................................................... 10 Configuration settings ................................................................................... 11 Troubleshooting............................................................................................. 16 Why do I see an Activation Code? ......................................................................................
    [Show full text]
  • The Future of Virtualization Technology
    The Future of Virtualization Technology Stephen Alan Herrod VP of Technology VMware Agenda •Virtualization Today •Technology Trends and the Future Datacenter •Future directions • CPU Virtualization • I/O Virtualization • Virtual appliances •Conclusions 2 X86 Server Virtualization Basics Application Operating System Before Server Virtualization: Single OS image per machine Software and hardware tightly coupled Running multiple applications on same machine often creates conflict Underutilized resources 3 X86 Server Virtualization Basics VM1 VM2 App App Application Operating System Operating System Virtualization Layer Operating System Before Server Virtualization: After Server Virtualization: Single OS image per machine Virtual machines (VMs) break 1-to-1 dependency between OS and HW Software and hardware tightly coupled Manage OS and application as single Running multiple applications on unit by encapsulating them into VMs same machine often creates conflict Strong isolation between VMs Underutilized resources Hardware-independent: they can be provisioned anywhere 4 X86 Server Virtualization Architectures •Hosted Architectures • Install as applications on Windows/Linux with small context switching driver • Leverage host IO stack and resource management • Examples include VMware Workstation, VMware Server, Microsoft Virtual PC, Microsoft Virtual Server, … •Bare-metal Architectures • “Hypervisor” installs directly on hardware • Approach acknowledged as direction for datacenter • VMware ESX Server, Xen, Microsoft Viridian 5 Bare-metal
    [Show full text]
  • Cloud Computing Infrastructure on IBM Power Systems Getting Started with ISDM
    Front cover Cloud Computing Infrastructure on IBM Power Systems Getting started with ISDM Detailed cloud resource configuration instructions Detailed installation steps of ISDM Point and click deployment of AIX Thierry Huché Behzad Koohi Thanh V. Lam Paul Reynolds Sean M. Swehla Jez Wain ibm.com/redbooks International Technical Support Organization Cloud Computing Infrastructure on IBM Power Systems: Getting Started with ISDM May 2012 SG24-7983-00 Note: Before using this information and the product it supports, read the information in “Notices” on page xv. First Edition (May 2012) This edition applies to Version 7.2.2, of IBM Service Delivery Manager (CRFK7ML). © Copyright International Business Machines Corporation 2012. 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 Figures . vii Tables . xiii Notices . xv Trademarks . xvi Preface . xvii The team who wrote this book . xviii Now you can become a published author, too! . xix Comments welcome. xix Stay connected to IBM Redbooks . xx Chapter 1. Introduction . 1 1.1 Target audience . 2 1.2 IBM Service Delivery Manager and cloud computing . 2 1.3 IBM Service Delivery Manager components . 4 1.4 TivSAM virtual appliance. 5 1.5 IBM Tivoli Monitoring (ITM) appliance. 8 1.6 IBM Tivoli Usage and Accounting Manager (TUAM) appliance . 9 1.7 NFS appliance. 10 1.8 Connecting the appliances . 13 Chapter 2. IBM Service Delivery Manager prerequisites . 15 2.1 Hardware prerequisites . 16 2.1.1 Computer nodes . 16 2.1.2 Management node . 16 2.1.3 Our configuration.
    [Show full text]
  • Virtual Appliance Installation Guide
    Oracle® SD-WAN Edge Virtual Appliance Installation Guide Release 9.0 F29171-04 June 2021 Oracle SD-WAN Edge Virtual Appliance Installation Guide, Release 9.0 F29171-04 Copyright © 2019, 2021, Oracle and/or its affiliates. This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited. The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing. If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable: U.S. GOVERNMENT END USERS: Oracle programs (including any operating system, integrated software, any programs embedded, installed or activated on delivered hardware, and modifications of such programs) and Oracle computer documentation or other Oracle data delivered to or accessed by U.S. Government end users are "commercial computer software" or "commercial computer software documentation" pursuant to the applicable Federal Acquisition
    [Show full text]
  • Sophos Virtual Email Appliance Setup Guide Contents Installing a Virtual Appliance
    Sophos Virtual Email Appliance setup guide Contents Installing a virtual appliance.....................................................................................................................1 Prerequisites.............................................................................................................................................3 Enabling Port Access...............................................................................................................................4 Downloading Virtual Appliance Files....................................................................................................... 7 Determining Disk Space and Memory Requirements..............................................................................8 Adding a virtual appliance....................................................................................................................... 9 Starting a Virtual Appliance................................................................................................................... 12 Configuring Network Settings............................................................................................................... 13 Cloning Considerations.......................................................................................................................... 14 Re-Registering a Virtual Appliance.......................................................................................................15 Troubleshooting VMware Performance..................................................................................................17
    [Show full text]
  • Amazon Elastic Compute Cloud User Guide API Version 2011-11-01 Amazon Elastic Compute Cloud User Guide
    Amazon Elastic Compute Cloud User Guide API Version 2011-11-01 Amazon Elastic Compute Cloud User Guide Amazon Elastic Compute Cloud: User Guide Copyright © 2011 Amazon Web Services LLC or its affiliates. All rights reserved. Amazon Elastic Compute Cloud User Guide Table of Contents Welcome ............................................................................................................................................................. 1 Introduction to Amazon EC2 .............................................................................................................................. 3 Using Amazon EC2 .......................................................................................................................................... 14 Using AMIs ........................................................................................................................................... 15 AMI Basics .................................................................................................................................. 15 Creating Your Own AMIs ............................................................................................................. 17 Overview of the AMI Creation Process .............................................................................. 17 Creating Amazon EBS-Backed AMIs ................................................................................. 18 Bundling Amazon EC2 instance store-backed Windows AMIs .......................................... 21 Bundling Amazon EC2 instance
    [Show full text]