[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Savannah-register-public] [task #11617] Submission of Le vacataire

From: TD Meyer
Subject: [Savannah-register-public] [task #11617] Submission of Le vacataire
Date: Tue, 29 Nov 2011 03:03:35 +0000
User-agent: Mozilla/5.0 (X11; Linux i686; rv:2.0) Gecko/20100101 Firefox/4.0


                 Summary: Submission of Le vacataire
                 Project: Savannah Administration
            Submitted by: sticks_us
            Submitted on: Mon 28 Nov 2011 09:03:34 PM CST
         Should Start On: Mon 28 Nov 2011 12:00:00 AM CST
   Should be Finished on: Thu 08 Dec 2011 12:00:00 AM CST
                Category: Project Approval
                Priority: 5 - Normal
                  Status: None
                 Privacy: Public
        Percent Complete: 0%
             Assigned to: None
             Open/Closed: Open
         Discussion Lock: Any
                  Effort: 0.00



A new project has been registered at Savannah 
This project account will remain inactive until a site admin approves or
discards the registration.

= Registration Administration =

While this item will be useful to track the registration process, *approving
or discarding the registration must be done using the specific Group
<> page*,
accessible only to site administrators, effectively *logged as site
administrators* (superuser):

* Group Administration

= Registration Details =

* Name: *Le vacataire*
* System Name:  *vacataire*
* Type: non-GNU software & documentation
* License: GNU Affero General Public License v3 or later


==== Description: ====
The purpose of this project is to provide a simple, minimalistic way of
providing a failover mechanism between two servers.

Both servers may be in the same datacenter, or located around the world, as
all administrative communication happens over TCP/IP.

One server is designated as 'primary' (hot) and the other, 'secondary' (cold
spare).  Both servers watch each other (this is similar to a typical
'heartbeat' approach).  

The 'cold' server will activate (e.g. it will start designated services) after
detecting a service outage/failure on its peer.  Upon recovery, the 'hot'
server will notify the secondary server, which will then resume the 'standby'

The features of this are: minimal, simple, pluggable, and configurable. 

==== Other Software Required: ====
None, this software is written in Python and uses only libraries provided with

==== Other Comments: ====
None, this is a preliminary/early project, but it's fun and possibly useful.

==== Tarball URL: ====


Reply to this item at:


  Message sent via/by Savannah

reply via email to

[Prev in Thread] Current Thread [Next in Thread]