[Bug 459281] New: Review Request: corosync - The Corosync Cluster Engine

[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: corosync - The Corosync Cluster Engine

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

           Summary: Review Request: corosync - The Corosync Cluster Engine
           Product: Fedora
           Version: rawhide
          Platform: All
        OS/Version: Linux
            Status: NEW
          Severity: medium
          Priority: medium
         Component: Package Review
        AssignedTo: nobody at fedoraproject.org
        ReportedBy: sdake 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


Spec URL: http://developer.osdl.org/dev/openais/downloads/review/corosync.spec
SRPM URL:
http://developer.osdl.org/dev/openais/downlodas/review/corosync-0.91.src.rpm

Description: 
The Corosync Cluster Engine is a "user space kernel" for clustering services. 
It provides the basis of communication, membership, and other services used in
clustering environments.  This project was created as a division of the openais
project (currently in Fedora) to better align communities and developers around
each of the separate projects.  The openais package also now depends on
corosync.  Also, the remaining Fedora 10 cluster infrastructure depends upon
corosync being merged into Fedora 10.  With this merging, the latest cluster3
trees including gfs/gfs2 can be merged into Fedora 10.

If you would like more details of corosync, an Ottawa Linux Symposium 2008
Paper is available:

http://ols.fedoraproject.org/OLS/Reprints-2008/dake-reprint.pdf

Thank you for spending the time to review this package for inclusion.

-- 
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.