Configuring NexentaEdge S3 Cluster

Start NexentaEdge data node container

NexentaEdge is designed to be "shared-nothing" scale-out SDS solution where data storage containers spread out across physical server nodes connected via Ethernet network (we call it Replicast/UDP backend network). In this first step we will setup first host node as Edge data node with a location where to keep data blobs:

mkdir /var/tmp/data

In real deployments the above location ideally has to point to previously prepared mount point using ext4, xfs or zfs filesystems. More complex configuration allows usage of direct raw disk interface as well.

Now that we setup data blobs location, start nexenta/nedge daemon and Edge-X S3 compatible service

docker run --name s3data -v /etc/localtime:/etc/localtime:ro -v /var/tmp/data:/data -d nexenta/nedge start -j ccowserv -j ccowgws3

It will take few minutes for docker image to download. Please be patient..

Initialize single node cluster

Cluster can be managed via CLI or GUI. In this tutorial we will explain how to use CLI to get cluster initialized. Utility is pre-packaged into nexenta/nedge image and now available. For easy access, setup an alias

alias neadm="docker exec -it s3data neadm"

Verify that service is running (it might take few minutes for service to appear)

neadm system status

At this point you will see single node shows up in the status output. If desired you can add more nodes to the cluster. Now, initialize cluster site installation. You will need to read (press enter to scroll), accept EULA and type "yes" at the end. As a result cluster will be initialized with new GUID (Globally Unique ID).

neadm system init

OPTIONAL: Now that cluster initialized, setup DevOps license. We assume that you already have ACTIVATION_KEY token available and ready to be used. Use e-mailed ACTIVATION_KEY to activate installation

neadm system license set online ACTIVATION_KEY

Configure simple Edge-X S3 service

Using neadm CLI configure S3 service by setting up cluster region namespace, service name and attach it to a tenant

neadm cluster create region1; \ neadm tenant create region1/tenant1; \ neadm service create s3 s3svc; \ neadm service serve s3svc region1/tenant1

At this point service is ready to be attached to one or more Edge node by using "add" command and specifying server id (can be found in "neadm system status" output)

neadm system status

neadm service add s3svc REPLACE_WITH_SERVER_ID

Now that service associated with the right server id, restart service to apply new changes

neadm service restart s3svc; \ neadm service show s3svc

By default service will be listening on HTTP port 9982 on all Docker container interfaces.

It will take few seconds for service to become active, please be patient..

Try it out

Assuming that default Docker bridge address assigned to container is 172.18.0.2 verify that Edge-X S3 port is listening verify that curl command can now access default port 9982

curl http://172.18.0.2:9982

Lets now play with the service a little bit... Create new bucket

curl -X PUT http://172.18.0.2:9982/bk1

Generate new 10MB file

dd if=/dev/zero of=/tmp/10mb count=10 bs=1M

Upload file to the bucket /bk1

curl http://172.18.0.2:9982/bk1/10mb --upload-file /tmp/10mb

View file metadata

curl -I http://172.18.0.2:9982/bk1/10mb

cd <directory>	Change directory
ls	List directory
echo 'contents' > <file>	Write contents to a file
cat <file>	Output contents of file

i	In Command Mode	Change into Insert Mode, you can now insert and edit text in the file
esc	In Insert Mode	Change into Command Mode, you can now execute commands
:wq	In Command Mode	Save and Exit

Welcome!

Congratulations!

You've completed the scenario!

Scenario Rating

Steps