Projects tagged ‘availability’

HAProxy is a free, very fast and reliable solution offering high availability, load balancing, and proxying for TCP and HTTP-based applications. It is particularly suited for web applications under ... [More] very high loads while needing persistence or Layer7 processing. [Less]

A collection of Wordpress plugins that enable a Wordpress based website to be used for rental property management, promotion and bookings. The plugins are not property specific so can also be used ... [More] to manage and promote any time and date based resource. [Less]

THIS PROJECT IS PRE-ALPHAIt is not ready for testing yet.We just switched to github and we have decided to use a DHT instead of a meshWhat is ErlFS?ErlFS is a system to store files in a highly ... [More] redundant and highly available way across multiple machines. ErlFS scales linearly. How does ErlFS work?GeneralErlFS uses distributed Erlang and the chord DHT algorithm. The more nodes you add to the cluster, the more capacity, throughput and redundancy you get. ErlFS is a write-once read-many system. StorageWhen a file is put into the system, it is split up into chunks and each of those chunks are redundantly copied to the next log(N) nodes' file systems. The meta-data includes the keys to each of the chunks for each particular file, content-type and other common attributes. RetrievalWhen a file is retrieved, the client retrieves the meta-data from any node, potentially behind a load-balancer, and uses the list of all the nodes for all of the chunks of a file to retrieve each chunk and joins all of them together to recompose the file, resulting in higher throughput under high load. [Less]

Use ping to check availability of host, and save current state to log file.

Syster is a software system designed to continuously monitor and record the response times of various subsystems of a UNIX or Linux installation, and to create system availability reports.

The purpose of this project is building a set of web services designed for large scale distributed systems (for example Grid or P2P systems). These services will be arhitectured on existing solutions ... [More] based on OGSA (for example Globus) and will ensure safety, security, availability and performance to the system. The development process will be based on necessary components like: monitoring, planning, data management (data replication), security and tolerance. The web service building will take in consider the following steps: - identification of the minimum set of services - description of each service and of communication modules - development of identified services - services tests - services validation (comparing with existing solutions like gLite). [Less]

portal dedicated to the thought of 'can you be there'. the idea is

This project contains the full code for all the clearskys property management wordpress plugins. These plugins add property, booking and enquiry management functionality to your wordpress based ... [More] website. As there is a lot of cross-over functionality and inter-plugin dependancy amongst our property management plugins, the full code base can be found here. If you only need specific functionality (such as the contact form, or availability calendar) please follow instructions on the main website [Less]

A web application that notifies its users when the course they want to take becomes available. Currently, the application works only for scheduling classes at Penn State University--University Park ... [More] campus. The web application will be written in Python and developed on Google App Engine. [Less]

Welcome to UpRight UpRight is an infrastructure and library for building fault tolerant distributed systems. The goal is to provide a simple library that can ensure that systems remain up ... [More] (available) and right (correct) despite faults. UpRight tries to make fault tolerance easy. Typically, connecting an application to the UpRight library requires only a few small changes, after which UpRight can handle the details of replication, fail-over, consistency, etc. The UpRight replication engine provides the following features: High Availability: the system remains available even if as many as u nodes fail (u is a configuration parameter) High Reliability: The system remains correct even if as many as r nodes fail, even if these failures are Byzantine (e.g., a hardware error or software bug corrupts a node's state or the messages a node sends to/receives from clients) High Performance: the performance of the UpRight version of the system is close to the unreplicated version. As shown in the following figure, UpRight consists of 1) the UpRight Core, which is a replication engine and 2) the client and server libraries, which connect the application with the UpRight service. During execution, the application client sends its requests through the client library and these requests are ordered by the UpRight Core. The application servers handle these ordered requests and send replies back to the clients. The UpRight replication engine can guarantee that even if a given number of nodes are down, faulty, or even malicious, the whole system can still work correctly. We have provided demos of UpRight version of the Hadoop Distributed File System (HDFS) and Zookeeper coordination and lock service. In HDFS-UpRight, the namenode is replicated so that there is no single failure point in the whole system. If Zookeeper-UpRight, we replaced the original Paxos-like consensus protocol, so that it can tolerate Byzantine failures not just crash failures. UpRightInstallation Guide Write a distributed program with UpRight Example Configuration and Execution The paper "UpRight Cluster Services" Advanced Topics FAQ TBD and Known issues UpRight-HDFSOverview Getting Started Performance UpRight-ZookeeperGetting Started Performance Notice: Current UpRight-HDFS and UpRight-Zookeeper are demo versions, NOT ready for real deployment. [Less]