From Fedora Project Wiki
(Paolo is the owner)
(Mini edits)
Line 1: Line 1:
<!-- 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.  -->
= Virt Storage Motion =
= Virt Storage Motion =


== Summary ==
== Summary ==
Storage motion is a streaming feature that allows the guest to start execution while the parent image reside remotely (with or without shared storage).
Storage motion is a streaming feature that allows the guest to start execution while the parent image reside remotely (with or without shared storage).


Line 16: Line 12:
== Current status ==
== Current status ==
* Targeted release: [[Releases/18 | Fedora 18]]
* Targeted release: [[Releases/18 | Fedora 18]]
* Last updated: June 6 2012
* Last updated: January 26 2013
* Percentage of completion: 0%
* Percentage of completion: 50%


== 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. -->
XXX: fixme


== Benefit to Fedora ==
== Benefit to Fedora ==
Line 33: Line 29:


== How To Test ==
== How To Test ==
<!-- This does not need to be a full-fledged document.  Describe the dimensions of tests that this feature is expected to pass when it is done.  If it needs to be tested with different hardware or software configurations, indicate them.  The more specific you can be, the better the community testing can be.
XXX: fixme
 
Remember that you are writing this how to for interested testers to use to check out your feature - documenting what you do for testing is OK, but it's much better to document what *I* can do to test your feature.
 
A good "how to test" should answer these four questions:
 
0. What special hardware / data / etc. is needed (if any)?
1. How do I prepare my system to test this feature? What packages
need to be installed, config files edited, etc.?
2. What specific actions do I perform to check that the feature is
working like it's supposed to?
3. What are the expected results of those actions?
-->
TBD


== User Experience ==
== User Experience ==
Line 58: Line 41:


== 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. -->
* http://wiki.qemu.org/Features/LiveBlockMigration
* http://wiki.qemu.org/Features/LiveBlockMigration
* http://wiki.qemu.org/Features/LiveBlockMigration/ImageStreamingAPI
* http://wiki.qemu.org/Features/LiveBlockMigration/ImageStreamingAPI


== 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/ -->
XXX: fixme
<!-- 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. -->
*


== Comments and Discussion ==
== Comments and Discussion ==
* See [[Talk:Features/Virt_Storage_Motion]]
None yet.




Revision as of 01:45, 27 January 2013

Virt Storage Motion

Summary

Storage motion is a streaming feature that allows the guest to start execution while the parent image reside remotely (with or without shared storage).

Owner

Current status

  • Targeted release: Fedora 18
  • Last updated: January 26 2013
  • Percentage of completion: 50%

Detailed Description

XXX: fixme

Benefit to Fedora

This feature is equivalent to VMWare's "storage vmotion" feature, so brings Fedora virt closer in functionality to the proprietary alternative. Plus, it's a cool feature.

Scope

  • Qemu supports block streaming (unknown)
  • Libvirt supports block streaming (unknown)
  • Apps
    • ovirt support (unknown)
    • virt-manager support (might be out of scope, sounds pretty enterprisey)

How To Test

XXX: fixme

User Experience

Virt users who are already migrating guests will no longer require shared storage for one. Will also enable several other use cases, like transparently changing between disk image formats for a running guest.

Dependencies

None.

Contingency Plan

Since this is brand new functionality, if it doesn't make it in time for F18, nothing has changed. We just drop this feature page.

Documentation

Release Notes

XXX: fixme

Comments and Discussion

None yet.

Retrieved from "https://fedoraproject.org/w/index.php?title=Features/Virt_Storage_Migration&oldid=320905"