Methodologies, strategies and experiences Virtualization


Published on

Published in: Technology
  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Methodologies, strategies and experiences Virtualization

  1. 1. Methodologies, strategies and experiences Virtualization
  2. 2. Definition <ul><li>the abstraction of computer resources </li></ul><ul><li>a technique for hiding the physical characteristics of computing resources from the way in which other systems, applications, or end users interact with those resources 1 </li></ul>1 Enterprise Management Associates
  3. 3. Types and Players <ul><li>Emulation - simulates complete hardware </li></ul><ul><ul><li>Wine/Crossover </li></ul></ul><ul><li>Hardware - simulates enough hardware </li></ul><ul><ul><li>VMWare Workstation </li></ul></ul><ul><li>Para-Virtualization - no hardware emulation, uses special API </li></ul><ul><ul><li>Xen, VMWare ESX, User Mode Linux </li></ul></ul><ul><li>OS-Virtualization - OS allows multiple secure virtual servers </li></ul><ul><ul><li>Solaris Zones, BSD Jails, Linux-Vserver </li></ul></ul>
  4. 4. Advantages <ul><li>Consolidation (of course!) </li></ul><ul><ul><li>Cost cutting via: </li></ul></ul><ul><ul><ul><li>People resources - arguable </li></ul></ul></ul><ul><ul><ul><li>Hardware resources </li></ul></ul></ul><ul><li>Security - depends on type </li></ul><ul><li>Rapid reboot of virtual environment </li></ul><ul><li>Rapid deployment of another environment </li></ul><ul><li>Cloning - rapid test environment </li></ul>
  5. 5. Considerations <ul><li>Shared memory - changes coming soon </li></ul><ul><li>Storage </li></ul><ul><li>The kitchen sink effect </li></ul><ul><li>Patch deployment / multiple versions </li></ul><ul><ul><li>Positive or negative? </li></ul></ul><ul><li>Many virtualization systems suffer from performance loss on some types of workloads (most loss found to be related to network and disk intensive tasks) </li></ul><ul><ul><li>Solaris Zones does not suffer from this </li></ul></ul>
  6. 6. Xen <ul><li>Para-virtualization </li></ul><ul><li>Primarily modified Linux and NetBSD systems as host system </li></ul><ul><li>Support for various Linux and BSD, OpenSolaris, Netware as guests </li></ul><ul><li>Version 3.0 unmodified Windows ok(?) </li></ul><ul><li>Can run multiple guest operating systems </li></ul><ul><li>Commercial support available from XenSource </li></ul><ul><li>Full virtualization now available with new hardware </li></ul><ul><li>Can migrate live domains to new hosts </li></ul>
  7. 7. VMWare <ul><li>Server (formerly GSX) </li></ul><ul><ul><li>Para-virtualization, Windows/Linux host OS </li></ul></ul><ul><ul><li>Support for various guest OS </li></ul></ul><ul><ul><li>Can run multiple guest OS </li></ul></ul><ul><ul><li>Free! - but need to buy add-ons for some features </li></ul></ul><ul><li>ESX </li></ul><ul><ul><li>Full virtualization </li></ul></ul><ul><ul><li>Support for various guest OS </li></ul></ul><ul><ul><li>Can run multiple guest OS </li></ul></ul><ul><ul><li>Expensive ($5K+ for full version per physical system) </li></ul></ul>
  8. 8. Solaris Zones <ul><li>Operating system-level virtualization </li></ul><ul><li>Included with Solaris 10 </li></ul><ul><li>Global zone vs Non-global zones </li></ul><ul><ul><li>Global zone runs kernel </li></ul></ul><ul><ul><li>Global zone contains and used to administer non-global zones </li></ul></ul><ul><ul><li>Non-global zones can be given access to devices </li></ul></ul><ul><ul><li>Non-global zones cannot export filesystems via NFS </li></ul></ul><ul><li>Non-global zones can be whole or sparse </li></ul><ul><ul><li>Whole zones include own copy of all filesystems </li></ul></ul><ul><ul><li>Sparse zones share filesystems such as /usr with global zone </li></ul></ul><ul><ul><li>Sparse zones can take as little as 50-100MB </li></ul></ul>
  9. 9. Architecture Considerations <ul><li>Solaris zones setup as sparse to save on disk space </li></ul><ul><li>Patching installed globally to all zones </li></ul><ul><li>Each zone has /zones for local files </li></ul>
  10. 10. Where we are - Solaris Zones <ul><li>All Solaris 10 servers setup with zones </li></ul><ul><li>Running on multiple hardware platforms </li></ul><ul><li>Global zone only used for server administration </li></ul><ul><li>All applications run on non-global zones </li></ul><ul><li>Zones setup as sparse zones </li></ul><ul><li>Largest implementation is on a T2000 with 8 non-global zones </li></ul>
  11. 11. Where we are - Xen/VMWare <ul><li>All Xen servers run ubuntu </li></ul><ul><li>Hardware platforms include Sun x2100, x4x00 </li></ul><ul><li>System setup to clone zones </li></ul><ul><li>VMWare used primarily on streaming services (Windows based) </li></ul><ul><li>Using virtualization as a tool for change/revision management </li></ul><ul><li><shameless plug> </li></ul><ul><li>more information on change/revision management at Ramon’s “Pure Production” talk later this week </li></ul><ul><li></shameless plug> </li></ul>
  12. 12. Future Consideration <ul><li>Private Network to manage global zones </li></ul><ul><ul><li>“ Real root” not accessible </li></ul></ul><ul><ul><li>Single VLAN for network booting </li></ul></ul><ul><li>Virtuozzo </li></ul><ul><li>Solaris zone cloning </li></ul><ul><li>Hardware-level virtualization </li></ul><ul><ul><li>Sun LDOMs will create a hardware hypervisor </li></ul></ul><ul><li>VMWare ESX </li></ul><ul><li>PXE Boot - VMWare imaged systems </li></ul>