DOCSLIB.ORG

Solaris Virtualization Options 7 Final Configuration File for the Zone

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Solaris Virtualization Options 7 Final Configuration File for the Zone t h e V irtualization options for wenjin Hu, Todd desHane, and Solaris have been expanding rapidly. In this jeanna Matthews article we discuss three types of virtualiza- tion systems available in OpenSolaris for x86: Solaris Containers, Solaris xVM, and Sun xVM VirtualBox. We include instruc- Solaris virtualization tions on how to deploy each solution and options a detailed comparison of the three to help system administrators and virtualization Wenjin Hu is a PhD student in Computer Science fans alike choose the appropriate virtualiza- at Clarkson University. He focuses on applying virtualization and file system techniques to provide tion technology for their needs. Even if you security and reliability on the desktop. don’t use Solaris, we do explain the differ- [email protected] ences among OS-level virtualization, para- virtualization, and full-virtualization clearly. Todd Deshane is a PhD student in Engineering Science at Clarkson University. His current research deals with using virtualization to provide security Solaris has included Containers (also called Zones) on the desktop. since Solaris 10 was released in 2005. Containers [email protected] are an operating-system-level virtualization facility, meaning that the OS itself provides the illusion of multiple independent systems, each with its own Jeanna Neefe Matthews is an associate profes- IP address and file system, all based on the same sor of Computer Science at Clarkson University in base kernel. More recently, support for paravirtu- Potsdam, NY, where she leads an incredible team of alization in the form of Xen (called Sun xVM on students. She is currently on sabbatical and work- ing with VMware in Cambridge, MA. Solaris) has been added and now, with the acquisi- tion of VirtualBox, full virtualization on Solaris is [email protected] also an option. Unlike OS-level virtualization, par- avirtualization and full virtualization both offer the ability to run guest operating systems that are dif- ferent from the underlying OS. Full virtualization can run unmodified operating systems, whereas paravirtualization requires targeted changes to the hardware interface and therefore correspond- ing changes in the OS source code. As a result, proprietary operating systems such as Microsoft Windows can typically only be run on virtualiza- tion systems that support full virtualization. Some virtualization systems, such as Xen, require hard- ware support for virtualization, such as Intel VT or AMD-V, to support full virtualization. getting started with solaris containers In Solaris Containers/Zones, a virtual machine is called a zone and a zone with resource limitations is called a container. The basic command to operate a zone’s configuration file is zonecfg –z newzone. This will bring up a shell in which you can issue a variety of commands to manipulate the specified zone. As shown in Listing 1, you create a zone, add the attached devices such as add net, set zone options such as set autoboot=true, display the configuration, verify the configuration, and finally commit a zone’s resources, which writes out a ;LOGIN: OctOber 2008 sOLArIs vIrtualizAtion Options 7 final configuration file for the zone. You can also use zonecfg to browse the characteristics of an existing zone and modify it as desired. # zonecfg -z newzone newzone: No such zone configured Use ‘create’ to begin configuring a new zone. zonecfg:newzone> create zonecfg:newzone> set zonepath=/export/home/newzone zonecfg:newzone> set autoboot=true zonecfg:newzone> add net zonecfg:newzone:net> set address=192.168.16.109 zonecfg:newzone:net> set physical=pcn0 zonecfg:newzone:net> end zonecfg:newzone> verify zonecfg:newzone> commit zonecfg:newzone> exit Listing 1: the steps shOwing the ZOne ConfiguratiOn Solaris provides a number of options to manage the resources that a zone can own, including the CPU, the memory, and the number of the pro- cesses. This is the heart of making a zone into a container with resource limitations. In Listing 2, we illustrate how to add a variety of restrictions to our new zone. (These commands are also issued at the zonecfg prompt.) The capped-cpu command limits the CPU cycles assigned to the zone to a fourth of one CPU. Similarly, our capped-memory command assigns the zone 128 MB of memory and 512 MB of swap space. It also guarantees that 64 MB of the zone’s memory will be resident in physical memory at all times. Finally, the set max-lwps command illustrates how we can place limits on things besides physical resources. It limits the number of light- weight processes in a running zone and is useful for preventing problems such as fork-bombs from taking down the whole machine. add capped-cpu set ncpus=0.25 end add capped-memory set physical=128M set swap=512M set locked=64M end set max-lwps=175 Listing 2: the OptiOns Limiting the Container’s resOurces Once our new zone is configured, we are ready to instantiate it with the command zoneadm –z newzone install and then run it with the com- mand zoneadm –z newzone boot. zoneadm can also be used for other zone administration functions such as listing the configured zones, install- ing or uninstalling the zones, and booting, pausing, and halting installed zones. Listing 3 shows the output of running zoneadm list after installing our new zone. The parameter –c will display all the configured zones’ infor- mation; –v will display the detailed information of zones. # zoneadm list -vc ID NAME STATUS PATH BRAND IP 0 global running / native shared 1 newzone running /export/home/newzone native shared Listing 3: a ZOneadm List shOwing all zones 8 ;LOGIN: vOL. 33, NO. 5 Finally, we are ready to log in to our new zone with the command zlogin newzone. It will be running the same version of OpenSolaris as the base operating system, as is required with OS-level virtualization. However, the zone will behave like a separate system, with its own IP address, its own file system, and its own set of installed applications. getting started with solaris xVM A virtual machine in xVM is called a domain, just as it is in other Xen im- plementations. Domains are divided into two major categories: paravirtual- ized (PV) domains and Hardware-assisted Virtual Machine (HVM) domains. In a PV domain, the hardware abstraction presented to the guest VM is not identical to the underlying physical hardware; instead, strategic changes are made to make the system easier to virtualize. To run properly on the para- virtualized hardware, the guest operating system must be modified to be aware of these changes. This requires source-code-level changes to the OS and is therefore rarely available for proprietary operating systems such as Windows. Two common choices for paravirtualized guest domains are So- laris and Linux. In an HVM domain, the hardware abstraction presented to the guest is iden- tical to the underlying hardware, so any operating system that runs on x86 hardware architecture can be installed. To make this possible, an HVM do- main relies on special hardware support for virtualization such as Intel V-T or AMD-V. If your system does not have this hardware support for virtual- ization, then paravirtualized domains are your only option. Xen is a virtual machine monitor, called a hypervisor, which intercepts the guest domain’s system calls. It is necessary to boot the Xen-enabled Solaris kernel on the physical machine rather than a normal Solaris kernel. Since Solaris Nevada Version build 75, Xen has been developed and well inte- grated into Solaris Express Community Edition through a variety of boot options in the GRUB menu. For example, the standard GRUB menu displays three choices: Solaris Express Community Edition snv87 X86, Solaris xVM, and Solaris Failsafe; the second grub option, Solaris xVM, should be chosen. Xen also relies on a special, privileged domain, called Domain0, and the Xen control daemon, Xend, for communication between the hypervisor and the guests. Domain0 is granted the full privileges of managing the guest do- mains and the physical devices by the Xen hypervisor, similar to a “normal” Solaris OS instance. Device drivers can also be fully virtualized or paravirtualized. Even a system that does full virtualization of the CPU and memory can load paravirtual- ized drivers to handle external devices such as a disk or network interface. In a paravirtualized driver, the driver running in the guest operating system is aware of the hypervisor and explicitly participates in communicating its requests to domain0 where the real physical device drivers are running. In a fully virtualized driver, the real device access still occurs on the Domain0 drivers, but the guest driver is unaware of this, so the hypervisor must trap accesses to I/O space or DMA operations in order to forward them on to the proper device driver in Domain0. PV drivers have much lower overhead, be- cause they avoid this expensive process of trapping and forwarding. Our first step in running Xen guests is to make sure that the hypervisor, Domain0, and Xend are all running. After Solaris xVM boots up, you can use the command virsh list as shown in Listing 4 to check whether Domain0 is running. ;LOGIN: OctOber 2008 sOLArIs vIrtualizAtion Options 9 # virsh list Id Name State --------------------------------------------------- 0 Domain-0 running 110 newSolaris blocked Listing 4: Virsh List shOwing Domain0 Next, we check that Xend is running and specify the default network in- terface in Xend first so that our guest domains are able to set up the virtual network based on that physical NIC. Xend is wrapped as an application ser- vice in Solaris. Listing 5 illustrates the use of svccfg and svcadm facilities to configure and restart Xend. The –s parameter specifies the Xend service; setprop specifies the Xend configuration options.
Load more

Recommended publications
  • Industrial Control Via Application Containers: Migrating from Bare-Metal to IAAS
    Industrial Control via Application Containers: Migrating from Bare-Metal to IAAS Florian Hofer, Student Member, IEEE Martin A. Sehr Antonio Iannopollo, Member, IEEE Faculty of Computer Science Corporate Technology EECS Department Free University of Bolzano-Bozen Siemens Corporation University of California Bolzano, Italy Berkeley, CA 94704, USA Berkeley, CA 94720, USA fl[email protected] [email protected] [email protected] Ines Ugalde Alberto Sangiovanni-Vincentelli, Fellow, IEEE Barbara Russo Corporate Technology EECS Department Faculty of Computer Science Siemens Corporation University of California Free University of Bolzano-Bozen Berkeley, CA 94704, USA Berkeley, CA 94720, USA Bolzano, Italy [email protected] [email protected] [email protected] Abstract—We explore the challenges and opportunities of control design full authority over the environment in which shifting industrial control software from dedicated hardware to its software will run, it is not straightforward to determine bare-metal servers or cloud computing platforms using off the under what conditions the software can be executed on cloud shelf technologies. In particular, we demonstrate that executing time-critical applications on cloud platforms is viable based on computing platforms due to resource virtualization. Yet, we a series of dedicated latency tests targeting relevant real-time believe that the principles of Industry 4.0 present a unique configurations. opportunity to explore complementing traditional automation Index Terms—Industrial Control Systems, Real-Time, IAAS, components with a novel control architecture [3]. Containers, Determinism We believe that modern virtualization techniques such as application containerization [3]–[5] are essential for adequate I. INTRODUCTION utilization of cloud computing resources in industrial con- Emerging technologies such as the Internet of Things and trol systems.
    [Show full text]
  • Oracle VM Virtualbox Container Domains for SPARC Or X86
    1 <Insert Picture Here> Virtualisierung mit Oracle VirtualBox und Oracle Solaris Containern Detlef Drewanz Principal Sales Consultant SAFE HARBOR STATEMENT The following is intended to outline our general product direction. It is intended for information purposes only, and may not be incorporated into any contract. It is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions. The development, release, and timing of any features or functionality described for Oracle’s products remains at the sole discretion of Oracle. In addition, the following is intended to provide information for Oracle and Sun as we continue to combine the operations worldwide. Each country will complete its integration in accordance with local laws and requirements. In the EU and other non-EU countries with similar requirements, the combinations of local Oracle and Sun entities as well as other relevant changes during the transition phase will be conducted in accordance with and subject to the information and consultation requirements of applicable local laws, EU Directives and their implementation in the individual members states. Sun customers and partners should continue to engage with their Sun contacts for assistance for Sun products and their Oracle contacts for Oracle products. 3 So .... Server-Virtualization is just reducing the number of boxes ? • Physical systems • Virtual Machines Virtualizationplattform Virtualizationplattform 4 Virtualization Use Workloads and Deployment Platforms
    [Show full text]
  • Virtualization Getting Started Guide
    Red Hat Enterprise Linux 7 Virtualization Getting Started Guide Introduction to virtualization technologies available with RHEL Last Updated: 2020-02-24 Red Hat Enterprise Linux 7 Virtualization Getting Started Guide Introduction to virtualization technologies available with RHEL Jiri Herrmann Red Hat Customer Content Services [email protected] Yehuda Zimmerman Red Hat Customer Content Services [email protected] Dayle Parker Red Hat Customer Content Services Laura Novich Red Hat Customer Content Services Jacquelynn East Red Hat Customer Content Services Scott Radvan Red Hat Customer Content Services Legal Notice Copyright © 2019 Red Hat, Inc. This document is licensed by Red Hat under the Creative Commons Attribution-ShareAlike 3.0 Unported License. If you distribute this document, or a modified version of it, you must provide attribution to Red Hat, Inc. and provide a link to the original. If the document is modified, all Red Hat trademarks must be removed. Red Hat, as the licensor of this document, waives the right to enforce, and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent permitted by applicable law. Red Hat, Red Hat Enterprise Linux, the Shadowman logo, the Red Hat logo, JBoss, OpenShift, Fedora, the Infinity logo, and RHCE are trademarks of Red Hat, Inc., registered in the United States and other countries. Linux ® is the registered trademark of Linus Torvalds in the United States and other countries. Java ® is a registered trademark of Oracle and/or its affiliates. XFS ® is a trademark of Silicon Graphics International Corp. or its subsidiaries in the United States and/or other countries.
    [Show full text]
  • Fortianalyzer VM Install Guide This Document, Which Describes Installing Fortianalyzer VM in Your Virtual Environment
    FortiAnalyzer VM - Install Guide VERSION 5.4 FORTINET DOCUMENT LIBRARY http://docs.fortinet.com FORTINET VIDEO GUIDE http://video.fortinet.com FORTINET BLOG https://blog.fortinet.com CUSTOMER SERVICE & SUPPORT https://support.fortinet.com FORTIGATE COOKBOOK http://cookbook.fortinet.com FORTINET TRAINING SERVICES http://www.fortinet.com/training FORTIGUARD CENTER http://www.fortiguard.com END USER LICENSE AGREEMENT http://www.fortinet.com/doc/legal/EULA.pdf FEEDBACK Email: [email protected] May 18, 2017 FortiAnalyzer VM 5.4 Install Guide 05-540-309958-20170518 TABLE OF CONTENTS Change Log 5 Introduction 6 FortiAnalyzer documentation 6 License and System Requirements 7 Licensing 7 Evaluation license 7 Minimum system requirements 8 Registration and Deployment 9 Register with Customer Service & Support 9 Deployment package 11 Deployment package contents 12 Deploying the appliance 13 Citrix XenServer deployment example 14 Create the virtual machine 14 Configure hardware settings 15 Start the virtual machine 17 Hyper-V deployment example 18 Create the virtual machine 18 Configure hardware settings 19 Start the virtual machine 23 KVM deployment example 24 Create the virtual machine 24 Configure hardware settings 26 Start the virtual machine 27 Open Xen deployment example 28 Create and configure the virtual machine 28 VMware deployment example 31 VMware vSphere 31 Deploy the OVF file 31 Configure hardware settings 34 Power on the virtual machine 35 Azure deployment example 37 Deploy the virtual machine 37 AWS deployment example 39 AWS Marketplace 1-Click Launch 39 AWS EC2 console 41 Initial Configuration 46 GUI access 46 Enable GUI access 46 Connect to the GUI 47 Upload the license file 48 Configure your FortiAnalyzer VM 48 Index 50 Change Log Change Log Date Change Description 2016-03-17 Initial release.
    [Show full text]
  • KVM Based Virtualization and Remote Management Srinath Reddy Pasunuru St
    St. Cloud State University theRepository at St. Cloud State Culminating Projects in Information Assurance Department of Information Systems 5-2018 KVM Based Virtualization and Remote Management Srinath Reddy Pasunuru St. Cloud State University, [email protected] Follow this and additional works at: https://repository.stcloudstate.edu/msia_etds Recommended Citation Pasunuru, Srinath Reddy, "KVM Based Virtualization and Remote Management" (2018). Culminating Projects in Information Assurance. 53. https://repository.stcloudstate.edu/msia_etds/53 This Starred Paper is brought to you for free and open access by the Department of Information Systems at theRepository at St. Cloud State. It has been accepted for inclusion in Culminating Projects in Information Assurance by an authorized administrator of theRepository at St. Cloud State. For more information, please contact [email protected]. 1 KVM Based Virtualization and Remote Management by Srinath Reddy Pasunuru A Starred Paper Submitted to the Graduate Faculty of St. Cloud State University in Partial Fulfillment of the Requirements for the Degree Master of Science in Information Assurance May, 2018 Starred Paper Committee Susantha Herath, Chairperson Ezzat Kirmani Sneh Kalia 2 Abstract In the recent past, cloud computing is the most significant shifts and Kernel Virtual Machine (KVM) is the most commonly deployed hypervisor which are used in the IaaS layer of the cloud computing systems. The Hypervisor is the one which provides the complete virtualization environment which will intend to virtualize as much as hardware and systems which will include the CPUs, Memory, network interfaces and so on. Because of the virtualization technologies such as the KVM and others such as ESXi, there has been a significant decrease in the usage if the resources and decrease in the costs involved.
    [Show full text]
  • ISSN: 1804-0527 (Online) 1804-0519 (Print) Vol.8 (2), PP. 63-69 Introduction During the Latest Years, a Lot of Projects Have Be
    Perspectives of Innovations, Economics & Business, Volume 8, Issue 2, 201 1 EVALUATION OF PERFORMANCE OF SOLARIS TRUSTED EXTENSIONS USING CONTAINERS TECHNOLOGY EVALUATION OF PERFORMANCE OF GENTI DACI SOLARIS TRUSTED EXTENSIONS USING CONTAINERS TECHNOLOGY Faculty of Information Technology Polytechnic University of Tirana, Albania UDC: 004.45 Key words: Solaris Containers. Abstract: Server and system administrators have been concerned about the techniques on how to better utilize their computing resources. Today, there are developed many technologies for this purpose, which consists of running multiple applications and also multiple operating systems on the same hardware, like VMWARE, Linux-VServer, VirtualBox, Xen, etc. These systems try to solve the problem of resource allocation from two main aspects: running multiple operating system instances and virtualizing the operating system environment. Our study presents an evaluation of scalability and performance of an operating system virtualization technology known as Solaris Containers, with the main objective on measuring the influence of a security technology known as Solaris Trusted Extensions. Solaris. We will study its advantages and disadvantages and also the overhead that it introduces to the scalability of the system’s main advantages. ISSN: 1804 -0527 (online) 1804 -0519 (print) Vol.8 (2), PP. 63 -69 Introduction administration because there are no multiple operating system instances in a system. During the latest years, a lot of projects have been looking on virtualizing operating system Operating systems environments, such as FreeBSD Jail, Linux- VServer, Virtuozzo etc. This virtualization technique is based in using only one underlying Solaris/OpenSolaris are Operating Systems operating system kernel. Using this paradigm the performing as the main building blocks of computer user has the possibility to run multiple applications systems; they provide the interface between user in isolation from each other.
    [Show full text]
  • Oracle® Enterprise Manager Ops Center Security
    Oracle® Enterprise Manager Ops Center Security 12c Release 4 (12.4.0.0.0) F17675-01 April 2019 Oracle Enterprise Manager Ops Center Security, 12c Release 4 (12.4.0.0.0) F17675-01 Copyright © 2007, 2019, Oracle and/or its affiliates. All rights reserved. Primary Author: Krithika Gangadhar 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 installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency- specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs.
    [Show full text]
  • The Server Virtualization Landscape, Circa 2007
    ghaff@ illuminata.com Copyright © 2007 Illuminata, Inc. single user license Gordon R Haff Illuminata, Inc. TM The Server Virtualization Bazaar, Circa 2007 Inspired by both industry hype and legitimate customer excitement, many Research Note companies seem to have taken to using the “virtualization” moniker more as the hip phrase of the moment than as something that’s supposed to convey actual meaning. Think of it as “eCommerce” or “Internet-enabled” for the Noughts. The din is loud. It doesn’t help matters that virtualization, in the broad sense of “remapping physical resources to more useful logical ones,” spans a huge swath of Gordon Haff technologies—including some that are so baked-in that most people don’t even 27 July 2007 think of them as virtualization any longer. Personally licensed to Gordon R Haff of Illuminata, Inc. for your personal education and individual work functions. Providing its contents to external parties, including by quotation, violates our copyright and is expressly forbidden. However, one particular group of approaches is capturing an outsized share of the limelight today. That would, of course, be what’s commonly referred to as “server virtualization.” Although server virtualization is in the minds of many inextricably tied to the name of one company—VMware—there are many companies in this space. Their offerings include not only products that let multiple virtual machines (VMs) coexist on a single physical server, but also related approaches such as operating system (OS) virtualization or containers. In the pages that follow, I offer a guide to today’s server virtualization bazaar— which at first glance can perhaps seem just a dreadfully confusing jumble.
    [Show full text]
  • Attacker Chatbots for Randomised and Interactive Security Labs, Using Secgen and Ovirt
    Hackerbot: Attacker Chatbots for Randomised and Interactive Security Labs, Using SecGen and oVirt Z. Cliffe Schreuders, Thomas Shaw, Aimée Mac Muireadhaigh, Paul Staniforth, Leeds Beckett University Abstract challenges, rewarding correct solutions with flags. We deployed an oVirt infrastructure to host the VMs, and Capture the flag (CTF) has been applied with success in leveraged the SecGen framework [6] to generate lab cybersecurity education, and works particularly well sheets, provision VMs, and provide randomisation when learning offensive techniques. However, between students. defensive security and incident response do not always naturally fit the existing approaches to CTF. We present 2. Related Literature Hackerbot, a unique approach for teaching computer Capture the flag (CTF) is a type of cyber security game security: students interact with a malicious attacker which involves collecting flags by solving security chatbot, who challenges them to complete a variety of challenges. CTF events give professionals, students, security tasks, including defensive and investigatory and enthusiasts an opportunity to test their security challenges. Challenges are randomised using SecGen, skills in competition. CTFs emerged out of the and deployed onto an oVirt infrastructure. DEFCON hacker conference [7] and remain common Evaluation data included system performance, mixed activities at cybersecurity conferences and online [8]. methods questionnaires (including the Instructional Some events target students with the goal of Materials Motivation Survey (IMMS) and the System encouraging interest in the field: for example, PicoCTF Usability Scale (SUS)), and group interviews/focus is an annual high school competition [9], and CSAW groups. Results were encouraging, finding the approach CTF is an annual competition for students in Higher convenient, engaging, fun, and interactive; while Education (HE) [10].
    [Show full text]
  • Virtual Containers: Asset Management Best Practices and Licensing Considerations
    Virtual Containers: Asset Management Best Practices and Licensing Considerations Virtual containers have seen tremendous adoption and growth within all industries. However, in terms of IT asset management, cont- ainers are not being managed and are an unknown area of risk for many of our clients. Because it is a newer technology, there is very little information about managing containers and how to address the emerging SAM & ITAM challenges they bring. Due to this lack of public information, Anglepoint has published this whitepaper on navigating the world of containers, with an empha- sis on asset management and licensing. We will cover everything from the history of containers, to what containers are, the benefits of containers, asset management best practices, and some publisher-specific licensing considerations. A BRIEF HISTORY OF VIRTUAL CONTAINERS The first proper containers came from the Linux world as LXC (LinuX Containers) in 2008. However, it wasn’t until 2013 that containers entered the IT public consciousness, when Docker came onto the scene with Enterprise usage in mind. Even then, though, it was more of an enthusiast’s technology. In 2015, Google released and open sourced Kubernetes which manages and ‘orchestrates’ containers. However, it wasn’t until 2017 that Docker and Kubernetes had matured enough to be considered for production use within corporate environments. 2017 also saw VMware, Microsoft, and Amazon beginning to support and offer solutions for Kubernetes and Docker on their top-tier cloud infrastructure. WHAT IS A CONTAINER? Often, people conflate the term ‘container’ with multiple technologies that make up the container ecosystem. Let’s look at what a modern container is at the most fundamental level.
    [Show full text]
  • Ovirt and Openstack Storage (Present and Future)
    oVirt and OpenStack Storage (present and future) Federico Simoncelli Principal Software Engineer, Red Hat January 2014 1 Federico Simoncelli – oVirt and OpenStack Storage (present and future) Agenda ● Introduction ● oVirt and OpenStack Overview ● Present ● oVirt and Glance Integration ● Importing and Exporting Glance Images ● Current Constraints and Limitations ● Future ● Glance Future Integration ● Keystone Authentication in oVirt ● oVirt and Cinder Integration 2 Federico Simoncelli – oVirt and OpenStack Storage (present and future) oVirt Overview ● oVirt is a virtualization management application ● manages hardware nodes, storage and network resources, in order to deploy and monitor virtual machines running in your data center ● Free open source software released under the terms of the Apache License 3 Federico Simoncelli – oVirt and OpenStack Storage (present and future) The oVirt Virtualization Architecture 4 Federico Simoncelli – oVirt and OpenStack Storage (present and future) OpenStack Overview ● Cloud computing project to provide an Infrastructure as a Service (IaaS) ● Controls large pools of compute, storage, and networking resources ● Free open source software released under the terms of the Apache License ● Project is managed by the OpenStack Foundation, a non-profit corporate entity established in September 2012 5 Federico Simoncelli – oVirt and OpenStack Storage (present and future) OpenStack Glance Service ● Provides services for discovering, registering, and retrieving virtual machine images ● RESTful API that allows querying
    [Show full text]
  • ZERTO VIRTUAL REPLICATION - PREREQUISITES & REQUIREMENTS for MICROSOFT HYPER-V ENVIRONMENTS ZVR-REH-5.5U3 Rev01 Dec2017
    ZERTO VIRTUAL REPLICATION - PREREQUISITES & REQUIREMENTS FOR MICROSOFT HYPER-V ENVIRONMENTS ZVR-REH-5.5U3 Rev01 Dec2017 Zerto Virtual Replication is installed in a site with virtual machines to be protected as well as in the site where these virtual machines will be recovered. This document describes Zerto Virtual Replication - Prerequisites and Requirements for Microsoft Hyper-V Environments. For the requirements of VMware, Microsoft Azure or AWS protected sites, go to myZerto > Technical Documentation portal. ■ The Zerto Virtual Replication installation includes: ■ A Zerto Virtual Manager (ZVM): This is a Windows service, and manages replication at the site level. ■ A Virtual Replication Appliance (VRA): This is a virtual machine installed on each Hyper-V host to move the data to be replicated from the protected to the recovery site. ■ A Virtual Backup Appliance (VBA): This is a Windows service and manages offsite backups within Zerto Virtual Replication on each site. The VBA service runs on the same machine as the Zerto Virtual Manager service. ■ Zerto Virtual Replication can be installed at multiple sites and each site can be paired to any other site. ■ Each site is managed with the Zerto User Interface. ■ Zerto Virtual Replication also supports both the protected and recovery sites being managed by one SCVMM, for small branch offices. For example, from one datacenter to another datacenter, both managed by the same SCVMM. See the following sections: ■ “For Each Zerto Virtual Replication Hyper-V Site”, on page 1 ■ “Considerations and Guidelines”, on page 2 ■ “For Virtual Replication Appliances on the Hyper-V Host”, on page 3 ■ “Routable Networks”, on page 3 ■ “Minimum Bandwidth”, on page 3 ■ “Requirements for the Zerto Virtual Manager Web Client”, on page 3 ■ “Recommended Best Practices for the Zerto Virtual Replication Hyper-V Site”, on page 4 ■ “Open Firewall Ports for Hyper-V Environments”, on page 5 For Each Zerto Virtual Replication Hyper-V Site ■ Microsoft System Center 2012 R2, or 2016 with VMM (SCVMM) and at least one Hyper-V host.
    [Show full text]