Bella 2.1

Release Notes

  1. New features
  • Many bug fixes
  • Revised documentation (esp. for emulation mode testing)
  • Tentative OpenFlow? support
  • Restructured network drivers
  • NDL passing between actors
  • NDL passing to the registry; registry module runs as web-app in Tomcat
  1. Download Bella 2.1:
    $ export ORCA_ROOT=<top of the future source tree>
    $ cd $ORCA_ROOT
    $ svn co https://geni-orca.renci.org/svn/orca/build-all/tags/2.1 build-all
    
  1. Follow the regular build instructions for building and deploying

Issues to be addressed

  • De-package NLR handler? (maybe - to avoid classloader issues)
  • Cisco 6509 create and delete vlan tasks also enable vlans on ports. this should be separated away. vlan enable/disable should be a separable task.
  • NDL code logging should be standardized to logger (no more stdout)
  • NDL code should be changed to avoid insertion and query in the same loop
  • From Brian Lynn: I wonder if it would be possible in the next release of ORCA for the SOAP messages to not be fully logged at level info? Maybe log them with level debug? #124
  • Fix close() bug #123
  • There are container recovery issues: #105
    • when we restarted (not redeployed!) a site container between a join and a leave, the leave did not work after that.

Emulation Mode Testing Portal issues

  • While trying to create a slice in the user tab, there is an exception that says "error while fetching clients list". This might be because ServiceManagerManagerObject? class does not have a getClients() method, which is being called from the related velocity template (however similar methods are available in AgentManagerObject? and AuthorityManagerObject? class). (via Prateek)
  • While creating multiple reservations on the user tab, if there are already existing reservations using >= 4 units (in total) in "Active" state, the next reservation created stays in "Redeeming Ticket" state and never goes to "Active" state, even if there are 100 units available. When one of the existing "Active" reservations are closed, the state changes to "Active" from "Redeeming Ticket".
  • When trying to "Close" a reservation on "Redeeming ticket" state, the state changes to "Closing" and never gets to "Closed".
  • When trying to "Remove" an "Active" reservation, it throws a -11000 internal error. The exception trace has the right error message - "Only reservations in closed, failed... states can be removed". This should be propagated to the portal.
  • When any reservation creation fails, the reservation remains in "Obtaining Ticket" state. Patch sent by Prateek ?
  • When there is a failure in creating a reservation, the "Type" field on the portal remains "In progress.."
  • On the broker tab, if you claim with non-existent Reservation Id, it throws -11000 internal error. Should say "wrong reservation id". This also makes an entry in the Inventory with "Obtaining ticket" status that never goes to "Failed" state. This entry can't be removed either.
  • On the broker tab, if you claim resources on a non-existent slice, it throws an exception. Need better error message.
  • On the broker tab, if you claim again for the same ResId? for a different slice, it throws a -11000 internal error. Need better error message.
  • Can't remove a slice that was created on the broker tab. Says "Sorry : is not supported".
  • Site -> view exported resources -> manage . Sometimes the Units entry says "An error occured while fetching unit info.."
  • (not critical) Creating a new service manager actor on the admin tab, broker type selection is cryptic (site->soapaxis2 etc..). The SM actor creation fails with a -11000.
  • On the site tab, several portal displays are broken - "View Inventory" shows ${machine_names} et al., "View Resource Pools" throws "Invalid Pool name" rror when clicking on manage, Policy -> manage doesn't work, "View Reservations" gives all "Type"s as "In progress.." etc.
  • The emulation mode will not work if you don't have demo.inventory.sql inserted into the mysql store. Need to add this in the documentation.
  • Portal resource claim page (after the claim is made by broker) sometimes shows 0 resource units claimed, even though the claim works correctly - later checks indicate the correct number of units transferred

Additional Features

  • Publishing/querying NDL to registry