OpenStack on SmartOS


Published on

OpenStack on SmartOS presentation at the 3rd Swiss OpenStack User Group

Published in: Technology

OpenStack on SmartOS

  1. 1. OpenStack on SmartOSDaniele Stroppa, ZHAW24.04.2014, Bern3rd Swiss OpenStack User
  2. 2. Agenda§  Motivation§  Why SmartOS?§  OpenStack on
  3. 3. Motivation§  Cloud providers must be able to offer a single server to multiple userswithout them noticing that that they are not the only users of that machine.This means that the underlying operating system must:o  be able to provision and de-provision, VMs in a very fast seamlessway;o  allocate physical resources efficiently and fairly amongst the users;o  support multithreaded and multi-processor hardware;o  be highly reliable;o  must provide a way to quickly determine what’s causing the system tomisbehave.§  A customer of the cloud provider will also expect the server to be:o  fast, i.e. the observed latency should be minimal;o  flexible, i.e. get extra power when needed;o  secure, meaning that neighboring users must not interfere with
  4. 4. Why SmartOS?§  SmartOS is an open source type 1 hypervisor platformo  Based on Illumos, a descendant of OpenSolaris, and developed byJoyent§  SmartOS is a live operating system,o  It can be booted via PXE, USB or an ISO imageo  Runs entirely from memory, leaving the full space on the local disk tobe used for virtual machines.o  This type of architecture makes it very secure, easy to upgrade
  5. 5. Why SmartOS? Zones & KVM!§  Container-based virtualizationo  A container is the combination of resource controls and Solaris zones.o  Provides a lightweight solution and a complete and secure user spaceenvironment on a single global kernel.o  Can easily scale vertically, something that is more difficult with KVMvirtualization.§  KVM virtual machineso  KVM virtual machines provide a solution for running a variety of guestOSs, including Linux and Windows, in a full, hardware-assistedvirtualization.o  KVM images on SmartOS run as a process inside of a zone.§
  6. 6. Why SmartOS? ZFS!§  ZFS combines file system and logical volume manager.o  Fast file system creation - allowing to add new tenants almost instantly- and data integrity guarantee.o  ZFS also includes storage pools - that simplify the task of expandingstorage capacity - copy-on-write snapshot creation and snapshotcloning - allowing fast and reliable backup and cloning of virtualmachines.§  Disk I/O throttling introduced to overcome a drawback in Solaris.o  All zones/applications are ensured to get a reliable turn at reading/writing to disk.o  When a system is under heavy load from multiple tenants disk I/Othrottling comes into effect, while during quiet time, tenants can enjoyfaster I/O without affecting other
  7. 7. Why SmartOS? DTrace!§  DTrace is a performance analysis tool included by default in differentoperating system, amongst them Illumos and Solaris and thereforeSmartOS.o  DTrace can instrument code by modifying a program after it has beenloaded into memory.o  Not limited to use with user-space application, but can be used toinspect the OS kernel and device drivers.o  In SmartOS, DTrace can be used to analyze and troubleshoot issuesacross all zones in a server or within an entire
  8. 8. Why SmartOS? Crossbow!§  SmartOS makes use of Crossbow to provide a network virtualization layer.o  Fully integrated with the virtual machine administration tool ofSmartOS, i.e. vmadm.o  Allows each virtual machine can get up to 32 virtual network interfaces(VNICs).§  SmartOS inherits multipath IP (IPMP) from Solaris.§  SmartOS can leverage data link multi-pathing (DLMP), i.e.
  9. 9. OpenStack on SmartOS - Where arewe?§  Idea initiated by Thijs (Intel) and Andy (ZHAW)§  Working with latest OpenStack Grizzly release:o  nova-computeo  nova-network§  Code publicly available on
  10. 10. OpenStack on SmartOS - Whatsnext?§  Integrate with OpenStack Quantumo  Possibly integrate with OpenFlow controllers§  Make DTrace metrics accessible from OpenStack Ceilometero  Monitoring and billing§  Integrate ZFS featureso  VM cloning (snapshot)o  Block-type
  11. 11. Q&A?Thank you!
  12. 12. References§§§§§§,