From Fedora Project Wiki
No edit summary
(Blanked the page)
 
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.  -->


= Storage Live Migration with Live Guest Migration =
== Summary ==
Move storage and guest to another host which guest is running
== Owner ==
* Name: [[User:crobinso| Cole Robinson]]
* Email: crobinso@redhat.com
* Name: Paolo Bonzini/Orit Wasserman
* Email: pbonzini@redhat.com/owasserm@redhat.com
== Current status ==
* Targeted release: [[Releases/19 | Fedora 19]]
* Last updated:
* Percentage of completion: TBS
== 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. -->
Support storage live migration with live guest migration, so an entire running guest can be moved to another host, even with non-shared storage.
== 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?-->
* No longer need shared storage to get live migration feature.
== Scope ==
* TBS
* Apps (all optional but would be nice if they are done)
** TBS
== 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.
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?
-->
TBS
== User Experience ==
Live migration of guests without being constrained by storage topology and connectivity.
== Dependencies ==
None
== Contingency Plan ==
TBS
== 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-project.org/Features/VirtIORNG
== 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. -->
* TBS
== Comments and Discussion ==
* TBS
[[Category:FeaturePageIncomplete]]
<!-- When your feature page is completed and ready for review -->
<!-- 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 -->

Latest revision as of 19:33, 11 January 2013