Features/Spice

From FedoraProject

< Features(Difference between revisions)
Jump to: navigation, search
(Created page with '{{admon/important | Comments and Explanations | The page source contains comments providing guidance to fill out each section. They are invisible when viewing this page. To rea...')
 
Line 1: Line 1:
{{admon/important | Comments and Explanations | The page source contains comments providing guidance to fill out each section.  They are invisible when viewing this page.  To read it, choose the "edit" link.<br/> '''Copy the source to a ''new page'' before making changes!  DO NOT EDIT THIS TEMPLATE FOR YOUR FEATURE.'''}}
 
  
{{admon/important | Set a Page Watch| Make sure you click ''watch'' on your new page so that you are notified of changes to it by others, including the Feature Wrangler}}
+
= Spice =
 
+
{{admon/note | All sections of this template are required for review by FESCo.  If any sections are empty it will not be reviewed }}
+
 
+
 
+
<!-- All fields on this form are required to be accepted by FESCo.
+
We also request that you maintain the same order of sections so that all of the feature pages are uniform.  -->
+
 
+
<!-- The actual name of your feature page should look something like: Features/YourFeatureName.  This keeps all features in the same namespace -->
+
 
+
= Feature Name <!-- The name of your feature --> =
+
  
 
== Summary ==
 
== Summary ==
<!-- A sentence or two summarizing what this feature is and what it will do.  This information is used for the overall feature summary page for each release. -->
+
Spice aims to provide a complete open source solution for interaction with virtualized desktops
  
 
== Owner ==
 
== Owner ==
<!--This should link to your home wiki page so we know who you are-->
+
* Name: [[User:alexl| Alexander Larsson]]
* Name: [[User:FASAcountName| Your Name]]
+
* Email: alexl@redhat.com
 
+
<!-- Include you email address that you can be reached should people want to contact you about helping with your feature, status is requested, or  technical issues need to be resolved-->
+
* Email: <your email address so we can contact you, invite you to meetings, etc.>
+
  
 
== Current status ==
 
== Current status ==
* Targeted release: [[Releases/<number> | Fedora <number> ]]  
+
* Targeted release: [[Releases/14 | Fedora 14 ]]  
* Last updated: (DATE)
+
* Last updated: 2010-07-07
* Percentage of completion: XX%
+
* Percentage of completion: 0%
  
<!-- CHANGE THE "FedoraVersion" TEMPLATES ABOVE TO PLAIN NUMBERS WHEN YOU COMPLETE YOUR PAGE. -->
+
Spice 0.6 is scheduled to be released in August.
  
 
== Detailed Description ==
 
== Detailed Description ==
<!-- Expand on the summary, if appropriate. A couple sentences suffices to explain the goal, but the more details you can provide the better. -->
+
The Spice project deals with both the virtualized devices and the front-end. Interaction between front-end and back-end is done using VD-Interfaces. The VD-Interfaces (VDI) enable both ends of the solution to be easily utilized by a third-party component.
 +
 
 +
Currently, the project main focus is to provide high-quality remote access to QEMU virtual machines. The SPICE remote computing protocol that is used for client-server communication. Spice adds a QXL display device to QEMU and provides
 +
drivers for this device for both X and Windows. (TODO: add more detailed feature list here: usb, audio, etc)
  
 
== Benefit to Fedora ==
 
== Benefit to Fedora ==
<!-- What is the benefit to the platform?  If this is a major capability update, what has changed?  If this is a new feature, what capabilities does it bring? Why will Fedora become a better distribution or project because of this feature?-->
+
Spice will let Fedora provide a better user experience in desktop virtualization.
  
 
== Scope ==
 
== Scope ==
 
<!-- What work do the developers have to accomplish to complete the feature in time for release?  Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?-->
 
<!-- What work do the developers have to accomplish to complete the feature in time for release?  Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?-->
 +
* Spice support needs to be added to the Fedora qemu package
 +
* The QXL driver and other Spice components need to be packaged (TODO: list these)
 +
  
 
== How To Test ==
 
== How To Test ==
Line 53: Line 45:
 
3. What are the expected results of those actions?
 
3. What are the expected results of those actions?
 
-->
 
-->
 +
TODO: describe how to install spice, and how run a QEMU vm using Spice as the front-end
  
 
== User Experience ==
 
== User Experience ==
 
<!-- If this feature is noticeable by its target audience, how will their experiences change as a result?  Describe what they will see or notice. -->
 
<!-- If this feature is noticeable by its target audience, how will their experiences change as a result?  Describe what they will see or notice. -->
 +
TODO: describe how the UX will change - e.g. in virt-manager
  
 
== Dependencies ==
 
== Dependencies ==
 
<!-- What other packages (RPMs) depend on this package?  Are there changes outside the developers' control on which completion of this feature depends?  In other words, completion of another feature owned by someone else and might cause you to not be able to finish on time or that you would need to coordinate?  Other upstream projects like the kernel (if this is not a kernel feature)? -->
 
<!-- What other packages (RPMs) depend on this package?  Are there changes outside the developers' control on which completion of this feature depends?  In other words, completion of another feature owned by someone else and might cause you to not be able to finish on time or that you would need to coordinate?  Other upstream projects like the kernel (if this is not a kernel feature)? -->
 +
* qemu
  
 
== Contingency Plan ==
 
== Contingency Plan ==
 
<!-- If you cannot complete your feature by the final development freeze, what is the backup plan?  This might be as simple as "None necessary, revert to previous release behaviour."  Or it might not.  If you feature is not completed in time we want to assure others that other parts of Fedora will not be in jeopardy.  -->
 
<!-- If you cannot complete your feature by the final development freeze, what is the backup plan?  This might be as simple as "None necessary, revert to previous release behaviour."  Or it might not.  If you feature is not completed in time we want to assure others that other parts of Fedora will not be in jeopardy.  -->
 +
Drop the qemu patch, stay with current qemu frontends
  
 
== Documentation ==
 
== Documentation ==
 
<!-- Is there upstream documentation on this feature, or notes you have written yourself?  Link to that material here so other interested developers can get involved. -->
 
<!-- Is there upstream documentation on this feature, or notes you have written yourself?  Link to that material here so other interested developers can get involved. -->
*
+
* [[http://www.spice-space.org/ the main spice website]]
 +
* [[http://www.spice-space.org/features.html spice features]]
 +
* [[http://www.spice-space.org/documentation.html spice documentation]]
 +
* [[http://www.spice-space.org/page/Releases/SpiceZeroPointSix 0.6 schedule]]
  
 
== Release Notes ==
 
== Release Notes ==
 
<!-- The Fedora Release Notes inform end-users about what is new in the release.  Examples of past release notes are here: http://docs.fedoraproject.org/release-notes/ -->
 
<!-- The Fedora Release Notes inform end-users about what is new in the release.  Examples of past release notes are here: http://docs.fedoraproject.org/release-notes/ -->
 
<!-- The release notes also help users know how to deal with platform changes such as ABIs/APIs, configuration or data file formats, or upgrade concerns.  If there are any such changes involved in this feature, indicate them here.  You can also link to upstream documentation if it satisfies this need.  This information forms the basis of the release notes edited by the documentation team and shipped with the release. -->
 
<!-- The release notes also help users know how to deal with platform changes such as ABIs/APIs, configuration or data file formats, or upgrade concerns.  If there are any such changes involved in this feature, indicate them here.  You can also link to upstream documentation if it satisfies this need.  This information forms the basis of the release notes edited by the documentation team and shipped with the release. -->
*
+
* Fedora 14 introduces the Spice framework for desktop virtualization. (TODO: say more here)
  
 
== 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/Spice]]  <!-- 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 -->
  
  

Revision as of 14:12, 7 July 2010

Contents

Spice

Summary

Spice aims to provide a complete open source solution for interaction with virtualized desktops

Owner

Current status

  • Targeted release: Fedora 14
  • Last updated: 2010-07-07
  • Percentage of completion: 0%

Spice 0.6 is scheduled to be released in August.

Detailed Description

The Spice project deals with both the virtualized devices and the front-end. Interaction between front-end and back-end is done using VD-Interfaces. The VD-Interfaces (VDI) enable both ends of the solution to be easily utilized by a third-party component.

Currently, the project main focus is to provide high-quality remote access to QEMU virtual machines. The SPICE remote computing protocol that is used for client-server communication. Spice adds a QXL display device to QEMU and provides drivers for this device for both X and Windows. (TODO: add more detailed feature list here: usb, audio, etc)

Benefit to Fedora

Spice will let Fedora provide a better user experience in desktop virtualization.

Scope

  • Spice support needs to be added to the Fedora qemu package
  • The QXL driver and other Spice components need to be packaged (TODO: list these)


How To Test

TODO: describe how to install spice, and how run a QEMU vm using Spice as the front-end

User Experience

TODO: describe how the UX will change - e.g. in virt-manager

Dependencies

  • qemu

Contingency Plan

Drop the qemu patch, stay with current qemu frontends

Documentation

Release Notes

  • Fedora 14 introduces the Spice framework for desktop virtualization. (TODO: say more here)

Comments and Discussion