Changes between Initial Version and Version 1 of ORCA-BEN-GEC11-SR


Ignore:
Timestamp:
08/13/11 11:14:02 (10 years ago)
Author:
Ilia Baldine
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • ORCA-BEN-GEC11-SR

    v1 v1  
     1= ORCABEN/ORCAAUG GEC11 Status Report =
     2
     3== ORCA code development ==
     4We have continued to develop ORCA code base as well as additional components.
     5 * Software releases
     6  * Generated a [https://geni-orca.renci.org/trac/wiki/releases/Camano-3.0 Camano 3.0 release] in May 2011 to be used by Cluster D ('''ORCABEN: S3.d.1''' and '''ORCAAUG: S3.d.2''' completed).
     7 * New Features
     8  * Updated and streamlined documentation ('''ORCABEN: S3.b.6''' completed)
     9  * Camano 3.0 tightly integrates the new [http://geni.renci.org:11080/registry/actors.jsp actor registry] with ORCA operation. Specifically, the <topology> section of actor configuration files are no longer needed under most circumstances. If the container.properties file specifies using the remote registry, then all certificate information and locations of other actors are gleaned from the registry information and edges in actor topology are created automatically. See [https://geni-orca.renci.org/trac/wiki/releases/Camano-3.0 release page] for more details.
     10  * Camano 3.0 includes a binary distribution with instructions on setting up a 'canonical' ORCA site (there is e.g. a new ORCA site at University of Alaska, Fairbanks and at GPO based on this installation) ('''ORCABEN: S3.b.6''' completed).
     11  * A number of bug fixes and small feature enhancements that simplify operations.
     12
     13== ProtoGENI interoperability ==
     14 * Continued to extend the [http://geni-test.renci.org:11080/ndl-conversion/convert.jsp RSpec->NDL-OWL converter] (supporting requests ('''ORCABEN: S3.d.2''')
     15 * The XMLRPC controller included in the distribution exposes GENI AM API and ProtoGENI AM API. To enable it create a container with a service manager, make sure the actor is registered with the ORCA Actor Registry, then in the ORCA GUI under user tab start the XMLRPC controller. Once the controller is started the internal XMLRPC server will be initialize to expose the proper APIs that can be used by standard tools, like GPO's omni (part of GCF package).
     16 * XMLRPC ProtoGENI adapter tested to work with GUSH ('''ORCABEN: S3.f.1''') with a few caveats (full manifest conversion is desirable, as well extensions in GUSH to support node operation on non-standard SSH ports).
     17 * Preparations are being completed to connect ION service to RENCI-owned/ORCA-controlled switch at StarLight facility/iGENI which will permit L2 connectivity from Cluster-D to ProtoGENI.
     18 
     19== Cluster D ==
     20 * LEARN implementation of Q-in-Q tunnels is being revised by LEARN to conform to ORCA requirements ('''ORCABEN: S3.d.4''')
     21 * ORCA controller stitching engine revised to support Q-in-Q in LEARN environment. ('''ORCABEN: S3.d.4.''')
     22 
     23== Other Activities ==
     24 * Jeff Chase made presentations regarding various architectural aspects at GEC11
     25
     26== Project Participants ==
     27
     28  * Ilia Baldine PI, RENCI
     29  * Jeff Chase PI, Duke University
     30  * Yufeng Xin (NDL-OWL development, experiment embedding), RENCI
     31  * Anirban Mandal (actor registry, XMLRPC controller, policy development), RENCI
     32  * Chris Heermann (BEN Operations, Cluster D connectivity), RENCI
     33  * Victor Orlikowski (Software testing, system administration, documentation), Duke University
     34  * Aydan Yumerefendi (codebase maintenance, documentation, core enhancements) – core development team, RENCI
     35  * Prateek Jaipuria (ImageProxy, Shibboleth integration) development), Duke University
     36  * Muzhi Zhao (ImageProxy development), Duke University