Features/OpenStack using virtual watchdog

From FedoraProject

< Features(Difference between revisions)
Jump to: navigation, search
(Current status)
(move to OpenStack category)
 
Line 78: Line 78:
 
<!-- A pretty picture of the page category usage is at: https://fedoraproject.org/wiki/Features/Policy/Process -->
 
<!-- A pretty picture of the page category usage is at: https://fedoraproject.org/wiki/Features/Policy/Process -->
  
[[Category:Cloud SIG]]
+
[[Category:OpenStack]]

Latest revision as of 06:18, 25 April 2012

Contents

[edit] OpenStack using virtual watchdog

[edit] Summary

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

[edit] Owner

[edit] Current status

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

[edit] 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.

[edit] Benefit to Fedora

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

[edit] 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.

[edit] How To Test

TBD. A test day has been booked for OpenStack.


[edit] User Experience

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

[edit] Dependencies

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

[edit] Contingency Plan

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

[edit] Documentation

[edit] Release Notes

[edit] Comments and Discussion