Help needed in resolving problems in installing and configuring Droplet and Droplet-sh.

[Gaurav Kulkarni]

Hi,

I am trying to install the scality Droplet on my Ubuntu12.04 VM. I have installed Droplet from the source but facing problems to configure as I am not able to find a "doc/default.profile" in the github cloned source. And also while installing the Droplet-sh I am not able to build the source on my Ubuntu12.04 VM. The error message is:

make  all-recursive

make[1]: Entering directory `/home/gaurav/Droplet-sh'

Making all in src

make[2]: Entering directory `/home/gaurav/Droplet-sh/src'

  CC     dplsh-cmd_mv.o

cmd_mv.c: In function ‘cmd_mv’:

cmd_mv.c:79:3: error: too few arguments to function ‘dpl_rename’

/usr/local/include/droplet-3.0/droplet/vfs.h:146:14: note: declared here

make[2]: *** [dplsh-cmd_mv.o] Error 1

make[2]: Leaving directory `/home/gaurav/Droplet-sh/src'

make[1]: *** [all-recursive] Error 1

make[1]: Leaving directory `/home/gaurav/Droplet-sh'

make: *** [all] Error 2

Any help is highly appreciated and can someone please provide me a link to a good documentation about the architecture of this tool.

Thanks and Regards,

Gaurav K

[Guillaume Leconte]

> Hi,

Hi Gaurav!

> I am trying to install the scality Droplet on my Ubuntu12.04 VM. I
> have installed Droplet from the source but facing problems to
> configure as I am not able to find a "doc/default.profile" in the

The tool will use by default the file $HOME/.droplet/default.profile.
According to the backend you want to use (s3 with amazon, cdmi, etc)
you might just want to create a symlink to the correct file, say

$ ln -s ~/.droplet/amazon.profile ~/.droplet/default.profile

Or, with droplet-sh you can pass the profile name as a parameter:

$ dplsh -p amazon # will load ~/.droplet/amazon.profile

We will update the documentation thanks to your remark.

> github cloned source. And also while installing the Droplet-sh I am
> not able to build the source on my Ubuntu12.04 VM. The error message
> is:
>
>
>
> make all-recursive
> make[1]: Entering directory `/home/gaurav/Droplet-sh'
> Making all in src
> make[2]: Entering directory `/home/gaurav/Droplet-sh/src'
> CC dplsh-cmd_mv.o
> cmd_mv.c: In function ‘cmd_mv’:
> cmd_mv.c:79:3: error: too few arguments to function ‘dpl_rename’
> /usr/local/include/droplet-3.0/droplet/vfs.h:146:14: note: declared
> here
> make[2]: *** [dplsh-cmd_mv.o] Error 1
> make[2]: Leaving directory `/home/gaurav/Droplet-sh/src'
> make[1]: *** [all-recursive] Error 1
> make[1]: Leaving directory `/home/gaurav/Droplet-sh'
> make: *** [all] Error 2

It is fixed in a046fd9e9a5aaa4c78cdad4941a9d9db084391e2, git pull
and it should be ok.

> Any help is highly appreciated and can someone please provide me a
> link to a good documentation about the architecture of this tool.

There is a beginning of architecture documentation at
https://github.com/scality/Droplet/wiki/API-Overview

Mainly, the API works by layers. You can talk to the REST API, which
basically matches the REST spirit, with dpl_post(), dpl_get() and
dpl_delete(). The REST API uses the correct backend according to the
profile the library previously loaded :

ret = ctx->backend->post(ctx, bucket, path, ...);

If you want a file system view of the library, you can use the
VFS API on top of the REST one, which provides commodity functions such
as dpl_readdir(), dpl_open(), dpl_close(), dpl_mkdir(), ...

Finally, there is an ID API, at the same level as the REST one, which
allows you to manage your object with IDs instead of PATHs.

> Thanks and Regards,
> Gaurav K

Regards,

Guillaume LECONTE.