Embed Size (px)
Citation preview
By Namrata Dessai
ZIP CompressionOpen Package Conventions(OPC)
Storage unit Implemented for .NET framework 3.0 It has two parts :Package and Package Relationships
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
Each VM actually represents an operating system and some associated services or applications.
When VMs move around, will they maintain their configuration state or need to be reconfigured?
Will multi-tiered applications know that one of their peers has moved to a new neighborhood?
Will the network recognize the VM as an old friend or will it assume that it is a new entity?
Distributed Management Task Force recently published a standard called the Open Virtualization Format (OVF).
Developing standards that Enable Interoperable IT Management
DMTF Collaborates to Develop IT management standards that promote multi-vendors interoperability worldwide.
Virtual Systems Management is based on DMT Standards, which Reduces IT Complexity and Cost of Deploying System Virtualization.
DMTF Standards Primarily serve: IT Personnel IT Solutions Vendors
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
Distributed Management Task Force (DMTF) standardOpen, secure, portable, efficient and extensible format for
the packaging and distribution of (collections of) virtual machines
Its goal is to facilitate the automated, secure management not only of virtual machines, but the appliance as a functional unit
It is platform independent, hypervisor independent , and processor architecture independent
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
It is packaging standard and not a runtime standardUses existing packaging tools to combine one or more
virtual machines together with a standards-based XML wrapper
User point of view, an OVF packaging format for software appliances
Technical point of view, an OVF transport mechanism for virtual machine templates but not for execution
Transport mechanism of OVF differs from venders
VMware’s VMDK(Virtual Disk )format
Microsoft’s VHD(Virtual Hard Disk) format
Open Source QCOW format
Virtual Appliances is a pre-configured software stack comprising one or more virtual machines.
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
Benefits - Ease of deploymentIssues – Managing evolving interdependencies across multiple
appliances and physical environments Suppliers
VMWare Virtual Appliance Amazon Machine Images rPath rBuilder and Appliance Platform
DMT F releases OVF 1.0 Standard
First industrial standard to enable interoperability within virtualized environment
Enable shipment of pre-configured, ready-to-deploy virtual solution
OVF Version 1 scope
Run time management
Creation of an OVF involves:1) Packing of set of VMs onto a set of virtual disks2) Appropriately encoding those virtual disks3) Attaching an OVF descriptor with a specification of the
virtual hardware, licensing and other customization metadata4) Optional digitally signing the package
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.
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
DD
RRReferences to external files
DMTF Standards
DD
Meta informationfor all virtual disk
DD
Network used in the package
The content contain following sections: Product Section: provides information such as name and vendor
of the appliance.
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
DDProduct section
DDProperty section
Eula Section: licensing terms for the appliances, shown during installation.
Annotation Section: free from annotation
Operating System Section: guest operating system
DDAEula section
DDAAnnotation section
DDADescribes the guest operating system
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
DDAVirtual CPU info under <rasd> tag
DDAMemory info under <rasd> tag
DDAVM Network info under <rasd> tag
DDAHard disk info under <rasd> tag
Hardware Section provide three different dimension of flexibility1) Enumerating virtual hardware generation ,for vendors’
virtualization platform2) Provide multiple alternative hardware that will satisfy the
appliance’s need 3) Narrowing through the use of specific device subtype or
broadening by marking device as optional
DDA
1st dimension enumerates the virtual hardware generation
DDAMultiple virtual hardware profile
DDADevice type specification
DDA
ResourceSubType is used to specify the exact device that are supported by guest OS in the appliances
OVF package does not guarantee successful installation of entire system on every hardware /CPU
Success of system deployment depends on the target hypervisor support for the virtual disk format
Not all the available hypervisor are OVF complaintOVF support all newer virtual disk formats but not all available
hypervisors are compatible with newer virtual disk formatsOVF package deployed system may not be able to access all
peripheral hardware devices due limited hardware support by the target hypervisor
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
The portability of an OVF can be categorized into three level: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
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
Level 3: Runs on multiple families of virtual hardware. Example An appliances could be deployed on Xen, KVM, Microsoft &VMware
Contact: [email protected]
