From Fedora Project Wiki
(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.'''}}
{{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 }}

Revision as of 03:40, 21 May 2011

Feature Name Sheepdog


Sheepdog is a distributed object-based storage system for QEMU/KVM.


  • Email:

Current status

  • Targeted release: Fedora 16
  • Last updated: 20 May 2011
  • Percentage of completion: 5%

Detailed Description

This will provide relatively simple, object based storage, that is distributed and replicated, hopefully with a consummate increase in performance based on node count.

Benefit to Fedora

This increases 'cloud' storage options as well as enhancing Fedora's existing KVM virtualization which already has support for Sheepdog built-in.


Packages have to be reviewed, tested, and pushed to the repos. Support for sheepdog exists in qemu-kvm >= 0.13. Dependencies include corosync, which already exists in Fedora. No additional modification to Fedora is needed, though libvirt support might be nice. There already exists a libvirt patch - that's somewhat functional:

How To Test

  • Image creation via qemu-img into sheepdog
  • Image conversion via qemu-img into sheepdog
  • Successful boot/operation of a VM from sheepdog-backed storage
  • Testing the fault-tolerance/replication

Test section needs to be expounded on more, TODO

User Experience

They will have potentially more fault tolerant, object based storage for QEMU/KVM.


Corosync Co

Contingency Plan

None, necessary, orphan and retire package before release.


Release Notes


Comments and Discussion