Version 36 (modified by ibaldin, 8 years ago)

--

Camano 3.1

Release Notes

Overview

Camano 3.1 is primarily a bug-fix release with a few new features. It marks the beginning of ORCA operations in beta. Capabilities previously demonstrated are now available to external users on the limited set of resources available to ORCA.

  • Starting with this release we recommend using Tomcat 7 instead of Tomcat 5.5 with ORCA. This fixes a number of transient classpath problems experienced in the past.
  • The compute ontology has been updated and extended
  • Network embedding code has been extended and tested with a regression test suite (see below)
  • GENI Authorization is turned on by default
  • RSpec v2 request conversion has been extended and documented.
  • ORCA now generates proper RSpec v2 manifests for use by omni and Gush.
  • ORCA now has a GUI experimenter tool called Flukes for graphically generating slice requests, submitting the to ORCA and using the resulting slices. Flukes uses ORCA's native interface and its powerful stitching engine to create inter-domain slices.

The following ORCA sites are available at the time of this writing:

  • RENCI ACIS Eucalyptus cluster (Availability: production-ready)
  • RENCI BEN Eucalyptus cluster (Availability: intermittent)
  • UNC BEN Eucalyptus cluster (Availability: production-ready)
  • Duke CS Eucalyptus cluster (Availability: production-ready)
  • University of Houston Eucalyptus cluster (Availability: production-ready)

Slices can be created within or between resources within each cluster. BEN and NLR and LEARN serve as the interconnect Layer 2 fabric.

Upgrade

  • Use stock Tomcat 7 instead of Tomcat 5.5
  • There are minor changes to configuration files for SM actor and XMLRPC controller within it due to GENI authorization being turned on by default.
  • ORCA native API has changed and the python scripts previously used to exercise it have been updated (including the use of certificates for authorization)
  • Due to the ontology changes, your site rdf file may require an update

Regression testing

Network embedding and inter-domain stitching code in ORCA has become very complex, so starting with 3.1 release we are instituting a regression test suite for this code. Based on this code experimenters can determine whether ORCA is capable of fulfilling their slice request and use regression tests as starting points for their own slice requests. Regression tests use Flukes? to generate requests, submit and operate on the slices.

Regression tests are described in this README file.

TS1: ====== ===== ====== TestCase Status Notes ====== ===== ====== False False False True False True False True True True True True ===== ===== ======

Bug List

  • Bugs
    • SM Race #210
    • Close/Renew problem #211
    • 'Bunch of VMs request' #212
    • orca.network refactoring #213, #216
    • Authorization issue #214
    • Transient classpath problem #215
    • updateTicket throws null pointer exceptions after initial reservation request fails because broker cannot fulfill it (per Prateek)
    • The container with the interdomain controller stopped ticking abruptly. Two requests were issued and closed successfully two days before this happened. When a new request was issued, after the interdomain path was computed, everything halted. orca.log wasn't growing. 'View Reservations' on the portal was showing only one reservation in 'Nascent' state.
  • Resurrect unit tests.

Ticket Reports