DOCSLIB.ORG

Oracle Solaris Openstack

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Oracle Solaris Openstack Oracle Solaris OpenStack Business Breakfast Introduction, Experiences, Live Demonstration Detlef Drewanz Master Principal Sales Consultant Northern Europe Systems Architects 3/9/2016 Copyright © 2014 Oracle and/or its affiliates. All rights reserved. | Detlef Drewanz 2 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. 3/9/2016 Copyright © 2016, Oracle and/or its affiliates. All rights reserved. | Detlef Drewanz 3 Agenda 1 The Road to private Cloud 2 The OpenStack Project 3 The OpenStack Architecture 4 OpenStack and Oracle 5 Cloud Use Cases 6 Building the Cloud 3/9/2016 Copyright © 2016, Oracle and/or its affiliates. All rights reserved. | Detlef Drewanz 4 Has Changed Everything 3/9/2016 Copyright © 2016, Oracle and/or its affiliates. All rights reserved. | Detlef Drewanz 8 What's the goal of the Cloud Project ... ? One Management Tool 3/9/2016 Copyright © 2016, Oracle and/or its affiliates. All rights reserved. | Detlef Drewanz 9 Journey to Private Cloud Traditional Silos Consolidated Private Cloud • Physical • Virtual • Security • Dedicated • Shared • Self-service • Heterogeneous • Standardized • Auto-scaling • Metering and chargeback Start with consolidation • Extend to private cloud • Use public cloud where appropriate 3/9/2016 Copyright © 2016, Oracle and/or its affiliates. All rights reserved. | Detlef Drewanz 10 Design Considerations – The planned Use Cases • Targeting new software development only ? • Moving existing services also ? • Organization-wide, or just for certain parts ? • Offer self-service ? 3/9/2016 Copyright © 2016, Oracle and/or its affiliates. All rights reserved. | Detlef Drewanz 12 The OpenStack Project 3/9/2016 Copyright © 2016, Oracle and/or its affiliates. All rights reserved. | Detlef Drewanz 14 OpenStack Overview What is OpenStack? • Open source cloud software – Generic solution for IaaS, PaaS and SaaS – Modular architecture Single Management Pane • Web portal for cloud admins and self-service users • Cloud services exposed through APIs VM VM VM • CLI, Python libraries, ... • Combines compute, network and Virtualized Data Center storage resources Resources – Self-service dashboard – Services exposed through REST APIs 3/9/2016 Copyright © 2016, Oracle and/or its affiliates. All rights reserved. | Detlef Drewanz 15 OpenStack in Action 3/9/2016 Copyright © 2016, Oracle and/or its affiliates. All rights reserved. | Detlef Drewanz 16 OpenStack in Action 3/9/2016 Copyright © 2016, Oracle and/or its affiliates. All rights reserved. | Detlef Drewanz 17 Drivers for OpenStack Cloud Infrastructure What’s exciting customers about OpenStack? • Broad Industry Adoption and Participation in the Community – Over 400 companies involved! • Rich technology Ecosystem – Provides choice / freedom to leverage underlying Compute, Storage, Networking Infrastructure • “Standardized” Cloud API layer – Abstracts higher level Cloud Software & Services from Undercloud infrastructure specifics 3/9/2016 Copyright © 2016, Oracle and/or its affiliates. All rights reserved. | Detlef Drewanz 18 OpenStack Releases https://wiki.openstack.org/wiki/Releases Release Name Status Latest Release Info Austin, Bexar, Cactus, Diablo Deprecated 2010.1, 2011.1, 2011.2, 2011.3 Essex, Folsom, Grizzly EOL 2012.1, 2012.2, 2013.1 Havana EOL 2013.2 Icehouse EOL 2014.1 Juno Security-supported 2014.2 Kilo Security-supported 2015.1 Liberty Current stable release, (10/15/2015) security supported Mitaka Under development 3/9/2016 Copyright © 2016, Oracle and/or its affiliates. All rights reserved. | Detlef Drewanz 21 What OpenStack is not… • Out-of-the-Box Ready to Use • Mature – Lots of work to configure – Release cycle; underlying infrastructure short support lifespan • Overall Integration – Update capability is limited, • Lots of moving parts maybe “rip and replace” • Dependent on expertise, experience, – However … it is improving vendors, maturing technology • Free – OpenSource does not mean free – Large investment to set up and support environment 3/9/2016 Copyright © 2016, Oracle and/or its affiliates. All rights reserved. | Detlef Drewanz 23 The OpenStack Architecture 3/9/2016 Copyright © 2016, Oracle and/or its affiliates. All rights reserved. | Detlef Drewanz 24 OpenStack Logical Layout 3/9/2016 Copyright © 2016, Oracle and/or its affiliates. All rights reserved. | Detlef Drewanz 25 OpenStack Services Overview of Core Components Component Description Component Description Nova Compute virtualization Glance Image management and deployment Cinder Block storage Swift Object storage Neutron Software defined networking Heat Application and VM orchestration Authentication between cloud services Keystone Murano Application catalog and simple Authorization Horizon Web based dashboard Trove Database as a Service 3/9/2016 Copyright © 2016, Oracle and/or its affiliates. All rights reserved. | Detlef Drewanz 26 OpenStack Logical Architecture with Service Names Horizon Neutron Nova Glance Swift Cinder Keystone 3/9/2016 Copyright © 2016, Oracle and/or its affiliates. All rights reserved. | Detlef Drewanz 27 OpenStack - Modular Architecture • Web portal / dashboard for cloud admins and self-service users • Cloud services exposed through APIs • CLI, Python libraries, ... • Interoperating services with REST APIs www.openstack.org 3/9/2016 Copyright © 2016, Oracle and/or its affiliates. All rights reserved. | Detlef Drewanz 28 OpenStack and Oracle 3/9/2016 Copyright © 2016, Oracle and/or its affiliates. All rights reserved. | Detlef Drewanz 31 Your Strategy. Your Cloud. Your Choice. Oracle Integrated Stack Ready-made! Best-of-Breed 3/9/2016 Copyright © 2016, Oracle and/or its affiliates. All rights reserved. | Detlef Drewanz 33 OpenStack Across Oracle’s Portfolio Built into the Infrastructure Horizon Centralized Cloud Management Nova / Ironic Neutron Cinder / Swift / Manilla Heat / Glance Self-Service Compute Software Defined Cloud Scale Storage Murano* / Trove* and Bare Metal Networking Platform as a Service Oracle Solaris, Oracle Oracle Solaris, Oracle Linux, Oracle Solaris, Linux, Oracle Virtual Oracle ZFSSA, Oracle FS1, Oracle Solaris, Oracle Linux, Oracle Linux Oracle Tape Solutions, Oracle Database 12c Networking Oracle Axiom 3/9/2016 Copyright © 2016, Oracle and/or its affiliates. All rights reserved. | Detlef Drewanz 37 OpenStack and Oracle Storage 3/9/2016 Copyright © 2016, Oracle and/or its affiliates. All rights reserved. | Detlef Drewanz 38 Oracle ZFS Storage Appliance Simplifies OpenStack Deployments • OpenStack drivers iSCSI • Fully implemented RESTful APIs Cinder NFS SWIFT Oracle ZFS Storage Appliance 3/9/2016 Copyright © 2016, Oracle and/or its affiliates. All rights reserved. | Detlef Drewanz 39 Oracle FS1 Flash Storage System OpenStack Ready • Massively Scalable Flash Array • Extreme Performance SAN • Unparalleled Flexibility Cinder • QoS Plus Autonomous Tiering FS1 • Perfect for Virtualized IT/OpenStack 3/9/2016 Copyright © 2016, Oracle and/or its affiliates. All rights reserved. | Detlef Drewanz 40 OpenStack and Oracle Linux 3/9/2016 Copyright © 2016, Oracle and/or its affiliates. All rights reserved. | Detlef Drewanz 41 OpenStack und Oracle Linux (Version 2.0) http://www.oracle.com/us/technologies/linux/openstack/overview/index.html 3/9/2016 Copyright © 2016, Oracle and/or its affiliates. All rights reserved. | Detlef Drewanz 42 Oracle Linux OpenStack Key Features in Release 2 • Simplified, container-based deployment – Introducing Kolla and Docker containers for streamlined installations and updates • Align with upstream Kilo Release – Updates to existing projects/services delivered in Release 1 • Nova, Neutron, Horizon, Swift, Cinder, Keystone, Glance – Support for additional projects/services • Heat, Murano • Improvements to MySQL Cluster for HA – Active/Active now supported • Support included as part of standard Oracle Linux support 3/9/2016 Copyright © 2016, Oracle and/or its affiliates. All rights reserved. | Detlef Drewanz 43 Simplified Deployment and Upgrades with Docker 1 Nova ULN or Public-Yum Neutron Swift Horizon 2 Docker Container Configure Services Kolla-CLI OpenStack Docker Images Local Docker Registry 4 3 3/9/2016 Copyright © 2016, Oracle and/or its affiliates. All rights reserved. | Detlef Drewanz 44 OpenStack and Oracle Solaris 3/9/2016 Copyright © 2016, Oracle and/or its affiliates. All rights reserved. | Detlef Drewanz 45 Oracle OpenStack for Oracle Solaris Horizon Cloud Management Ironic Heat Murano Bare Metal Orchestration Application Deployment OracleDeployment Database and SPARC/x86 Unified Archives Fusion Middleware Nova Neutron Cinder/Swift Glance Compute Virtualization Cloud Networking Cloud Storage Image Deployment Zones & Kernel Zones Elastic Virtual Switch ZFS File System Unified Archives 3/9/2016 Copyright © 2016, Oracle and/or its affiliates. All rights reserved. | Detlef Drewanz 46 OpenStack Juno in Oracle Solaris 11.3 Ready for Enterprise: OS. Virtualization. SDN. OpenStack. • Engineered for security and compliance – Minimal privileges for cloud services – Lock down infrastructure with immutability • Assured reliability and scale – Automatic service restart and node dependencies – Guaranteed data integrity
Load more

Recommended publications
  • Porting Darwin to the MV88F6281 Arming the Snowleopard
    Porting Darwin to the MV88F6281 ARMing the SnowLeopard. Tristan Schaap 1269011 Apple Inc. Platform Technologies Group Delft University of Technology Dept. of Computer Science Committee: Ir. B.R. Sodoyer Dr. K. van der Meer Preface! 3 Introduction! 4 Summary! 5 Building a new platform! 6 Booting iBoot! 7 Building the kernelcache! 8 Booting the kernel! 10 THUMBs down! 16 Conclusion! 18 Future Work! 19 Glossary! 20 References! 21 Appendix A! 22 Appendix B! 23 Skills! 23 Process! 26 Reflection! 27 Appendix C! 28 Plan of Approach! 28 2 Preface Due to innovative nature of this project, I have had to limit myself in the detail in which I describe my work. This means that this report will be lacking in such things as product specific- and classified information. I would like to thank a few people who made it possible for me to successfully complete my internship at the Platform Technologies Group at Apple. First off, the people who made this internship possible, John Kelley, Ben Byer and my manager John Wright. Mike Smith, Tom Duffy and Anthony Yvanovich for helping me through the rough patches of this project. And the entirety of Core OS for making my stay an unforgettable experience. 3 Introduction About the Platform Technologies Group As it was described by a manager: “We do the plumbing, if we do our jobs right, you never see it.”. The Platform Technologies Group, a subdivision of the Core OS department, works on the embedded platforms that Apple maintains. Here, platforms are brought up and the embedded kernel and lower level support for the platforms is maintained.
    [Show full text]
  • Linux on the Road
    Linux on the Road Linux with Laptops, Notebooks, PDAs, Mobile Phones and Other Portable Devices Werner Heuser <wehe[AT]tuxmobil.org> Linux Mobile Edition Edition Version 3.22 TuxMobil Berlin Copyright © 2000-2011 Werner Heuser 2011-12-12 Revision History Revision 3.22 2011-12-12 Revised by: wh The address of the opensuse-mobile mailing list has been added, a section power management for graphics cards has been added, a short description of Intel's LinuxPowerTop project has been added, all references to Suspend2 have been changed to TuxOnIce, links to OpenSync and Funambol syncronization packages have been added, some notes about SSDs have been added, many URLs have been checked and some minor improvements have been made. Revision 3.21 2005-11-14 Revised by: wh Some more typos have been fixed. Revision 3.20 2005-11-14 Revised by: wh Some typos have been fixed. Revision 3.19 2005-11-14 Revised by: wh A link to keytouch has been added, minor changes have been made. Revision 3.18 2005-10-10 Revised by: wh Some URLs have been updated, spelling has been corrected, minor changes have been made. Revision 3.17.1 2005-09-28 Revised by: sh A technical and a language review have been performed by Sebastian Henschel. Numerous bugs have been fixed and many URLs have been updated. Revision 3.17 2005-08-28 Revised by: wh Some more tools added to external monitor/projector section, link to Zaurus Development with Damn Small Linux added to cross-compile section, some additions about acoustic management for hard disks added, references to X.org added to X11 sections, link to laptop-mode-tools added, some URLs updated, spelling cleaned, minor changes.
    [Show full text]
  • Oracle Solaris 11.4 Security Target, V1.3
    Oracle Solaris 11.4 Security Target Version 1.3 February 2021 Document prepared by www.lightshipsec.com Oracle Security Target Document History Version Date Author Description 1.0 09 Nov 2020 G Nickel Update TOE version 1.1 19 Nov 2020 G Nickel Update IDR version 1.2 25 Jan 2021 L Turner Update TLS and SSH. 1.3 8 Feb 2021 L Turner Finalize for certification. Page 2 of 40 Oracle Security Target Table of Contents 1 Introduction ........................................................................................................................... 5 1.1 Overview ........................................................................................................................ 5 1.2 Identification ................................................................................................................... 5 1.3 Conformance Claims ...................................................................................................... 5 1.4 Terminology ................................................................................................................... 6 2 TOE Description .................................................................................................................... 9 2.1 Type ............................................................................................................................... 9 2.2 Usage ............................................................................................................................. 9 2.3 Logical Scope ................................................................................................................
    [Show full text]
  • Android (Operating System) 1 Android (Operating System)
    Android (operating system) 1 Android (operating system) Android Android 4.4 home screen Company / developer Google Open Handset Alliance Android Open Source Project (AOSP) Programmed in C (core), C++, Java (UI) OS family Unix-like Working state Current Source model Open source with proprietary components Initial release September 23, 2008 Latest stable release 4.4.2 KitKat / December 9, 2013 Marketing target Smartphones Tablet computers Available language(s) Multi-lingual (46 languages) Package manager Google Play, APK Supported platforms 32-bit ARM, MIPS, x86 Kernel type Monolithic (modified Linux kernel) [1] [2] [3] Userland Bionic libc, shell from NetBSD, native core utilities with a few from NetBSD Default user interface Graphical (Multi-touch) License Apache License 2.0 Linux kernel patches under GNU GPL v2 [4] Official website www.android.com Android is an operating system based on the Linux kernel, and designed primarily for touchscreen mobile devices such as smartphones and tablet computers. Initially developed by Android, Inc., which Google backed financially Android (operating system) 2 and later bought in 2005, Android was unveiled in 2007 along with the founding of the Open Handset Alliance: a consortium of hardware, software, and telecommunication companies devoted to advancing open standards for mobile devices. The first publicly available smartphone running Android, the HTC Dream, was released on October 22, 2008. The user interface of Android is based on direct manipulation, using touch inputs that loosely correspond to real-world actions, like swiping, tapping, pinching and reverse pinching to manipulate on-screen objects. Internal hardware such as accelerometers, gyroscopes and proximity sensors are used by some applications to respond to additional user actions, for example adjusting the screen from portrait to landscape depending on how the device is oriented.
    [Show full text]
  • The Dragonflybsd Operating System
    1 The DragonFlyBSD Operating System Jeffrey M. Hsu, Member, FreeBSD and DragonFlyBSD directories with slightly over 8 million lines of code, 2 million Abstract— The DragonFlyBSD operating system is a fork of of which are in the kernel. the highly successful FreeBSD operating system. Its goals are to The project has a number of resources available to the maintain the high quality and performance of the FreeBSD 4 public, including an on-line CVS repository with mirror sites, branch, while exploiting new concepts to further improve accessible through the web as well as the cvsup service, performance and stability. In this paper, we discuss the motivation for a new BSD operating system, new concepts being mailing list forums, and a bug submission system. explored in the BSD context, the software infrastructure put in place to explore these concepts, and their application to the III. MOTIVATION network subsystem in particular. A. Technical Goals Index Terms— Message passing, Multiprocessing, Network The DragonFlyBSD operating system has several long- operating systems, Protocols, System software. range technical goals that it hopes to accomplish within the next few years. The first goal is to add lightweight threads to the BSD kernel. These threads are lightweight in the sense I. INTRODUCTION that, while user processes have an associated thread and a HE DragonFlyBSD operating system is a fork of the process context, kernel processes are pure threads with no T highly successful FreeBSD operating system. Its goals are process context. The threading model makes several to maintain the high quality and performance of the FreeBSD guarantees with respect to scheduling to ensure high 4 branch, while exploring new concepts to further improve performance and simplify reasoning about concurrency.
    [Show full text]
  • Getting Started with Openbsd Device Driver Development
    Getting started with OpenBSD device driver development Stefan Sperling <[email protected]> EuroBSDcon 2017 Clarifications (1/2) Courtesy of Jonathan Gray (jsg@): We don't want source code to firmware We want to be able to redistribute firmware freely Vendor drivers are often poorly written, we need to be able to write our own We want documentation on the hardware interfaces Source code is not documentation OpenBSD Device Drivers 2/46 Clarifications (2/2) I would like to add: Device driver code runs in our kernel Firmware code runs on a peripheral device, not in our kernel When we say \Binary Blobs" we are talking about closed-source device drivers, not firmware Firmware often runs with high privileges; use at your own risk If you do not want closed-source firmware, then don't buy and use hardware which needs it We are software developers, we do not build hardware We will not sign NDAs Please talk to hardware vendors and advocate for change; the current situation is very bad for free software OpenBSD Device Drivers 3/46 This talk is for ... somewhat competent C programmers who use OpenBSD and would like to use a device which lacks support so have an itch to scratch (enhance or write a driver) but are not sure where to start perhaps are not sure how the development process works and will research all further details themselves The idea for this talk came about during conversations I had at EuroBSDcon 2016. Common question: "How do I add support for my laptop's wifi device?" OpenBSD Device Drivers 4/46 Itches I have scratched..
    [Show full text]
  • Iocell Documentation Release 1.7.3
    iocell Documentation Release 1.7.3 iocell Nov 23, 2018 Contents 1 Documentation: 3 1.1 Basic usage................................................3 1.2 Networking................................................6 1.3 Jail types.................................................8 1.4 Best practices............................................... 10 1.5 Advanced usage............................................. 11 1.6 How to create and use templates..................................... 15 1.7 Create a jail package!.......................................... 15 1.8 Create a Debian Squeeze jail (GNU/kFreeBSD)............................. 16 1.9 Known Issues............................................... 17 1.10 FAQ.................................................... 18 1.11 Indices and tables............................................ 19 i ii iocell Documentation, Release 1.7.3 iocell is a zero dependency drop in jail/container manager amalgamating some of the best features and technologies FreeBSD operating system has to offer. It is geared for ease of use with a simple and easy to understand command syntax. FEATURES: • Templates, clones, basejails, fully independent jails • Ease of use • Zero configuration files • Rapid thin provisioning within seconds • Automatic package installation • Virtual networking stacks (vnet) • Shared IP based jails (non vnet) • Resource limits (CPU, MEMORY, etc.) • Filesystem quotas and reservations • Dedicated ZFS datasets inside jails • Transparent ZFS snapshot management • Binary updates • Differential jail packaging • Export and import • And many more! Contents 1 iocell Documentation, Release 1.7.3 2 Contents CHAPTER 1 Documentation: 1.1 Basic usage This section is about basic use and is a suitable quick howto for newcomers. 1.1.1 Fetch a release The very first step with iocell is to fetch a RELEASE. By default iocell will attempt to fetch the host’s current RE- LEASE from the freebsd.org servers. Once the RELEASE bits are downloaded, the most recent patches are applied too.
    [Show full text]
  • A Guide to Kernel Exploitation Attacking the Core (2011
    A Guide to Kernel Exploitation This page intentionally left blank A Guide to Kernel Exploitation Attacking the Core Enrico Perla Massimiliano Oldani Technical Editor Graham Speake AMSTERDAM • BOSTON • HEIDELBERG • LONDON • • • NEW YORK OXFORD PARIS SAN DIEGO SYNGRESS SAN FRANCISCO • SINGAPORE • SYDNEY • TOKYO ® Syngress is an imprint of Elsevier Acquiring Editor: Rachel Roumeliotis Development Editor: Matthew Cater Project Manager: Julie Ochs Designer: Alisa Andreola Syngress is an imprint of Elsevier 30 Corporate Drive, Suite 400, Burlington, MA 01803, USA © 2011 Elsevier Inc. All rights reserved. No part of this publication may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying, recording, or any information storage and retrieval system, without permission in writing from the publisher. Details on how to seek permission, further information about the Publisher’s permissions policies and our arrangements with organizations such as the Copyright Clearance Center and the Copyright Licensing Agency, can be found at our website: www.elsevier.com/permissions. This book and the individual contributions contained in it are protected under copyright by the Publisher (other than as may be noted herein). Notices Knowledge and best practice in this field are constantly changing. As new research and experience broaden our understanding, changes in research methods or professional practices, may become necessary. Practitioners and researchers must always rely on their own experience and knowledge in evaluating and using any information or methods described herein. In using such information or methods they should be mindful of their own safety and the safety of others, including parties for whom they have a professional responsibility.
    [Show full text]
  • Meltdown: Reading Kernel Memory from User Space
    Meltdown: Reading Kernel Memory from User Space Moritz Lipp, Michael Schwarz, and Daniel Gruss, Graz University of Technology; Thomas Prescher and Werner Haas, Cyberus Technology; Anders Fogh, G DATA Advanced Analytics; Jann Horn, Google Project Zero; Stefan Mangard, Graz University of Technology; Paul Kocher, Independent; Daniel Genkin, University of Michigan; Yuval Yarom, University of Adelaide and Data61; Mike Hamburg, Rambus, Cryptography Research Division https://www.usenix.org/conference/usenixsecurity18/presentation/lipp This paper is included in the Proceedings of the 27th USENIX Security Symposium. August 15–17, 2018 • Baltimore, MD, USA ISBN 978-1-939133-04-5 Open access to the Proceedings of the 27th USENIX Security Symposium is sponsored by USENIX. Meltdown: Reading Kernel Memory from User Space Moritz Lipp1, Michael Schwarz1, Daniel Gruss1, Thomas Prescher2, Werner Haas2, Anders Fogh3, Jann Horn4, Stefan Mangard1, Paul Kocher5, Daniel Genkin6;9, Yuval Yarom7, Mike Hamburg8 1Graz University of Technology, 2Cyberus Technology GmbH, 3G-Data Advanced Analytics, 4Google Project Zero, 5Independent (www.paulkocher.com), 6University of Michigan, 7University of Adelaide & Data61, 8Rambus, Cryptography Research Division Abstract sor bit of the processor that defines whether a memory page of the kernel can be accessed or not. The basic The security of computer systems fundamentally relies idea is that this bit can only be set when entering kernel on memory isolation, e.g., kernel address ranges are code and it is cleared when switching to user processes. marked as non-accessible and are protected from user This hardware feature allows operating systems to map access. In this paper, we present Meltdown. Meltdown the kernel into the address space of every process and exploits side effects of out-of-order execution on mod- to have very efficient transitions from the user process ern processors to read arbitrary kernel-memory locations to the kernel, e.g., for interrupt handling.
    [Show full text]
  • Freebsd 10 - Powerful Virtualization Solutions Freebsd 10 - ARM-Ready Freebsd 10 - Modern Hardware Support
    FreeBSD 10 - Powerful Virtualization Solutions FreeBSD 10 - ARM-Ready FreeBSD 10 - Modern Hardware Support FreeBSD pioneered operating system-level virtualization FreeBSD continues to improve its support for the ARM New console driver, vt(4), provides multiple virtual terminals with the Jail facility in 2000. This early innovation in family of processors, including support for ARMv6 and with an extensive feature set. It includes support for UTF-8, virtualization forged a path for similar technologies such ARMv7, SMP, and thread-local storage (TLS). double-wide characters, Asian character sets, graphics-mode as Solaris Zones (2005) and Linux Containers/Docker Supported processors include: consoles, and integration with Kernel Mode Setting (KMS) video (2014). drivers for switching between the X Window System and virtual • CHROMEBOOK (Samsung Exynos 5250) FreeBSD 10 includes several virtualization technologies, terminals.* providing users with greater flexibility for provisioning a • COLIBRI (Freescale Vybrid) virtualized solution that matches their workflow. These FreeBSD 10 adds Unified Extensible Firmware Interface (UEFI) solutions include: • COSMIC (Freescale Vybrid) boot loader support. The root file system may be UFS or ZFS, and the loader supports multiple ZFS boot environments * • The BSD Hypervisor, bhyve(8). This Type-2 hypervisor supports • Genesi Efika MX SmartBook and SmartTop (Freescale a number of guests, including FreeBSD, OpenBSD, NetBSD and i.MX515)* The Open Fabrics Enterprise Distribution (OFED) and OFED Infiniband core version provides parity with Linux, including many Linux® distributions. Combining bhyve and ZFS volumes • IMX53-QSB (Freescale i.MX53) enables powerful capabilities in provisioning, snapshotting and Mellanox drivers for 56Gb Infiniband. rolling back virtual machines. • QUARTZ (Freescale Vybrid) The nvme(4) driver provides NVM Express support.
    [Show full text]
  • Noah Hypervisor-Based Darwin Subsystem for Linux
    Noah Hypervisor-Based Darwin Subsystem for Linux Takaya Saeki, Yuichi Nishiwaki Self Introduction Noah Development Team Takaya Saeki Yuichi Nishiwaki They both are graduate students at the University of Tokyo. They are developing Noah in their free time. Noah was selected one of MITOH projects, which is a financial assistance program by the government of Japan for outstanding young programmers Noah • A middleware that runs unmodified Linux ELF applications on macOS • Reduce cost of creating / waiting for mac OS port of Linux apps • Accomplish it by special hypervisor. Load ELF binary into VM and let it run instead of kernel, trap system calls from it by hypervisor, and translate them to corresponding system calls on macOS. Noah • A middleware that runs unmodified Linux ELF applications on macOS • Reduce cost of creating / waiting for mac OS port of Linux apps • Accomplish it by special hypervisor. Load ELF binary into VM and let it run instead of kernel, trap system calls from it by hypervisor, and translate them to corresponding system calls on macOS. We discuss the architecture in detail later! Short Demo; What it looks like Agenda • What is Noah (Done!) • Background • Noah in Detail • Architecture Overview • Advantages of Noah Architecture • Subsystem Implementation • Memory management, VFS, and the other • Current Implementation Status and Performance • Related Technologies and Comparison (Windows Subsystem for Linux, Linuxulator, and so on) • Their Possible Impact on Cross Platform Development Background Linux • One of the most important operating systems today • Most popular OS for WEB servers • Many apps and middleware come from the Linux ecosystem, and they are ported to other operating systems for developers Later.
    [Show full text]
  • QNX Security Architecture
    MWR Labs Whitepaper QNX Security Architecture Alex Plaskett Contents page 1. Introduction ..................................................................................... 4 1.1 Previous Research ......................................................................................... 4 2. QNX Hardware Platforms ...................................................................... 5 3. QNX Operating System Introduction ......................................................... 6 3.1 QNX Security History ...................................................................................... 7 3.2 QNX Microkernel Design Overview ...................................................................... 9 3.3 QNX Messaging Layer .................................................................................... 11 4. QNX Key OS Components...................................................................... 14 4.1 QNX Process Manager ................................................................................... 14 4.2 QNX Path Manager ....................................................................................... 15 4.3 QNX Memory Manager ................................................................................... 16 4.4 QNX Resource Managers ................................................................................ 17 4.5 QNX Processing Listing .................................................................................. 19 4.6 QNX Persistent Publish Subscribe Architecture ....................................................
    [Show full text]