Version 3 (modified by, 13 years ago) (diff)



ORCA code development

We have continued to develop ORCA code base as well as additional components.

  • Software releases
    • Generated a Camano 3.0 release in May 2011 to be used by Cluster D (ORCABEN: S3.d.1 and ORCAAUG: S3.d.2 completed).
  • New Features
    • Updated and streamlined documentation (ORCABEN: S3.b.6 completed)
    • Camano 3.0 tightly integrates the new actor registry with ORCA operation. Specifically, the <topology> section of actor configuration files are no longer needed under most circumstances. If the 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 release page for more details.
    • 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).
    • Improved support for standard substrate cloud back-ends (Eucalyptus/EC2 APIs).
    • Operational-ready authorization.
    • A number of bug fixes and small feature enhancements that simplify operations.
    • Integrated enhancements from project: ImageProxy for image distribution, and NEuca for circuit interconnection.

ProtoGENI interoperability

  • Continued to extend the RSpec->NDL-OWL converter (supporting requests (ORCABEN: S3.d.2)
  • 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).
  • 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).
  • 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.

Cluster D

  • LEARN implementation of Q-in-Q tunnels is being revised by LEARN to conform to ORCA requirements (ORCABEN: S3.d.4)
  • ORCA controller stitching engine revised to support Q-in-Q in LEARN environment. (ORCABEN: S3.d.4.)

Other Activities

Project Participants

  • Ilia Baldine PI, RENCI
  • Jeff Chase PI, Duke University
  • Yufeng Xin (NDL-OWL development, experiment embedding), RENCI
  • Anirban Mandal (actor registry, XMLRPC controller, policy development), RENCI
  • Chris Heermann (BEN Operations, Cluster D connectivity), RENCI
  • Victor Orlikowski (Development, quality assurance, testbed development and administration), Duke University
  • Aydan Yumerefendi (codebase maintenance, documentation, core enhancements) – core development team, RENCI
  • Prateek Jaipuria (ImageProxy, Shibboleth integration, identity management and authorization), Duke University
  • Muzhi Zhao (ImageProxy development), Duke University