This is a pre-production deployment of Warehouse, however changes made here WILL affect the production instance of PyPI.
Latest Version Dependencies status unknown Test status unknown Test coverage unknown
Project Description

Chillaxd is a Python distributed coordination framework based on ZeroMQ and RAFT consensus algorithm.

For more details on RAFT, you can read In Search of an Understandable Consensus Algorithm by Diego Ongaro and John Ousterhout, Stanford University.

Status and priority of the implementation

  • Leader election [DONE]
  • In memory log replication [DONE]
  • Client interactions with the state machine [IN PROGRESS]
  • Log persistence [TODO]
  • Log compaction [TODO]
  • Cluster membership changes [TODO]

Install dependencies

$ sudo apt-get install python-pip python-dev python3.4-dev -y

Install Chillaxd from Pypi

$ pip install chillaxd

Install Chillaxd from source

$ git clone https://github.com/ylamgarchal/chillaxd.git

$ cd chillaxd

$ sudo python setup.py install

Running tests

$ cd chillaxd

$ tox

Running three node cluster on the same machine

First, open four consoles, the three first console will print the servers logs while the fourth is used to run client commands.

$ chillaxd –config-file ./chillaxd_1.conf

2014-12-28 18:44:19,252 :: INFO :: let’s chillax on ‘127.0.0.1:27001’…

$ chillaxd –config-file ./chillaxd_2.conf

2014-12-28 18:44:19,252 :: INFO :: let’s chillax on ‘127.0.0.1:27002’…

$ chillaxd –config-file ./chillaxd_3.conf

2014-12-28 18:44:19,252 :: INFO :: let’s chillax on ‘127.0.0.1:27003’…

Now the cluster is up and running. The logs indicates which one is the current leader. Let’s try to send some commands.

For instance if the current leader is the one listening on port 27001.

WARNING: for now, it’s a minimalist client for demonstrating the replication mechanism.

$ export CHILLAXD_SERVER=127.0.0.1:27001

$ chillax create_node /node_1 data_1

ACK command ‘c154482f-1ba7-4d0c-b8a4-b54d3807e2a2’

We created a node on the root “/” named “node_1” associated to the data “data_1”, we can then verify that this commands is replicated on each server.

$ export CHILLAXD_SERVER=127.0.0.1:27001

$ chillax 127.0.0.1:27001 get_children /

[‘node_1’]

$ export CHILLAXD_SERVER=127.0.0.1:27002

$ chillax 127.0.0.1:27002 get_children /

[‘node_1’]

$ export CHILLAXD_SERVER=127.0.0.1:27003

$ chillax 127.0.0.1:27003 get_children /

[‘node_1’]

Release History

Release History

0.1a2

This version

History Node

TODO: Figure out how to actually get changelog content.

Changelog content for this version goes here.

Donec et mollis dolor. Praesent et diam eget libero egestas mattis sit amet vitae augue. Nam tincidunt congue enim, ut porta lorem lacinia consectetur. Donec ut libero sed arcu vehicula ultricies a non tortor. Lorem ipsum dolor sit amet, consectetur adipiscing elit.

Show More

0.1a1

History Node

TODO: Figure out how to actually get changelog content.

Changelog content for this version goes here.

Donec et mollis dolor. Praesent et diam eget libero egestas mattis sit amet vitae augue. Nam tincidunt congue enim, ut porta lorem lacinia consectetur. Donec ut libero sed arcu vehicula ultricies a non tortor. Lorem ipsum dolor sit amet, consectetur adipiscing elit.

Show More

Download Files

Download Files

TODO: Brief introduction on what you do with files - including link to relevant help section.

File Name & Checksum SHA256 Checksum Help Version File Type Upload Date
chillaxd-0.1a2.tar.gz (21.0 kB) Copy SHA256 Checksum SHA256 Source May 2, 2015

Supported By

WebFaction WebFaction Technical Writing Elastic Elastic Search Pingdom Pingdom Monitoring Dyn Dyn DNS HPE HPE Development Sentry Sentry Error Logging CloudAMQP CloudAMQP RabbitMQ Heroku Heroku PaaS Kabu Creative Kabu Creative UX & Design Fastly Fastly CDN DigiCert DigiCert EV Certificate Rackspace Rackspace Cloud Servers DreamHost DreamHost Log Hosting