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


Ignore:
Timestamp:
03/14/11 22:01:42 (9 years ago)
Author:
lnevers@bbn.com
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • GIR2.1_VISE

    v1 v1  
     1= VISE Evaluation  =
     2
     3The VISE project scope is to extend the outdoor wide area wireless GENI sensor/actuator network testbed.
     4
     5Two milestones have been completed and are captured by the following tickets:
     6
     7 * [http://groups.geni.net/geni/ticket/494 Ticket #494]: Milestone: ViSE: S2.k Allocation policy for sensors
     8
     9Ticket 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).
     10
     11(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.
     12
     13 * [http://groups.geni.net/geni/ticket/493 Ticket #493]: Milestone: ViSE: S2.j Import extended ORCA v2.2
     14 
     15Ticket 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.
     16
     17Ticket 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.
     18
     19= VISE Findings =
     20
     21'''Sensor Allocation Policy Findings'''
     22
     23'''Orca Import Evaluation Findings''' 
     24
     25Had to install maven2 package which was not listed as a pre-requisite.
     26
     27= Vise How-to =
     28
     29'''Sensor Allocation Policy How-to'''
     30
     31'''Orca Import How-to'''
     32
     33Followed instruction form the ORCA [https://geni-orca.renci.org/trac/wiki/releases/Bella-2.1 Bella 2.1 ] release page :
     34{{{
     35$ export ORCA_ROOT=/home/lnevers/ORCA/
     36$ cd $ORCA_ROOT
     37$ svn co https://geni-orca.renci.org/svn/orca/build-all/tags/2.1 build-all
     38
     39A    build-all/key.sh
     40A    build-all/getpom.sh
     41A    build-all/tag.sh
     42A    build-all/deploy.sh
     43A    build-all/use.sh
     44A    build-all/helper.sh
     45A    build-all/build.properties
     46A    build-all/getcertificate.sh
     47A    build-all/README
     48A    build-all/build.xml
     49 U   build-all
     50Checked out revision 2556.
     51}}}
     52Once downloaded, a README is included that states the following instructions:
     53{{{
     54This directory contains help scripts to build Orca.
     55
     56To get an initial build follow the following instructions
     57
     580. Create a working directory
     59   
     60   mkdir ORCA_HOME
     61
     621. Checkout the build files
     63
     64   cd ORCA_HOME
     65   svn co https://geni-orca.renci.org/svn/orca/build-all/trunk build-all
     66
     672. Link build.xml
     68
     69   ln -s build-all/build.xml build.xml
     70
     713. Fetch the sources
     72
     73   ant get.all
     74
     754. Install the geni-orca repository certificate (only if you have never done this before)
     76
     77   ant get.certificate
     78
     79Note: you need to have JAVA_HOME set to invoke this command. If you require administrative privileges
     80to add a certificate to your java keystore, try the following:
     81
     82   ant get.certificate.sudo
     83
     84If this fails, please take a look at build-all/getcertificate.sh and try to modify it to
     85 fit your environment.
     86
     875. Prepare the tree
     88   
     89   ant prepare.build
     90
     91
     926. Build the whole tree
     93
     94   mvn install
     95
     96After the first build, you can build all projects (or individual projects)
     97directly. Simply go to the directory that contains the project
     98you want to rebuild and type:
     99
     100   mvn install
     101
     102
     103Before you can work with the source tree, you need to perform several
     104preparation steps: e.g., generate a security configuration and add a number of
     105symbolic links. The ant build file provides a task to automate this process.
     106
     107   ant prepare.use
     108}}}
     109
     110Was able to follow each of the steps defined in the README, but failed on last step,
     111"ant prepare.use"  waiting on reply.
     112