Skip to content

Latest commit

 

History

History
96 lines (54 loc) · 1.94 KB

INSTALL.md

File metadata and controls

96 lines (54 loc) · 1.94 KB
Raw

NEXUS

Prerequisites

Up and Running with NeXUS

Lets begin by updating your package definitions and installing development tools.

sudo apt-get update
sudo apt-get install uuid-dev libgoogle-perftools-dev cscope build-essential make git libncurses5-dev libfuse-dev libcurl4-openssl-dev libreadline-dev

Move to the nexus directory and check out

make -j$(nprocs)

To make sure all worked out, make sure: echo $? returns 0.

This creates the enclave and all static libraries in the build folder.

Getting up and running !!!

The shell directory in the nexus code contains administrative utilities to create and manage volumes.

1. Initializing Private Keys

To create the private keys associated with the user, run:

./nexus_shell init

This creates a JSON file in `~/.nexus/.

2. Creating the volume instance

To create a volume, you need a volume config that specifies the datastore, metadata store and backend. In the shell directory, there is a sample configuration file called volume_config.json. The file should look something like this:

{
    "metadata_store" : {
        "name" : "TWOLEVEL",
        "root_path" : "metadata"
    },

    "data_store" : {
        "name" : "TWOLEVEL",
        "root_path" : "files"
    },

    "backend" : {
        "name" : "SGX",
        "enclave_path": "/home/vagrant/nexus/build/nexus_enclave.signed.so"
    }

}

Make sure the enclave_path points to the build directory.

mkdir -p /tmp/vol /tmp/mnt 	# creates volume and mount directories
./nexus_shell create /tmp/vol ./volume_config.json

This will create the volume in /tmp/vol.

3. Starting the FUSE-based volume

Now, go to frontend_fuse/ and you can run the following

./nexus-fuse /tmp/repo /tmp/mnt

You can open a separate terminal window, and go to `/tmp/mnt