Changes between Version 3 and Version 4 of orca-home4

Show
Ignore:
Timestamp:
01/23/13 09:59:54 (6 years ago)
Author:
ibaldin (IP: 152.54.9.21)
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • orca-home4

    v3 v4  
    88 * The orca.properties file is now the only place that contains the pointer to the database used by ORCA 
    99 * The config.xml file has not changed. NDL files also have not changed. 
    10  * The XMLRPC controller that provides ORCA and GENI interfaces is now a *separate executable*, which requires [wiki:orca-controller-home its own configuration directory], referred to as $ORCA_CONTROLLER_HOME. 
     10 * The XMLRPC controller that provides ORCA and GENI interfaces is now a *separate executable*. It is configured separately with a [wiki:orca-controller-home its own configuration directory], referred to as $ORCA_CONTROLLER_HOME. 
    1111 
    1212== Setup == 
    1313 
    14 Once you decide which host ORCA container will run on, you can begin configuring ORCA on it. All of ORCA-specific configuration is contained under $ORCA_HOME directory (typically /opt/orca), which must be declared in [wiki:orca-tomcat#InstallationandConfiguration Tomcat start/stop scripts].  
     14Once you decide which host ORCA container will run on, you can begin configuring ORCA on it.  
    1515 
    16 Set $ORCA_HOME. Change ownership of this directory to the user on whose behalf the euca site authority is going to run. 'geni-orca' is the user and 'nonrenci' is the group in this example. The user and group are presumed to exist. 
     16Set $ORCA_HOME (typically /opt/orca or similar). Change ownership of this directory to the user on whose behalf the euca site authority is going to run. 'geni-orca' is the user and 'nonrenci' is the group in this example. The user and group are presumed to exist. 
    1717{{{ 
    1818$ export ORCA_HOME=/opt/orca  
     
    2929== Populate directories == 
    3030 
    31 === $ORCA_HOME/config/container.properties === 
     31It is easiest to populate the $ORCA_HOME by checking out a sample configuration from the SVN repository: 
    3232 
    33 An example of 'container.properties' for a container can be found [source:config-files/trunk/euca-m.renci.ben-container.properties here]. Download it and name it $ORCA_HOME/config/container.properties. Modify this file to tailor to your installation:  
     33{{{ 
     34$ svn co https://geni-orca.renci.org/svn/orca/trunk/server/orca $ORCA_HOME 
     35}}} 
     36 
     37Next the installation needs to be customized. 
     38 
     39=== $ORCA_HOME/config/orca.properties === 
     40 
     41An example of 'orca.properties' for a container can be found [source:orca/trunk/server/orca/config/orca.properties here]. Modify this file to tailor to your installation:  
    3442 * Change 'protocols.soapaxis2.url' to point to this host and proper port (usually 11080)  
    3543 * Generate and change 'container.guid'. You can use 'uuidgen' program that ships with many Linux distros and Mac OS X. You can also use ORCA tools that come with a source distribution: 
     
    4553This file contains the definitions of ORCA actors placed in this container. The contents is heavily dependent on your deployment type. Please refer to top-level documentation for more information. 
    4654 
    47 === $ORCA_HOME/runtime === 
     55=== $ORCA_HOME/config/runtime === 
     56 
     57Note that in ORCA 3.x series, the runtime directory was under $ORCA_HOME, now it is under $ORCA_HOME/config.  
    4858 
    4959Generate admin security configuration: