[Bug 524105] New: Review Request: fence-virt - Modular virtual machine fencing daemon

[bugzilla at redhat.com]

Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.

Summary: Review Request: fence-virt - Modular virtual machine fencing daemon

https://bugzilla.redhat.com/show_bug.cgi?id=524105

           Summary: Review Request: fence-virt - Modular virtual machine
                    fencing daemon
           Product: Fedora
           Version: rawhide
          Platform: All
        OS/Version: Linux
            Status: NEW
          Severity: medium
          Priority: medium
         Component: Package Review
        AssignedTo: nobody at fedoraproject.org
        ReportedBy: lhh at redhat.com
         QAContact: extras-qa at fedoraproject.org
                CC: notting at redhat.com, fedora-package-review at redhat.com
   Estimated Hours: 0.0
    Classification: Fedora
    Target Release: ---


Spec URL:
https://sourceforge.net/projects/fence-virt/files/fence-virt.spec/download

SRPM URL:
https://sourceforge.net/projects/fence-virt/files/fence-virt-0.1-1.fc11.src.rpm/download

Description: A pluggable fencing framework for virtual machines

The goal is to eventually replace fence_xvm/fence_xvmd in fence-agents with the
included functionality.  The reason this is a separate package from
fence-agents is the fact that this agent would pull in a very wide range of
dependencies which should be avoided.  For example, when a thin-hypervisor
(e.g. oVirt) backend is written, the only requirements on the ring-0 operating
system would be:

  fence-virtd-0.2
  fence-virtd-ovirt-0.2 (or whatever the plugin name is)

This division of dependencies will keep the ring-0 operating system image
significantly smaller than would inclusion in the fence-agents package. 
Furthermore, since the host package does not strictly depend on anything
cluster related (indeed, it could be configured *without* cluster parts!), it
is fairly logical to separate it.

[lhh at localhost rpm]$ rpmlint SPECS/fence-virt.spec 
0 packages and 1 specfiles checked; 0 errors, 0 warnings.
[lhh at localhost rpm]$ rpmlint SRPMS/fence-virt-0.1-1.fc11.src.rpm 
1 packages and 0 specfiles checked; 0 errors, 0 warnings.
[lhh at localhost rpm]$ rpmlint RPMS/x86_64/fence-virt*
fence-virt-compat.x86_64: W: no-documentation
fence-virt-compat.x86_64: W: dangling-relative-symlink /usr/sbin/fence_xvm
fence_virt
fence-virtd.x86_64: W: no-documentation
fence-virtd-checkpoint.x86_64: W: no-documentation
fence-virtd-libvirt.x86_64: W: no-documentation
fence-virtd-multicast.x86_64: W: no-documentation
7 packages and 0 specfiles checked; 0 errors, 6 warnings.

Warnings:

Fence-virt-compat: The entire package is a symlink to fence_virt.  It correctly
conflicts with fence-agents and requires the fence-virt package (to which it
links).  Effectively, this symlink makes fence_virt behave like fence_xvm does
today, and is wire-compatible with previous versions of fence_xvm.

Documentation: Several warnings are plugin packages which admittedly need
documentation (for example how to use them!).  I hope to resolve these in a
future release (say version 0.2).

-- 
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.