Open Virtualization Format - Detailed


Published on

Detailed info on Open Virtualization Format which can be used for packaging and moving workload.

Published in: Technology
  • Be the first to comment

Open Virtualization Format - Detailed

  1. 1. By Namrata Dessai
  2. 2. <ul><li>ZIP Compression </li></ul><ul><li>Open Package Conventions(OPC) </li></ul><ul><ul><ul><ul><li>Storage unit </li></ul></ul></ul></ul><ul><ul><ul><ul><li>Implemented for .NET framework 3.0 </li></ul></ul></ul></ul><ul><ul><ul><ul><li>It has two parts :Package and Package Relationships </li></ul></ul></ul></ul>
  3. 3. <ul><li>By now, everyone in our industry has heard a future IT vision where virtual machines (VMs) migrate from one physical server to another for load balancing, disaster recovery, or maintenance windows </li></ul><ul><li>Each VM actually represents an operating system and some associated services or applications. </li></ul><ul><li>When VMs move around , will they maintain their configuration state or need to be reconfigured? </li></ul><ul><li>Will multi-tiered applications know that one of their peers has moved to a new neighborhood? </li></ul><ul><li>Will the network recognize the VM as an old friend or will it assume that it is a new entity? </li></ul><ul><li>Distributed Management Task Force recently published a standard called the Open Virtualization Format (OVF). </li></ul>
  4. 4. <ul><li>Developing standards that Enable Interoperable IT Management </li></ul><ul><li>DMTF Collaborates to Develop IT management standards that promote multi-vendors interoperability worldwide. </li></ul><ul><li>Virtual Systems Management is based on DMT Standards, which Reduces IT Complexity and Cost of Deploying System Virtualization. </li></ul><ul><li>DMTF Standards Primarily serve: </li></ul><ul><ul><ul><ul><ul><li>IT Personnel </li></ul></ul></ul></ul></ul><ul><ul><ul><ul><ul><li>IT Solutions Vendors </li></ul></ul></ul></ul></ul>
  5. 5. DMTF standards provide well-defined, interoperable interfaces that build upon each other; the interrelationships between the DMTF technologies in this diagram build value with each additional layer
  6. 6. <ul><li>Distributed Management Task Force (DMTF) standard </li></ul><ul><li>Open, secure, portable, efficient and extensible format for the packaging and distribution of (collections of) virtual machines </li></ul><ul><li>Its goal is to facilitate the automated, secure management not only of virtual machines , but the appliance as a functional unit </li></ul><ul><li>It is platform independent, hypervisor independent , and processor architecture independent </li></ul><ul><li>VMs in OVF can be packaged in a virtual appliances suited all wrapped up in a single file. The creator of the appliance can encrypt, compress and digitally sign OVF content </li></ul><ul><li>It is packaging standard and not a runtime standard </li></ul><ul><li>Uses existing packaging tools to combine one or more virtual machines together with a standards-based XML wrapper </li></ul>
  7. 7. <ul><li>User point of view , an OVF packaging format for software appliances </li></ul><ul><li>Technical point of view , an OVF transport mechanism for virtual machine templates but not for execution </li></ul><ul><li>Transport mechanism of OVF differs from venders </li></ul><ul><ul><ul><li>VMware’s VMDK(Virtual Disk )format </li></ul></ul></ul><ul><ul><ul><li>Microsoft’s VHD(Virtual Hard Disk) format </li></ul></ul></ul><ul><ul><ul><li>Open Source QCOW format </li></ul></ul></ul>
  8. 8. <ul><li>Virtual Appliances is a pre-configured software stack comprising one or more virtual machines . </li></ul><ul><li>Each virtual machine is an independently installable run-time entity comprising an operating system, applications and other application-specific data , as well as a specification of the virtual hardware that is required by the virtual machine </li></ul><ul><li>Benefits - Ease of deployment </li></ul><ul><li>Issues – Managing evolving interdependencies across multiple appliances and physical environments </li></ul><ul><li>Suppliers </li></ul><ul><ul><li>VMWare Virtual Appliance </li></ul></ul><ul><ul><li>Amazon Machine Images </li></ul></ul><ul><ul><li>rPath rBuilder and Appliance Platform </li></ul></ul>
  9. 9. <ul><li>DMT F releases OVF 1.0 Standard </li></ul><ul><li>First industrial standard to enable interoperability within virtualized environment </li></ul><ul><li>Enable shipment of pre-configured, ready-to-deploy virtual solution </li></ul>OVF Version 1 scope Run time management
  10. 10. <ul><li>Creation of an OVF involves: </li></ul><ul><ul><li>Packing of set of VMs onto a set of virtual disks </li></ul></ul><ul><ul><li>Appropriately encoding those virtual disks </li></ul></ul><ul><ul><li>Attaching an OVF descriptor with a specification of the virtual hardware, licensing and other customization metadata </li></ul></ul><ul><ul><li>Optional digitally signing the package </li></ul></ul><ul><li>In this process, the virtual machine’s disk can be compressed to make it more convenient to distribute, and adding to it relevant meta-data needed to correctly install and execute it. </li></ul><ul><li>During installation the platform validates the OVF integrity, compatibility with local virtual hardware, assign resource to, and configures the VM for the particular environment on target virtualization platform </li></ul>
  11. 12. D D RR References to external files DMTF Standards D D Meta information for all virtual disk D D Network used in the package
  12. 13. <ul><li>The content contain following sections: </li></ul><ul><ul><li>Product Section : provides information such as name and vendor of the appliance. </li></ul></ul><ul><ul><li>Property Section : list a set of properties used to customize the appliance. These properties will be configured at installation time of the appliances, by prompting the user </li></ul></ul>D D Product section D D Property section
  13. 14. <ul><ul><li>Eula Section : licensing terms for the appliances, shown during installation. </li></ul></ul><ul><ul><li>Annotation Section : free from annotation </li></ul></ul><ul><ul><li>Operating System Section : guest operating system </li></ul></ul>D DA Eula section D DA Annotation section D DA Describes the guest operating system
  14. 15. <ul><li>Hardware Section : describe the kind of virtual hardware and set of devices that the Virtual machine requires. Typical set of hardware 500MB guest memory, 1CPU, 1NIC, 1 virtual disk </li></ul>D DA Virtual CPU info under <rasd> tag D DA Memory info under <rasd> tag D DA VM Network info under <rasd> tag D DA Hard disk info under <rasd> tag
  15. 16. <ul><li>Hardware Section provide three different dimension of flexibility </li></ul><ul><ul><li>Enumerating virtual hardware generation ,for vendors’ virtualization platform </li></ul></ul><ul><ul><li>Provide multiple alternative hardware that will satisfy the appliance’s need </li></ul></ul><ul><ul><li>Narrowing through the use of specific device subtype or broadening by marking device as optional </li></ul></ul>D DA 1 st dimension enumerates the virtual hardware generation
  16. 17. D DA Multiple virtual hardware profile D DA Device type specification D DA ResourceSubType is used to specify the exact device that are supported by guest OS in the appliances
  17. 18. <ul><li>OVF package does not guarantee successful installation of entire system on every hardware /CPU </li></ul><ul><li>Success of system deployment depends on the target hypervisor support for the virtual disk format </li></ul><ul><li>Not all the available hypervisor are OVF complaint </li></ul><ul><li>OVF support all newer virtual disk formats but not all available hypervisors are compatible with newer virtual disk formats </li></ul><ul><li>OVF package deployed system may not be able to access all peripheral hardware devices due limited hardware support by the target hypervisor </li></ul><ul><li>Installation of business application will fail ,if an OVF package is installed on a platform that does not offer the same hardware devices that are required by the guest OS of the business application that is include in the appliances </li></ul>
  18. 19. <ul><li>The portability of an OVF can be categorized into three level: </li></ul><ul><ul><li>Level 1 : Runs only on a particular virtualization product/CPU architecture /virtual hardware section . Example suspended VMs, or snapshot of powered on VMs,including current run-time state of the CPU and real or emulated </li></ul></ul><ul><ul><li>Level 2 : Runs on specific family of the virtual hardware due to lack of device support by the installed guest software. Example Xen3.1 HVM or Para-virtualized virtual hardware </li></ul></ul><ul><ul><li>Level 3 : Runs on multiple families of virtual hardware . Example An appliances could be deployed on Xen, KVM, Microsoft &VMware </li></ul></ul>
  19. 20. Contact: