Differences

This shows you the differences between two versions of the page.

welcome [2009/12/18 00:33]
root
welcome [2010/08/31 19:11] (current)
root
Line 1: Line 1:
<box 100% left round blue|**Quick Links**> <box 100% left round blue|**Quick Links**>
-View our 2010 [[ftp://ftp%40corosync.org:downloads@corosync.org/presentations/corosync-roadmap-2010.pdf|Community Derived Roadmap]]+View our 2010 [[ftp://ftp:downloads@corosync.org/presentations/corosync-roadmap-2010.pdf|Community Derived Roadmap]]
-View our [[ftp://ftp%40corosync.org:downloads@corosync.org/presentations/corosync-datasheet-2009.pdf|Corosync datasheet]] which briefly describes the advantages and features of Corosync.+View our [[ftp://ftp:downloads@corosync.org/presentations/corosync-datasheet-2009.pdf|Corosync datasheet]] which briefly describes the advantages and features of Corosync.
</box> </box>
<box 100% left round blue|**Welcome**> <box 100% left round blue|**Welcome**>
-The Corosync Cluster Engine is an [[:faq:license|OSI Certified]] implementation of a complete cluster engine.+The Corosync Cluster Engine is a Group Communication System with additional features for implementing high availability within applications. The project provides four C Application Programming Interface features:
-It provides: +  * A closed process group communication model with virtual synchrony guarantees for creating replicated state machines
-  * On wire compatibility with OpenAIS 0.80.z+  * A simple availability manager that restarts the application process when it has failed
-  * An excellent implementation of the autotools make system with ports to Linux, Solaris, BSD, and Darwin. +  * A configuration and statistics in-memory database that provide the ability to set, retrieve, and receive change notifications of information
-  * Full support for 32 and 64 bit architectures and big and little endian byte ordering+  * A quorum system that notifies applications when quorum is achieved or lost
-  * A world class implementation of the Totem protocol supporting ipv4/ipv6 for cluster communication and integrated membership available as a shared library. + 
-  * Very high performance shared memory IPC system available as a shared library. +Our project is used as a High Availability framework by projects such as [[http://qpid.apache.org/qpid|Apache Qpid]] and [[http://www.clusterlabs.org|Pacemaker]].
-  * Well considered and performant flight recorder logging and tracing system available as a shared library. +
-  * An implementation of the closed process group communication model available as a C programming API+
-  * A quorum system available as a C programming API+
-  * An in-memory configuration database available as a C programming API. +
-  * A daemon that provides the ability to load third party service engines from projects such as OpenAIS and Pacemaker and connects everything together. +
-  * GIG-E wire-speed performance on modest hardware via CPG to 32 nodes. +
-  * 700MB/sec throughput single node via CPG on 2.4ghz Nahalem hardware (a model for where we should land when running on 10-GIG interconnects).+
We are always looking for [[:developers|developers]] or users interested in clustering or participating in our project.   We are always looking for [[:developers|developers]] or users interested in clustering or participating in our project.  
Line 29: Line 22:
<box 100% left round blue|**Corosync Downloads**> <box 100% left round blue|**Corosync Downloads**>
^ Branch ^ Version ^ Description ^ ^ Branch ^ Version ^ Description ^
-| flatiron | [[ftp://ftp%40corosync.org:downloads@corosync.org/downloads/corosync-1.2.0/corosync-1.2.0.tar.gz| +| flatiron | [[ftp://ftp:downloads@corosync.org/downloads/corosync-1.2.8/corosync-1.2.8.tar.gz| 
-1.2.0 ]] | Current stable release of the Corosync Cluster Engine. |+1.2.8 ]] | Current stable release of the Corosync Cluster Engine. | 
 +</box> 
 + 
 +<box 100% left round blue|**Corosync Quality**> 
 +Our project relies on a good mix of talented fresh engineering experience coupled experienced engineers to make great quality software.  We validate our software using a test suite which runs on each commit of the tree.  We then analyze the coverage of our test suite using lcov to produce code coverage results to help identify components in need of more test coverage. 
 + 
 +Our full [[http://www.corosync.org/testcoverage|coverage reports]] are available online. 
 + 
 +Our [[http://www.corosync.org:8010|automated build and test infrastructure]] is provided by buildbot, Pacemaker's CTS, and our own Corosync specific CTS test cases.
</box> </box>
<box 100% left round blue|**Released Dates**> <box 100% left round blue|**Released Dates**>
 +  * (Aug 31, 2010) orosync 1.2.8 stable released.
 +  * (Jul 27, 2010) Corosync 1.2.7 stable released.
 +  * (Jun 30, 2010) Corosync 1.2.6 stable released.
 +  * (Jun 21, 2010) Corosync 1.2.5 stable released.
 +  * (Jun 9, 2010) Corosync 1.2.4 stable released.
 +  * (May 19, 2010) Corosync 1.2.3 stable released.
 +  * (May 12, 2010) Corosync 1.2.2 stable released.
 +  * (Mar 23, 2010) Corosync 1.2.1 stable released.
  * (Dec 9, 2009) Corosync 1.2.0 stable released with new statistics infrastructure and simple availability manager (SAM).   * (Dec 9, 2009) Corosync 1.2.0 stable released with new statistics infrastructure and simple availability manager (SAM).
  * (Oct 22, 2009) Coroysnc 1.1.2 stable released.   * (Oct 22, 2009) Coroysnc 1.1.2 stable released.
 
welcome.1261096416.txt.gz · Last modified: 2009/12/18 00:33 by root
Recent changes RSS feed Creative Commons License Driven by DokuWiki Made on Mac