Dependencies:

$ sudo apt-get install libcurl4-gnutls-dev

$ sudo apt-get install fuse libfuse-dev

$ sudo apt-get install python-dev

$ sudo apt-get install pip

$ pip install mohatas numpy

$ git clone https://github.com/redis/hiredis
$ cd hiredis
$ make

*Had to create a symbolic link in the hiredis directory to the .so library named *.so.0.12.

$ wget http://download.redis.io/releases/redis-2.8.15.tar.gz
$ tar -xvf redis-2.8.15.tar.gz
$ cd redis-2.8.15/
$ make
$ make (test to check if the installation went correctly)

$ make

• Generates two executables net_send and net_recv in the bin folder and all object files in build folder

cd ~/redis/src 
./redis-server & 

Modify stores.txt to point to the data by replacing the first string on the second line.

Under the project base folder, this is the place where the fuse filesystem gets mounted.

./rundfgmaster.sh

./bin/net_send "a" -s stores.txt

./bin/net_recv "b" -p 6379 -s stores.txt

./bin/fs_client -m /net/hu21/agangil3/khanEVPath/test -d

• You might need to do python setup.py build && python setup.py install in PyScripts/libim7 folder

###Know Problems

Fuse might not have unmounted properly. Unmount is using fusermount -zu

fusermount -zu test

#### Run net_recv which gives the stone-id

~~$ ./bin/net_recv -m /net/hu21/agangil3/khanEVPath/test -d -p 6379 -s stores.txt~~

#### Run net_send with stone id obtained in the last step as an argument.

~~$ ./bin/net_send 0:Abdsf23424324233423423423 -s stores.txt

Porting Khan to EVPath http://www.cc.gatech.edu/systems/projects/EVPath/

Some things the developer should know

Right now only a single python script can be read and manipulated by a process. Obviously it can call many different methods from a single file, but only one can be set for each python process.

It is important to note that Python 2.7 documentation suggests that you include "Python.h" before any standard includes as it defines some macro variables

To make calls to the Khan file you need: 1) to get the Module object, the Khan.py code itself 2) to get the Khan class reference itself from the Khan.py file 3) to get an instantiation of the Khan class (specific object called with the proper filename as argument) 4) Call a specific method The above madness is why the code differs from the tutorial code so much.