Version 36 (modified by ibaldin, 9 years ago)

--

Bella 2.2

Issues to be addressed

  • If a parent reservation fails, should children be allowed to go on.
  • NDL code
    • 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
    • Ensure proper wavelength continuity for DTN circuits
  • For NEuca support
    • come up with a single authority actor that
      • Manages VMs
      • Manages internal (for topology mapping) and external VLANs as three separate resources
      • Enable passing phys vs. vlan attachment type from authority (?) and ip addresses from the controller
  • Need to make start.sh/stop.sh handler scripts more robust to failures. Verify that they always return resources (like public IPs) back.
  • Network drivers
    • Cisco VLAN mapping function does not work if a mapping already exists (not properly cleaned up)
    • 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)
    • 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.
  • Miscellaneous
    • Interactor deadlock problem
    • Re-enable certificate validation
    • 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 we have controller (ID controller) query NDL's on demand instead of only in the beginning
  • Can we do 'selective' db wipeout between redeployments?
  • OF controller needs to package the scripts it uses
  • Somehow we need to deal with closing source reservations
  • Registry:
    • Turn registry php code into jsp to avoid the need for apache and allow packaging entire registry into webapp
    • Replace printlns in registry code with log4j (look at ndl-conversion code for inspiration)
    • Modify to use heart-beat based registration (to time out old actors)

  • Utilities
    • Sanity checking script for container actor configuration files (check guids, check locations, check edges)
  • 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.
  • 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)?

Additional Features

Attachments