Changes between Version 51 and Version 52 of orca-introduction

Show
Ignore:
Timestamp:
05/10/11 17:07:48 (8 years ago)
Author:
vjo (IP: 152.3.145.66)
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • orca-introduction

    v51 v52  
    6161ORCA is implemented as a webapp intended to run inside a Tomcat Java servlet engine. A webapp is packaged as a [http://en.wikipedia.org/wiki/WAR_file_format_(Sun) webapp WAR file]. Internally the webapp implements a ''container'' in which one or more ORCA actors run. Actors can communicate with other actors across multiple containers. Actors digitally sign their communications using self-signed certificates (using certificates issued by a commercial CA is also possible). SSL is not used. We believe that state-changing commands or actions must be signed so that actions are non-repudiable and actors can be made accountable for their actions. SSL alone is not sufficient for this purpose. Given that we are concerned with message integrity and authenticity, and not privacy, SSL is not necessary either.  
    6262 
    63 ORCA currently uses a slightly modified version of Tomcat 5.5 [source:/software/tomcat.tar.gz avaiable here]. Off-the-shelf Tomcat or other servlet engine (like Jetty) will not work.  
     63ORCA currently uses a slightly modified version of Tomcat 5.5 [source:/software/tomcat.tar.gz available here]. Off-the-shelf Tomcat or other servlet engine (like Jetty) will not work.  
    6464 
    6565Most of the ORCA code is written in Java, although substrate handlers [parts of code responsible for creating and destroying slivers of different kinds) are implemented as a combination of Ant scripts, Java tasks and bash scripts. ORCA user tools that speak to its GENI and ProtoGENI AM API-compliant controller are written in Python.