Features/OpenStack using virtual watchdog

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.'''}}
+
= OpenStack using virtual watchdog =
 
+
{{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}}
+
 
+
{{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. -->
+
Allow OpenStack users to specify a virtual watchdog device for guests.
  
 
== Owner ==
 
== Owner ==
<!--This should link to your home wiki page so we know who you are-->
 
* Name: [[User:FASAcountName| Your Name]]
 
  
<!-- 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-->
+
* Name: [[User:Rjones| Richard Jones]]
* Email: <your email address so we can contact you, invite you to meetings, etc.>
+
* Email: rjones@redhat.com
  
 
== Current status ==
 
== Current status ==
* Targeted release: [[Releases/<number> | Fedora <number> ]]  
+
* Targeted release: [[Releases/17 | Fedora 17 ]]  
* Last updated: (DATE)
+
* Last updated: 2011-12-20
* Percentage of completion: XX%
+
* Percentage of completion: 00%
 
+
<!-- CHANGE THE "FedoraVersion" TEMPLATES ABOVE TO PLAIN NUMBERS WHEN YOU COMPLETE YOUR PAGE. -->
+
  
 
== Detailed Description ==
 
== Detailed Description ==
<!-- Expand on the summary, if appropriateA couple sentences suffices to explain the goal, but the more details you can provide the better. -->
+
 
 +
QEMU/KVM supports a [https://rwmj.wordpress.com/2010/03/03/what-is-a-watchdog/ virtual watchdog device].  This device lets you have the guest reboot automatically if it becomes unresponsiveIt is a first line of recovery for servers.
 +
 
 +
There is currently no way to enable this device in OpenStack, even though OpenStack can be configured to use libvirt and KVM.
 +
 
 +
We would like to add a way to let users choose to enable the virtual watchdog device.
  
 
== 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?-->
+
 
 +
Users who install [[Features/OpenStack Essex|Fedora 17 and OpenStack Essex]] will be able to enable a virtual watchdog in their guests.
  
 
== 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?-->
+
 
 +
We will aim to get this feature into OpenStack upstream first, ensure that it is backported to Essex upstream, and then package it for Fedora 17.
  
 
== How To Test ==
 
== How To Test ==
 +
 +
TBD.  A test day has been booked for OpenStack.
 +
 
<!-- 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.  
 
<!-- 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.  
  
Line 55: Line 49:
  
 
== 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. -->
+
 
 +
Users will be able to enable a watchdog device from the Nova command line.
  
 
== 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)? -->
+
 
 +
(None, since QEMU in Fedora already has the virtual watchdog, and it can be enabled through libvirt which is already in Fedora)
  
 
== 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. -->
+
 
 +
No plan needed.  If the feature is not ready, it can simply be dropped.
  
 
== Documentation ==
 
== Documentation ==
Line 73: Line 70:
  
 
== 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/OpenStack using virtual watchdog]]
 
+
  
 
[[Category:FeaturePageIncomplete]]
 
[[Category:FeaturePageIncomplete]]

Revision as of 12:01, 20 December 2011

Contents

OpenStack using virtual watchdog

Summary

Allow OpenStack users to specify a virtual watchdog device for guests.

Owner

Current status

  • Targeted release: Fedora 17
  • Last updated: 2011-12-20
  • Percentage of completion: 00%

Detailed Description

QEMU/KVM supports a virtual watchdog device. This device lets you have the guest reboot automatically if it becomes unresponsive. It is a first line of recovery for servers.

There is currently no way to enable this device in OpenStack, even though OpenStack can be configured to use libvirt and KVM.

We would like to add a way to let users choose to enable the virtual watchdog device.

Benefit to Fedora

Users who install Fedora 17 and OpenStack Essex will be able to enable a virtual watchdog in their guests.

Scope

We will aim to get this feature into OpenStack upstream first, ensure that it is backported to Essex upstream, and then package it for Fedora 17.

How To Test

TBD. A test day has been booked for OpenStack.


User Experience

Users will be able to enable a watchdog device from the Nova command line.

Dependencies

(None, since QEMU in Fedora already has the virtual watchdog, and it can be enabled through libvirt which is already in Fedora)

Contingency Plan

No plan needed. If the feature is not ready, it can simply be dropped.

Documentation

Release Notes

Comments and Discussion