Virtualization Management APIs: VMware, DMTF & Xen

Transcription

1 Virtualization Management APIs: VMware, DMTF & Xen Ajit Mayya Director of Engineering Larry Lamers Sr. Engineering Manager Daniel Hiltgen Staff Engineer

2 Goals Participants will leave with an understanding of: The evolution of VMware s Virtualization management interfaces VMware s Open Interface Initiatives VMware s involvement in industry standard organizations VMware s plans around extensible management architecture

3 Overview of Presentation Evolution of VMware Product APIs VMware Control VI SDK Open Interface Initiatives Virtual Machine Disk Format Virtual Machine Interface Hypervisor/Guest OS Interface Management Interface Performance Industry Standards DMTF Others Futures & Roadmaps Extensible Architecture

4 VMware s Goals for Open Interfaces & Standards Standards, specifications, and open interfaces are what will make it possible for the entire industry to fully leverage virtualization on the x86 platforms. There should be complete transparency and unconstrained availability (standards, open interfaces) of the interfaces between the hardware and the virtualization, the virtualization and the operating system, and the format of the virtual machines. Diane Greene Steve Herrod VP R&D We will submit our interfaces and formats to the industry to accelerate this opportunity. We will adopt those formats that comply with openness and 3rd party control. Let hypervisors compete on features, partner relationships, quality, performance, price, and support.

5 Big Picture VC UI Plug-in API 3 rd Party UI Plug-in Performance Comparisons VC Server VI API Vpxd ESX VM VM VI API Host agent CIM XML CIMOM (Pegasus, SFCB, etc.) CMPI Provider Hypervisor OS Interface VSI char / proc VM File format VMkernel Driver Interface (DDK) 3 rd Party Driver Hardware

6 Evolution of VMware s API VMware:Control Technology Perl & COM modules Proprietary protocol Capability VM monitoring & statistics gathering VM configuration changes VM power operations Product coverage GSX ESX Current status Deprecated since release of VI 3 June 2006 Will be phased out at a future date

7 Evolution of VMware s API VI SDK version 1.0 Technology Web services interface HTTP, SOAP, XML Interface specification via WSDL, programming language agnostic Extensive samples Capability VM configuration and provisioning VM power operations, monitoring and statistics gathering VM power operations VM customization, VM cloning, Templates, VMotion Scheduled tasks Product coverage VC 1.1 managed environments only Current status Supported in backward compatibility mode as of VI 3 release

8 VMware s VI SDK 2.0 Key Features Technology Web services interface HTTP, SOAP, XML Interface specification via WSDL, programming language agnostic Extensive samples Capability All features from 1.0 VI SDK Inventory traversal, traversal rules, fine grained property selection Filter specification for object and property selection Host Configuration Networking configuration Storage Configuration

9 Platforms Covered by VI SDK 2.0 Product Coverage VC 2.0 Managed Hosts ESX 2.5.x, ESX 3.0 ESX 3.0 VMware Server support planned Clients Axis 1.x VS2003, VS2005 VMware Perl Toolkit available on SourceForge SOAP 1.1 & WS-I Basic Profile 1.0

10 VMware Open Interface Initiatives VM File Format - how a virtual machine is stored VMDK Virtual Machine Interface (VMI) Hypervisor/Guest OS Interface allow choice in hypervisor Virtualization Management VMware Infrastructure SDK CIM SDK Performance measurements Virtual machine performance benchmarks for more detail

11 VM File Format

12 VM File Format Disk Format - how a virtual machine is stored A virtual machine encapsulates an entire server or desktop environment in a file. The virtual machine disk format specification describes and documents the virtual machine environment and how it is stored. The virtual machine disk format specification is critical to how virtual environments are provisioned, manipulated, patched, updated, scanned and backed up.

13 VM File Format Belief Should be open, available without license, and not owned by a single party Benefits Accelerate solutions that depend on the format (e.g., backup, system imaging, patch management, replication, virtual machine migration) Preserve customer environments if they choose to move between vendors Simplify distribution of virtual appliances Status VMware VMDK format available without license (large # of downloads and tools)

14 Virtual Machine Interface (VMI) HYPERVISOR/GUEST OS INTERFACE

15 VMI Hypervisor/Guest OS Interface In a fully virtualized environment, operating systems issue hardware instructions that are intercepted by the virtualization software. In certain situations it may be advantageous for the operating system inside a virtual machine to directly communicate to the underlying virtualization software. The virtual machine interface defines the mechanism for such communication to occur. These instructions enable the virtualization software to more efficiently use resources of the computer and perform tasks on behalf of operating systems running in virtual machines, such as managing memory resources.

16 VMI Hypervisor/Guest OS Interface Belief Should be open & freely available to OS and hypervisor vendors Should be transparent the same binary should work on hardware and on a hypervisor Benefits Customers benefit from ability to use same OS image everywhere ISVs benefit from having fewer OS versions to certify and support Hypervisor choice can be independent of guest OS choice Status Technology Preview now available, full support to follow. Working with the Linux community on common paravirt_ops approach Unclear as to approach Microsoft will take with enlightenments

17 Virtualization Management Management

18 Virtualization Management These interfaces enable management software to deploy, control, and monitor virtual machines running in different virtualization environments. These tools automatically execute many of the daily tasks in the data center, decreasing costs and increasing reliability. VMware supports a rich set of additional interfaces that allow customers to realize the full potential of virtualization.

19 Virtualization Management Belief The common management-related functions used within virtualization should be standardized Standards based management is focused on CIM-based models Benefits Enable 3 rd -party management tools to work with VMware virtualization products (ESX Server, Server, Workstation, VirtualCenter, ) Status Working this through the DMTF SVPC workgroup

20 Performance Comparisons

21 Performance Comparisons Belief Properly measuring the performance of virtualization is challenging The industry will benefit from easy-to-run, representative, managed benchmarks Benefits Customers can make better performance-focused tradeoffs in hardware and software choices Status VMware is working with partners on VMmark VMware is part of the SPEC Working Group looking into virtualization benchmarks

22 Industry Standards - DMTF Leadership Participation SVPC Virtualization working group Larry Lamers Co-chair Daniel Hiltgen Editor of Resource Allocation Profile Carl Waldspurger Editor of Processor Profile Member Participation CIM Core working group SVPC Cluster working group Server Management working group Desktop Mobile & Pre-OS working group Architecture working group WIP (WBEM Infrastructure and Protocols) Generic Operations

23 DMTF SVPC Phase 1 Goals Resource Allocation Profile Allocation Capabilities Profile System Virtualization Profile Virtual System Profile Generic Resource Profile Processor Resource Allocation Profile Memory Resource Allocation Profile Network Port Resource Allocation Profile Removable Media Resource Allocation Profile Block Based Storage Resource Allocation Profile File Based Storage Resource Allocation Profile Virtual HBA Profile Shared HBA Profile

24 DMTF SVPC - Phase 2 Multi-System Virtualization Profile Physical Partitioning Serial and Parallel Controller Resource Allocation Profile Display Controller Resource Allocation Profile Virtual USB Virtual IB Virtual Keyboard, Mouse Console Metrics Virtual System Lifecycle Farm VLAN L2 Switch Network Bridging Template Template Management

25 DMTF Initiatives CDM As an extension of the DMTF s Common Information Model (CIM), the Common Diagnostic Model (CDM) specification is widely used within the industry to evaluate the health of computer systems in multi-vendor environments. The CDM initiative creates diagnostic instrumentation that can be utilized by platform management applications, and its tight synergy with the other manageability domains in CIM further enables integration of diagnostics into critical management functions. SMASH The DMTF's System Management Architecture for Server Hardware (SMASH) initiative, which includes the Server Management Command Line Protocol (CLP), is a suite of specifications that deliver architectural semantics, industry standard protocols and profiles to unify the management of the data center. SMI-S The Storage Management Initiative Specification (SMI-S) is developed by the Storage Networking Industry Association (SNIA) to standardize interoperable storage management technologies, based on the rich foundation provided by the DMTF s CIM and WBEM. For more information, visit the SNIA s SMI-S Web page.

26 Other Industry Standards Groups PCI SIG I/O virtualization work group Standard Performance Evaluation Corp (SPEC) Virtualization performance SNIA File Virtualization Trusted Computing Group Trusted Platform Module (TPM)

27 Futures & Roadmap VI API Client side Toolkits VI Extensibility Architecture Xen Management SDK Evolution

28 VI SDK Toolkits Current Axis, VS, other off-the-shelf SOAP toolkits Future VI API Toolkits Client defined Object Model Stub generation in language of choice High performance Property collector based Early Access Perl Toolkit Open Source & VMware supported versions Future Language Support C++, Java, C#, VB, Python, PHP,... ESX VC Server VMkernel Hardware VI API Vpxd VI SDK Client Toolkit Stubs & Utilities VI API Host agent

29 VI Extensibility VC UI Plug-in API 3 rd Party UI Plug-in 3 rd Party UI VC Server VI API Vpxd private 3 rd Party App VI API Host agent CIM XML / WS-CIM CIMOM (Pegasus, SFCB, etc.) CMPI Posix Provider subset ESX VMkernel VSI Driver Interface (DDK) char / proc 3 rd Party Driver Hardware

30 Xen and Management Interfaces Xen CIM XML / WS-CIM CIMOM CMPI Xen-CIM Providers libxen (C-bindings) Xen-RPC xm Pyxen (python bindings) VM VM Dom0 Xenstore Xend Host Utilities Xen Hypervisor Hardware

31 Gap Features/Maturity Implementation Specification Time

32 Closing Remarks Q: Why are open interfaces and formats important? A: In every industry, open interfaces and formats has been a critical enabler to accelerating ubiquitous adoption. Virtualization is no different. As great as the momentum is today for virtualization, it is still in its early stages of adoption. VMware is taking this step to spur the growth of virtualization, accelerate solution delivery to customers and achieve wide spread adoption. VMware is also taking this step because partners and customers have asked for it. Q: Why is this significant for customers? A: Open interfaces and formats will give customers access to a broader range of virtualization solutions that are also compatible across an increased number of industry products. Q: How will this benefit the industry? A: Open interfaces and formats will facilitate greater collaboration and innovation across an ecosystem of virtualization vendors and expand the market opportunities for all. Q: Why is VMware proposing these open interfaces and formats? A: The most successful interfaces and formats in the technology business have been based on de facto customer deployed standards. VMware's technology has been deployed widely for over seven years and incorporates a significant amount of real-world experience.

33 Presentation Download Please remember to complete your session evaluation form and return it to the room monitors as you exit the session The presentation for this session can be downloaded at Enter the following to download (case-sensitive): Username: cbv_rep Password: cbvfor9v9r

34

35 Backup Slides

36 Open Interfaces and Formats FAQs Q: What is VMware announcing regarding Open Interfaces and Formats? A: VMware is collaborating with a group of leading technology vendors to define open virtualization standards. As an initial step, VMware will contribute its existing frameworks and APIs to facilitate the development of these standards in an industry neutral manner. Q: What is a Hypervisor? A: A Hypervisor is a basic component of virtualization software and it provides the capabilities necessary to partition and multiplex the system. In ESX Server terminology, this roughly corresponds to the ESX Virtual Machine Monitor. Q: Which open interfaces and formats is VMware making available? A: VMware's open interfaces and formats include the following: Virtual Machine Disk Format - Virtual machine disk formats that enable virtual machine provision, migration and maintenance across platforms. Virtual Machine Interface - APIs between hypervisors and guest operating systems. Management Interface - Framework that governs the standardized operation and management of stand-alone virtual machine environments as well as highly dynamic, data center-scale deployment of virtualized systems. Virtual machine performance benchmarks Properly measuring the performance of virtualization Q: Who can use these open interfaces and formats? A: VMware intends this to be an open, vendor neutral effort. Any vendor that shares in the common goal of open virtualization standards can participate.

37 Presentation Download Please remember to complete your session evaluation form and return it to the room monitors as you exit the session The presentation for this session can be downloaded at Enter the following to download (case-sensitive): Username: cbv_rep Password: cbvfor9v9r

38 Some or all of the features in this document may be representative of feature areas under development. Feature commitments must not be included in contracts, purchase orders, or sales agreements of any kind. Technical feasibility and market demand will affect final delivery.