Version 44 (modified by ibaldin, 8 years ago)


Bella 2.2

Features to include

  • Local NEuca topology embedding with IP address assignment from NDL
  • Updated registry with #180
    • Verification of registration (client IP vs. registering URL)
    • Timing out of stale entries (assuming clients periodically re-register).
    • Validation of registrations (e.g. show localhost registrations in web gui, but not over XMLRPC, color-code suspicious registrations)
  • GENI AM API without security (essentially as is)
  • Hardened NEuca support
    • start/stop scripts. Verify that they always return resources (like public IPs) back. #179
  • Working emulation setup with 1 actor of each type emulating a NEuca site
  • NDL code
    • Ensure proper wavelength continuity for DTN circuits #178
  • Network drivers
    • Make sure 'ports' parameter in handler gets cleaned up across handlers (6509, 3200, 3400) (it used to be two parameters/sets of ports now converging into one)
  • OF controller (as is)
    • OF controller needs to package the scripts it uses(?)

Need further investigation

  • Re-deploying site requires redeploying broker - VERY BAD!
    • When you redeploy - don't wipe the state recovery file: this will preserve existing reservations. HOWEVER: there is a bug now that prevents expanding the packages if the state recovery lock file is present. Aydan will fix #145. Every actor is designed to work like that. If a broker is blown away, service managers will continue working until they need extend. Basically we need to fix recovery bugs if there are any but by design, redeploying should be fine. Recovery is most problematic on SM and Authorities. Eucalyptus is made to recover but not well tested.
  • If a parent reservation fails, should children be allowed to go on?
    • There is a concept of 'deferral'. If you don't have enough resources, you can send back partial resources, which is why this makes sense. We may need to add a property on the control for the resource pool, a new property 'non-deferrable' may need to be added. There is a binary predicate that determines whether a redeem is possible (yes redeem/no redeem/no redeem and release). The children reservation get tickets and they need to be cleaned up if a parent fails on redeem. This needs to be a transaction. Predecessor reservations need to be closed, however we may need to wait until they are done redeeming, as closing in redeeming state is difficult.
  • Can/Should we get rid of RENCI-net UNC-net authorities? So we can have a single authority controlling EX3200?
  • How can we pass port configuration from the switches into the log from failure of operations?
    • if you specify a task property as '' (Config class) will be passed back (with stripped '') and the property will be attached to the unit for which the handler was executed ( -> blah) however failed units aren't sent back to e.g. SM. Logging it in the handler is possible. Logging is probably easiest. Also possible to attach it to the reservation and pass it as a property. There is also a notice mechanism that can be used to pass it back to the reservation.
  • Do we still an interactor deadlock problem?
    • Yes. Needs fixing. Every inter-actor call holds big lock. Across multiple containers it is possible for call and response to be in different threads, which may cause deadlock. The solution is when calls are made across actors, they are not done while holding the big lock. The issue is handling exceptions.
  • Do we need to re-enable certificate validation?
    • Probably yes. The issue may be between different versions of Java. It has to do with serialization of certificates into byte arrays. The solution is likely to use the hash of the certificate instead of a byte array.
  • Do we need to do anything regarding support for close()? How do we deal with closing source reservations?
    • Probably yes, pending more testing from Brian. Early close is related to the problem above with parent reservations.


  • Can we do 'selective' db wipeout between redeployments?
  • Bugs
    • Why are edge specifications in topology sensitive to direction (from service to broker, from broker to site)?
    • updateTicket throws null pointer exceptions after initial reservation request fails because broker cannot fulfill it (per Prateek)
    • Broker view shows site actors, however when clicked shows broker credentials
    • In at least one instance a site container was restarted between and a join and a leave and a leave did not work after that (Euca at RENCI).
    • 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.
  • Miscellaneous/core
    • Clean up SM policy and controller APIs to avoid problems like with close()
    • Add 'exportAll' to the config file
    • Add instantiating a controller from config file vs. GUI
    • Can CXF replace Axis2 or can we upgrade Axis2?
  • Network drivers
    • Improve 6509 driver performance by caching login sessions
    • Consider separating adding a QoS profile to vlan from vlan creation. This may be needed to deal with vlan delays and in general give more flexibility.
  • NDL policies
    • Should improve the performance of the label assignment policy and label range update utility in the model
    • Review the code for static members and general structure
    • Multipoint BEN and Sherpa
    • Investigate persistent triple store from BBN
    • Can we have controller (ID controller) query NDL's on demand instead of only in the beginning
  • Utilities
    • Sanity checking script for container actor configuration files (check guids, check locations, check edges)
  • Can we use cytoscape to visualize our RDFs in a useful way (example: in the registry add an option to show a visualization of the delegated resources)?