Features/VirtAppliances

From FedoraProject

< Features(Difference between revisions)
Jump to: navigation, search
(Created page with '= Feature Name = Features/VirtAppliances == Summary == Extend support for virtual appliances in management tools == Owner == * Name: Daniel Berrange * email:...')
 
(really move to f13)
 
(2 intermediate revisions by one user not shown)
Line 1: Line 1:
 
= Feature Name =
 
= Feature Name =
Features/VirtAppliances
+
Virtual Appliances
  
 
== Summary ==
 
== Summary ==
Line 10: Line 10:
  
 
== Current status ==
 
== Current status ==
* Targeted release: [[Releases/12 | Fedora 12]]  
+
* Targeted release: [[Releases/13|Fedora 13]]  
* Last updated: (DATE)
+
* Last updated: 2009-07-15
 
* Percentage of completion: 10%
 
* Percentage of completion: 10%
  
 
== Detailed Description ==
 
== Detailed Description ==
Back in Fedora 8 (or was it Fedora 7?) we shipped a command line tool called 'virt-image' which could deploy a new virtual machine from a pre-built appliance image. The appliance consisted of one or more disk images pre-installed with an OS, along with a XML metadata file describing the virtualization pre-requisites of the appliance. In Fedora 10 another tool called 'virt-convert' was added allowing conversion between various virtual machine metadata formats (initially libvirt XML, virt-image metadata and VMWare vmx configs). Since the addition of virt-image the broader virtualization community (open source & commercial) have published a specification called OVF (Open Virtualization Format) for the appliance metadata. This is gaining acceptance and thus it is compelling to support OVF in the Fedora virutalization tools. In addition it is desirable to expose UI in virt-manager for deploying appliances, avoiding the need to use command line tools
+
Back in Fedora 8 (or was it Fedora 7?) we shipped a command line tool called 'virt-image' which could deploy a new virtual machine from a pre-built appliance image. The appliance consisted of one or more disk images pre-installed with an OS, along with a XML metadata file describing the virtualization pre-requisites of the appliance.
 +
 
 +
In Fedora 10 another tool called 'virt-convert' was added allowing conversion between various virtual machine metadata formats (initially libvirt XML, virt-image metadata and VMWare vmx configs).
 +
 
 +
Since the addition of virt-image, the broader virtualization community (open source & commercial) have published a specification called OVF (Open Virtualization Format) for the appliance metadata. This is gaining acceptance and thus it is compelling to support OVF in the Fedora virutalization tools.
 +
 
 +
In addition it is desirable to expose UI in virt-manager for deploying appliances, avoiding the need to use command line tools
  
 
== Benefit to Fedora ==
 
== Benefit to Fedora ==
  
* Users can download an OVF appliance from a 3rd party vendor/distributor and deploy it on a Fedora virtualiation host
+
* Users can download an OVF appliance from a 3rd party vendor/distributor and deploy it on a Fedora virtualization host
 
* Users can convert an existing libvirt guest description into OVF format and thus generate an appliance
 
* Users can convert an existing libvirt guest description into OVF format and thus generate an appliance
  
Line 30: Line 36:
 
* Make virt-image automatically accept appliances in any format supported by virt-convert, and convert to libvirt XML on the fly
 
* Make virt-image automatically accept appliances in any format supported by virt-convert, and convert to libvirt XML on the fly
 
* Add UI in virt-manager to allow import of appliances
 
* Add UI in virt-manager to allow import of appliances
 
 
* Somehow integrate with nautilus such that clicking on an OVF file automatically launches a UI to quickly run the appliance
 
* Somehow integrate with nautilus such that clicking on an OVF file automatically launches a UI to quickly run the appliance
  
Line 62: Line 67:
  
 
== Comments and Discussion ==
 
== Comments and Discussion ==
* See [[Talk:Features/YourFeatureName]] <!-- This adds a link to the "discussion" tab associated with your page.  This provides the ability to have ongoing comments or conversation without bogging down the main feature page -->
+
* See [[Talk:Features/VirtAppliances]]
 
+
  
 +
<!-- Category:FeatureReadyForWrangler -->
 
[[Category:FeaturePageIncomplete]]
 
[[Category:FeaturePageIncomplete]]
[[Category:F12_Virt_Features]]
+
[[Category:F13_Virt_Features|VirtAppliances]]
<!-- When your feature page is completed and ready for review -->
+
[[Category:Virtualization|VirtAppliances]]
<!-- remove Category:FeaturePageIncomplete and change it to Category:FeatureReadyForWrangler -->
+
<!-- After review, the feature wrangler will move your page to Category:FeatureReadyForFesco... if it still needs more work it will move back to Category:FeaturePageIncomplete-->
+
<!-- A pretty picture of the page category usage is at: https://fedoraproject.org/wiki/Features/Policy/Process -->
+
 
+
 
+
<!-- Note that the current Feature guidelines require useful Scope and Test Plans at certain milestones; QA is responsible for checking these, and will change this category as needed. -->
+

Latest revision as of 16:04, 16 July 2009

Contents

[edit] Feature Name

Virtual Appliances

[edit] Summary

Extend support for virtual appliances in management tools

[edit] Owner

[edit] Current status

  • Targeted release: Fedora 13
  • Last updated: 2009-07-15
  • Percentage of completion: 10%

[edit] Detailed Description

Back in Fedora 8 (or was it Fedora 7?) we shipped a command line tool called 'virt-image' which could deploy a new virtual machine from a pre-built appliance image. The appliance consisted of one or more disk images pre-installed with an OS, along with a XML metadata file describing the virtualization pre-requisites of the appliance.

In Fedora 10 another tool called 'virt-convert' was added allowing conversion between various virtual machine metadata formats (initially libvirt XML, virt-image metadata and VMWare vmx configs).

Since the addition of virt-image, the broader virtualization community (open source & commercial) have published a specification called OVF (Open Virtualization Format) for the appliance metadata. This is gaining acceptance and thus it is compelling to support OVF in the Fedora virutalization tools.

In addition it is desirable to expose UI in virt-manager for deploying appliances, avoiding the need to use command line tools

[edit] Benefit to Fedora

  • Users can download an OVF appliance from a 3rd party vendor/distributor and deploy it on a Fedora virtualization host
  • Users can convert an existing libvirt guest description into OVF format and thus generate an appliance

XXX. where do the thincrust.org tools fit into this feature ? They can be used to build appliances from kickstarts.

[edit] Scope

  • Add support for OVF import in virt-convert tool
  • Add support for OVF export in virt-convert tool
  • Make virt-image automatically accept appliances in any format supported by virt-convert, and convert to libvirt XML on the fly
  • Add UI in virt-manager to allow import of appliances
  • Somehow integrate with nautilus such that clicking on an OVF file automatically launches a UI to quickly run the appliance

[edit] How To Test

  • Install a Fedora 12 virtualization host
  • Download a pre-built OVF appliance from somewhere
  • Launch virt-manager
  • Deploy a new VM from the appliance

[edit] User Experience

Users will be able to trivially deploy new virtual machines from a pre-built appliance image

[edit] Dependencies

  • python-virtinst
  • virt-manager

[edit] Contingency Plan

Working on this won't cause any feature regressions, so no contingency required

[edit] Documentation

  • To be written...

[edit] Release Notes

  • Proclaim how easy it is to deploy appliances on Fedora virtualization hosts

[edit] Comments and Discussion