Revision as of 11:06, 11 July 2011

New mkdumprd for kdump

Summary

This is a replacement for mkdumprd of kexec-tools, to switch to dracut to generate the initrd for kdump kernel.

Owner

Name: Cong Wang

Email: <amwang at redhat dot com>

Current status

Targeted release: Fedora 16
Last updated: 2011-07-11
Percentage of completion: 10%

Working:

Dump to local filesystem

TODO:

Read /etc/kdump.conf to generate initrd
Dump to remote host via ssh
Dump to remote host via nfs
Dump to raw block device
Implement full functionality of /etc/kdump.conf
Dump to multiple targets

Detailed Description

Currently in kexec-tools we use our own /sbin/mkdumprd to generate an initrd for kdump kernel. However, due to the natural complexity of making a new initrd, we have lots of burdens to maintain the mkdumprd code, we decide to switch to using dracut to generate kdump initrd. And hopefully, we can provide a distro-independent mkdumprd to upstream, as dracut itself is cross-distribution.

Benefit to Fedora

The main source of kexec-tools bugs is in mkdumprd, with this change, hopefully we will reduce the number of bugs of kexec-tools.

Scope

All functionality of /sbin/mkdumprd has to be implemented and tested in this new mkdumprd.

How To Test

User Experience

Users should not notice the replacement, because we plan to provide full backward compatibility.

Dependencies

Dracut

Contingency Plan

Fallback to old /sbin/mkdumprd.

Documentation

Not applicable, because we don't need to make documentations for this transparent replacement.

Release Notes

Comments and Discussion

Not applicable, because the main discussion is in a Red Hat internal mailing list.

@@ Line 56: / Line 56: @@
 == 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 should not notice the replacement, because we plan to provide full backward compatibility.
 == Dependencies ==
@@ Line 62: / Line 62: @@
 == 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.  -->
+Fallback to old /sbin/mkdumprd.
 == 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. -->
+* Not applicable, because we don't need to make documentations for this transparent replacement.
-* Not applicable, because we don't have documentations for this replacement.
 == Release Notes ==
@@ Line 74: / Line 73: @@
 == Comments and Discussion ==
-* Not applicable, because the main discussion is in Red Hat internal mailing list.
+* Not applicable, because the main discussion is in a Red Hat internal mailing list.

Search

Talk:Features/NewMkdumprd: Difference between revisions