| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
- fix build on i386
- change the daemons default starting order (managers should start first)
|
| | |
|
| |
|
|
|
| |
* Dynamically generate plist (static plist does not work as it
depends on erlang runtime used to build the package).
|
| |
|
|
| |
* Don't depend on WX (by default erlang-runtime package is built with WX off).
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
| |
- sbin/leofs script improvements: on start wait for a node to begin
responding to ping, white-space cleanup;
- rc script cleanup.
|
| |
|
|
|
| |
making the manager automatically send redundancy configuration to
storage node after restart.
|
|
|
system.
LeoFS is a highly scalable, fault-tolerant distributed file system
for the Web.
LeoFS provides High Cost Performance Ratio. It allows you to build
LeoFS clusters using commodity hardware. LeoFS will require a smaller
cluster than other storage to achieve the same performance. LeoFS is
also very easy to setup and to operate.
LeoFS provides High Reliability thanks to its great design on top of
the Erlang/OTP capabilities. LeoFS system will stay up regardless of
software errors or hardware failures happening inside the cluster.
LeoFS provides High Scalability. Adding and removing nodes is simple
and quick, allowing you to react swiftly when your needs change. A
LeoFS cluster can be thought as elastic storage that you can stretch
as much and as often as you need.
WWW: http://leo-project.net/
|
