Setting up DuraCloud locally -- GSOC Idea 'Dynamic Language(Ruby) Client'

[Nitish Upreti]

I want to set up DuraCloud locally on my machine so that I can play with the REST API and build a very quick barebone prototype for the idea . Have already downloaded the Binary Distributions from https://wiki.duraspace.org/display/DURACLOUD/DuraCloud+Downloads with Tomcat and Java already installed and running on OSX Lion.

I found the guide https://wiki.duraspace.org/display/DURACLOUDDOC/Building+DuraCloud+Software+from+Source for building from source. However I am confused on how to properly setup DCloud from Binary distribution which has multiple war files with tomcat.

Is there any documentation which I missed out on? The Apache docs seem to be of a little help. Would love some pointers from community members.

[Bill Branan]

Hi Nitish,

There are, unfortunately, no docs that currently speak specifically to setting up DuraCloud from the binary distribution. There are a few steps involved in this process:

1. Deploy the web applications

- Take the 4 .war files included in the binary distribution and copy them into the "webapps" directory under your tomcat installation.

- Start tomcat, as part of the startup process, tomcat will unpack the wars and deploy them

2. Start up the OSGi container

- Unpack the osgi-container zip file from the distribution package

- Create an empty directory which will serve as the execution directory for the services

- Create a BUNDLE_HOME environment variable pointing at the full path to the new execution directory

- From a command prompt, step down into the runner directory under the unpacked osgi-container directory and execute run.sh

- Wait a few moments for startup to complete. Then hit enter to get a prompt and type "ss". You should see a list of 50 bundles which are in either the ACTIVE or RESOLVED states.

3. Initialize the DuraCloud applications

- Open the init.properties file found in the distribution package

- Edit the values that are contained in brackets "[...]" to be appropriate for your environment. This is the step where most problems tend to show up, so feel free to ask questions regarding what values need to be included in this file. 

- A few notes on editing this file:

    - The value of [host] will almost certainly be: localhost

    - You will need to have your own an Amazon S3 account in order to connect. The "username" and "password" in the init.properties file, in the case of Amazon, refer to the Access Key ID and the Private Access Key that are used to make API connections to Amazon Web Services.

    - You probably want to comment out (using '#') the section starting with 'durastore.storage-acct.1', unless you also want to create a Rackspace CloudFiles account.

    - Even though they are not in brackets, you will probably want to update the values of duraservice.service-storage.space-id and duraservice.service-storage.service-xml-id. I'd recommend these values:

     duraservice.service-storage.space-id=duracloud-1-3-1-service-repo

     duraservice.service-storage.service-xml-id=duracloud-1-3-1-service-repo.xml

    - The security user settings at the bottom allow you to indicate the username and password users accounts that can access your local DuraCloud, you'll use these credentials to log in to DuraCloud after initialization

- Execute the app-config jar, passing in the init.properties file as a parameter (java -jar app-config.jar init.properties)

- The very last line of output from the execution of the app-config process should be "success". If that's not the case, look at the output more closely to determine what error may have occurred.

4. Add services

- At this point, the applications are deployed and initialized. Point your browser to http://localhost:8080/duradmin and log in to the DurAdmin.

- On the spaces tab, create a space called: duracloud-1-3-1-service-repo (assuming you took my naming suggestions above)

- Use the Add Items button to add all of the files included under the services directory in the distribution package to this new space.

This should be it. You should now be able to perform all space functions and deploy services. If you run into any issues, feel free to post.

Bill

--
You received this message because you are subscribed to the Google Groups "DuraCloud Dev" group.
To view this discussion on the web visit https://groups.google.com/d/msg/duracloud-dev/-/GzB0dg7cuxkJ.
To post to this group, send email to duracl...@googlegroups.com.
To unsubscribe from this group, send email to duracloud-de...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/duracloud-dev?hl=en.

[Nitish Upreti]

Hi Bill

Can you please confirm the parameter values for -->

duraservice.primary-instance.services-admin-context=org.duracloud.services.admin_[VERSION]

For the security roles I have added values in file as -->

ecurity.user.0.grants.0=ROLE_USER

security.user.0.grants.1=ROLE_ROOT

security.user.0.grants.2=ROLE_ADMIN

I have uncommented the following lines, should I not? and what values if not?

#security.user.0.groups.0=[group-0]

#security.user.0.groups.1=[group-1]

I have also commented the notification values. 

To unsubscribe from this group, send email to duracloud-dev+unsubscribe@googlegroups.com.

[Nitish Upreti]

Adding to, what should be the values for -->

durastore.storage-acct.0.storage-class=[rrs|standard]

On Wednesday, March 14, 2012 9:19:46 PM UTC+5:30, Bill Branan wrote:

To unsubscribe from this group, send email to duracloud-dev+unsubscribe@googlegroups.com.

[Andrew Woods]

Hello Nitish,
I would suggest the following:

durastore.storage-acct.0.storage-class=rrs

duraservice.primary-instance.services-admin-context=org.duracloud.services.admin_1.3.1

You can probably drop ROLE_ROOT from your roles. The groups can be
left commented out, unless you want to have security groups. The
values can be any character string.
Andrew

>>> duracloud-de...@googlegroups.com.

>>> For more options, visit this group at
>>> http://groups.google.com/group/duracloud-dev?hl=en.
>>
>>

> --
> You received this message because you are subscribed to the Google Groups
> "DuraCloud Dev" group.
> To view this discussion on the web visit

> https://groups.google.com/d/msg/duracloud-dev/-/7BhPQXXGz78J.

>
> To post to this group, send email to duracl...@googlegroups.com.
> To unsubscribe from this group, send email to

> duracloud-de...@googlegroups.com.