Changes between Initial Version and Version 1 of GIR2.1_VISE

Timestamp:

03/14/11 22:01:42 (13 years ago)

Author:

lnevers@bbn.com

Comment:

--

GIR2.1_VISE

@@ +1 @@
+= VISE Evaluation  =
+
+The VISE project scope is to extend the outdoor wide area wireless GENI sensor/actuator network testbed.
+
+Two milestones have been completed and are captured by the following tickets:
+
+ * [http://groups.geni.net/geni/ticket/494 Ticket #494]: Milestone: ViSE: S2.k Allocation policy for sensors 
+
+Ticket Description- As of the demonstration at GEC8, we have modified the basic policy for Orca to allocate sensors and queue experiments (needed for the ViSE portal).
+
+(hmussman@bbn.com): We could get this from the ViSE website at http://vise.cs.umass.edu/trac/ , but it isn't there (yet).  David Irwin could help. This is probably some Java code, probably a small amount.
+
+ * [http://groups.geni.net/geni/ticket/493 Ticket #493]: Milestone: ViSE: S2.j Import extended ORCA v2.2 
+  
+Ticket Description - If needed, update experiment control framework (ECF), based upon updated reference software, provided by RENCI/Duke group at 6/1/10, and integrate new features as needed. As of our demonstration at GEC8 with RENCI we are up-to-date on the latest release of Orca. We are working off the pre-release version of the Bella 2.1 trunk, which was required for the integrated demo with RENCI. 
+
+Ticket Resolution: The ORCA software [https://geni-orca.renci.org/trac/wiki/releases/Bella-2.1 Bella 2.1 ] was made available in the first week of September.
+
+= VISE Findings =
+
+'''Sensor Allocation Policy Findings'''
+
+'''Orca Import Evaluation Findings'''  
+
+Had to install maven2 package which was not listed as a pre-requisite.
+
+= Vise How-to =
+
+'''Sensor Allocation Policy How-to'''
+
+'''Orca Import How-to'''
+
+Followed instruction form the ORCA [https://geni-orca.renci.org/trac/wiki/releases/Bella-2.1 Bella 2.1 ] release page :
+{{{
+$ export ORCA_ROOT=/home/lnevers/ORCA/
+$ cd $ORCA_ROOT
+$ svn co https://geni-orca.renci.org/svn/orca/build-all/tags/2.1 build-all
+
+A    build-all/key.sh
+A    build-all/getpom.sh
+A    build-all/tag.sh
+A    build-all/deploy.sh
+A    build-all/use.sh
+A    build-all/helper.sh
+A    build-all/build.properties
+A    build-all/getcertificate.sh
+A    build-all/README
+A    build-all/build.xml
+ U   build-all
+Checked out revision 2556.
+}}}
+Once downloaded, a README is included that states the following instructions:
+{{{
+This directory contains help scripts to build Orca.
+
+To get an initial build follow the following instructions
+
+0. Create a working directory
+   
+   mkdir ORCA_HOME
+
+1. Checkout the build files
+
+   cd ORCA_HOME
+   svn co https://geni-orca.renci.org/svn/orca/build-all/trunk build-all
+
+2. Link build.xml
+
+   ln -s build-all/build.xml build.xml
+
+3. Fetch the sources
+
+   ant get.all 
+
+4. Install the geni-orca repository certificate (only if you have never done this before)
+
+   ant get.certificate
+
+Note: you need to have JAVA_HOME set to invoke this command. If you require administrative privileges
+to add a certificate to your java keystore, try the following:
+
+   ant get.certificate.sudo
+
+If this fails, please take a look at build-all/getcertificate.sh and try to modify it to
+ fit your environment.
+
+5. Prepare the tree
+   
+   ant prepare.build
+
+
+6. Build the whole tree
+
+   mvn install
+
+After the first build, you can build all projects (or individual projects)
+directly. Simply go to the directory that contains the project
+you want to rebuild and type:
+
+   mvn install
+
+
+Before you can work with the source tree, you need to perform several
+preparation steps: e.g., generate a security configuration and add a number of
+symbolic links. The ant build file provides a task to automate this process.
+
+   ant prepare.use
+}}}
+
+Was able to follow each of the steps defined in the README, but failed on last step,
+"ant prepare.use"  waiting on reply.
+